Montana Disaster & Emergency Services — SECC Familiarization Series
Module 6: A Day in the SECC
Putting it all together — one operational period, start to finish.
This is the last module in the series — and it's where everything from Modules 1 through 5 comes together. Instead of another concept, this one walks through a single operational period at Partial or Full Activation, hour by hour.
About 6–8 minutes. As you go, notice how many earlier concepts show up in a normal day: activation staffing, the Information Management Section, PIRs, and the ISP all make an appearance.
Once the SECC activates, its work is organized into operational periods — set blocks of time, typically 24 hours, each with its own objectives, staffing, and products. Every operational period follows a defined rhythm of briefings and meetings, sometimes called the "battle rhythm."
That rhythm can flex based on incident conditions and activation level, but the underlying pattern is consistent: brief, set objectives, plan, execute, report, hand off. That pattern repeats every day the SECC is activated.
New operational period begins. Overnight staff briefs the day shift; Section Chiefs review the current ISP with their teams.
Information briefing and hazards summary distributed. Command and General Staff, and subordinate sections, brief in turn.
This is the SECC's version of "starting the day" — everyone gets the same current picture before any decisions get made.
Section Chiefs review current objectives, revise as needed, and finalize objectives for the upcoming operational period.
Approved objectives go out. The Situational Awareness Unit begins the Incident Collection Plan; the Planning Support Unit starts updating the ISP.
ISP updates are reviewed together — often in person early in an activation, shifting to virtual once the rhythm is established.
This is where Module 5's information chain does its work — PIRs and EEIs collected that morning feed directly into these midday planning products.
Typically issued once daily, more often if the operational tempo requires it.
Key SECC staff finalize the State ISP for the upcoming operational period.
The finalized ISP is posted to CORE, giving every section and partner the same approved plan for the next period.
A situation briefing with partners — ESFs, local and tribal jurisdictions, and other partners — to sync information and efforts across everyone supporting the incident.
Day staff wraps the operational period and hands off — to an overnight shift if one is staffed for this incident, or directly into the next day's 0700 briefing if it isn't. Section Chiefs review the status of the current ISP either way.
Many SECC activations run a single extended day shift — often 0700–1900 or similar — with no standing night shift. On larger or longer incidents, the SECC Manager may stand up overnight coverage, typically Information Management and Resource Support staying active to monitor conditions and track open Requests for Assistance.
A 24-hour cycle isn't automatic — it's a staffing decision the SECC Manager makes based on what the incident actually requires.
On longer activations, the Sync Briefing's exact time often shifts to work around the field Incident Management Team's own briefing schedule and the SECC's daily rhythm — but it's typically still held in the late afternoon, and on Partial or Full Activations it can run daily for the life of the incident.
Then it starts again — the next operational period's 0700 shift change begins the cycle over.
One operational period touches nearly everything this course covered:
Every meeting is about supporting the field, not directing it — Module 1 and 2.
Information Management and Resource Support drive the day's rhythm — Module 3.
This rhythm exists at Partial and Full Activation — Module 4.
And underneath all of it: the PIRs, EEIs, and lifeline-based information chain from Module 5, feeding the COP that every briefing in this timeline depends on.
No score, no pressure — just a quick way to reinforce the key ideas.
1. What happens at the SECC Objectives Meeting?
2. Where is the finalized Incident Support Plan (ISP) posted each operational period?
3. Is overnight staffing a standard part of every SECC activation?
4. Why does the SECC repeat the same daily rhythm during an activation?
Content in this module is drawn from the Montana DES SECC Operations Manual (2026), the ISM 230 Daily Meeting Schedule, and the Incident Support Plan Process document. This is a familiarization course; it is not a substitute for position-specific training or the manual itself.
You now have a working understanding of why the SECC uses ISM, how it compares to ICS, how it's organized, how activation works, how information becomes the Common Operating Picture, and how a typical operational period runs.