Site supervision only fulfils its purpose when the project owner can learn three things from a single document: the current state of the works, what risks exist, and what has to be decided next. The report is the instrument that turns technical fieldwork into a basis for decisions. When it is vague, generic or merely photographic, it stops being useful.
This text sets out the structure DINAMESTRIA uses in its periodic supervision reports, together with the reasoning behind each chapter.
1. Identification and context
Every report begins by fixing the context: identification of the development and its location, project owner, contractor and coordination, report number and period, date of the site visit and conditions found. It looks bureaucratic, but it is what allows anyone, months later, to reconstruct precisely who knew what and when. Decisive information in any contractual discussion.
2. Progress of the works
This section describes what has actually been executed, by work front and by discipline: structure, masonry, finishes, water and drainage, electrical, HVAC, metalwork, external works.
Two practical requirements:
- Percentages per chapter, not a vague overall figure. Works reported as "70% complete" without breakdown hide stalled fronts.
- Comparison against the approved programme, stating the deviation in days and which fronts sit on the critical path.
3. Technical compliance and quality control
This is the core of the report. It must state what was checked, against which reference, and with what result:
- compliance with the construction design and with approved changes;
- material tests and certificates (concrete, steel, insulation, windows, waterproofing);
- inspection of elements that become concealed after execution — reinforcement before concreting, waterproofing before protection layers, services before ceilings and walls are closed;
- dated and captioned photographic records, tied to the item inspected rather than merely illustrative.
A useful report clearly distinguishes a non-conformity (a departure from the design or the standards, with a deadline for correction) from an observation (a technical recommendation with no breach involved).
4. Register of non-conformities and actions
Each non-conformity needs its own reference, an objective description, probable cause, consequence if left uncorrected, proposed action, responsible party and deadline. And, in the following report, its closure status. Without that follow-up the list of non-conformities keeps growing and never resolves. This is the most common symptom of supervision without practical consequence.
5. Programme, planning and output
Analysis of compliance with the works programme: output for the period, comparison with planned output, causes of delay (weather, approvals, supply, labour, owner-instructed changes) and the foreseeable impact on completion. Where delay is attributable to the contractor, this must be expressly recorded with its reasoning as that is what supports any later application of penalties.
6. Cost, measurement certificates and additional works
The report must reconcile what was built with what is being invoiced: measurement certificates validated in the period, cumulative invoicing against the contract sum, price revisions, and additional or omitted works with technical justification, cost estimate and the owner's decision. Additional works carried out without prior formal approval should be flagged as a risk, not normalised.
7. Health, safety, environment and site facilities
Verification of the health and safety plan, site conditions, collective and personal protective measures, signage, access, construction and demolition waste management and noise. It does not replace the site safety coordinator, but it ensures the project owner has visibility of a risk that is also theirs.
8. Decisions pending with the project owner
The section most valued by decision-makers. A short, dated list of what is awaiting a decision. Finishes selection, approval of changes, authorisation of additional works, responses to requests for information with the impact of each day of waiting. It turns the report into a management tool rather than a record of events.
9. Conclusions and recommendations
An honest summary: overall status, main risks ranked by criticality, and concrete recommendations for the next period. Three to five paragraphs are enough; the people who have to decide rarely read the appendices first.
Frequency and format
As a practical rule:
- a monthly report on ordinary projects, with a short weekly note during critical phases;
- a fortnightly or weekly report where the programme is tight, penalties are material, or several disciplines run in parallel;
- ad-hoc reports whenever an event occurs with an impact on time, cost or safety.
The format should stay stable between periods. Comparability — same structure, same indicators, same numbering of non-conformities — is what allows trends to be read instead of isolated snapshots.
The most frequent mistake
Reports that are extensive in description and silent in conclusion. Fifty pages of photographs are no substitute for one page stating: the works are 12 days behind, attributable to window supply; three non-conformities remain open on roof waterproofing; and a decision on the external paving has been pending since 14 April.
That last page is what protects the investment.
Do you need supervision with reports that support decisions? DINAMESTRIA monitors developments through every phase, with control of quality, programme and cost. Talk to us or request a proposal.