Crew double-booking in construction — how to catch it before Tuesday morning

Crew double-booking is one of those mistakes that sounds avoidable until you've made it three times. It's not a competence problem. It's a structural one: when you assign crews across multiple projects, weeks, and a rolling schedule, the human eye can't see the conflict the moment it's created. By the time you'd catch it manually, you've already moved on to the next thing.

The classic patterns

Why spreadsheets won't fix it

You can write conditional formatting that flags the same crew name appearing on the same date. It works for the simple case. It breaks the moment you have:

• Multiple sheets per region
• Crew names entered with slight typos ("Crew A" vs "CrewA" vs "A")
• AM/PM splits
• Pour-type-specific subteams within a crew
• Anyone editing the file simultaneously

The formula either gives you false positives (you stop trusting it) or false negatives (you stop noticing it). Either way, you're back to discovering double-bookings at 6:45 AM Tuesday.

What "good" detection looks like

The detection that actually works has four properties:

1. Real-time — fires the moment the second assignment is created, not when someone runs a check later
2. Visible at both pours — a red warning badge on every pour pill where the conflict exists, not just one
3. Click-to-jump — clicking the badge takes you to the other pour so you can resolve it without searching
4. Survives export — the conflict list ships on the XLSX and PDF schedules so the field sees it too, not just the office

Detection that doesn't have all four still leaves the failure mode in place: the conflict exists in the data but nobody sees it until it's too late.

The cost of one double-booking

A typical concrete sub:

• Crew arrives at the wrong job → 1 hour lost to figuring out where they're supposed to be
• Ready-mix truck waiting at the right job → $200/hour waiting time
• Pump operator standing → $150/hour wasted
• GC's super now noting that you're unreliable → not directly priced but priced in the next bid

One incident is >$500 in hard costs alone. Three a year is $1,500. The reputational cost is bigger but harder to measure.

How Planning Ops handles it

Place & Finish Hub indexes pours by crew and date in real time. It flags the same P&F crew booked twice in a day — and, when the optional Screeds and Pumps & Operators add-ons are on, the same laser screed #, screed operator, pump unit, or pump operator double-booked too. Subcontractors are surfaced as a soft FYI, and canceled pours are excluded so they never trip a false alarm. The moment you create a conflicting assignment:

• Both pours get a red ⚠ badge
• Clicking the badge opens a popover with the conflicting pour ID, project, and time
• A rose banner above the grid lists every active conflict
• An in-editor warning fires as you assign, before you save
• The conflict list ships on every Schedule XLSX and PDF export — your field crew sees it too

The detection runs whether the conflict is created in the daily Schedule or the 365-day Lookahead, and survives drag-drop, mass-edit, and import operations. The getting-started guide covers turning the add-ons on under Admin → Schedule Features.