Call, message or letter: choosing the channel for a site communication
A stair is blocked by a delivery, the finishing crew needs tomorrow’s access time and the owner has requested extra work. All three messages land in the same group chat. One needs action now, one needs an agreed plan and one may need a formal notice.
Choose the channel by the urgency, the decision-maker and the record the message needs. Use direct contact for an issue that cannot wait for someone to read a queue, a shared written message for routine coordination and the prescribed procedure for contractual communication. Then confirm important conversations in writing. A fast message can reach a person without creating the record or satisfying the notice requirements you need later.
Match the message to the decision
- State the action first. Decide what the recipient must do and by when. A request to clear a route is different from a request to price a change, even if both concern the same delivery.
- Contact the person who can act. For an urgent site issue, use the established site emergency or safety procedure where applicable. For routine work, contact the responsible trade lead rather than adding a larger group.
- Put coordination where affected people can find it. Identify the area, activity and timing in a short written update. Separate the agreed decision from a suggestion still waiting for an answer.
- Check the contractual route. Before sending a cost, time or scope notice, check who receives it, its required content and the permitted delivery method. Do not assume a chat message has the same status as a formal notice.
- Confirm the conversation. Record the people involved, the location, the agreed action and anything still unresolved. Ask for a correction if your summary does not match the other person’s understanding.
- Close the loop in the same record. Mark whether the action happened or a decision changed. Send a fresh update to those affected rather than expecting them to discover a reply buried in an older thread.
Common mistakes
- Putting an urgent request in a busy thread without confirming that anyone responsible has seen it.
- Adding every manager to a message when one named person can decide.
- Assuming an email subject line alone makes a communication a valid contractual notice.
Checklist
Before you send the message
- What action do you need?
- Who has authority to take it?
- When must they respond?
- Which procedure determines the channel?
- Where will the decision be recorded?
- Who needs to hear the outcome?
Check your understanding
A foreman confirms a scope change by phone. Is a short chat summary enough?
