Track delays in Scheduling

Require a reason every time a task slips, so you know what's driving delays and can report on them. When delay tracking is on and someone pushes a task to a later date, BuildPass prompts them to tag a reason before the change is saved - no more dates moving silently.

How delay tracking works

When a task is moved to a later date, a Reason for delay required prompt appears before the change can be saved:

• Pick a delay reason from your own tags - Material Delay, Weather, Sub No Show, QA Check Failed, or whatever suits your team
• See which downstream tasks the slip impacts before you commit
• Add an optional note for extra context
• Save the new date, or cancel to leave the task where it was

If no reason is selected, the task reverts to its original dates, so nothing slips without an explanation. Every confirmed change is captured as an audit record of what moved, why, and who made it - giving you structured delay data you can report on, like how many slips a build had and what caused them.

Setting it up

Delay tracking is configured in two places:

• Delay reason tags (admin): Set up your list of reasons in Scheduling global settings. They pull across every project so reasons stay consistent.
• Per schedule: Turn on Reason required to change date under Delay Tracking in a schedule's settings. It's per project and per schedule, so you can switch it on once a site manager takes over the running schedule rather than during planning. Turning it on also enables Critical path view, so critical tasks are highlighted in red.

To get started, set up your delay reasons in Scheduling global settings first, then open any schedule, go to Settings > Delay Tracking, and switch on Reason required to change date.