Who this update is for
A service-specific reference for affected employees, service owners, and support agents.
This fictional example shows how Alder Works communicates an interruption to Northstar, its travel-booking service. Use this page for confirmed Northstar impact and updates; it is not the organization-wide crisis communication destination.
Service owner: confirm which tasks are affected, approve the employee-facing wording, and confirm recovery scope. Support agent: share the approved wording and capture reports that remain unresolved. Specialist responder: investigate technical issues and return confirmed findings to the service owner.
Here, “affected” means the task may fail for some employees; “unaffected” means the task remains available according to the latest confirmed update.
Reference snapshot
Illustrative authored snapshot—not a live work queue or system of record. Times are UTC.
| Reference | Illustrative detail |
|---|---|
| Service | Northstar travel booking |
| Affected task | Some new bookings may not complete |
| Known impact | Some employees may be unable to finish a new booking |
| Unaffected task | Saved itineraries remain viewable |
| Last confirmed update | 18 June 2026, 14:00 UTC |
| Next update due | 18 June 2026, 14:30 UTC |
| Update owner | Northstar service owner |
Approved wording examples
Use wording that matches the currently confirmed impact. Do not promise a restoration time or state an unverified cause.
When the reported task is affected
“Some employees are currently unable to complete a new Northstar travel booking. Saved itineraries remain viewable. We will post the next update by 14:30 UTC, including if there is no change.”
- Name the affected task and the known unaffected task.
- Keep the next-update time aligned with the current snapshot.
When the reported task is not in the confirmed impact
“The current update says saved itineraries remain viewable; the interruption described here concerns some new bookings. If you are seeing a different problem, tell support which task you tried and what happened so it can be checked.”
- Do not dismiss a report solely because it differs from the known impact.
- Record the task and observed result for the service owner or specialist responder.
Support-agent handoff
“I can share the confirmed service update, but I cannot confirm a cause or an individual recovery time. I’ll record the issue you described and route it to the service owner for review.”
- Relay only confirmed wording.
- Pass unresolved reports to the service owner or designated specialist responder.
Update rhythm
Keep the employee update and reference snapshot aligned.
-
1
Confirm impact
The service owner confirms affected and unaffected tasks with the specialist responder before the wording is shared.
-
2
Publish the approved summary
State the service, observed impact, unaffected task if known, confirmation time, and next update time.
-
3
Update at the stated time
In this example, publish the next update at 14:30 UTC even if there is no new progress. State plainly when the confirmed status has not changed.
-
4
Revise sooner when confirmed impact changes
When confirmed information changes the affected scope or recovery handoff, the service owner updates the wording and timestamp rather than waiting for the scheduled update.
-
5
Close with recovery scope and handoff
The service owner states which tasks are confirmed available and when that was checked. Support agents route reports that remain unresolved to the service owner or designated specialist responder.