A scheduling conflict is a plan that cannot happen: one crew booked at two jobs, a technician without the right skill, or a start time that lands before materials arrive. Before you move a single appointment, decide whether the conflict is real or whether the board is just stale.
Is it a real conflict or a stale calendar?
A real conflict means two jobs need the same crew, the same skill, or the same equipment at the same hour. A stale calendar only looks like one: yesterday's job was never closed out, so it still holds a slot nobody is standing in. The board is wrong, not the plan.
| What the board shows | Real conflict | Stale calendar |
|---|---|---|
| Two jobs, one crew, 8 a.m. | Both are confirmed and unfinished. The crew can only be in one place. | The first job finished yesterday and was never marked complete. |
| A technician booked all day | The work runs to 4 p.m., including the drive back. | Cut short at noon; nobody updated the record. |
| A job waiting on materials | Supplier confirmed delivery Thursday. Nothing starts before then. | Delivery landed yesterday. The note never got added. |
Closing out a job means marking it finished, noting anything left over, and releasing the crew. A real conflict costs a decision: one job moves, one customer gets a call. A stale calendar costs one message to the crew lead, so check before you drag appointments.
Two jobs need the same crew at 8 a.m. What do you do?
Confirm the conflict is real, check who is actually available, decide which job moves, tell the affected customer before they call you, then put the change on the schedule everyone reads. In that order, most 8 a.m. conflicts are settled in fifteen minutes.
Imagine a fictional eight-person plumbing company. Crew A is booked at two jobs at 8 a.m.: a water heater swap across town and a rough-in on a small addition. Crew B looks free, but only Crew A carries the gas ticket the swap needs.
The swap leaves a house with no hot water and needs that ticket, so it holds 8 a.m. with Crew A. The rough-in has no inspection booked and nobody home, so it moves to 11 a.m. and Crew B starts the demo.
- Spot it the night before
Check tomorrow's first job for every crew before you close the laptop.
- Check real availability
Ask the crew leads what actually finished and who is working tomorrow.
- Decide by what cannot flex
Tickets, inspections, no heat or hot water. The job with flex moves.
- Tell the customer before they call
Send a new arrival window at 7 a.m., not an apology at 8:20.
- Confirm it reaches the shared board
Post the new times, then get one acknowledgement from each crew lead.
Why isn't an open calendar slot the same as capacity?
An open slot only says nobody has typed anything into that box yet. Capacity is the work a crew can actually finish there, and it needs four things to line up: people who are working, the skills and tickets the job requires, travel time, and access to the site.
Those four also decide how much work a week can hold, which is capacity planning. The end-of-day check-ins that catch tomorrow's conflict fill out the daily log too, and field service reporting covers what belongs in it.
Barry is not a dispatch board and not a route optimizer. It surfaces crew check-ins and schedule updates in the chat the crew already uses, so the person making the 7 a.m. call has current facts. Keep Jobber, or whatever you run the schedule in, and add Barry on top.
There are three practical ways to do this: use a spreadsheet, ask your accountant or bookkeeper, or connect your tools so Barry AI can check calendars and crew updates, find conflicts, and propose a plan for your approval.
Barry, check tomorrow's connected schedule and crew updates for double bookings, missing skills, travel gaps, or delayed jobs. Ask about unclear details and propose a revised plan for my approval.
