SOP: Communication Awareness (Client + Team)
Standard Operating Procedure · Construction Project Management · Site Engineers, Site Managers & Project Managers
1. What is Communication Awareness?
Communication Awareness is the ability to recognize what you are saying, how you are saying it, who is receiving the message, how they might understand it, and what action should follow.
In Khmer: แាแแแ់แឹแแ្แុแแាแแ្แាแ្แ័แแាแ់แแ แឺแាแแแ្แแាแแ្แុแแាแแឹแแា แើแแំแុแแិแាแแข្แី แិแាแแៅแាแ់แข្แแแា แើแข្แแแแួแแแ់แ៉ាแแូแ แ្แេแ แ ើแแ្แូแแាแแแแ្แแាแแข្แីแแ្แ។
Communication Awareness is more than speaking clearly. It includes listening, observing, confirming, documenting, and following up.
Repeat the cycle until the communication objective is achieved.
2. Why is Communication Awareness important?
A construction project involves clients, engineers, architects, supervisors, subcontractors, suppliers, and workers. Poor communication can cause:
- Rework because instructions were misunderstood.
- Additional costs from unauthorized changes.
- Project delays because problems were reported too late.
- Client dissatisfaction due to unclear expectations.
- Safety incidents because hazards were not communicated.
- Conflict between engineers, workers, and management.
The purpose of this SOP is to establish consistent, documented communication between stakeholders. Its structure follows core communication-planning principles of ISO 9001:2015 clause 7.4 and project management guidance from PMI.
3. SOP Objectives
Every 8AM Contractor employee shall:
- Understand before responding.
- Communicate facts instead of assumptions.
- Respect the person receiving the message.
- Report problems early, not after they become serious.
- Confirm instructions before implementing them.
- Record important discussions, approvals, and decisions.
- Follow up until the required action is completed.
4. Communication Awareness: Client vs Team
| Dimension | Client communication | Team communication |
|---|---|---|
| Main objective | Build trust and align expectations | Coordinate safe, correct execution |
| Focus | Progress, quality, cost, time, decisions | Work sequence, safety, quality, resources |
| Language | Professional, clear, nontechnical where appropriate | Direct, practical, technically accurate |
| Listening | Understand client expectations and concerns | Understand site conditions and obstacles |
| Main risk | Misunderstanding scope, price or completion date | Mistakes, rework and unsafe execution |
| Required outcome | Documented agreement or next decision | Confirmed instruction and completed task |
5. SOP Procedure: Seven Steps
NOTICE: Become aware of the situation
Before communicating, observe the facts, the environment, the people involved and their emotional state.
Ask: What happened? What do I actually know? What is uncertain? Is anyone under pressure? Is there an immediate risk?
THINK: Assess the message
Identify your purpose and separate verified facts from assumptions. Consider cost, quality, schedule, safety and contract requirements before making a commitment.
Ask: Why am I communicating? Who needs this information? Am I authorized to make this decision?
SPEAK: Communicate clearly and respectfully
State the issue, evidence, potential impact, recommended action and required response. Avoid blaming others, unnecessary jargon and promises without verification.
CONFIRM: Check understanding
Ask the recipient to explain or acknowledge the instruction, including the task, responsible person, deadline and any constraints.
For critical site work, use read-back: the recipient repeats the instruction in their own words.
RECORD: Maintain communication evidence
Capture decisions in the appropriate project record: meeting minutes, site instruction, RFI, drawing register, variation register, daily report or email.
Telegram may support coordination, but contractual approvals must use the authorized persons and methods specified in the contract.
ESCALATE: Report unresolved or high-risk issues
Inform the responsible manager when the issue exceeds your authority, remains unresolved, or threatens cost, time, quality or safety. Do not conceal bad news.
FOLLOW UP: Verify the result
Check whether the action was completed correctly. Close the record only after verification and inform affected people of the outcome.
6. SOP-A: Client Communication
A1. Before communicating with a client
The Project Manager or authorized representative shall review the relevant drawings, contract scope, latest schedule, progress, open issues, cost implications and approval status.
Never provide an unverified date, price or technical assurance as a confirmed commitment.
A2. During communication
Use the following structure:
Explain the current situation, why it matters, recommended action and what approval or decision is needed.
Example: Client requests additional wall work
A3. After communication
Document the outcome and send a confirmation that records the decisions, outstanding questions, action owners and dates. Do not treat a casual verbal agreement as a formal variation authorization.
7. SOP-B: Team Communication
B1. Morning briefing
The Site Engineer or Site Manager should communicate:
- Today's work priorities and locations.
- The approved drawings and applicable method statements.
- Required workers, equipment and materials.
- Key hazards and safety controls.
- Quality inspection points.
- Dependencies, responsibilities and completion targets.
Before workers start critical activities, verify that they understand their tasks and safety precautions.
B2. During execution
The Site Engineer must observe work progress, listen to concerns, verify unclear details and stop incorrect work before it creates rework.
Example: Rebar installation
Instead of saying “Install the rebar correctly,” communicate the drawing revision, bar diameter, number, spacing, cover, lap and inspection requirement.
Install the beam reinforcement according to the latest approved structural drawing. Verify the bar size, quantity, stirrup spacing, concrete cover and anchorage details. Request inspection before closing the formwork or casting concrete.
B3. End-of-day reporting
Each workday, capture actual progress, manpower, major materials, inspections, delays, safety concerns, photos and the next-day plan. Clearly identify unresolved items with owners.
8. Communication Responsibility Matrix
| Communication | Responsible role | Frequency / trigger |
|---|---|---|
| Client progress update | Project Manager | Weekly or contractual requirement |
| Client scope/change request | Project Manager | On receipt |
| Morning work briefing | Site Manager / Site Engineer | Daily |
| Technical clarification / RFI | Site Engineer → PM / Designer | When unclear |
| Cost or quantity implications | QS / Estimator → PM | Before commitment |
| Safety hazard escalation | Any worker → Supervisor / PM | Immediately |
| Project coordination meeting | PM + Site Team | Weekly |
| Site daily report | Site Engineer | Daily |
| Approval and decision register | PM / Document Controller | As decisions occur |
These are proposed 8AM operating responsibilities. The approved project organization chart and delegation-of-authority matrix take precedence.
9. Communication Channels and Escalation
| Situation | Primary channel | Required control |
|---|---|---|
| Routine site coordination | Telegram / face-to-face | Confirm owner and task |
| Technical uncertainty | RFI / approved project record | Obtain clarification before affected work |
| Client progress | Email / formal report / meeting | Issue documented progress |
| Scope or contract change | Formal VO / change process | Written authorized approval |
| High-risk delay or dispute | Phone + documented notice | Prompt PM escalation |
| Immediate safety danger | Direct warning, stop work, emergency response as required | Protect people first, then report and record |
For imminent danger, workers must be empowered to move to safety and stop affected work where authorized. No messaging or approval process should delay necessary emergency action.
Proposed response-time targets
Critical safety issue: Immediate
Urgent blocking issue: Acknowledge within 30 minutes during working hours
Routine request: Acknowledge within 1 working day
Unresolved action: Follow up by assigned due date
Internal targets proposed for adoption. Contractual deadlines, emergency procedures and applicable legal requirements override them.
10. Communication Awareness Checklist
11. Ready-to-use Communication Templates
PROJECT PROGRESS UPDATE Project: [Name] Reporting date: [Date] 1. Completed work: 2. Current work: 3. Progress against schedule: 4. Issues / risks: 5. Required client decisions: 6. Next planned activities: 7. Next update date: Prepared by: [PM]
SITE ISSUE REPORT Project: [Name] Date and time: Location: Issue observed: Verified facts / evidence: Potential safety / quality / cost / schedule impact: Immediate control action: Recommended solution: Decision / approval required: Responsible person: Required response by: Reported by:
TEAM WORK INSTRUCTION Project: [Name] Date: Task: Location: Drawing / method statement reference: Required quality / safety controls: Assigned person / crew: Required completion: Inspection / hold point: Recipient confirmation: Issued by:
If Blogger blocks inline scripts, the template text remains visible and can still be selected and copied manually.
12. Performance Measurement (KPIs)
Use measurable outcomes rather than simply counting messages.
| KPI | Proposed initial target |
|---|---|
| Daily site reports submitted on time | ≥95% |
| Weekly client updates issued as planned | 100% |
| Critical safety hazards escalated | 100% |
| Formal variations implemented only after required approval | 100% |
| Action items closed by due date | ≥90% |
| Rework caused by communication errors | Trending downward |
Targets should be confirmed by management after a pilot period, with particular attention to reporting quality and whether issues are actually resolved.
13. Example: Real Construction Situation
Scenario: The client changes the tile specification after procurement.
The Site Engineer receives a message asking to replace the approved floor tile with a larger imported tile.
Incorrect response: “Okay, we will change it.”
Correct response: The Site Engineer acknowledges the request, confirms the proposed product and affected areas, notifies the PM, and checks with the estimator/procurement team on existing stock, unit-rate difference, availability and schedule impact. The PM submits any required variation and obtains contractual approval before directing the changed work.
Learning point: Good communication protects both the client relationship and the project's cost, schedule and contractual controls.
14. Daily Leadership Awareness Practice
At the beginning of every workday, ask yourself:
- What important information does my client need today?
- What must my team understand before starting?
- Which decisions or instructions remain unclear?
- What problem am I delaying or avoiding reporting?
- Who needs feedback or confirmation from me?
At the end of the day, review whether important information was delivered, understood, recorded and acted upon.
15. Implementation Roadmap for 8AM Contractor
Assign communication owners, confirm approved channels, and introduce the team briefing and daily reporting templates.
Apply the seven-step cycle to client requests, technical clarifications and site issues. Review communication mistakes without blame.
Maintain the action register, decision register and variation register. Review overdue replies and unresolved problems at the weekly site meeting.
Audit a sample of communications, interview client-facing and site staff, review KPI results, correct weaknesses and formally approve the refined SOP.
16. Final Principle
Awareness → Clarity → Confirmation → Accountability → Results
For an effective Site Engineer, communication awareness means noticing problems early, making instructions understandable, listening without defensiveness, maintaining accurate records and closing the feedback loop.
For a Project Manager, it means communicating transparently with clients while protecting the project's scope, budget, schedule and contractual obligations.