Scheduled maintenance notice
Northstar Works sample: staff sign-in and shared files Medium priority
Planned window: 12 November 2026, 22:00–23:30 UTC. During this window, staff sign-in and shared-files services may be unavailable while maintenance is carried out. Save shared-file changes beforehand and move work that requires staff sign-in outside the window. A completion notice will be posted here after the maintenance team confirms the work is complete.
What is changing
Fictional example: Northstar Works
Northstar Works is the fictional organization used for this worked example. Its IT and Security team has scheduled maintenance affecting staff sign-in and shared files. The window is planned for 12 November 2026, 22:00–23:30 UTC.
During the window, employees may be unable to sign in to services that depend on staff authentication or open shared files. The times and impacts below are illustrative sample details, not a live availability report. Use the published completion notice on this page before resuming work that depends on the affected services.
Maintenance window by region
Sample local times for the dated maintenance window above.
| Region | Local date | Local window |
|---|---|---|
| UTC reference | 12 November 2026 | 22:00–23:30 |
| London | 12 November 2026 | 22:00–23:30 |
| New York | 12 November 2026 | 17:00–18:30 |
| Singapore | 13 November 2026 | 06:00–07:30 |
Plan around the affected services
Use the guidance for the service your work depends on.
What may be affected
Signing in to services that depend on staff authentication may be unavailable during the scheduled window.
Workaround
Complete sign-in-dependent reviews or handoffs before the window, or schedule them for after the completion notice is posted. Do not assume an existing session will remain available.
What may be affected
Opening shared files or saving changes to them may be unavailable during the scheduled window.
Workaround
Save and close shared-file edits before the window. If your task can proceed without the file, use an already-authorized working copy only where your team's approved process permits it; otherwise move the task outside the window.
Who does what
Responsibilities for planning and communicating the maintenance window.
Affected employees
Plan work that depends on sign-in or shared files around the published window.
- Save and close shared-file edits before the window.
- Move sign-in-dependent work outside the window.
- Check this page for the authored completion notice before resuming affected work.
Service owners
Coordinate the employee-facing impact details for the services they own.
- Confirm the affected services and audience against approved operational information.
- Provide the IT and Security content owner with the approved impact and workaround wording.
- Notify the content owner when the maintenance outcome is ready to communicate.
IT specialists
Carry out the technical work and provide the confirmed outcome through the established internal handoff.
- Use the approved technical change process for the maintenance work.
- Escalate an unexpected impact through the organization's established IT and Security route.
- Provide the confirmed completion or revised-window information to the content owner for publication.
A practical coordination example
A London colleague has a review that requires staff sign-in at 22:15 UTC on 12 November. They move that review to before the published window, save and close their shared-file edits, and wait for the completion notice on this page before resuming work that depends on either service.
This is planning guidance, not a guarantee that a service will be available at a particular time. If the notice changes or an unexpected impact occurs, follow the organization's established IT and Security help route rather than relying on the sample schedule.
Completion update
After the maintenance team confirms the outcome, the IT and Security content owner posts an update here stating whether the work is complete or whether the planned window has changed. Until that authored update appears, this notice does not provide a live service-status check. For a correction or help, use your organization's established IT and Security help route.