Avoiding conflicts from the outset

Gantway calculates conflicts automatically on every planning change — moving, assigning, releasing, everything triggers the check. Resolved conflicts are marked as done on their own; no one has to tick them off. The check runs in the background; right after a change the list in the sidebar under Conflicts can lag for a moment — refreshing once shows the fresh state.

The list makes the least work when little is on it. Five levers:

The five levers

1. Maintain capacities honestly. A workstation that realistically handles two orders in parallel should not be set up with capacity 4 — otherwise Gantway warns too late or never. You maintain this at the bottom of the sidebar under Settings → "Master Data" → tab "Slots".
2. Watch the availability traffic light when scheduling. Whoever picks green dates does not produce the double booking in the first place.
3. Record absences before planning. An entered vacation immediately redirects the assignment — one added afterward creates conflicts in finished plans retroactively.
4. Set dependencies without gaps. A successor that starts right at the predecessor's end is not a conflict — only a start before it is. Missing dependencies, however, no one checks: where no dependency line is drawn, nothing can be violated either.
5. Check materials early against the to-buy list. The material shortage arises across orders — another order too can eat away your own stock.