Schedule & Delay Risk
See which projects will finish late, and why — progress against time, late phases and milestones, blocked tasks and hours lost on site — before the date slips.
An early warning from your phase plan. It compares how much of each job is done with how much of the time has gone, adds what is late or blocked on site, and gives every project a risk level with its reasons.
📷 Screenshot spot — a Schedule & Delay Risk portfolio run: the Projects table with Progress %, Time elapsed %, SPI, Committed end, Forecast finish, Slip days and Risk, and the Top reasons list beside it
Save as static/img/screenshots/ai-delay-risk.png and replace this box with 
What it reads
For each active project you can open (up to 25), or the one you choose — projects that are a prospect, closed, cancelled, substantially complete or in DLP are skipped:
- The project's planned start, planned end, revised end and extension of time.
- The phase plan — planned dates, weightage and progress of each phase.
- Milestones and their planned dates.
- Overdue and blocked site tasks, with the reasons given for blocking.
- The last 14 days of DPRs — hours lost and weather.
What you get
- Projects — Project, Progress %, Time elapsed %, SPI, Committed end, Forecast finish, Slip days, Risk.
- Key figures: Projects read, Late, At risk, Watch, Milestones overdue, Phases past planned end — and for one project, Physical progress, Time elapsed, Schedule performance index and Forecast slip.
- Top reasons, Late phases and milestones, and How this is worked out.
How it works out the dates
| Figure | Rule |
|---|---|
| Committed end | The revised end if set; otherwise the planned end plus the extension of time |
| Physical progress | Rolled up from the lowest-level phases by weightage (a simple average where no weightage is set); a completed phase counts 100%, a cancelled one is ignored |
| Time elapsed % | Days since start ÷ planned duration |
| SPI | Progress % ÷ time elapsed %. Below 1 means behind |
| Forecast finish | Start + days elapsed × 100 ÷ progress % — given only once 10% of the time has passed and 5% of the work is done; before that, "too early to extrapolate" |
| Slip days | Forecast finish minus committed end |
Risk levels
| Level | When |
|---|---|
| LATE | Past the committed end and not finished, or forecast to finish 30 days or more late |
| AT_RISK | Forecast 7 days or more late, or any high alert — a phase or milestone 14 days or more overdue |
| WATCH | Any forecast slip, or any medium alert |
| ON_TRACK | None of the above |
Alerts: past the committed end (critical); forecast 30+ days late (high) or 7–29 days (medium); a phase past its planned end, or a milestone overdue (high from 14 days, else medium); a phase started late (medium from 14 days, else low); blocked tasks (medium); 5 or more overdue tasks or any overdue High/Urgent task (medium, else low); 16 or more working hours lost in 14 days (medium, 8 or more low); project on hold (medium — time keeps running against the end date). Bad weather means heavy rain, storm or extreme heat.
Run it
- In the sidebar, open Workspaces › Site and click Schedule & Delay Risk under AI agents.
- Leave Project on All projects for every project you can open, or choose one for a deeper look.
- Click Run agent.
- Start with the LATE and AT_RISK rows, then Top reasons. Each alert links to the project's schedule, site or overview tab.
Run it every week
It can run itself every Monday at 07:00 — off until your Company Admin switches it on in its Schedule & delivery panel. Each Company Admin and Project Manager then gets their own run, covering their own projects, as the latest result on this page. Nothing is emailed.
Safeguards
- It creates nothing. It reports and explains.
- It reads as you. If you cannot read site tasks or DPRs, those checks are left out and How this is worked out says so — they are never guessed.
Zaptiz keeps a plan at project and phase level, not a task-level baseline, so this is not a critical-path analysis. A straight-line forecast also overstates delay early in a job, because real progress follows an S-curve — which is why it waits for 10% of the time and 5% of the work.
Tips
- The forecast is only as good as phase progress. Keep weightage and progress up to date on the Schedule tab.
- Record extensions of time or a revised end date when they are granted, or the project shows late against a date nobody holds you to.
- A project with no planned dates or no phases gets a low alert telling you what to set up.
Related
- Schedule — phases, weightage, progress and milestones.
- Site tasks — clear blocked and overdue tasks.
- DPR — where hours lost and weather come from.
- DPR Summariser — a week of site reports on one page.