Here is a professional SOP tailored for your construction workflow as a GC 👇
SOP: Communication Between Project Manager and Site Engineer
1. Purpose
To ensure clear, fast, and professional communication between the Project Manager (PM) and Site Engineer (SE) so that construction work is executed correctly, on time, within budget, and according to quality and safety standards.
2. Objective
This SOP aims to:
- eliminate confusion between office and site
- ensure correct execution of drawings and plans
- reduce delays and rework
- improve decision-making speed
- maintain strong control of Time – Cost – Quality – Safety (T-C-Q-S)
3. Scope
This SOP applies to:
- Project Manager
- Site Engineer
- Site Supervisor / Foreman
- Quantity Surveyor (QS)
- Procurement Team
Covers:
- daily site operations
- reporting system
- technical clarification
- issue escalation
- progress tracking
- resource coordination
4. Definitions
Project Manager (PM)
Responsible for overall project control: planning, cost, coordination, client communication, and final decision-making.
Site Engineer (SE)
Responsible for site execution: supervision, technical guidance, site problem solving, and reporting.
Daily Report
A daily record of site activities, progress, manpower, materials, and issues.
RFI (Request for Information)
Formal request for clarification on drawings, specifications, or site conditions.
5. Core Principles
Communication between PM and SE must be:
- clear and structured
- fast and responsive
- fact-based (data, not opinion)
- solution-oriented
- documented
6. Roles and Responsibilities
6.1 Project Manager (PM)
- provide clear instructions and project direction
- review progress and performance
- make decisions on cost, design, and schedule
- coordinate with client, architect, and consultants
- approve major site actions
- support SE in problem-solving
6.2 Site Engineer (SE)
- execute work based on drawings and instructions
- supervise site activities daily
- report progress, issues, and risks
- coordinate with foreman and workers
- ensure quality and safety compliance
- raise problems early (do not wait)
7. Communication Structure
7.1 Daily Communication
Used for:
- progress update
- manpower status
- material usage
- minor issues
Tools:
- Telegram / WhatsApp group
- phone call
- daily report
7.2 Formal Communication
Used for:
- technical issues
- design clarification
- delay or cost impact
- major decisions
Tools:
- RFI
- report document
7.3 Meeting Communication
Used for:
- weekly planning
- coordination
- problem solving
Tools:
- weekly meeting
- meeting minutes
- action log
8. Daily Communication Workflow
Step 1: Morning (Before Work Start)
Site Engineer reports:
- today's plan
- manpower
- equipment
- materials available
- expected work zones
PM:
- confirms priority tasks
- adjusts plan if needed
Step 2: During Work
SE updates PM if:
- problem occurs
- drawing unclear
- material shortage
- delay risk
- safety issue
PM:
- gives direction or solution
- escalates if required
Step 3: End of Day Report
SE sends:
- work completed
- progress %
- manpower used
- materials used
- issues/problems
- photos
PM:
- reviews progress
- checks against schedule
- gives feedback
9. Weekly Communication Workflow
Weekly Meeting Agenda:
- progress vs schedule
- completed work
- next week plan
- material status
- manpower planning
- problems and solutions
- risk and delay analysis
Output:
- meeting minutes
- action items
- responsible person
- deadline
10. Technical Issue Workflow
When site problem occurs:
Step 1: Site Engineer
- identify issue
- check drawings
- measure actual condition
- take photos
- propose solution (if possible)
Step 2: Send to PM
Include:
- description
- location
- drawing reference
- impact (time/cost/quality)
- proposed solution
Step 3: PM Action
- review issue
- decide directly OR
- coordinate with architect/engineer
Step 4: Final Instruction
- PM sends clear instruction
- SE confirms understanding
- work proceeds
11. Escalation Procedure
Escalate to PM immediately when:
- safety risk
- structural concern
- cost increase
- schedule delay
- design conflict
Do NOT:
- make major decision alone
- continue unclear work
- hide problems
12. Information Standard (Every Message Must Include)
- project name
- date
- location (grid/area/level)
- description of issue
- drawing reference
- photo or sketch
- required action
13. Reporting System
13.1 Daily Report (SE → PM)
Must include:
- progress (%)
- work done
- manpower
- materials
- equipment
- issues
- photos
13.2 Weekly Report (PM)
- summary progress
- schedule comparison
- cost status
- key risks
- client update
14. Common Problems & Actions
Problem 1: Site work does not follow drawing
Action:
- stop work
- verify drawing
- report to PM
- correct before continuing
Problem 2: Delay due to missing material
Action:
- report early
- inform procurement
- adjust work sequence
Problem 3: SE does not report issue early
Action:
- enforce daily reporting
- create checklist
- monitor KPI
Problem 4: PM gives unclear instruction
Action:
- SE must ask for clarification
- confirm in writing
15. Communication Behavior Standard
Good Communication
- “Today we completed 70% of slab reinforcement.”
- “Issue at Grid A-2, beam depth conflict.”
- “We propose to adjust level by 50mm, please confirm.”
Bad Communication
- “Work not done.”
- “There is problem.”
- “I don’t know.”
16. KPI for Communication
- daily report submission rate
- response time
- number of site issues resolved
- number of reworks
- delay due to communication failure
17. Tools Recommended
- Telegram group (site communication)
- Google Drive (documents & drawings)
- Excel / Dashboard (tracking)
- RFI Log system
- Photo report system
18. Approval Authority
| Decision Type | Responsible |
|---|---|
| Daily work execution | Site Engineer |
| Technical issue | PM + Engineer |
| Cost impact | PM |
| Design change | Architect + PM |
| Safety stop | SE (immediate) |
19. Final Rule
Site Engineer must:
- report early
- not hide problems
- follow instruction
- document everything
Project Manager must:
- respond fast
- give clear direction
- support the site
- control project performance
20. Conclusion
Strong communication between PM and SE is the heart of project success.
If communication is:
- slow → project delays
- unclear → mistakes happen
- undocumented → conflict occurs
But if communication is:
- fast
- clear
- professional
👉 The project becomes controlled, efficient, and profitable.
If you want, I can convert this into your Smart-Book HTML (no background, clean blog style, with search + highlight + navigation chips) for Sarim Insight.