A large event becomes stressful when decisions arrive in the wrong order. A team can be busy for weeks and still discover that permits, venue access, technical power or guest movement were never properly closed. Activity is not readiness.
This ninety-day model is a sequencing framework, not a claim that every event needs exactly ninety days. A smaller programme may compress it; a city-scale or government event may require a year. Calibrate the duration, but protect the logic: define, test, commit, integrate, assure, operate and learn.
The operating model
The plan runs through seven gates. Each gate has a decision owner, evidence requirement and exit condition. Work can overlap, but a downstream commitment should not hide an unresolved upstream assumption.
- Define: Agree purpose, audience, scope, governance, success measures and constraints.
- Test: Challenge the concept against venue, authority, production, safety, budget and supplier realities.
- Commit: Approve the delivery baseline and appoint accountable workstream owners.
- Integrate: Connect creative, content, technical, guest, protocol, transport and venue plans.
- Assure: Replace verbal confidence with permits, drawings, confirmations, tests and rehearsals.
- Operate: Move to a live command rhythm with short reporting and explicit escalation.
- Learn: Close commercial, operational and stakeholder obligations and capture reusable lessons.
At every gate, maintain six controls: the integrated schedule, scope matrix, cost forecast, risk register, decision log and action tracker. These are not separate administration streams. Together they explain what is promised, when it must happen, what it costs, what threatens it and who must decide.
Days 90–60: truth and feasibility
Days 90–75 define the truth. Confirm the event objective, audience, owner, budget range, experience promise, decision hierarchy and non-negotiables. Convert soft ambitions into testable outcomes. “Create impact” is not enough; define what guests, sponsors, authorities and the client should be able to see or measure.
The gate outputs should include:
- an approved brief and scope boundary;
- a stakeholder and decision-rights map;
- a milestone schedule and first cost model;
- success measures and reporting ownership; and
- an initial risk and assumptions register.
Days 74–60 test feasibility. Walk the venue, validate capacity and access, identify authority pathways, test power and rigging assumptions, map transport and guest flows, scan supplier availability and examine weather or environmental constraints. A concept is only viable when the operational system around it is viable.
Record assumptions with an owner and expiry date. “Venue can provide 800 amps” is not a fact until the venue or appointed technical authority confirms it. Unverified assumptions should be visible in the risk register and cost forecast, not buried in meeting notes.
Days 59–30: lock and coordinate
Days 59–45 establish the delivery baseline. Appoint workstream owners, define interfaces, secure critical suppliers and freeze enough of the concept for detailed design. The baseline should include the approved scope, schedule, budget, floor plan, production approach, procurement plan and governance rhythm.
Days 44–30 are for integration. Weekly meetings should be decision-led, not a tour of status updates. Each workstream arrives ready to answer four questions:
- What changed against the baseline?
- What is blocked, by whom and until when?
- What decision is required, from whom and by what latest date?
- What new dependency or risk does this create for another team?
Use look-ahead planning. The master schedule may contain hundreds of tasks; the working conversation should focus on the next two weeks, critical-path items and decisions whose delay will create irreversible cost or schedule impact. Every action needs one owner and one due date. Shared ownership usually means no ownership.
Days 29–3: prove readiness
Days 29–14 convert project documents into operational tools. Draft the run sheet, staffing plan, accreditation matrix, transport schedule, VIP movement plan, emergency procedures, communications plan, supplier contact sheet, signage schedule and rehearsal programme. Cross-reference them so changes do not create contradictions.
Days 13–3 are an assurance period. Close permits, inspect evidence, reconcile guest data, validate crew credentials, confirm deliveries and test scenarios. Use three readiness states:
- Red: No credible plan or the due date has failed.
- Amber: Plan exists, but evidence, dependency or approval remains open.
- Green: Named owner, approved evidence and tested delivery route are in place.
“It should be fine” is amber. Green requires evidence. For high-consequence items, the evidence may be an approved drawing, permit, signed method statement, system test, physical inspection or completed rehearsal. The standard of proof should be proportionate to the risk.
Final 72 hours and close
In the final 72 hours, protect the operation from unnecessary change. Establish the command structure, freeze controlled documents, brief every team and confirm escalation authority. New requests enter change control with their cost, timing, safety and cross-workstream effects stated. “Small change” is not a category; impact determines the decision.
On event day, the question changes from “what should happen?” to “what is happening now?” Use brief operational cycles: current status, next critical milestone, exceptions, decisions and public-facing implications. Keep leadership informed without flooding the command channel.
After the event, reconcile costs, incidents, supplier performance, client actions and asset returns. Hold a structured review while evidence is fresh. Assign each lesson to a process owner with a completion date. A project is not complete when the last guest leaves; it is complete when obligations are closed and the organisation has learned.
KPI dashboard
These are recommended operating targets that teams must calibrate to scope, complexity, risk and approval environment.
| KPI | Formula | Cadence | Recommended target |
|---|---|---|---|
| Milestone reliability | Milestones completed on time ÷ milestones due × 100 | Weekly; daily final 14 days | ≥90%; critical path 100% |
| Decision ageing | Sum of days open ÷ open decisions | Twice weekly | <3 days; zero past latest date |
| Action closure rate | Actions closed on time ÷ actions due × 100 | Weekly | ≥90% |
| Readiness evidence | Green critical controls ÷ critical controls × 100 | Daily final 14 days | 100% before doors |
| Scope stability | Approved changes after baseline ÷ baseline deliverables × 100 | Weekly | <5%, calibrated by event |
| Forecast variance | (Forecast final cost − approved budget) ÷ approved budget × 100 | Weekly | Within approved tolerance |
| Rehearsal pass rate | Scenarios passed ÷ scenarios tested × 100 | Each rehearsal | 100% for critical scenarios |
Illustrative worked example
Illustrative scenario only; this is not an Ahmed or client outcome. At day 45, a corporate event has 40 due milestones. Thirty-four are complete, so milestone reliability is 34 ÷ 40 = 85%, below the recommended 90% range. Five of the six late items depend on final stage dimensions, and that decision is already four days old.
The dashboard reveals one constraint rather than six unrelated failures. The project director schedules a decision session with the authorized client owner, technical lead and venue. The stage footprint is approved that day, affected drawings are reissued and each downstream task receives a revised evidence deadline. At the next review, 18 of 19 due milestones are complete: 94.7% reliability.
The important move is not celebrating the improved percentage. It is removing the decision bottleneck, recording the approved baseline and checking whether acceleration created cost, safety or supplier risk elsewhere.
Leading and lagging indicators
Leading indicators predict readiness: decision ageing, assumption closure, critical-path reliability, evidence completion, open red risks and rehearsal pass rate. They tell leaders where intervention can still change the outcome.
Lagging indicators confirm what occurred: final cost variance, late opening, incidents, missed deliverables, client acceptance and closure time. Both matter. A project can open on time through heroic recovery while carrying weak leading indicators; that is not a repeatable operating model.
Evidence and standards
- ISO 21502:2020 provides guidance for project management across different delivery approaches, sizes and complexities.
- UK HSE: Getting started with event safety sets out proportionate planning, clear responsibility, risk assessment, contractor competence and emergency preparation.
- UK HSE: Managing an event covers coordination, information, competence, monitoring and post-event review.
- FEMA: Incident Action Plan development explains the operational planning cycle used to turn objectives into controlled assignments and briefings.
