DPGE1002 Chap.6 Emergency Summit Workflow
Emergency Summit Workflow
The Emergency Summit is a decision process built from an incident briefing, stakeholder preparation, agenda-based comparison, negotiated trade-offs and a confirmed action plan. This chapter shows how to separate facts from unknowns, prepare options rather than a fixed speech, integrate other contributions and close with responsibilities, timing, safeguards and review triggers that make consensus operational.
Read the incident before defending the role. List established facts, uncertain claims, immediate risks, affected groups and decisions that fall within the meeting's authority. Distinguishing an unknown from a fact prevents urgency from turning into invention. Then interpret the same incident through the stakeholder's priority, evidence and authority.
Prepare a preferred action, a minimum acceptable outcome and a feature that can be traded. Add one benefit, one limitation and one mitigation so the proposal can survive evaluation. A prepared option is not a script. New information or another stakeholder's evidence should be able to change its scope, timing or safeguards. Use the agenda to move from shared understanding to decision.
Clarify contributions, compare proposals against agreed criteria and invite information that the group is missing. Interaction becomes visible when one contribution alters another person's reasoning or the design of the action. When disagreement persists, identify the priority behind each position and offer a conditional trade. Consensus does not require every participant to prefer the final package.
It requires an action they can support because the main risks and priorities have been addressed sufficiently. Close by stating the action, owner, timing, constraint, safeguard and evidence that will trigger review or change. Preserve credible unresolved risk in the monitoring plan.
An operational consensus gives participants one testable interpretation of what happens next rather than a vague sense that the discussion ended politely.
What this chapter covers
- 01
Incident facts and unknowns
- 02
Stakeholder decision boundaries
- 03
Preferred and minimum outcomes
- 04
Interaction that develops proposals
- 05
Operational consensus and review
Worked example · free
Respond to a campus water-supply incident
- +1Separate established facts from unknown water-quality and repair information.
- +1State each stakeholder's urgent priority and authority.
- +1Propose temporary closure, alternative study space and regular updates.
- +1Modify the closure to allow escorted refrigeration checks.
- +1Assign actions and identify the evidence that triggers reopening.
Key terms
- Incident briefing
- The shared factual account that defines immediate risks, unknowns and decisions.
- Decision boundary
- The priority or limit a stakeholder cannot abandon without losing its role.
- Action plan
- A sequence of assigned steps with timing, safeguards and review.
- Consensus
- A general agreement participants can support despite different first preferences.
Emergency Summit Workflow FAQ
Should I memorise a summit speech?
No. Prepare evidence, a preferred action, a minimum acceptable outcome and tradeable conditions. The live incident and other contributions should change how you explain and refine the proposal. Prepare short contribution shapes instead: connect to the last point, add relevant stakeholder information and ask for the next decision.
How do I show interaction in the discussion?
Reformulate useful points, compare proposals, ask focused questions, invite missing information and offer design changes. Interaction is visible when another contribution alters the group's reasoning or action. Merely answering another speaker is insufficient when the response leaves the proposal, evidence and group decision exactly where they were.
What belongs in the final consensus?
State the action, responsible actor, timing, safeguard, condition that changes the plan and review method. Record any credible unresolved risk instead of pretending it disappeared. The closing summary should be specific enough that participants could later determine whether the agreed response occurred and when it should change.
Exam move
Use unfamiliar incidents so preparation does not become scripting. Give each stakeholder a preferred action, a limit and one trade. Run the discussion with an agenda and stop whenever a claim lacks evidence or authority. Practise closing in under one minute with an operational summary that every participant can confirm or correct. Before starting, give the group a fact sheet containing both knowns and unknowns.
Require speakers to label uncertainty and propose how missing information will be checked. Appoint an observer to track whether contributions present, connect, compare, modify or confirm. Halfway through, introduce one credible incident update and record which proposals change.
In the closing minute, each stakeholder should listen for action, ownership, timing, safeguard and review trigger, then correct only what is inaccurate or unsupported. After practice, compare the final plan with the opening positions and identify the evidence or trade responsible for every change. Use that record as reflection material rather than relying on a general memory of performance.