SOP: Communication Between Site Manager and Site Engineer

 Here is a professional SOP designed specifically for your site-level control 👇


SOP: Communication Between Site Manager and Site Engineer

1. Purpose

To establish a clear, fast, and disciplined communication system between the Site Manager (SM) and Site Engineer (SE) to ensure smooth site execution, strong team coordination, and control of Time – Cost – Quality – Safety (T-C-Q-S).


2. Objective

This SOP aims to:

  • align site strategy (SM) with execution (SE)
  • prevent miscommunication on site
  • improve productivity and workflow
  • reduce mistakes and rework
  • ensure proper reporting and control

3. Scope

Applies to:

  • Site Manager
  • Site Engineer
  • Foreman / Supervisor
  • Workers

Covers:

  • daily operations
  • task assignment
  • technical clarification
  • problem solving
  • reporting system
  • site coordination

4. Definitions

Site Manager (SM)
Responsible for overall site control: planning, manpower, coordination, progress, and performance.

Site Engineer (SE)
Responsible for technical execution: drawings, measurements, supervision, and ensuring correct work on site.


5. Core Principles

Communication must be:

  • direct and clear
  • fast and practical
  • based on facts (drawing, measurement, site condition)
  • solution-focused
  • well documented

6. Roles and Responsibilities

6.1 Site Manager (SM)

  • plan daily and weekly work
  • assign tasks to SE and foreman
  • control manpower and productivity
  • monitor progress and performance
  • solve operational problems
  • coordinate with Project Manager

6.2 Site Engineer (SE)

  • execute work based on drawings
  • check dimensions and levels
  • supervise technical work
  • guide foreman and workers
  • report progress and issues
  • ensure quality and safety

7. Communication Structure

7.1 Daily Communication

Used for:

  • work planning
  • progress update
  • manpower control
  • site issues

Tools:

  • face-to-face (morning briefing)
  • site walk
  • Telegram group

7.2 Technical Communication

Used for:

  • drawing clarification
  • technical problems
  • measurement issues

Tools:

  • marked drawings
  • sketches
  • photos
  • RFI (if needed)

7.3 Reporting Communication

Used for:

  • progress tracking
  • issue reporting
  • performance monitoring

Tools:

  • daily report
  • checklist
  • photo report

8. Daily Workflow

8.1 Morning Briefing (Start of Day)

Site Manager:

  • explains daily plan
  • defines priority work
  • assigns zones and tasks
  • confirms manpower

Site Engineer:

  • confirms understanding
  • prepares drawings and layout
  • checks materials and tools

8.2 During Work

Site Engineer must:

  • monitor execution
  • check dimensions and quality
  • guide workers
  • report any issue immediately

Site Manager must:

  • monitor progress
  • support problem solving
  • adjust manpower if needed

8.3 End of Day

Site Engineer reports:

  • work completed
  • progress (%)
  • manpower used
  • problems/issues
  • photos

Site Manager:

  • reviews performance
  • compares with plan
  • prepares next day plan

9. Task Assignment System

Rule:

SM assigns → SE explains → Foreman executes

Flow:

  1. SM assigns task
  2. SE explains drawing and method
  3. Foreman leads workers
  4. SE checks quality
  5. SM checks progress

10. Technical Issue Workflow

When issue occurs:

Step 1: Site Engineer

  • identify problem
  • check drawing
  • measure actual condition
  • take photo
  • propose solution

Step 2: Inform Site Manager

Include:

  • location
  • problem description
  • drawing reference
  • impact
  • proposed solution

Step 3: Site Manager Decision

  • approve solution OR
  • escalate to PM/Engineer

Step 4: Execution

  • SE explains to team
  • work continues

11. Escalation Rules

Escalate immediately if:

  • safety risk
  • structural issue
  • major design conflict
  • delay risk

Do NOT:

  • continue wrong work
  • hide problems
  • guess without confirmation

12. Information Standard

Every communication must include:

  • location (grid/area/level)
  • task or issue
  • drawing reference
  • measurement
  • photo/sketch
  • required action

13. Reporting System

13.1 Daily Report (SE → SM)

Include:

  • progress (%)
  • completed work
  • manpower
  • materials used
  • equipment
  • issues
  • photos

13.2 Checklist System

  • quality checklist
  • safety checklist
  • inspection checklist

14. Common Problems & Solutions

Problem 1: Workers don’t understand drawing

Solution:

  • SE explains with sketch
  • use simple language
  • show physical reference

Problem 2: Wrong execution on site

Solution:

  • stop work
  • correct immediately
  • retrain team

Problem 3: Poor communication between SM and SE

Solution:

  • daily briefing mandatory
  • use checklist
  • standard reporting format

Problem 4: Delay due to miscoordination

Solution:

  • improve planning
  • update progress daily
  • assign clear responsibility

15. Communication Behavior Standard

Good Communication

  • “Column at Grid C-3 is misaligned by 20mm.”
  • “We completed 80% of brickwork today.”
  • “Need 10 more workers for tomorrow.”

Bad Communication

  • “Work not good.”
  • “There is problem.”
  • “Something wrong.”

16. KPI for SM–SE Communication

  • daily report accuracy
  • response time
  • number of rework cases
  • productivity rate
  • delay due to miscommunication

17. Tools Recommended

  • Telegram (site communication)
  • printed drawings
  • checklist forms
  • photo reporting
  • progress tracking sheet

18. Authority Matrix

Decision TypeResponsible
Daily executionSite Engineer
Work planningSite Manager
Technical issueSM + Engineer
Safety stopSE / SM (immediate)
Major decisionProject Manager

19. Golden Rules

Site Engineer:

  • check before execute
  • report early
  • guide workers clearly

Site Manager:

  • plan clearly
  • assign correctly
  • control performance

20. Conclusion

The relationship between Site Manager and Site Engineer is the engine of the construction site.

If communication fails:

  • work becomes chaotic
  • mistakes increase
  • delays happen

If communication is strong:

  • work flows smoothly
  • team is organized
  • project succeeds

If you want, I can turn this into your Smart-Book HTML (clean Sarim Insight style with search + highlight + quick navigation) so you can post directly on your blog.

Previous Post Next Post
📑