The site schedule changes: who tells who, and how
Rain, a client who postpones, a material that is missing: the site schedule shifts. How to alert the whole crew in one go, without twenty contradictory calls.

By Jérôme Knops
Published October 11, 2026 · 5 min read

It is seven in the morning, rain makes the site impossible, and the foreman moves everyone to another job. He calls the first tradesman, who calls the second, who forgets the third. That one shows up an hour later, alone, in front of a locked gate.
The short answer: one message, sent at once to everyone concerned, replaces the chain of phone calls. The rest explains what that message needs to contain, and who is allowed to send it.
Why the schedule shifts almost every week
A site schedule is never fixed for more than a few days. The reasons are always the same:
- weather, which blocks some work and allows other work instead;
- a client who is away or postpones the handover walkthrough;
- a material that was not delivered, or delivered in the wrong quantity;
- a broken piece of equipment, or a sick tradesman;
- a previous job that runs longer than planned.
None of these causes is rare. A company running several sites at once lives through at least one change like this every week. The schedule itself is not the problem: what breaks is how it gets passed on.
How the information gets lost between two people
The change is decided in a few seconds, often standing on site, on the phone. How it spreads, though, takes the most fragile path there is: one call, then another, then a message everyone hopes got relayed.
- The first person told is not always the right one. The foreman calls whoever he has on hand, not necessarily the person leaving earliest the next day.
- Every relay rewords it. "We're changing sites" becomes "we're starting later", then "we're not coming". The meaning shifts at every step.
- People who are away get nothing. A tradesman on leave the day before, or simply unreachable at that moment, finds out about the change by showing up on site.
- Nothing keeps a record. The next day, nobody knows who was supposed to tell whom, or whether the message actually went out.
The outcome is never the same for everyone: part of the crew ends up in the right place, another part shows up where nothing is happening, and the site manager hears about it last, from a client waiting for a crew that never arrives.
What a schedule change needs to carry
A well-communicated schedule change fits into four pieces of information, always the same, in the same order:
| Information | Example |
|---|---|
| Who is affected | The painting crew, lot 2 |
| The new site or time | Dupont site, 9 am instead of Martin site |
| The reason, one line | Rain, roof work postponed |
| Who confirms they read it | Each recipient, before 7:30 am |
The last point is the one most often skipped, and it is the most useful: a message sent is not a message read. Without confirmation, the foreman does not know whether he still has to call someone, and he calls everyone just in case, which lands him right back in the original problem.
Who is allowed to send the change
One person decides and sends it, never several in parallel. When the site manager and the foreman each send their own version, one says 8 am, the other says 9 am, and the crew picks whichever one it prefers to believe.
What it costs when it goes wrong
Take a crew of six people. A poorly communicated change sends one or two people out for nothing, either to a closed site or with the wrong materials loaded. Count 45 minutes lost, at a loaded cost of €35 an hour: a little over €26 per incident.
If this happens once a week over a 40-week season, that is more than €1,000 a year, for a single crew. A company running three or four crews quickly passes €3,000 a year, without counting the site manager's time spent piecing together what was actually said. That figure leaves out what is harder to put a number on: the tradesman waiting on a sidewalk, and the client who sees a crew show up at the wrong moment.
The same disorder, on the paperwork side, eventually weighs on the site margin that only gets checked at the end, since a wasted trip costs hours attached to no billable task at all.
What changes with an application built for the company
An application built around the way the company actually works replaces the chain of calls with a single action.
- A change is entered once, with the site, the time and the reason.
- It goes out at once to everyone affected, on their phone, at the same moment.
- Everyone confirms with a tap, and the foreman immediately sees who has not opened the message yet.
- The change keeps a record: who decided, at what time, and who was told. Useful the day a client asks for an explanation.
The next morning's schedule stays visible to everyone at all times, not only at the moment it changes. Crews who already log their hours from the field find the same phone for this information, with no new tool to learn.
What not to do
Do not multiply the channels. One message on a group chat, another by phone and a third on a board at the yard guarantee that nobody has the same version.
Do not wait for a break to pass the word on. The shorter the gap between the decision and the message going out, the less time there is for someone to travel for nothing.
The site schedule that shifts: the key takeaways
A construction schedule changes almost every week, for reasons that are always legitimate. What costs money is not the change itself, but how it spreads through a chain of calls and relays that distorts the message and forgets whoever is away.
A well-passed change fits into four fixed pieces of information, comes from a single person, and gets confirmed by every recipient. That is what avoids wasted trips, and lets the site manager see, at a glance, who already knows and who still does not.

Founder and CTO of Edenio
Jérôme Knops is the founder of Edenio, where he designs and builds custom business applications for construction, supply chain and distribution companies. He runs the scoping meetings, writes the code, and stays the person you talk to once the tool is in production.
See all their articles
Jérôme Knops
