1. Confirm the test boundary
- Define the buildings, networks, systems and operating modes included.
- Identify what is explicitly excluded and whether exclusions affect expected outcomes.
- Confirm the fire strategy, cause-and-effect revision and client acceptance criteria being used.
2. Prove commissioning prerequisites
- Confirm fire alarm, ASD, interfaces and dependent systems have completed the agreed commissioning stage.
- List active faults, isolations, temporary works, disabled outputs and outstanding configuration changes.
- Check that software versions, panel databases and backups are controlled.
3. Challenge ASD and airflow assumptions
- Record the HVAC and airflow conditions under which ASD tests were completed.
- Confirm whether final Day-1 airflow, containment and pressure relationships differ.
- Identify scenarios that require dynamic testing rather than reliance on static results.
4. Map high-consequence interfaces
- Prioritise smoke control, AHU shutdown, suppression, access control, lifts, alarms, monitoring and operator actions.
- Confirm expected timing, status feedback, reset behaviour and dependencies.
- Assign one owner for evidence from each interface.
5. Make the script executable
- State prerequisites, trigger, expected response, timing, evidence points, stop criteria and recovery steps.
- Confirm who controls the test, who records, who can stop and who accepts the result.
- Plan how failed scenarios will be isolated, corrected and retested.
6. Prepare the evidence trail
- Use consistent scenario IDs across scripts, logs, defect records, photographs and retest evidence.
- Confirm event logs and third-party system records can be exported or retained.
- Agree how deviations, partial passes and residual risks will be reported.
Use proportionately. This guide supports project preparation; the applicable fire strategy, specification, legislation and standards determine the actual project requirements.