DPR Summariser
A week of daily progress reports on one page — work done, missing reports, weather and hours lost, crew by trade, idle plant and the issues that keep coming back.
Seven DPRs take half an hour to read. This agent reads them for you, counts what can be counted, and quotes what the site wrote — useful for the weekly review and the client's progress meeting.
📷 Screenshot spot — a DPR Summariser result for one project: the figures strip (Reports filed / expected, Reporting coverage, Missing reports, Working hours lost), the Day by day table with one "No report" row, and the Crew by trade table
Save as static/img/screenshots/ai-dpr-summariser.png and replace this box with 
What it reads
- The project's DPRs for the period you choose (1 to 31 days) — labour lines by trade, plant lines, weather, hours lost, status, and the text written for work executed, work planned tomorrow, issues faced and instructions received.
- The project's overdue site tasks.
- The project's actual start date, so days before the job started do not count as missing.
DPRs carry no rates or amounts, so every role that can run it sees the same report.
What you get
- A headline such as "7 day(s): 5 of 6 expected daily reports filed (1 missing); 12 working hours lost; average crew 48."
- Key figures: Reports filed / expected, Reporting coverage, Missing reports, Working hours lost, Bad-weather days, Awaiting approval (overdue), Average crew a day, Peak crew, Crew, second half vs first, Latest claimed progress.
- Day by day — Date, Weather, Headcount, Man-hours, Hours lost, Status ("No report" where one is missing).
- Crew by trade — Trade, Man-days, Man-hours, Average a day.
- Plant — Machine, Used h, Idle h, Idle %.
- Work done & recurring issues, summarised from the site's own words.
How it counts
| Figure | Rule |
|---|---|
| Expected days | Every date in the period except Sundays, days before the project started, and today if today's report is not in yet (a DPR is filed at the end of the day). A report filed on a Sunday still counts. |
| Coverage | Expected days with a DPR ÷ expected days |
| Headcount, man-hours | Sum of labour lines; man-hours = headcount × hours (8 when not given) |
| Average crew | Over days that have a report — a missing day is unknown, not zero |
| Crew trend | Average of the first half of the period against the second half |
| Idle % | Idle ÷ (used + idle) hours, as written in the DPRs |
| Bad weather | Light rain, heavy rain, storm or extreme heat |
Alerts
| Alert | Severity |
|---|---|
| 2 or 3 reports missing | Medium (4 or more: high) |
| Reports awaiting approval for more than 2 days | Medium |
| Reports returned and not re-submitted | Low |
| 8 or more working hours lost | Medium (16 or more: high) |
| A machine idle more than 30% of its logged hours | Low (50% or more: medium) |
| Crew down 25% or more in the second half | Medium |
| Overdue site tasks | Low (5 or more: medium) |
Run it
- In the sidebar, open Workspaces › Site and click DPR Summariser under AI agents.
- Choose the Project.
- Set Days to cover (7 by default) and, to look back from an earlier date, Up to (default today).
- Click Run agent.
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, Project Manager and Site Engineer then gets a run covering every active project they can read (up to 10), as the latest result on this page. The admin can also change the thresholds there: Days, Include sundays, Hours lost threshold, Idle pct threshold, Crew drop pct, Awaiting days.
Safeguards
- It creates nothing. A DPR is the site engineer's to file and the PM's to approve.
- A sentence that quotes a figure not in the counted facts is dropped.
- If the AI is unavailable, you still get every figure, with the work and issues quoted as written on site.
The summary is only as good as the DPRs. Ask sites to fill work executed and issues faced in a line or two every day — the recurring-issues list comes from those words.
Tips
- Run it before the weekly site meeting and work down the missing and awaiting-approval alerts first.
- A falling crew in the second half is often the first sign of a subcontractor pulling labour.
- An idle machine here is worth checking against its hire terms.
Related
- DPR — file, return and approve the daily reports.
- Labour — the muster roll behind the crew numbers.
- Equipment — plant logs and utilisation.
- Labour & Plant Productivity — output against your norms.