The short answer: Construction site communication is how instructions, updates, requests and decisions move between the site team, the project manager, the developer's office, contractors and consultants. Good site communication means every message reaches the person who must act on it, in a form they can act on, and leaves a record that can be found later.
It is 10:15 am. The architect told the site engineer on a call yesterday that the L4 bathroom layout has changed. The engineer mentioned it in one of six WhatsApp groups. The plumbing contractor is not in that group. By lunch, his crew has chased sleeves into the wrong wall.
Nobody on that project lacked communication. There were calls, groups, emails and a morning meeting. What was missing was a system: who needs to know, through which channel, in what format, and where the record lives. This guide sets out that system for developers, contractors and project managers.
What is construction site communication?
Construction site communication covers every exchange of information that affects work on site: instructions from consultants, progress updates from engineers, material requests from supervisors, approvals from the project manager, safety alerts, drawing revisions and decisions made in meetings. It runs in four directions:
- Downward: developer and PM to site team and contractors (instructions, priorities, approvals).
- Upward: site to office (progress, labour, materials, problems, requests).
- Sideways: between trades and contractors working in the same area (sequencing, handovers, clashes).
- Outward: to consultants, authorities, buyers and lenders (queries, inspections, status reports).
Most failures happen at the joins between these directions, when a message crosses from one group of people to another and nobody owns its arrival.
Why site communication matters so much
Poor communication rarely shows up as a line item. It shows up as rework, waiting and dispute. In the 2018 Construction Disconnected study by FMI and Autodesk, a survey of nearly 600 construction professionals, respondents said poor project data and miscommunication caused 48% of rework in the US, and that they spent about 35% of their time, over 14 hours a week, on non-productive activities such as looking for information, resolving conflicts and fixing mistakes.
Your numbers will differ by market and project, but the pattern is familiar on any site:
- Rework: work built to an old instruction or a superseded drawing.
- Waiting: crews idle while an approval, answer or material request sits unread.
- Follow-up overhead: the PM spends the morning calling the site to ask what is happening.
- Disputes: nobody can prove what was instructed, when, or by whom.
We explored the root cause in more depth in your construction project doesn't have a communication problem, it has an information problem. This guide is the practical side: how to set up communication so information arrives and stays findable.
The main communication channels on a construction site
No single channel is right for everything. The mistake is using one channel for every kind of message, or letting each person pick their own.
| Channel | Best for | Main risk |
|---|---|---|
| Face-to-face / site walk | Explaining work on the spot, safety briefings, resolving clashes | No record unless someone writes it down |
| Phone calls | Urgent issues that need a decision in minutes | Verbal instructions with no trace; repeated "what's the update?" calls |
| Chat groups (e.g. WhatsApp) | Quick updates, photos, voice notes from site | Messages buried in many groups; no owner, status or structure |
| Formal correspondence with consultants, vendors and clients | Slow for site issues; site staff rarely check it | |
| Meetings | Coordination between trades, weekly progress review | Decisions not minuted or followed up |
| Registers and forms | Formal records: site instructions, RFIs, inspections, deliveries | Filled late, kept on paper, hard to search |
| Project app | One place for updates, requests, approvals and documents | Fails if the site team won't use it |
Who needs to know what: a simple communication matrix
A communication matrix states, for each type of information, who sends it, who must receive it, how fast, and where it is recorded. It sounds formal, but even a one-page version removes most "I didn't know" problems.
| Information | From | To | When | Recorded in |
|---|---|---|---|---|
| Daily progress, labour, materials | Site engineer | PM, developer office | Daily, fixed cut-off | Daily progress report |
| Material request | Supervisor / contractor | PM, store, purchase | As needed, with lead time | Indent register |
| Design query | Site engineer | Architect / structural consultant | As soon as found | RFI log |
| Instruction or change | Consultant / PM | Site engineer, affected contractors | Before work proceeds | Site instruction register |
| Drawing revision | Consultant / document controller | Everyone working from that drawing | On issue | Drawing register + transmittal |
| Safety incident or near miss | Anyone on site | Safety officer, PM | Immediately | Incident / near-miss report |
| Delay or hindrance | Site engineer | PM, contractor concerned | Same day | Hindrance register / DPR |
| Status for client or buyers | PM / developer | Client, buyers, lender | Weekly or monthly | Progress report |
The 8 most common site communication problems
- Too many groups. One group per block, per trade, per contractor, plus "office" and "urgent". Each message lands in one, and the right person is in another.
- Verbal instructions. A consultant changes something during a site walk. Nobody writes it down, and weeks later nobody agrees what was said.
- Superseded information. An old drawing, BOQ or instruction is still being used because the update didn't reach everyone. See the most dangerous drawing on a construction site.
- No owner. A request is posted to a group and everyone assumes someone else will act.
- Decisions buried in chat. The approval exists, but it is message 214 of a long thread.
- Language gaps. Instructions written in one language for a crew that works in another.
- Update chasing. The office calls the site several times a day because there is no reliable status it can check itself.
- Late reporting. Problems surface in the end-of-day report or the weekly meeting, when they could have been solved at 10 am.
How to build a site communication plan in 8 steps
- List the stakeholders. Developer's office, PM, site engineers, supervisors, each contractor, architect, structural and MEP consultants, safety officer, store, purchase, client.
- Fill in the matrix. For each information type above, agree sender, receiver, timing and record.
- Choose one channel per job. For example: site updates and requests in the project app or one structured group; formal correspondence by email; instructions and RFIs on numbered forms.
- Set naming and format rules. Use the same names for blocks, levels, grids and activities as the drawings and schedule.
- Define response times. Material request acknowledged within a few hours; RFI answered within an agreed number of working days; safety issues immediately.
- Set an escalation path. If an answer is late, who is the next person up, and when?
- Fix the daily and weekly rhythm (below).
- Brief everyone on day one, including every new subcontractor, and repeat it when people change.
A daily and weekly communication rhythm
| When | What | Who |
|---|---|---|
| Start of shift | 10–15 minute huddle: today's targets, safety focus, blockers, materials expected | Site engineer, supervisors, contractor foremen |
| During the day | Updates posted when work finishes: pours completed, deliveries received, issues found | Supervisors, store, engineers |
| Midday | Quick check of open requests and anything blocking the afternoon | Site engineer, PM |
| End of day | Daily progress report and tomorrow's plan | Site engineer → PM |
| Weekly | Progress review and look-ahead: plan vs actual, next 2–3 weeks, approvals and materials needed | PM, contractors, consultants as needed |
| Monthly | Status report to developer, client or lender | PM / developer |
The end-of-day report is easier when the day's updates were captured as they happened. Our guide to the daily progress report shows what it should contain.
How to write a site message someone can act on
Most site messages fail because they leave the reader to guess. A useful request answers five questions: what, where, how much, by when, and who must act.
| Vague | Actionable |
|---|---|
| "Cement needed." | "Need 50 bags OPC 53 at Tower B store by 8 am tomorrow for L8 columns. 12 bags in stock. @Priya please approve." |
| "Plumbing issue on 4th floor." | "L4 flat 402 bathroom: sleeve positions clash with beam B12 on Rev 2 drawing. Work stopped in 402 only. RFI raised to MEP consultant, need reply by Thursday." |
| "Slab done." | "L7 slab Grid A–F cast, 142 cum, 6 cubes taken. Curing started 4 pm." |
The same structure works for voice notes. Ask supervisors to say the location first, then the issue, the quantity and what they need.
RFIs, site instructions and escalation
Some messages must be formal, because they change scope, cost or responsibility:
- Request for information (RFI): a numbered query to a consultant when drawings or specifications are unclear or conflict. Log the date raised, the question, who must answer, and the date answered.
- Site instruction: a written instruction from an authorised person to carry out, change or stop work. If it affects cost or time, it may lead to a variation under the contract.
- Transmittal: a record of which drawings or documents were issued, to whom, and when.
- Escalation matrix: who to go to next if an issue is not resolved within the agreed time, from site engineer to PM to project director.
Follow your contract's notice and approval requirements. A chat message is useful evidence of what happened, but it may not replace a formal notice the contract requires.
Multilingual crews and voice notes
On many sites in India, the Gulf and Southeast Asia, the people doing the work speak a different language from the people managing it. Written English instructions often don't land.
- Brief crews in the language they work in, and confirm understanding by asking them to repeat the key points.
- Use photos and marked-up drawings instead of long text.
- Accept voice notes from supervisors, but make sure someone turns them into a record: what was reported, where, and what action follows.
- Keep safety signage and toolbox talks in the crew's languages.
How to measure whether site communication is working
- Follow-up calls per day from the office to the site asking for status. It should fall.
- Request response time: how long indents, RFIs and approvals wait for an answer.
- Same-day logging: share of site events (deliveries, pours, issues) recorded on the day they happen.
- Open issue age: how many issues are older than a week, and who owns them.
- Rework caused by information: rework traced to an old drawing, missed instruction or unclear request.
Site communication checklist
- Is there one agreed channel for site updates and requests, instead of many groups?
- Does every request have a location, quantity, deadline and named owner?
- Are verbal instructions written up the same day and confirmed by the person who gave them?
- Do RFIs and site instructions have numbers, dates and status?
- Does everyone working from a drawing get told when it is revised?
- Can the PM see today's status without phoning the site?
- Is there an escalation path with response times?
- Are new contractors briefed on the communication rules on day one?
Where software fits
Site teams use chat because it is fast and they already know how. The problem is not chat itself, but that chat messages stay unstructured: no type, no owner, no status, scattered across groups.
Brikito, construction management software with Brik AI built in, keeps the chat habit and adds the structure. In BrikChat, Brik AI reads each message, voice note and photo and tags it as an update, attendance, enquiry or ticket. A material request becomes an indent routed to the project manager, progress feeds the live dashboard, and anyone on the project can ask Brik privately about stock, attendance, approvals or the latest drawing. Replies and orders are drafted for the PM to approve; nothing is sent automatically. It works in English and six Indian languages, so the site can keep talking the way it already does.
Frequently asked questions
Why is communication important in construction?
Construction depends on many people acting on the same information at the right time. When instructions, revisions or requests don't reach the right person, the result is rework, idle crews, delays and disputes over who said what.
What are the main communication barriers in construction projects?
Common barriers are information scattered across many chat groups, verbal instructions with no record, outdated drawings still in use, unclear ownership of requests, language differences between managers and crews, and problems reported too late to act on.
Is WhatsApp good for construction project communication?
WhatsApp is fast and familiar, so it works well for quick updates and photos. It struggles as a system of record: messages are spread across groups, have no owner or status, and decisions are hard to find later. Many teams keep chat for speed and move requests, approvals and records into a structured tool.
What is a communication plan in construction?
A communication plan sets out who needs which information, who sends it, through which channel, how quickly, and where it is recorded. It usually includes a stakeholder list, a communication matrix, meeting rhythm, response times and an escalation path.
What is an RFI in construction?
An RFI (request for information) is a formal, numbered query from the site or contractor to a designer or consultant when drawings or specifications are unclear or conflict. It is logged with the date raised, the person responsible for answering, and the date answered.
How can developers track site updates without visiting the site?
Agree a fixed set of daily updates (progress, labour, materials, delays, safety and tomorrow's plan), capture them during the day in one place, and give the office a live view of that record. Site photos and, where available, CCTV help confirm what the updates say.
Communicate once, in the right place
The goal is not more messages. It is fewer, clearer messages that reach the person who must act and stay findable afterwards. Agree the matrix, pick one channel per job, write requests that can be acted on, and close every verbal decision in writing. Do that, and the "what's the latest update?" calls start to disappear.