📍 When to use this template
- After each clash detection run (typically before GFC).
- Coordination meeting input.
- Design completion + handover documentation.
- Forensic / claim resolution if construction issues arise.
Sections & fields
Preview of the template structure. Download Excel to fill on site.
1Run Header6 fields
Software + Version
_____________
Models Run (Architecture, Structure, MEP, etc.)
_____________
Tolerance Settings
_____________
Approval (PMC / Client)
_____________
2Clash Summary6 fields
Discipline Pair (e.g., HVAC vs Structure)
_____________
Total Clashes
_____________
Critical (Life Safety / Code)
_____________
Major (Coordination)
_____________
Minor (Cosmetic)
_____________
Resolved (% This Run)
_____________
3Critical Clashes Detail7 fields
Description + Location
_____________
Disciplines Affected
_____________
Resolution Owner
_____________
Image / Screenshot Reference
_____________
4Trend3 fields
Total Clashes (per run, historical)
_____________
Closure Rate per Cycle
_____________
Time to Resolution (avg)
_____________
💡 Sample filled excerpt
Run 14-May-2026 (Navisworks). Architectural × Structure: 23 (3 critical). MEP × Structure: 18 (1 critical). MEP × MEP: 9. Total: 50 (5 critical). Avg resolution: 6 days. Trend: Run 3 of 5; 75 % resolved cumulatively.
⚖ Compliance notes
- Critical clashes must be resolved before GFC issuance.
- Per ISO 19650, the BEP defines acceptance criteria + closure thresholds.
- Clash count alone is misleading — severity classification is essential.
- Document any deferred / accepted clashes (with engineering justification).