Construction Daily Log: What to Include & How to Write It
A construction daily log takes 20 minutes to write and 20 hours to reconstruct. CIOB identifies site records as the primary evidence base in adjudication. Here's exactly what to include.
A construction daily log is the most underrated document in construction. It takes 20 minutes to write properly. It takes 20 hours to reconstruct from memory when a dispute lands on your desk six months later.
Most site managers fill it in poorly — or not at all — because nobody explained why it matters until they needed it and didn't have it.
This guide covers exactly what goes into a daily log, how to write one that holds up legally, and why digital logs are replacing paper on every serious project.
- CIOB guidance consistently emphasises that contemporaneous site records — daily logs, instruction registers, and correspondence — are the primary evidence base in construction adjudication and arbitration (CIOB)
- A construction daily report written the same day is dramatically more credible in disputes than one reconstructed from memory even a week later
- Every issue entry must include three elements: cause, quantified impact (hours or days lost), and action taken with a timestamp
- Digital logs that site managers build incrementally through the day are 80% complete by end of shift — reducing the end-of-day burden to under 3 minutes
What Is a Construction Daily Log and Why Does It Matter?
A construction daily log (also called a site diary or daily report) is a chronological record of everything that happened on site on a given day: who was there, what work was done, what materials arrived, what problems occurred, and what decisions were made.
It serves two purposes that most PMs only appreciate once they have been through a dispute or delay claim:
Operational purpose
The daily log creates continuity. A new site manager who takes over mid-project can read two weeks of logs and understand exactly where things stand — without a three-hour handover meeting.
Legal purpose
In disputes, extensions of time claims, and insurance investigations, the daily log is the first document requested. A well-maintained log proves what happened and when. A poorly maintained one — or no log at all — means you are defending yourself with guesswork.
CIOB guidance consistently emphasises that contemporaneous site records — daily logs, instruction registers, and correspondence — are the primary evidence base in construction adjudication and arbitration.
Source: CIOB — Understanding Delay and Disruption in Construction Contracts
What Every Daily Log Must Include
A daily log that only records "work progressed on Level 3 MEP" is useless in a dispute. Here is the minimum that belongs in every entry:
Date, weather and site conditions
Weather is not filler — it is a contractual record. Rain delays, extreme heat affecting concrete pours, and wind restrictions on crane operations all have legal and scheduling implications. Record conditions at morning start and any significant changes during the day.
Workforce on site
Record every trade on site, the company name, the number of workers, and their location/activity. This becomes critical when a subcontractor claims they were fully resourced and making progress — and your log shows three workers instead of the fifteen quoted.
Work completed today
Be specific. "Formwork erected to column C4-C7, third floor slab poured from grid 3 to grid 6, waterproofing to roof membrane sections A and B completed and inspected" is useful. "Work progressed on structural frame" is not.
Materials delivered and equipment on site
Record all deliveries: supplier, material type, quantity, condition on arrival (especially any damage or shortages). Record plant and equipment on site — particularly if delays are caused by equipment breakdowns.
Visitors and inspections
Every client visit, engineer inspection, authority inspection, and subcontractor meeting should be recorded. Include who attended and the outcome of any decisions made.
Issues, delays and variations
This is the most important section. Record every problem that occurred, its cause (as best you know it), and what action was taken. If work was stopped or delayed — record it explicitly, with the reason. If a verbal instruction was given on site, record it here and follow up with a written confirmation.
Open RFIs and pending information
A brief note on any outstanding information requests that are affecting work. This creates a paper trail that supports extension of time claims.
How to Write a Daily Log That Holds Up in Disputes
The difference between a daily log that helps you and one that hurts you comes down to three habits:
Write it the same day. Memory degrades fast. A log written the following week is a reconstruction, not a record — and it shows. Courts and adjudicators know the difference.
Be factual, not interpretive. Record what you observed, not your conclusions about why it happened or who is to blame. "Six of the eight scheduled MEP workers were not on site" is a fact. "MEP subcontractor is mismanaging their team" is an opinion. Facts hold up; opinions create arguments.
Record the impact of every issue. "Concrete pour to slab B3 delayed by 4 hours due to late readymix delivery" is a complete record. "Concrete was late" is not. The impact (time lost, work affected, sequence disrupted) is what supports a delay claim.
Understanding the contractual context for these records matters too. The daily log is the evidence base for extension of time claims, variation valuations, and defects liability documentation — all governed by specific contract clauses. For a PM-level overview of which contract provisions daily records directly support, see the guide to construction contract management and key clauses. For the broader document management system that keeps daily logs organised and retrievable, see the guide to construction document control.
— "When we audited daily log quality across 8 active sites for a UAE infrastructure contractor, fewer than 20% of entries included a quantified impact statement on issues. Every site manager knew a delay had occurred. Almost none had recorded how many hours were lost or what work was affected. That gap between awareness and documentation is where EOT claims collapse." — Viacheslav Muliukin, Founder & CEO, Banamind
Paper vs Digital Daily Logs: What Field Teams Actually Prefer
Paper logs are still used on most construction sites. They require no training, no connectivity, and no battery. For a small residential project with one site manager, paper works.
The problems start at scale:
- Paper logs cannot be searched. Finding a specific incident recorded three months ago requires reading through every page of every diary.
- Paper is easily lost or damaged. One flood, one fire, one missing folder, and your records are gone.
- Paper logs sit in a site office. The PM, client, and QS cannot see them without physically visiting or requesting copies.
- Paper creates transcription work. Someone has to re-enter the information into a weekly report or monthly summary.
Digital daily logs solve all of these problems. The best implementations let site managers submit a log from their phone in under five minutes — using voice notes, photos, and a simple form rather than a blank page. The result is a searchable, timestamped record that management can access in real time.
The common objection is adoption: "my site managers won't use an app." In practice, the teams that struggle with adoption are usually asking site managers to do more work, not less. A digital log that is faster to complete than a paper one gets used.
Free Construction Daily Log Template
Two versions below: a blank template to copy and fill in, and a completed example showing exactly how each field should look. Download the formatted Word/PDF at the end of this section.
Blank Template
PROJECT DAILY LOG
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Project: | Date:
Project no.: | Day:
Site manager: | Report no.:
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
WEATHER
Morning: °C | Afternoon: °C
Conditions:
Restrictions (if any):
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
WORKFORCE ON SITE
Trade | Company | Scheduled | Present | Location / Activity
| | | |
| | | |
| | | |
TOTAL: ____ workers (planned: ____)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
WORK COMPLETED TODAY
(Be specific — reference location, grid, floor, section)
-
-
-
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
MATERIALS RECEIVED
Supplier | Material | Qty | Delivery time | Condition / Notes
| | | |
| | | |
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
PLANT & EQUIPMENT
Item | Status | Notes
| |
| |
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
VISITORS & INSPECTIONS
Time | Name | Company | Purpose | Outcome / Decision
| | | |
| | | |
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
ISSUES, DELAYS & VARIATIONS
# | Issue | Cause | Impact on programme | Action taken / by whom
1 | | | |
2 | | | |
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
OUTSTANDING RFIs (affecting work)
RFI # | Subject | Issued to | Date issued | Impact if unresolved
| | | |
| | | |
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
TOMORROW'S PLANNED WORK
-
-
-
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Site Manager signature: _______________ Date: ___________
Key rules when filling in:
- Write it the same day — never reconstruct from memory
- Workforce: record actual headcount per trade, not "subcontractors on site"
- Issues: always include cause + impact + action — "concrete was late" is not a record
- Weather: don't skip — it's contractual evidence for delay claims
- RFIs: only list those currently blocking or at risk of blocking work
Completed Example
PROJECT DAILY LOG
| Project | Al Barsha Mixed-Use Tower — Phase 2 |
| Project no. | BNM-2024-047 |
| Site manager | Ahmed Al-Rashidi |
| Date | 14 May 2026 — Wednesday |
| Report no. | 047 |
WEATHER
| Period | Conditions | Temperature |
|---|---|---|
| Morning 07:00 | Clear, light wind | 28°C |
| Afternoon 13:00 | Sunny, gusty | 34°C |
| Evening 17:00 | Clear | 31°C |
High wind advisory issued at 14:30 — tower crane suspended for 90 minutes (14:30-16:00). See Issues #2.
WORKFORCE ON SITE
| Trade | Company | Scheduled | Present | Location / Activity |
|---|---|---|---|---|
| Structural | Al Futtaim Construction | 18 | 18 | Level 7 — column formwork & rebar |
| MEP | Emirates MEP LLC | 12 | 8 | Levels 4-5 — conduit installation |
| Waterproofing | Gulf Seal Co. | 6 | 6 | Basement B2 — membrane application |
| Finishing | Al Noor Interiors | 10 | 10 | Level 3 — plastering |
| TOTAL | 46 | 42 | 4 below plan — MEP shortfall, see Issues #1 |
WORK COMPLETED TODAY
- Level 7: Formwork to columns C4-C9 erected, inspected and approved for pour (structural engineer sign-off 11:30)
- Level 7: Rebar to columns C4-C6 complete; C7-C9 approx. 60% complete
- Level 5: MEP conduit installed in corridors A and B; units 501-508 pending (see Issues #1)
- Basement B2: Waterproofing membrane applied to sections 3 and 4 (of 6 total — on programme)
- Level 3: Plastering to units 301-306 complete and inspected; units 307-312 in progress (est. 70%)
MATERIALS RECEIVED
| Supplier | Material | Qty | Delivery time | Condition |
|---|---|---|---|---|
| Arabian Cement Co. | Ready-mix concrete C35 | 18 m³ | 09:15 | Good |
| Al Hamad Steel | Rebar T16 | 4.2 t | 11:40 | 2 bent bars rejected and returned — see delivery note DN-2026-0514 |
| Gulf Seal | Waterproofing membrane | 200 m² | 08:00 | Good |
PLANT & EQUIPMENT
| Item | Status | Notes |
|---|---|---|
| Tower crane | Operational / suspended 14:30-16:00 | Wind restriction — see Issues #2 |
| Concrete pump | Operational | |
| Passenger hoist | Operational | |
| Backup generator | Standby |
VISITORS & INSPECTIONS
| Time | Name | Company | Purpose | Outcome |
|---|---|---|---|---|
| 09:00 | Eng. Khalid Hassan | Emaar (Client) | Weekly walkthrough | Satisfied with Level 3; requested confirmed pour date for Level 7 — advised 15 May AM |
| 11:30 | Structural inspector | Dubai Municipality | Formwork inspection Level 7 | Approved. Permit to pour issued — ref DM-2026-0514-07 |
ISSUES, DELAYS & VARIATIONS
| # | Issue | Cause | Impact on programme | Action taken |
|---|---|---|---|---|
| 1 | MEP — 4 workers absent | Subcontractor: transport problem | Units 501-508 MEP conduit delayed est. 1 day. No critical path impact yet — 2 days float remaining. | Written notice sent to MEP PM 14:23. Recovery plan requested by 16 May EOD. |
| 2 | Tower crane suspended 90 min | Wind speed exceeded 45 km/h | Rebar lift to Level 7 delayed; columns C7-C9 not completed today. No critical path impact — rescheduled to 07:00 tomorrow. | Crane operator notified. Lifts rescheduled. |
| 3 | 2 rebar bars rejected | Visible bend damage on delivery | Nil — replacement ordered same day | Supplier notified; replacement confirmed for 15 May AM delivery. Delivery note DN-2026-0514 filed. |
OUTSTANDING RFIs (blocking or at risk)
| RFI # | Subject | Issued to | Date issued | Impact if unresolved |
|---|---|---|---|---|
| RFI-047 | MEP penetration detail — shear wall Level 6 | Structural engineer | 10 May 2026 | Level 6 MEP cannot start — now 4 days outstanding, response overdue |
| RFI-051 | Waterproofing spec — B1 lift pit | Architect | 13 May 2026 | B1 lift pit waterproofing on hold — 5-day window before programme impact |
TOMORROW'S PLANNED WORK
- Level 7: Complete rebar to C7-C9 (07:00 start); concrete pour to C4-C6 (scheduled 09:00, subject to pump availability)
- Level 5: MEP conduit to units 501-516 (subject to full crew attendance)
- Basement B2: Waterproofing sections 5 and 6 — complete membrane by EOD
- Level 3: Complete plastering to units 307-312
Site Manager signature: Ahmed Al-Rashidi Date: 14 May 2026
What makes this log useful in a dispute: Every issue has a cause, a quantified impact ("1 day delay", "2 days float remaining"), and a documented action with a timestamp. If this project ends up in adjudication, Issues #1 and #2 are already formatted as the basis of an extension of time claim.
Download the blank template as Word/PDF → banamind.ai/reports
Frequently Asked Questions
What is a construction daily log?
A construction daily log (also called a site diary or daily report) is a contemporaneous record of everything that happened on a construction site on a given day — workforce numbers, work completed, materials received, equipment status, visitors, issues, and delays. It serves both operational (handover, continuity) and legal (dispute, EOT claims) purposes.
What must be included in a construction daily log?
Every daily log should include: date and weather conditions; actual workforce headcount per trade and company; specific work completed (referenced by location and activity); all material deliveries; plant and equipment status; visitors and inspection outcomes; any issues or delays with their cause and programme impact; and outstanding RFIs affecting current work. Vague entries such as "work progressed" have no value in a dispute.
How detailed should a construction daily log be?
Specific enough that someone who was not on site could understand exactly what happened, what problems occurred, and what the effect on the programme was. For issues and delays, always record: the cause (as observed), the quantified impact (hours or days lost, work affected), and the action taken (with names and times). This level of specificity is what makes a log usable in adjudication.
Can a daily log written from memory be used in a dispute?
Logs reconstructed from memory after the fact carry significantly less weight in adjudication and arbitration than contemporaneous records written the same day. Adjudicators can identify retrospective logs by inconsistencies in language and detail. The standard instruction is always: write it the same day, every day.
What is the difference between a paper and digital daily log?
Paper logs require no technology but cannot be searched, are at risk of loss or damage, are not accessible to off-site management in real time, and require manual transcription into reports. Digital logs are searchable, timestamped, backed up automatically, visible to the whole project team in real time, and can be built incrementally through the day using photos and voice notes rather than a single end-of-day session.
How Banamind Automates Daily Log Creation from the Field
The most common reason daily logs are incomplete is that site managers are filling them in at the end of a 10-hour day from memory. The log becomes a summary rather than a record.
Banamind works differently: site managers submit updates throughout the day — a photo from the pour, a voice note about the delivery issue, a quick check-in when the inspection happens. The AI compiles these inputs into a structured daily log automatically.
By the time the site manager reviews it at day's end, the log is 80% complete. They confirm, adjust, and sign off in under three minutes. Completed logs can be compiled into formal progress reports with Banamind's AI-generated reports feature, then shared directly with clients or exported as PDFs.
The result is a daily log that actually reflects what happened — because it was built in real time, not reconstructed at 7pm.
Last updated: May 2026