Contents

Offshore Advantages guide

Define a client SLA across two time zones

An SLA that defines the clock, the handoff, the response window, and the exception across time zones.

Define a client SLA across two time zones — editorial guide illustration

Key takeaways

  • Define the start and stop of the clock.
  • Name the handoff owner.
  • Record the exception path.

How to approach: Define a client SLA across two time zones

An SLA across time zones should make the clock and the handoff explicit. Start with the start event, the response window, the handoff, and the exception. An SLA that ignores the time zone will be measured differently by each side.

Use the same format for every handover so the next reader can scan it. Keep the SLA to the commitments the team can actually meet. An aggressive promise that is missed is worse than a realistic one.

Name the owner in the same line as the action. A control that depends on memory is not yet a control.

Define the clock

Write the event that starts the clock and the event that stops it. Record the business hours and the time zone. Keep the original note beside the corrected version.

Test the rule on one real shift before applying it to both. Record whether weekends and holidays count. An SLA that is silent on the calendar will be disputed.

Separate what was observed from what was assumed. A control that depends on memory is not yet a control.

Name the handoff

Record the person who owns the request at each stage. A request that crosses a shift should have a named receiver. Ask whether a new reviewer could act on the record without a conversation.

Review the first few notes together before the process expands. Record the confirmation. A handoff without a confirmation is not a handoff.

A short note with four fields is easier to use than a long narrative. Record the exception and the person who approved it.

Record the exception

Write what happens when the window cannot be met. Record the escalation and the client communication. Keep the evidence with the record rather than in a separate log.

If the source is unclear, route the question instead of guessing. Record the review of missed windows. A repeated miss may point to a coverage or scope problem.

Record the date and the source so the next reviewer can repeat the check. Use the same format for every handover so the next reader can scan it.

Sources

  1. NIST Cybersecurity Framework: Connect access and change decisions with written controls and reviewable evidence.
  2. NIST Privacy Framework: Use a risk-based approach for personal data handled by an offshore team.
  3. U.S. Small Business Administration: General guidance on documenting recurring operations.
  4. U.S. Department of Labor: Public guidance on recordkeeping and employment practices.
  5. GAO Green Book: Internal control standards for operations and reporting.