The ticket ownership path
- 1 / IntakeIdentify the user and request
Create or locate the ticket, client context and current impact.
- 2 / AuthorityIs the action included and permitted?
Check the runbook, identity requirements and change approval.
Supplier can act
Perform the agreed work and keep the action history with the ticket.
MSP or client decision needed
Transfer diagnostics and the next decision to a named accepting owner.
Carry these through the handoff, then close against the agreed acceptance criteria.
Required fields
| Field | What belongs in it |
|---|---|
| Incident and tenant | Stable ticket ID, client and affected asset/service |
| Business impact | Users or service affected and current severity rationale |
| Evidence | Observations, relevant timestamps and linked action history |
| Action and authority | Completed changes, approvers and current runbook |
| Current state | Restored, mitigated, waiting or unresolved |
| Next decision | A specific action or approval needed |
| Receiving owner | Named accountable role and acceptance time |
| Customer update | Last message, communication owner and next deadline |
| Fallback | Escalation route if acceptance or approval fails |
Keep passwords and raw confidential documents in the approved systems. A handoff should refer to controlled evidence rather than duplicating secrets into email. The MSP must decide what the external service is allowed to view and transmit.
Filled illustrative example
Incident AH04 concerns a test client's file service. The overnight team observes failures at 06:10 UTC, opens the incident at 06:12 and applies an approved temporary mitigation at 06:25. Business access is restored, but the underlying capacity issue is unresolved. The next decision is whether the daytime engineer approves a permanent storage change.
The receiving service owner accepts at 07:00 UTC. The last customer update was at 06:30, and the agreed next update is at 07:30. If acceptance fails, the retained on-call owner is contacted and the overnight team keeps coordination until the fallback accepts. These identifiers and times are invented to show a complete handoff; they are not provider results.
This incident should not be marked permanently resolved merely because the temporary mitigation restored access. Keep the remediation task linked and assign its owner. Make any SLA pause or dependency explicit, including who authorized the pause and what restarts the clock.
Test the calendar seam
Document coverage using a named timezone and the relevant date, not only a fixed UTC offset. Ask how local clock changes and client holidays affect the next receiving shift. Confirm whether the provider observes your client's calendar, its own delivery-center calendar or a negotiated list. Continuous marketing language does not answer that question.
Give a repeated local time its offset
For a handoff on 1 November 2026 in America/New_York, 01:30 occurs twice. NIST's 2026 daylight-saving rules (external website), checked 19 October 2026, explain the autumn return from 02:00 to 01:00. Agree which occurrence owns the transfer and write its UTC offset alongside the date and named timezone.
| Occurrence on 1 November 2026 | Handoff time in America/New_York | Same instant in UTC |
|---|---|---|
| First 01:30 | 01:30, UTC-04:00 | 05:30 UTC |
| Second 01:30 | 01:30, UTC-05:00 | 06:30 UTC |
These are two different instants, one hour apart. Keep the sending owner responsible until the agreed receiver accepts. If an update deadline falls between the two, write the actual instant rather than sorting messages by the repeated wall-clock label.
Check the client's zone separately from the delivery team's zone. For the week beginning 26 October 2026, the dated coverage planner counts 169 elapsed hours for America/New_York and 168 for America/Winnipeg. The current IANA release notes (external website), checked 19 October 2026, include Manitoba's move to permanent UTC-05:00 on 31 October. Reusing another city's clock pattern can therefore create the wrong shift plan.
In the handoff worksheet, enter the receiving shift and update deadline with their date, named timezone and offset, adding the UTC equivalent where useful. Times in that draft stay as entered; use the dated planner for coverage totals and agree the actual service calendar with the provider.
Review and improve
Sample handoffs that were accepted, delayed and rejected. Look for missing next actions, incorrect severity, repeated diagnostic work and late customer updates. Correct the process rather than hiding the failures in an average response time. A published MSP support-routing account describes giving clients help desk and account-specific escalation contacts. Use the after-hours guide to define the purchase and the SLA worksheet to separate clocks. Run this handoff in the NOC pilot or desk pilot before expanding coverage.