Anyone being scheduled for a site needs to know three things. Where to go in the morning, who they are working with, and what materials to bring. In many companies these three pieces of information sit in three different places. The address is in the weekly list. The team composition was discussed by WhatsApp the night before. The material comes from a short note from the foreman, often verbally.

This is not poorly organised. It has grown that way. And it works as long as no one calls in sick, no team is reshuffled at short notice, and everyone reads their email. The moment one of these conditions breaks, the phone starts ringing. Several times.

In many companies the scheduling system is the official one. Alongside it runs a second, unofficial system: emails, calls, WhatsApp groups, whiteboards. Both run in parallel. When the official schedule changes, the unofficial system has to be updated by hand.

Why this creates hidden friction

The friction shows up in hours, not minutes. A dispatcher in a 30-person company easily spends seven to ten hours a week passing information between systems. The foreman asks the office, the office asks back, the employee calls because the email never arrived. Each interaction is small. Stacked together they amount to a part-time half-day.

Then come the downstream costs. People who are scheduled wrong drive to the wrong site once. People who do not know the team has changed start the day with a misunderstanding. People who do not know what materials are needed are back at the warehouse two hours later.

These problems are not solved by better Excel. They are communication problems caused by a scheduling system that does not cover communication.

A case from an electrical contractor in the Basel region

The current issue of eTrends magazine (2/26) describes the move of an electrical company with around 50 employees to a digital scheduling tool. The original motivation was practical. Excel became error-prone as soon as multiple people edited it.

The interesting part is what was named afterwards as the biggest effect. It was not the cleaner weekly view. It was not the mobile app either. It was the fact that the tool established itself as a communication channel. What used to be settled by email or phone, who is on which site, who is paired up with whom, now sits directly in the schedule.

The general manager describes the result this way: “We tried it, and everyone says: we can’t go back to the Excel list.” The junior project manager adds: “The biggest advantage over Excel is that everyone has access at any time and changes are visible immediately.”

Neither statement is about features. Both are about visibility, currency and shared information. Those are communication attributes, not planning attributes.

What actually changes

Treating the schedule as the central source of information removes a series of small daily questions. Three examples from a typical day.

The phone call “am I in Zurich today or is it Winterthur?” disappears. The information sits in the employee’s app with address and meeting point. Anyone who checks the schedule the night before knows where to go in the morning.

The email from the foreman “Person X is out today, Y is filling in” disappears. The change is made in the schedule, and everyone sees it immediately. No one has to write a separate notice.

The question “who am I on site with today?” disappears. The team is shown in the same view as the assignment. Anyone who wants to know who they are riding with simply checks the app.

None of these are dramatic. Together they add up to several hours a week that no longer get lost to back and forth.

Three conditions for this to work

For a schedule to take on this role, it has to meet three conditions.

First, it must be accessible to everyone, not just the office. If the person on site has no access, the email survives. A mobile view is therefore not a nice-to-have but a precondition.

Second, it must be current. A schedule that is printed once a week cannot fill this role. Changes have to be visible to everyone immediately.

Third, it must show enough context that follow-up questions become unnecessary. Just “employee X on site Y” is not enough. Who is paired up with whom, what materials are needed, what is special about the job, all of that should be attachable to the assignment itself.

Anyone meeting these three conditions is not just building a scheduling system. They are building a communication system that handles scheduling along the way. The simplest test is one week. For one week, every piece of information related to an assignment is communicated only in the schedule. No emails, no WhatsApp messages, no side lists. Anyone who still misses the old system afterwards has found a gap in the new tool. Anyone who does not miss it has the answer.