Mechanical Systems BIM Clash Escalation and Alignment Notice
Coordinate multi-trade MEP spatial conflict resolutions by issuing an actionable clash directive email.
Deploy this template when 3D model coordination detects hard clashes between HVAC ductwork, plumbing, and structural elements. It drafts an alignment email specifying reroute ownership and model commit deadlines.
Role: Principal MEP Coordination Engineer managing building information modeling (BIM) spatial integration for high-density assets.
Context
- Project & Model Milestone: {{development_phase}}
- Target Building Level: {{building_zone}}
- Responsible Trade Subcontractor: {{lead_subcontractor}}
- Clash Matrix Summary: {{clash_severity_summary}}
- Recommended Routing Adjustment: {{proposed_reroute_solution}}
- Model Resubmission Deadline: {{sign_off_deadline}}
Task
Write a targeted coordination email to trade contractors resolving a high-severity MEP clash in the digital coordination model, ensuring alignment prior to field fabrication.
Method
- Reference the specific coordination clash ID and spatial coordinates located in {{building_zone}}.
- Summarize the geometric overlap between MEP disciplines as noted in {{clash_severity_summary}}.
- Articulate why the current routing violates design clearance or building code requirements.
- Present the technical rationale for the proposed routing change ({{proposed_reroute_solution}}).
- Assign explicit revision responsibilities to {{lead_subcontractor}}.
- Define the strict deadline for updated IFC/RVT file submission ({{sign_off_deadline}}).
- Outline the downstream impact on prefabrication schedules if resolution is delayed.
Constraints
- MUST reference specific model coordinates or grid intersections.
- MUST assign clear single-point ownership for the geometry updates.
- MUST NOT recommend field adjustments that bypass the digital coordination sign-off.
- Word count MUST stay between 200 and 320 words.
Output format
- Subject line: Project tag, Level indicator, Clash ID, and Action required
- Salutation to Trade Leads
- Spatial Conflict Overview (concise tabular or bulleted format)
- Routing Instruction & Spatial Re-allocation (bulleted technical notes)
- Model Commit Milestone & Required Deliverables
- Engineering sign-off
Self-review
- Confirm that {{clash_severity_summary}} includes trade specifics (e.g., duct vs. pipe).
- Verify that the resubmission date ({{sign_off_deadline}}) is prominent and unambiguous.
- Ensure no ambiguous trade boundaries exist in the instructions.
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.