The command center is not the steering committee, and it is worth being precise about the difference on the named operator side of an EHR cutover. The named steering committee that met weekly through pre-cutover is a sponsor-level body — the CIO, the CMIO, the VP of Customer Success, the program sponsor on the vendor side. It owns the readiness boundary in calendar terms. It signed cell five on Friday. It does not run activation. The command center is a different room with a different cadence and a different authority. It is the twenty-four hour floor of named operators during cutover week, the room where the downtime procedure is rehearsed against a live radio, and the room where the floor and the system collide when the floor runs faster than the workflow. We sit in it for seven days. We sign out of it when the stabilization boundary passes, and the named client-side owner takes the read. The two rooms are not interchangeable, and an engagement that treats them as one has confused the readiness list with the org chart before activation day has even arrived.
Decision authority has to be named before the floor cuts over, and the cell on the readiness list that holds it is not a titles cell. The triad on shift during cutover week is a named FDE operator, a named client-side owner, and a named clinical informatics lead — three names, written against the same Friday, on the same sheet the floor reads from when the radio crackles. The named clinical owner on the downtime procedure page in the engagement playbook is the same person whose name is on the command-center radio, the same person the named units page when their downtime fallback fires, and the same person whose name the named FDE operator goes looking for on second shift. That name is set in pre-cutover. It is signed in cell five on the Friday that closes readiness. If the readiness list closes with a roster slot — "clinical owner" — instead of a name, the cutover opens with a slot, and a slot is what gets reached for when the floor needs a person. The ready list writes names. The activation runs names. Same names, same cell, same Friday.
The go/no-go decision point is a Friday cell-five read, not an activation-day vote. The "go" word was signed at the readiness boundary on the Friday before cutover, against the readiness list, against the named owners, against the named workflows the floor was tested against. The cell was signed. The "go" word was spoken. Activation day is execution against the signed cell five — not a re-litigation of the readiness list at six a.m. while the floor is in motion. An engagement that re-votes the go/no-go on activation day has lost the readiness boundary, and what looks like caution is in practice a stabilization failure-in-waiting. We do not re-vote on activation day. We run against the signed cell five, we hold the radio open for the named triad, and we treat any activation-day pressure to call the "no" word as a readiness-list failure that belongs on the readiness list from week zero, not on the cutover floor at midnight. Same Friday, same cell, same signed names.
What the command center actually decides during activation week is narrower than the org chart suggests, and the named triad holds the line against anything that broadens it. Triage decisions between the floor and the vendor — is the order entry a workflow drift or a configuration error, who answers in the next five minutes — land on the named FDE operator, with the named clinical informatics lead reading the cell. Minor non-clinical changes — a label, a print template, a unit of measure in a picklist — are held until week two. The readiness list has a cell for them, and the cell is signed in the second week, not in cutover week, because the floor is faster than the change request queue. Downtime procedure activation when the fallback path actually fires is escalated through the named clinical informatics lead, with the named client-side owner signing the activation slip against the playbook page. The stabilization handoff slip-date — the date the named FDE operator transfers the read to the named client-side owner — is signed by the named triad on a Friday, not on an emergency basis midweek. Each decision has a cell. Each cell has a name.
The activation day log is written by the same three names on the same Friday as the cell-five review. The cadence is what closes the gap between activation and stabilization cleanly. The named FDE operator writes the same Friday cell review one day early against the activation-day floor — the readiness list, the signed cell five, the named owners, the named workflows, and the named radio events of the previous twenty-four hours. The named client-side owner carries the read: the floor side of the cell, the units the floor actually ran, the downtime procedure pages the named triad rehearsed. The named clinical informatics lead signs the same cell. Handoff into day-seven stabilization is a continuous write, not a separate event — the same log closes one cell and opens the next. The activation day log is the cell-by-cell ledger turned by one quarter turn. The same composition question that drives the prior post on clinical informatics team composition holds for the command center just as it holds for cutover week, and the same frequently asked questions on the FAQ page walk through what the named triad signed against and what the floor held to it.