Required
Ownership moves
Clear Range
The Relief
The shift changed. Nobody can say who owns the work.
The incoming period misses actions or repeats them because ownership never arrived.
DEMONSTRATION SCENARIO
This is a demonstration scenario. It is not a live demonstration and does not report an executed result.
The situation
An outgoing command holds open actions. A relief to the incoming period is required before release.
The next period cannot say who owns the open work.
Why this is hard
The next period can be blind because the relief never happened, because a radio failed, or because a map is stale. A message that was sent and not accepted is a different break.
Repairing a radio or refreshing a map should not count unless that is what the missing ownership turns out to be.
What the operator can see
Gap
Actual
Ownership unclear
At risk. The next period
What V8Y must determine
V8Y must determine whether the relief occurred, whether a radio or a map is the real break, and what the incoming command can restate before release.
What may happen next
The incoming period misses or duplicates actions.
What counts as recovery
Not recovery
Success is not a sent note.
Recovery
Success is that incoming command can restate ownership and the open actions.
Observed results
No executed results are published for this thread.
What this evaluation would test
- A missing relief distinguished from a dead radio, a stale map, and a send that was not accepted.
- Not the same as a request that was sent and ignored.
- Both commands own the transfer.
- Recovery is restated ownership, not radio health.
These are the conditions the evaluation would test. They are not reported results.
Operational basis
View operational basis and sources
Derived from Maui’s 2023 after-action record and wildland transfer-of-command practice: continuity fails when shift changes do not pass open actions and ownership. The checklist and timers here are synthetic.
Maui Emergency Management Agency. 2023 wildfire after-action report. 2023.
Related threads
The Open Loop is the other transfer problem.
Discuss evaluating this situation
Does your environment face a similar problem?
The request keeps this mission and thread. It is not a claim that the demonstration has been validated in your environment.
The printable flyer is being revised and is not available for download.