Open demo
Cases / Planning & controls
Planning & controls

Compile the weekly progress report

Mark up where the programme actually is, gather the week of diary entries and photos that prove it, and issue one honest report the client can read in two minutes.

3 steps10 minGeneral contractorProject / construction managerDeveloper / client

How it works, step by step

3 steps across the platform - what you do at each one, and why it matters.

1

Update progress on the programme

Schedule

Walk the programme and set the real percent complete on each active task, mark what started and finished this week, and let it show the slippage against the baseline rather than hiding it.

Why: A report built on wishful percentages fools nobody for long and destroys your credibility when the truth lands. Honest actuals now are what make the finish date you quote believable.

InMaster programmeProgress this weekOutUpdated percent completeSlippage vs baseline
2

Pull the week of evidence

Daily Diary

Gather the daily diary entries, labour and plant counts, weather and the site photos from the week, so the progress you are claiming is backed by a dated record of what actually happened on the ground.

Why: A number without evidence is just an opinion the client can dispute. The diary and photos are also the contemporaneous record that carries the weight if a delay claim is argued months later.

InDaily diary entriesSite photosOutDated evidence packLabour and plant counts
3

Publish the report

Reports

Pull the progress, the key photos and the look-ahead into one report, call out the risks and the help you need from the client, and issue it on the same day every week.

Why: A report that always lands on the same day, reads straight and flags problems early is what builds the trust that gets decisions made fast. A late, spun report does the opposite.

InUpdated progressEvidence packLook-aheadOutWeekly progress reportClient actions and risks

More in Planning & controls