Hybrid Incident-Command Practicum, Day One

Protect the exercise's integrity rather than the clock. The remote group did not miss content, they missed decisions and state. Re-running the clock does not restore state.

• Best option: at the next natural break, have the on-site group brief the remote group on the two decisions taken and the current state, then run one joint inject that requires the remote site to act on that state. Costs about 15 minutes and preserves a single shared scenario.
• Cheaper but worse: let the remote group run a compressed parallel version. They arrive at a different state and the capstone can no longer be joint.

Fix the cause before Day 2: a phone bridge as backup audio, a designated remote co-facilitator at the second site, and printed inject packets so a video drop degrades to audio-only instead of stopping the exercise.

Then flag the consequence now, not at grading: identify which lost injects map to capstone criteria. If a criterion was exercised only in the window the remote site missed, its validity for those 10 learners is compromised, and the evaluator needs that information before the capstone, not after scores are posted.

They are the same problem: airtime is going to whoever is loudest, and in a hybrid room the remote participant has a microphone while the quiet on-site learners do not.

• Structure rather than exhort. 'Each table reports one thing no one has said yet' allocates airtime by design, not by assertiveness.
• Give the dominant participant a role that consumes the energy: scribe, timekeeper, or devil's advocate with a two-sentence limit. Redirecting is easier than suppressing.
• For the two silent learners, do not cold-call in the large room. Use a paired think-aloud or a 60-second written 'your decision is' card, then have them report their partner's answer. Lower exposure, and you learn whether the silence is disengagement or lack of confidence - which determines what you do next.
• Ration the remote audio: one speaker at a time enforced by the co-facilitator, with chat used for running commentary that does not need to be spoken.

Name the norm once, at the start of Day 2, as a housekeeping item. A scolding mid-exercise costs more airtime than it recovers.

Treat this as a validity and safety problem, not a scheduling inconvenience. A fail on fatigue-impaired performance is measurement error, and a pass tells you nothing about capability. Incident-command performance degrades under fatigue in exactly the ways the capstone tests: decision speed and error-checking.

Options, in order:

1. Reschedule those three to a make-up capstone within two weeks, same evaluator, same rubric. Protects the score and the credential.
2. If the credential deadline is immovable, run the capstone but record the fatigue condition on the scoring sheet and require a re-check before the credential is treated as confirmed.
3. Do not let them sit and then 'adjust the score' - you cannot adjust a live observation after the fact.

Then fix the schedule: night-shift learners booked immediately after a shift is a design defect that recurs every cohort. Raise it with the program owner in writing this week.

Document the three names and the reason now. Reconstructing why a score was discounted, six weeks later, is how a defensible decision becomes an indefensible one.