Improving communication between office and field

Most friction between the office and the field is not about careless people. It comes from the plan living in too many places: a whiteboard in the yard, a spreadsheet on the dispatcher's laptop, a group text and a 5:30 AM phone call.

When something changes, each copy drifts a little further from the others. This guide covers the habits that keep the office and the field working from the same version of the day, whatever tools you use.

Where office and field communication breaks down

Before changing anything, look at where messages actually get lost. On most heavy civil jobs, the same weak points come up again and again.

• More than one source of truth. If the whiteboard, the spreadsheet and the group chat can disagree, sooner or later they will.
• Changes by side channel. A dispatcher calls one foreman about a truck swap and forgets the foreman who is losing the truck.
• No confirmation. A message was sent, so the office assumes it was received and understood.
• Vague times and places. "Be there early" or "the north end" means different things to different people.
• Field information that never comes back. Breakdowns, delays and quantities stay in the foreman's head or notebook until the next morning, or later.
• Too much noise. When every message goes to everyone, people stop reading, and the one that matters gets missed.

Each of these has a practical fix. None of them needs new software to start, although the right tools make the fixes easier to keep up.

Keep one plan, and make it the only plan

Decide where the plan for each day lives, then retire the copies. If the published plan says it, it is true. If it is only in a text message, it is not the plan yet.

That single plan should answer the questions a crew asks before leaving the yard:

• Which project, which address or station, and where to report on site.
• Who is on the crew and who is in charge.
• Which machines, trucks and trailers are assigned, by unit number.
• The times that matter, stated separately: crew start, first load or first delivery, and truck report time.
• The work planned: activity, material, quantity, and site notes such as access, traffic control set-up or utility locates.

Write it so a new labourer could follow it without a phone call. Use unit numbers and full names rather than "the big roller" or "Mike's crew".

Set a rhythm for the plan

Communication improves when everyone knows when the plan is built and when it is final. A predictable rhythm beats a perfect plan that arrives at a different time every day.

A common pattern for crews working day shifts looks like this:

1. Early afternoon: foremen send tomorrow's needs to the office: crew, equipment, trucks, materials and start times.
2. Mid to late afternoon: the dispatcher drafts the plan, checks for double-booked people and machines, and books trucks and materials.
3. Evening or early morning: the plan is published, after any weather call or plant confirmation.
4. During the day: changes go through one person and are republished, not passed along by word of mouth.

Adjust the times to your work. Night paving, for example, shifts the whole cycle. What matters is that the cut-offs are known and kept.

For a step-by-step method, see how to build a daily construction dispatch schedule.

Agree how changes are made

Plans change: weather, a breakdown, an inspector's call, a plant delay. The goal is not to stop changes. It is to make every change travel the same way.

Write down a short change rule and share it with foremen and dispatch:

• One owner. One person, usually the dispatcher or operations manager, changes the published plan. Foremen request changes; they do not make side arrangements that bypass the plan.
• Update the plan first, then talk. Change the plan, then call or message the people affected. A phone call without a plan update leaves the record wrong.
• Tell everyone the change touches. A truck swap affects the crew losing the truck, the crew getting it, and the driver or broker. List them before you send anything.
• Say exactly what changed. "Revision 2: first load on the Main Street job moves from 7:30 to 9:30 AM for the weather; crew start stays at 7:00 AM" is clearer than "see updated plan".

Close the loop with confirmation

Sending a message is not the same as it being received. High-risk fields use closed-loop communication for this. In healthcare, one version is called a check-back: the sender gives the message, the receiver repeats it back, and the sender confirms it was understood.

On a jobsite, the same idea scales down to a few habits:

• Ask each foreman to confirm the day's assignment, not just open it.
• For a change that matters, such as a new start time or a truck swap, ask for a reply that restates it: "Copy, first load moved to 9:30."
• Follow up on silence. If a crew lead has not confirmed by an agreed time, call them.
• At the morning crew meeting, the foreman walks the crew through the plan, so it reaches people who have not read it.

Bring the field's information back

The office plans tomorrow from what happened today. If production, delays and issues arrive late or not at all, tomorrow's plan is built on guesses.

Make the return trip as deliberate as the outbound one:

• Issues during the day. A machine down, a truck missing, a site that is not ready. The foreman reports it as it happens, with the unit number, the effect on the work and a photo where it helps.
• Production at the end of the shift. Quantities by activity, location, loads or tickets, hours, and any delays with their causes.
• Notes for tomorrow. What the crew needs, what work is left, and anything the next crew must know.

Keep the report short enough to finish at the tailgate. A short report sent every day is worth more than a long one sent when someone remembers. For what to include, see practical daily reports for road construction.

Give each channel a purpose

Group chats and phone calls are not the problem. They become the problem when they carry the plan itself.

• The plan: the published dispatch, one per day, with its revisions.
• Urgent problems: a phone call, followed by a written record of the issue.
• Project discussion: a channel per project or crew, so a paving question is not buried under an earthworks thread.
• Follow-ups: anything with an owner and a due date, written as a task rather than a chat message.

Keep company-wide messages rare, so people still read them when it counts.

Checklist for the office and the field

Use this as a starting point and adapt it to your crews.

For the office

• Publish one plan per day, at a predictable time.
• State crew start, first load and truck report times separately.
• Use unit numbers and full names for every assignment.
• Route every change through one owner, and republish the plan.
• Tell each person a change affects exactly what changed.
• Follow up on any assignment not confirmed by the cut-off.

For the field

• Confirm the day's assignment before leaving for site.
• Walk the crew through the plan at the morning meeting.
• Request changes through dispatch, not side arrangements.
• Report issues as they happen, with a unit number and a photo where useful.
• Send production and notes for tomorrow before the end of the shift.

Where software fits

Tools help when they make the good habit the easy one: one place for the plan, a record of revisions, and a simple way for the field to confirm and report. They support the rhythm and the change rule; they do not replace them.

STRACTA is built around this loop. The office plans and publishes the daily dispatch, and crews review and acknowledge their assignment in My Day on a phone.

When the dispatcher publishes an update, affected users get an in-app notification. Field issues and daily production come back to the office from the same phone.