Construction reporting

Cadence

One site record. Three reports that read from it, and never disagree about what it says.

Sample project: Northgate Exchange
Reporting period: July 2026
Contains: Daily, weekly, monthly
Status: Illustrative sample

Request the sample packPDF, 16 pages Open the live demoThe reports, in the browser Watch the intro25 seconds

The live demo

Three reports, one record

The demo runs on Northgate Exchange, a fictitious project. Every figure the daily record can answer is a window over it, so those numbers can only be wrong in one place. The rest come from the cost report, the programme and the registers — the section below marks which is which, one section at a time.

Every site day

Daily

The capture layer. The site team enters the day once, from a phone, and the record is closed. Everything above reads it.

Progress planned against actual
Manpower, plant and weather
Constraints and photographs

Open the daily

Monday to Sunday

Weekly

A full site week rolled up, plus what moved in the registers, issued the following Wednesday.

Progress trend and shortfall
Register movement and variance
Decisions owed, two week look ahead

Open the weekly

Month end

Monthly

Four to five weeks rolled up into trend, cost and forecast. The report the board reads.

S curve, actual against plan
Cost plan, cash flow, handover drift
RAG, value engineering, procurement

Open the monthly

Client cut Daily Weekly Monthly

Themes Studio Classic Editorial

Where it starts

How the record gets in

Before any of those three reports exists, somebody stands at the gate at the end of the shift and enters the day. One entry, about five minutes, on a phone. That entry is the record — everything above it is a window over the same rows.

Northgate Exchange Day 168

Report date

Friday 12 June 2026

Progress

Cumulative actual44.00%

Cumulative planned47.00%

Activities today

Core wall reinforcement12 / 16 t

Transfer-slab formwork0 / 180 m²

Blinding, waterproofing395 / 380 m²

Manpower

Direct · indirect148 · 23

Conditions

WeatherOvercast, 27°C

Rain hours1.5

Equipment

Excavators · cranes · pumps3 · 2 · 2

Delays and issues

L3 transfer-slab details still outstanding. Formwork crew stood down at 09:00.

Photographs

Submit the day17:35 · site team

Every field on that screen is a column Cadence reads by name. Nothing is retyped afterwards: the same entry is the daily report the same evening, part of Wednesday's weekly, and part of the month-end pack.

Same eveningDaily

The entry, formatted and issued. Four of its six sections are the record itself.

WednesdayWeekly

The week's records, summed and trended. The charts plot them; nobody rebuilds them.

Month endMonthly

Four to five weeks of the same rows, under the cost and programme picture.

Said plainly: capture runs on the site app that feeds Cadence, not inside Cadence. The screen above is drawn to that app's field set rather than photographed from it, because Cadence reads the daily record — it does not collect it. If you already run a daily return, Cadence reads yours.

What that entry cannot answer

Everything on it is something somebody on site saw. A monthly also carries figures nobody on site holds:

Cost plan progression, cash flow and the variation position
Programme forecast, milestone slip and the critical path
Register movement — RFI, RFA, NCR, permits
Every RAG call, the watchlist and the value engineering register

None of that rolls up from a daily return, here or anywhere else. The next section marks all 39 sections for which do and which do not.

The part most decks leave out

Capture once. Report three ways. For the half that rolls up.

Of the 39 sections across the three reports, 8 are written by the daily record itself. The rest are judgement or belong to another document, and no reporting tool changes that. Here is which is which, section by section, so nothing in the demo or the pack has to be taken on trust.

8 sections Derived

Computed from the daily records in the period. Nobody types them, and they cannot disagree with each other, because they are the same rows.

10 sections Authored

Judgement — the RAG call, the watchlist, the narrative. Written once, in the report that owns it, instead of three times in three documents that drift.

14 sections Imported

Owned by the cost report, the programme or a register. Cadence renders them. Today they are keyed in at report time — this is not a live feed and is not sold as one.

7 sections Mixed

A derived figure sitting beside an imported or authored one — where a reader is most likely to assume the whole section rolled up. Each is split out below.

Weekly — 10 sections
#	Section	Source	Which part
01	The week at a glance	Derived	The week's daily records, summed and trended.
02	Status by workstream	Authored	Every RAG letter and every "what changed" line is a call.
03	Decisions we need	Authored	Including the date each one stops being cheap.
04	Register movement	Imported	RFI, RFA, NCR and permit registers, each owned in its own tracker.
05	Progress and productivity	Mixed	Actual series derived; the planned series imported from the programme.
06	Where the week went	Authored	Aggregates the daily attribution, which is itself a judgement.
07	Site photographs	Derived	The week's daily photographs. Nothing re-collected.
08	Critical path	Imported	From the programme file.
09	Commercial position	Imported	From the cost report and the current valuation.
10	Look ahead, two weeks	Mixed	Activities imported from the programme; the commentary authored.

Monthly — 23 sections
#	Section	Source	Which part
01	Headline KPIs	Mixed	Progress derived; budget, opening date and package award imported; four tiles are calls.
02	Percent-of-completion	Mixed	Progress POC derived; financial and per-package POC from the cost report.
03	Construction snapshot	Mixed	Major works derived from the month's dailies; constraints and risks authored.
04	Site photographs	Derived	The month's daily photographs.
05	RFIs and RFAs	Imported	The RFI/RFA tracker.
06	Permits, safety, quality	Mixed	Safety and manhours derived from the daily; permits from the statutory tracker.
07	RAG matrix	Authored	The most-read tile in the report, and not one character of it rolls up.
08	Watchlist	Authored	What counts as critical is a decision, not a query.
09	High-level schedule	Imported	The programme file, forecast against baseline.
10	Milestone variance	Imported	Two issues of the programme, differenced.
11	Opening date movement	Mixed	Dates imported from successive programme issues; the reason authored.
12	Where design is slipping	Imported	The design tracker.
13	Discipline status	Imported	The design tracker.
14	Design impact scenarios	Authored	What a day of slip costs downstream is modelling, not a record.
15	Cost plan progression	Imported	Successive cost plan iterations, from the cost report.
16	Open design decisions	Imported	The design authority's own running memo.
17	VE register	Authored	Maintained by the CM team; every saving band is an estimate.
18	VE driven by design	Authored	A filter over the same authored register.
19	Cost summary	Imported	Approved, awarded, variations, anticipated final — all from the cost report.
20	Billing, contractors	Imported	Certified payment applications.
21	Recent payments	Imported	Certificates issued this period.
22	Procurement and consultants	Imported	The procurement tracker and the professional-fees pool.
23	Next actions	Authored	Owner, action, date.

Daily — 6 sections
#	Section	Source	Which part
01	The day at a glance	Derived	The day's entry, totalled.
02	Work completed today	Captured	Activity, zone, planned, actual. This is the entry.
03	Conditions and plant	Captured	Weather, rain hours, equipment on site.
04	Constraints raised today	Captured	The constraint and its owner.
05	Why the day landed there	Authored	The site manager's read of the day. Dropped from the client cut.
06	Site photographs	Captured	Dated on upload, not at week end.

So the claim, stated exactly: capture the site record once, and the daily, the weekly and the monthly are three windows over it. Everything the record cannot answer is written down once, in one place, instead of three times in three documents that then disagree. That is a smaller promise than "it writes itself", and it is one we can hold to on your project.

Request the sample pack, PDF