The short answer: Construction site documentation is the set of records a project keeps about what was planned, instructed, delivered, built, tested and approved on site. The core documents are the daily progress report, labour and material records, quality and test records, drawing and instruction registers, safety records, measurement and billing records, and the handover file.
Eighteen months after a slab was cast, a buyer reports cracks. The developer asks three questions: which concrete was used, were cubes tested, and did the results pass? The site engineer who managed the pour has left. The cube register is a notebook somewhere in the site office. The test report is in someone's email.
Good site documentation is what lets a project answer questions like these in minutes instead of weeks. It is also what keeps today's work under control: knowing what was delivered, what was built, and what still needs approval. This guide lists every report a typical building project needs, who owns it, how often it is updated, and how to keep it useful rather than just complete.
What is construction site documentation?
Site documentation is the written and photographic record of a construction project as it happens. It includes routine reports (daily, weekly, monthly), registers that track items over time (drawings, RFIs, materials, tests), event records (instructions, incidents, delays) and the final records handed to the owner.
It serves five purposes:
- Control: showing whether work, cost and quality are on track while there is still time to act.
- Quality assurance: proving that materials and workmanship were checked and met the specification.
- Payment: supporting measurements, contractor bills and supplier invoices.
- Protection: providing contemporaneous evidence when delays, variations or defects are disputed.
- Handover and compliance: giving the owner, authorities and residents what they need to operate and maintain the building.
The construction documentation map: every report, owner and frequency
Use this as a master list. Not every project needs every record, but every project should decide deliberately which ones it keeps.
| Document | Frequency | Usual owner |
|---|---|---|
| Daily | ||
| Daily progress report (DPR) | Daily | Site engineer |
| Daily labour report (DLR) / attendance | Daily | Site engineer / timekeeper |
| Site diary | Daily | Site in-charge |
| Goods receipt note (GRN) and material issue register | Per delivery / issue | Store keeper |
| Equipment log | Daily | Site engineer / plant operator |
| Toolbox talk and visitor records | Daily | Safety officer / security |
| Per activity | ||
| Inspection request and checklist (per ITP) | Before each hold point | Site engineer, QA/QC |
| Pre-pour checklist / pour card | Every pour | Site engineer |
| Concrete pour record and cube register | Every pour | QA/QC engineer |
| Measurement book (MB) entries | As work is measured | Site engineer / QS |
| Non-conformance report (NCR) | When a defect is found | QA/QC engineer |
| Event-based | ||
| Site instruction register | Each instruction | PM / site engineer |
| RFI log | Each query | Site engineer |
| Drawing register and transmittals | Each issue / revision | Document controller |
| Delay / hindrance register | Each delay | Site engineer |
| Minutes of meeting | Each meeting | Meeting chair / PM |
| Incident and near-miss reports | Each event | Safety officer |
| Weekly / monthly | ||
| Weekly progress report and look-ahead | Weekly | PM / planning |
| Monthly progress report | Monthly | PM |
| Stock statement and material reconciliation | Monthly | Store / QS |
| Labour reconciliation | Monthly / per bill | Site engineer / accounts |
| Running account (RA) bill with measurements | Per billing cycle | QS / contractor |
| Handover | ||
| As-built drawings | At completion | Contractor / consultant |
| Snag list and close-out record | Before handover | PM / QA |
| Test certificates and commissioning records | At completion | QA / MEP contractor |
| Operation and maintenance manuals, warranties | At completion | Contractor / suppliers |
| Statutory completion and occupancy documents | At completion | Developer / liaison |
Daily records: the backbone of site documentation
Daily records are where most other documents get their facts. If they are late or vague, the weekly report, the bill check and the delay claim all inherit the problem.
- Daily progress report: work done against plan, labour, equipment, materials, delays, safety and tomorrow's plan. Our DPR guide includes a format and a filled example.
- Daily labour report: headcount by trade and contractor. It is the basis for checking labour bills at month end.
- Site diary: a running narrative of events, verbal instructions, visitors, weather and anything unusual. It is often the record that settles "who said what".
- GRN and issue register: what arrived against which purchase order, in what condition, and where it went. See construction material management for the full indent-to-consumption chain.
Quality records: inspections, pours and tests
Quality records prove that hidden work was checked before it was covered. Once a slab is cast, the reinforcement inside it can only be verified on paper.
An inspection and test plan (ITP) lists each activity's hold points, what is checked, the acceptance criteria and who signs off. Each inspection then produces a signed checklist, with photos, before work moves on.
For concrete, Indian practice follows IS 456:2000 for sampling. The minimum frequency is set by the quantity of concrete in the pour, with each sample made up of three cubes:
| Quantity of concrete in the work | Number of samples |
|---|---|
| 1–5 m³ | 1 |
| 6–15 m³ | 2 |
| 16–30 m³ | 3 |
| 31–50 m³ | 4 |
| 51 m³ and above | 4, plus 1 for each additional 50 m³ or part |
Check the current code and your project specification, which may require more. The cube register should link each set of cubes to the pour (location, grade, date, quantity, supplier ticket) and record the 7-day and 28-day results. When a result fails, the non-conformance report records what was found, what was decided and who approved the decision.
Measurement and billing records
Every rupee, dirham or dollar paid to a contractor should trace back to a measurement. The measurement book records the quantity of work done, where it was measured and who measured and checked it. Running account bills are built from those measurements, and labour and material reconciliations confirm that claimed quantities match what the site actually recorded. When measurement lags the work, bills are paid on estimates, and over-payments are hard to recover later.
Drawings, instructions and changes
Many disputes come down to a single question: what was the contractor told to build, and when? Three registers answer it:
- Drawing register: every drawing, its current revision, issue date and who received it. Superseded prints should be withdrawn or clearly marked. See the most dangerous drawing on a construction site.
- Site instruction register: every written instruction, who issued it, and whether it affects cost or time.
- RFI log: every design query, who must answer, and how long the answer took.
If a consultant gives an instruction verbally on site, record it the same day and ask them to confirm it in writing.
Safety records
Safety documentation typically includes the site safety plan, induction records for every worker, daily toolbox talk records, permits to work for high-risk tasks (work at height, hot work, confined spaces, excavation), equipment and scaffold inspection tags, and incident and near-miss reports with corrective actions. Requirements vary by country and state, so align them with local regulations and your contract.
Documentation required by regulators
Beyond good practice, some records are required by law. Two examples relevant to developers in India:
- RERA: under Section 11 of the Real Estate (Regulation and Development) Act, 2016, promoters must keep their project page on the state RERA website updated quarterly, including the status of the project and approvals taken and pending. Accurate site progress records make those updates straightforward.
- Labour codes: since 21 November 2025, India's four labour codes have replaced 29 central labour laws, including the Building and Other Construction Workers Act, 1996, which is now covered by the Occupational Safety, Health and Working Conditions Code and the Code on Social Security (AZB & Partners summary). Registers and returns must follow the codes and the applicable state rules.
Projects in the UAE, Singapore and Sri Lanka have their own authority requirements; our market guide covers the main regulators. Take local advice for specific obligations.
7 rules that make site documents useful
- Record it when it happens. Records written at the end of the day, or the end of the week, are reconstructions.
- Date, time, location, person. Every entry needs all four. "L7 slab, Grid A–F, 12 Nov, 4:10 pm, R. Kumar."
- Use reference numbers. GRN, PO, RFI, instruction and drawing numbers let records link to each other.
- Add photos. A dated photo of reinforcement before a pour is worth pages of description.
- Keep one source of truth. Each record lives in one agreed place, not in three spreadsheets and a phone.
- Get sign-off. Inspections, measurements and instructions should show who approved them.
- Decide retention up front. Agree how long each record is kept, considering the contract, defect liability period, tax and limitation rules, and where it is archived.
Common documentation mistakes
- Filling registers from memory days later.
- Copying yesterday's report forward and editing a few numbers.
- Records that describe activity ("work in progress") instead of quantity and location.
- Cube results that can't be traced to the pour they came from.
- Verbal instructions that never reach the instruction register.
- Paper records lost when a site engineer leaves or the site office moves.
- So many forms that the important ones get skipped.
Paper vs digital site documentation
| Paper and spreadsheets | Digital records in one app | |
|---|---|---|
| Speed of entry | Slow; often written up later | Captured on the phone as work happens |
| Photos | Separate, hard to link | Attached to the record, time-stamped |
| Finding a record | Search folders and inboxes | Search by location, date or reference |
| Reports | Rebuilt manually each day or month | Generated from logged records |
| Risk of loss | High when people or offices change | Low, with backups and access control |
| Adoption risk | Familiar to everyone | Fails if the site team won't use it |
Site documentation checklist
- Is there a master list of records, with an owner and frequency for each?
- Is the DPR submitted at a fixed time every day, with quantities and causes of delay?
- Does every delivery have a GRN linked to a purchase order?
- Can every cube result be traced to a pour, location and supplier ticket?
- Is every hold point inspected and signed off before work is covered?
- Are drawings, RFIs and site instructions numbered and logged?
- Can the PM find any record from last month in under five minutes?
- Is there a handover file being built during the project, not after it?
Where software fits
Most site documents are built from the same few facts: who was on site, what arrived, what was built, what went wrong. The work is in collecting those facts and typing them into many different formats.
Brikito, construction management software with Brik AI, captures those facts once, where the team already works. Selfie check-ins give attendance, chat messages become indents and progress updates, and drawings are version-controlled with the latest revision tagged on site. From that record, BrikDocs generates the DPR, DLR, GRN, stock statement, BOQ, BBS and other reports in a tap, ready for the engineer to review rather than rebuild.
Frequently asked questions
What documents are required on a construction site?
Most building sites keep a daily progress report, labour attendance, a site diary, material receipt and issue records, a drawing register, site instruction and RFI logs, inspection checklists, concrete pour and cube test records, safety records, minutes of meetings, measurement records and, at the end, a handover file with as-built drawings and certificates.
What is the difference between a site diary and a daily progress report?
A daily progress report is a structured summary of quantities and status for management. A site diary is a narrative, time-stamped log of events, instructions, visitors and observations. The DPR shows progress; the diary records what happened and who said what.
How many cubes should be taken for concrete testing?
Under IS 456:2000, the minimum is one sample for 1–5 m³, two for 6–15 m³, three for 16–30 m³, four for 31–50 m³, and four plus one more for each additional 50 m³ or part above that. Each sample is usually three cubes. Project specifications may require more.
Who is responsible for site documentation?
The site engineer usually owns daily records and inspections, the store keeper owns material records, the QA/QC engineer owns test records, the safety officer owns safety records and the project manager is accountable for the documentation system as a whole.
How long should construction records be kept?
It depends on the contract, the defect liability period, tax and statutory requirements and limitation periods for claims. Many organisations keep core project records for several years after completion. Agree a written retention policy at the start of the project and take local legal advice.
Why is site documentation important in construction disputes?
Records made at the time of the work, such as daily reports, site diaries, instructions and photos, are often the best evidence of what was instructed, what was built and what caused a delay. Without them, disputes depend on memory and are harder to resolve.
Documents are only as good as the moment they are made
A complete set of forms filled in at month end protects nobody. The value of site documentation comes from recording facts when they happen, linking records to each other, and making them easy to find. Start with the daily records and the quality records; almost everything else is built on them.