Conflicts
Double bookings and missed deadlines: what the engine checks, what it will never do for you, and why a conflict can come from a job you cannot see.
The engine finds problems; people fix them. It will never quietly reshuffle work to make a conflict disappear.
The two kinds
- Double booking. Someone's assigned hours exceed the shop day, for example 12 hours of work against a 10-hour day. Fix by reassigning a task or spreading the dates.
- Deadline. The computed finish runs past a work-stream or project deadline, counted in working days. Fix by adding people, trimming scope, or moving the deadline honestly.
The count is per project, the check is shop-wide
The number on the planner counts conflicts touching this project. The engine itself looks at every worker across the whole shop, which is why a double booking can appear here and be caused by a job you have no access to.
The other job is what has to move, and the person to talk to is whoever owns it.
The shop Schedule page is the shop-wide board of deployed work. Resolve on a planner conflict opens that board.
Deployed work comes first
Conflicts on deployed work sort to the top for a reason: two deployed promises that cannot both be kept means someone on the floor finds out the hard way.
Clear those before anything on a stream still in planning.
Notifications
You are notified once, when a conflict is new on deployed work. Re-runs that find nothing new stay silent, and everything currently known is always visible in the panel.
Common questions
Why did nothing move after I fixed a conflict?
The engine never moves work, it re-checks. If the conflict is gone, the row clears on the next pass within seconds. Dates only change when a person changes them.
Why didn't I get notified about a conflict I can see?
Notifications fire once, when a conflict is new on deployed work. Everything currently known is always visible in the panel.