Question 09 · Repair & Reuse · Decision rhythm
Recommendation: use daily operations for safe execution and containment, weekly coordination for shared dependencies within delegated limits, and monthly governance for policy, funding and scope. If waiting would miss an explicit decision deadline, convene the authorised owner sooner. A faster meeting does not confer more authority.
Exact question: Which decisions belong in daily operations, weekly coordination and monthly governance?
Fictional what-if workspace. Changes stay in this tab and reset on reload; no record is saved and no external system is changed.
Keep today’s work safe and feasible across North and South hubs.
Proposed practice: a short daily review; a safety hold is immediate, not delayed until the meeting.
Resolve supplier and shared-resource dependencies before they affect the 12-week launch.
Proposed practice: one cross-hub coordination forum each week, with exception meetings when necessary.
Make reserved policy and funding decisions with the accountable authority present.
“Monthly governance” is the supplied “Monthly board” forum. Cadence is not a reason to miss the last safe decision date.
Try the boundary
Start with the grant funding decision: its urgency score is 4, yet it stays monthly while the planned board is early enough. Compare equality with a one-day breach. The numerical timing values below are authored what-if assumptions, not supplied operational evidence.
All days are whole working days from now, where day 0 means today. Equality is explicitly permitted, with zero spare time; monitor it closely. The implementation lead includes whatever preparation, execution and buffer the scenario requires. A real launch would agree these values and the threshold with its owners.
Baseline illustration loaded; no decision has been approved.
Inputs changed. The result below is the previous illustration; select Simulate routing to replace it.
Correction route: edit the inputs and simulate again. Reset restores the grant illustration at the equality boundary. Reload also clears this tab’s changes. The result is an ephemeral routing recommendation, not an approval, meeting booking or saved record.
These four records are preserved. Urgency helps describe attention; the fixture supplies no urgency-to-cadence rule. An urgency score of 4 alone therefore does not move the grant decision into daily operations.
| ID / decision | Urgency | Normal forum | Decision owner / authority | Permitted action |
|---|
The input labels the fifth column “authority”; this answer uses it as the accountable decision owner without splitting a named collective such as “Sponsor / board” into invented individuals. Exact approval arrangements inside that collective are unknown.
Daily review should leave a named owner, an immediate containment action where needed, and a next check. Weekly coordination should leave a shared dependency plan and a clear boundary on delegated spend. Monthly governance should leave an explicit policy, funding or scope decision with rationale.
For every exception, bring the decision needed, evidence, options, latest safe decision time, authority required and consequences of delay. Record the actual outcome in the real project’s agreed decision log; this page does not create that log.
Do not wait for governance to make work safe. Hold the pilot when sign-off is missing while the Assurance lead arranges the qualified review.
The case fixes a 12-week, £240,000 launch with six shared staff and two hubs. It provides no meeting calendar, consequence dates, delegated-spend limit, quorum rules or evidence that funding has changed. Those uncertainties remain unresolved.
The threshold is a transparent proposed rule, not a supplied policy or a prediction. It assumes a decision made on the latest safe day can be implemented in time. If the lead already exceeds the available time, earlier escalation cannot restore the lost time; containment and replanning are also needed.
Safety release still requires qualified sign-off. Board approval still requires the real authorised people. No scenario, urgency score or routing label satisfies either gate.
These are deterministic arithmetic expectations. The private author receipt records observed local checks; browser review is separate. No operational performance improvement has been measured.