← All insights
Scheduling

The cost of scrambling: reactive scheduling in the equipment-centric specialty trades

One urgent job squeezed in at 6:45 a.m. can unravel the rest of the day. What the scramble costs, in the industry's own figures, and what changes when the board runs on one record.

A dispatch board at 6:45 am with an urgent job squeezed in and the rest of the day's jobs turned late or cancelled.

The 6:45 a.m. emergency, and what it does to the rest of the day

It’s 6:45 a.m.

An urgent job request comes in. A high-priority customer needs a crew now. Operations can’t say no: this is a major account.

  • Dispatch scrambles to rework the schedule.
  • Planners hunt down available operators and equipment.
  • The operations manager reroutes crews, which leaves other jobs short-handed.
  • Sales reassures the customer, "We’ve got this."

But do they?

Because as soon as that one emergency job gets squeezed in, everything else starts to unravel.

A scheduled crew loses its machine, so another job slips.
A certified operator is rerouted, so another job falls behind.
A second crew loses its forklift to the emergency, so its job waits.
Dispatch is drowning in calls, trying to fix the ripple effect.
The yard is reloading trucks to chase the changes.
A lower-priority customer, tired of the delays, cancels the contract.

And by noon, no one knows what’s happening anymore.

That is the fog of operations: decisions made without clear, current, connected operational truth. Nobody on that morning did anything wrong. Dispatch, the yard and the field were each working from a different picture, at a different age, so every fix created the next problem. Two of the fog's eight faces are on that board: dispatch conflicts and idle crews.

What the industry's own figures say it costs

A morning like that costs time first, then money, then customers.

FMI's study Construction Labor Productivity: The $20 Billion Opportunity (2023) surveyed more than 250 senior leaders of self-performing contractors. Four of its findings describe the morning above.

  • Contractors lost approximately $30 billion to $40 billion to labor inefficiencies in 2022.
  • Contractors believe 11 to 15 percent of field labor costs are wasted or unproductive, and 60 percent say the figure is 11 percent or more.
  • 79 percent say they could improve productivity by 6 percent or more with better management alone, and FMI puts a 6 to 10 percent gain at 2 to 3 percent to the bottom line, in many cases a 50 to 100 percent improvement in profitability.
  • 45 percent saw labor productivity decline; 23 percent saw it improve.

These figures describe construction's self-performing contractors as a class. In the trades where a machine bills by the hour and a certified crew is paid regardless, each line is more expensive per incident.

The emergency job is the trigger. The loss comes from planning and visibility, and the research says the same: planning, communication and collaboration are three of the top four internal factors affecting labor productivity (FMI, 2023).

Why one emergency job breaks the whole board

The scheduling problem is a visibility problem. In these trades every job is a configuration of equipment, support gear, crew, certifications, permits and site conditions, and a change to any one of them re-decides the rest. When the board cannot see all of those variables together, the fix for one job quietly breaks three others.

Uncertain equipment readiness. From the office nobody can say whether the machine is where the record says, inspected, and allowed to work, so dispatch guesses at availability and buys insurance with rentals and buffers.
Fragmented systems. The board is a whiteboard, the timecards are in another app and the quote is in a document, so no one view is trusted enough to run the day and every change is reworked by hand in all of them.
Weak handoffs. The change is made in the office and reaches the crew by call, text and memory, often after they have left the yard.
Delayed field inputs and missing documentation. The office learns what happened on Friday on Monday, and the stamped plan lives on a server or in a truck, so the conflict shows at the gate instead of at planning.

What changes when the board runs on one record

Ribbiot's founder spent twelve years inside a crane company, and the platform was built for the trades where the job is a configuration. Ribbiot is the operational layer that runs on top of a company's accounting system: one record that connects people, process and equipment from the first quote to the final invoice. The board on that record sees the same equipment, people and documents the quote and the field ticket do, which is what makes the morning above play out differently.

When one resource moves, the board stays true. Tasks hold the people and the equipment inside them, so the machine, its operator, and the rest of the crew can each be on a job for different hours, and a conflict shows at planning instead of at the gate.
Before a resource is pulled, the board shows what is actually available: which machines are free and allowed to work, with their inspections current, and which people are free, with the documents the job requires attached before the first resource moves.
A change made on the board in the office reaches the field on the same mobile work order before the truck leaves, so the last-minute change does not travel by group text.
The field sees the same work order on mobile that dispatch built in the office, with what is required, when, and with which resources, which removes the separate paperwork and the group text.
The field's truth comes back the same day. Forms, inspections and timecards are submitted from the job site against the work order, so the office knows what happened on Friday on Friday, while the crew is still on site and the fix still exists.

The emergency job still comes in at 6:45. The difference is that the board shows what it displaces before anyone commits, the change reaches the crew before the truck leaves, and the day is rebuilt on the record instead of in the dispatcher's head. Command is the module that runs the board, and it is live.

Readiness before the job starts, visibility while it runs, clarity when it closes

The companies that stopped scrambling have three things in common.

  • Readiness before work starts: equipment verified ready, the right crews available with the certifications the job requires attached to the job, and a schedule that reflects what the business can actually execute before the first resource moves.
  • Visibility while the work is underway: the field captures from the job site against the work order the same day, so the office sees what happened while it can still act on it.
  • Financial clarity at closeout: invoices prepared in days instead of weeks, payroll reconciled against verified hours, and margin visible per job while the decisions that set it are still in reach.

Readiness is the outcome that turns a reactive operation into one that can plan.

Where does the scramble start in your operation?

Walk one job: bring one job to a 60-minute discovery call, and we will trace where the day came apart and what it cost.

Remove the Fog of Operations

Bring one job.Get a clearer operating picture, from readiness to revenue.

Walk one job