Here is a professional SOP focused on coordination between Site Engineer (Civil/Structural) and MEP Engineer — very important for avoiding clashes on your projects 👇
SOP: Communication Between Site Engineer and MEP Engineer
1. Purpose
To ensure clear, coordinated, and timely communication between the Site Engineer (SE) and MEP Engineer so that all MEP works are properly integrated with structural and architectural elements, minimizing clashes, rework, and delays.
2. Objective
This SOP aims to:
- prevent MEP vs structural/architectural clashes
- ensure correct installation of services (electrical, plumbing, HVAC)
- reduce rework and site conflict
- improve coordination efficiency
- maintain quality, safety, and project schedule
3. Scope
Applies to:
- Site Engineer (Civil/Structural)
- MEP Engineer (Electrical, Plumbing, HVAC)
- Foreman (civil & MEP)
- Site Supervisor
Covers:
- layout coordination
- embedment works (sleeves, conduits, boxes)
- installation sequence
- inspections
- testing and handover
4. Definitions
Site Engineer (SE)
Responsible for structural and architectural execution, dimensions, and site control.
MEP Engineer
Responsible for all mechanical, electrical, and plumbing systems installation and performance.
Clash
Conflict between MEP services and structural/architectural elements.
Shop Drawing
Detailed drawing showing actual installation layout on site.
5. Core Principles
Communication must be:
- proactive (before work starts)
- coordinated (not isolated work)
- accurate (based on drawings and measurements)
- documented
- solution-oriented
6. Roles and Responsibilities
6.1 Site Engineer (SE)
- provide structural and architectural layout
- ensure correct slab, beam, wall positions
- coordinate embedment before concrete works
- review MEP openings affecting structure
- supervise civil works
6.2 MEP Engineer
- provide MEP shop drawings
- coordinate routing of services
- define sleeves, conduits, and openings
- ensure system functionality and compliance
- supervise MEP installation
7. Communication Structure
7.1 Pre-Work Coordination (Most Important)
Used before:
- slab casting
- beam/column works
- wall construction
Tools:
- coordination meeting
- shop drawings
- marked-up plans
7.2 Daily Site Coordination
Used for:
- work sequence
- progress update
- minor issues
Tools:
- site walk
- Telegram group
- verbal + confirmation
7.3 Technical Communication
Used for:
- clashes
- design conflicts
- missing details
Tools:
- RFI
- marked drawing
- sketches
- photos
8. Critical Workflow: Before Concrete Work
Step 1: MEP Engineer
- submit shop drawing
- mark all:
- conduits
- sleeves
- openings
- embedded items
Step 2: Site Engineer Review
- check against:
- structural drawings
- beam/slab positions
- rebar layout
Step 3: Coordination
- adjust routing if clash occurs
- confirm position and levels
Step 4: Site Marking
- mark on slab/beam
- verify on site
Step 5: Inspection
- joint inspection (SE + MEP)
- confirm before casting
Step 6: Approval
- sign inspection checklist
- proceed with concrete
9. Installation Workflow (After Structure)
Step 1: MEP Engineer
- install services according to approved shop drawing
Step 2: Site Engineer
- check:
- no damage to structure
- no unauthorized cutting
- correct position
Step 3: Coordination
- adjust if needed
- avoid interference with other systems
10. Clash Detection Workflow
When clash occurs:
Step 1: Identify
- SE or MEP Engineer detects issue
Step 2: Verify
- check drawings
- measure site condition
Step 3: Report
Include:
- location
- type of clash
- drawing reference
- photo
- impact
Step 4: Solution
Options:
- reroute MEP
- adjust level
- modify opening (if approved)
Step 5: Approval
- SE + MEP Engineer
- escalate if structural impact
11. Rules for Structural Safety
MEP Engineer must NOT:
- cut beam/column without approval
- drill slab without permission
- modify structural elements
Site Engineer must:
- protect structural integrity
- review all MEP openings
- approve embedment before casting
12. Information Standard
Every communication must include:
- location (grid/level/area)
- service type (electrical/plumbing/etc.)
- drawing reference
- dimension/level
- photo/sketch
- required action
13. Reporting System
Daily Report
Include:
- MEP work progress
- civil work progress
- coordination issues
- pending items
Inspection Checklist
- sleeve position
- conduit installation
- embedment
- opening size/location
14. Common Problems & Solutions
Problem 1: Missing sleeve before concrete
Solution:
- stop work if possible
- drill only with approval
- improve pre-check system
Problem 2: MEP clashes with beam
Solution:
- reroute below/above beam
- adjust ceiling level
- redesign if needed
Problem 3: Unauthorized cutting of structure
Solution:
- stop work immediately
- report to PM
- evaluate structural safety
Problem 4: Poor coordination
Solution:
- daily coordination meeting
- shared drawings
- checklist before execution
15. Communication Behavior Standard
Good Communication
- “Electrical conduit conflicts with beam at Grid B-2.”
- “Sleeve required at slab level +3.00m.”
- “Please confirm opening size 150mm.”
Bad Communication
- “Pipe cannot pass.”
- “There is problem.”
- “Fix it.”
16. KPI for SE–MEP Communication
- number of clashes detected before execution
- number of rework cases
- number of missing sleeves
- response time
- coordination meeting effectiveness
17. Tools Recommended
- coordinated shop drawings
- Telegram group
- checklist forms
- photo reports
- RFI log
18. Authority Matrix
| Decision Type | Responsible |
|---|---|
| MEP routing | MEP Engineer |
| Structural approval | Site Engineer |
| Clash resolution | SE + MEP |
| Major change | PM + Consultant |
19. Golden Rules
Site Engineer:
- check before concrete
- protect structure
- coordinate early
MEP Engineer:
- plan routing early
- follow approved drawings
- never cut structure without approval
20. Conclusion
The connection between Site Engineer and MEP Engineer is critical.
If coordination fails:
- concrete is broken
- structure is damaged
- cost increases
- project delays
If coordination is strong:
- work is clean
- installation is smooth
- project is efficient and professional
If you want, I can convert this into your Smart-Book HTML (Sarim Insight style: no background, search + highlight + navigation chips) so you can post directly on your blog.