Extended incidents
Ransomware recovery, a breach with notices to send, and a plant restart under engineering validation can each run for weeks. The organization built for the first night wears out by the second week.
This page covers the change from hours to weeks: working limits, rotating command, a slower cycle, a smaller organization, and a record that survives every handover. Shift-to-shift mechanics are on Command and handover and The planning cycle.
Working limits
Set these in policy as part of preparing, and give the Safety Officer authority to enforce them. The values are starting points.
| Limit | Starting point |
|---|---|
| Operational period | 12 hours while containment is active. 24 hours once recovery is routine |
| Time on duty in one shift | 13 hours at most, including briefing and handover |
| Longest shift | 16 hours, approved by the Incident Commander and logged with the reason |
| Rest between shifts | At least 11 hours off duty. Travel counts as duty |
| Days off | From the second week, at least 36 hours clear of duty in every 7 days |
| Time on the incident | 14 days, then 3 days off before any further incident duty |
The A, B, C rotation in the staffing math meets the rest rule. From the second week, give each person their 36 hours by adding a relief for one shift, or by moving to 24-hour periods with a smaller night crew.
These limits sit inside the wildland fire standards in NWCG PMS 902, May 2025 edition. NWCG lists it as current in October 2026; the limits below were checked September 2026. PMS 902 sets a minimum 2:1 work-to-rest ratio, counting travel as work. It treats shifts over 16 hours as the exception, justified by the Incident Commander or Agency Administrator in the daily records, and allows none over 24 hours. Its standard assignment is 14 days, followed by 3 mandatory days off, with an extension of up to 14 more days and 2 days off before the 22nd day.
Fatigue
Supervisors watch for these signs in every shift and report them to the Safety Officer:
- Errors in routine work: the wrong host, a typo in a command, a ticket closed early
- Repeated questions on the bridge, and slower answers
- Items missed at handover
- Short tempers and arguments over small points
- Nodding off, or long stretches without a break or a meal
- Someone refusing relief because nobody else knows their part
| # | Item | Owner |
|---|---|---|
| 1 | Hours on duty and last-slept times checked on the ICS 211 each period | Safety Officer |
| 2 | Anyone past the duty limit relieved, after a handover | Safety Officer |
| 3 | Any destructive or irreversible change by someone past 10 hours on duty checked by a second person | Operations |
| 4 | Anyone nobody else can relieve paired with a relief this period, and their knowledge written down | Planning |
| 5 | A ride home arranged for anyone too tired to drive | Logistics |
| 6 | Names at or near the limits, and the actions taken, put in the safety message and the handover | Safety Officer |
Rotating the Incident Commander
Command changes at each shift by transfer. Over weeks, the command team rotates as well. Bring in a fresh team, meaning an Incident Commander, a deputy and section chiefs, when any of these is true:
- The current team reaches 14 days on the incident.
- The incident will run at least two more weeks.
- The main effort changes, such as from containment to notification and litigation.
- Update times or objectives slip for two periods in a row.
- The Safety Officer reports that the team cannot be relieved inside the limits.
The incoming team shadows for one full operational period and takes command at the start of the next. It is briefed from the current IAP, the ICS 209, the decision register and the open action tracker.
Change the Planning Section Chief one period after the Incident Commander, so someone in command saw both teams. The outgoing Incident Commander stays reachable for a week. The Documentation unit leader stays through the change.
Battle rhythm
Slow the cycle as the work settles. The Incident Commander sets the period length in the IAP, and each change is an entry in the decision register.
| Stage | Period | Planning cycle | ICS 209 | Move on when |
|---|---|---|---|---|
| Active containment | 12 hours | A full cycle each period, each shift planning the other's | Each period, and before each executive update | No new scope for two periods, and containment is intact |
| Recovery | 24 hours | One cycle a day, with an operations briefing at each shift change | Daily | Critical services restored and eradication verified |
| Long tail | 1 week | Objectives and planning meetings weekly, tactics as needed | Weekly, and at any change in scope or impact | The demobilization plan closes the incident |
The long-tail organization
Weeks two to six are rebuilds on a schedule, monitoring, notices, claims, regulator questions and legal holds. Run them with a smaller organization on business hours.
| Seat | Weeks two to six |
|---|---|
| Incident Commander | One named Incident Commander on business hours, with a named backup |
| Operations | A recovery group on the rebuild schedule, and a monitoring group watching for the attacker's return |
| Planning | The timeline, the decision register, the open action tracker and the demobilization plan |
| Legal advisor | Notices, regulator questions, legal holds |
| Public Information Officer | Notices to people and customers, call center scripts, media |
| Liaison | The insurer, law enforcement, suppliers, and regulators through counsel |
| Finance/Admin | Claims, invoices, the cost summary |
Fold Logistics into Planning once temporary access and loaned hardware are closed out. Fold Intelligence/Investigations into Operations once the forensic report is final, unless law enforcement or litigation still needs it.
Close the Safety Officer seat once nobody works outside business hours and no work touches a physical process. Release people through the demobilization check-out.
One record across rotations
- One incident record, one timeline, one decision register and one open action tracker for the whole incident. Numbering continues across teams.
- Each incoming Incident Commander reads the open entries in the decision register before taking command.
- A decision stands until a new entry reverses it and names the new facts that justify the change.
- Corrections are new entries. The earlier entry stays, marked as replaced.
- Board, regulator and customer reports come from the same record, as in board and government reporting.
Stepping down executive and board updates
The update schedule sets the cadence while the incident is active. Stepping it down is an executive group decision, entered in the register, once impact has stopped growing and recovery runs to plan. Announce each change in the update before it takes effect, with the time of the next update.
| Stage | Executives | Board |
|---|---|---|
| Active containment | As the severity sets. For SEV 1, every 30 minutes until mitigated, then every 2 hours | The same day, then daily |
| Recovery | Twice a day at fixed times | Daily, or as the executive sponsor sets |
| Long tail | Weekly, and at once on any change in scope or impact, or any notice sent | At each scheduled meeting, with a written update when a notice goes out or a regulator acts |
Planning starts the demobilization plan as soon as the long tail begins.