HomeResources

Construction Daily Report Examples: Good vs. Weak Entries You Can Copy

A good construction daily report example has specific, dated, factual entries: who worked, how many hours, what they installed and where, what got in the way and for how long, what happened on safety, and who visited. Below are side-by-side weak and strong entries for each section, followed by two complete sample reports: one for a normal day and one for a day with a delay.

For the step-by-step process, see how to write a construction daily report. For a blank form, grab the free daily report template.

Weak vs. strong entries by section

Weather

Weak Strong
Rainy. Light rain 6:30 AM to 9:45 AM, 0.3 in. at site gauge. 51 F at 7 AM. Exterior work held until 10:00 AM.
Hot. 96 F at 2 PM. Heat plan in effect. Roofing crew took water and shade breaks hourly and stopped at 2:30 PM.

Manpower

Weak Strong
Electricians on site. Northline Electric: 1 foreman, 5 journeymen, 1 apprentice. 7 workers, 56 hours. Level 2 east.
Usual crews. 6 companies, 31 workers, 248 hours (breakdown in manpower table).

Work performed

Weak Strong
Framing continued. Ridgeline Framing installed 180 LF exterior wall framing, Building C, Level 2, gridlines A to D. 60% of Level 2 exterior walls complete.
Started plumbing. Summit Mechanical installed underground sanitary, Wing B, 92 LF of 4 in. PVC. Ready for inspection Thursday.

Delays

Weak Strong
Waiting on RFI. RFI 112 (beam pocket at grid C4) open 6 days. Steel crew of 4 moved off C4 to D-line. C4 bay cannot proceed until answered.
Inspector late. Inspection scheduled 9:00 AM. Inspector arrived 1:15 PM. Concrete crew (5) idle 9:00 AM to 10:30 AM, then reassigned to curbs.

Safety

Weak Strong
Safety good. 5 pre-task plans received. No incidents or near misses.
Guy got hurt. 10:20 AM: Ridgeline carpenter cut left hand with utility knife, Level 2. First aid on site, returned to work. Corrective action: cut-resistant gloves required for sheathing cuts, reviewed at 1 PM huddle.

Visitors and direction

Weak Strong
Architect walked site. Architect K. Lin on site 10:00 AM to 11:30 AM. Walked Level 1. Verbally approved alternate grout color at restrooms; confirmed by email 3:12 PM.

Sample report 1: a normal production day

Project: Harbor View Medical Office Building, Report #088 Prepared by: M. Ortiz, Superintendent Weather: 7 AM 58 F clear, 3 PM 72 F clear, wind 5 to 10 mph. No weather impact. Manpower:

  • Ironclad Steel: 6 workers, 48 hrs, erecting Level 3 beams
  • Pacific Decking: 4 workers, 32 hrs, Level 2 deck
  • Northline Electric: 5 workers, 40 hrs, underground at site lighting
  • general contractor labor: 2 workers, 16 hrs, cleanup and fall protection
  • Total: 17 workers, 136 hrs Work performed:
  • Ironclad set 22 of 38 Level 3 beams, gridlines 1 to 4.
  • Pacific installed 4,200 SF metal deck, Level 2, gridlines 1 to 3.
  • Northline trenched and installed conduit for 6 site light bases, north lot. Equipment: 90-ton crane, working 7 AM to 3:30 PM. Mini excavator, working. Deliveries: Level 3 joists, 2 trucks, ticket 7781 and 7782, no damage. Safety: 4 pre-task plans received, crane swing radius barricaded. No incidents. Visitors: Special inspector, bolting at Level 2, passed. Tomorrow: Finish Level 3 beams. Deck Level 2 gridlines 3 to 5.

Sample report 2: a day with a delay

Project: Lincoln Elementary Modernization, Report #203 Weather: 7 AM 44 F, 11 AM 49 F, rain 11:20 AM to 3:00 PM, 0.6 in. Manpower: Delta Drywall 8 (64 hrs), Bayside Roofing 5 (14 hrs, sent home 11:30 AM), Summit Mechanical 4 (32 hrs). Total 17 workers, 110 hrs. Work performed: Delta hung board, Classrooms 201 to 204. Summit set 3 VAV boxes, 2nd floor corridor. Bayside installed 6 squares of underlayment, Roof Area B, before rain. Delays: Rain stopped all roofing 11:20 AM. Bayside crew sent home 11:30 AM, 26 hours lost. Roof Area B now 2 days behind lookahead. Owner notified by email 12:05 PM. Open items: Fire damper submittal (Summit) returned revise and resubmit. Corridor ceiling close-in at risk for next week. Safety: 5 pre-task plans received. Near miss 9:40 AM: unsecured ladder at stair 2 slid when climbed; worker uninjured. Ladder tagged out; all ladders checked for feet and tie-off by 10:30 AM. Photos: 9 attached (roof underlayment before rain, standing water at Area B, tagged ladder).

Patterns worth copying

  • Times on everything that stopped work. Start and stop times turn "it rained" into lost hours.
  • Running counts. "Day 6 of RFI 112" tells the reader the trend without opening older reports.
  • Tomorrow line. One line about the next day turns the report into a short lookahead.
  • Notice references. When you notified the owner, write when and how.

How to use these examples with your team

Examples work best when the whole team sees them early. A few ways superintendents and PMs use a page like this:

  • At the preconstruction meeting: show subs the weak and strong columns so everyone knows the standard before day one.
  • In a foreman onboarding packet: include one full sample report so new foremen can model it.
  • During weekly review: pick one weak entry from last week (without naming anyone) and rewrite it together.

Getting entries like these without the typing

Most superintendents and foremen know what good entries look like. The hard part is writing them at the end of a 10-hour day. Cascade is SMS-first field intelligence for general contractors and subcontractors: superintendents and foremen text in their day, along with their subs, and Cascade builds the daily report in a consistent structure. Product scope: Daily reports, manpower and hours by sub, photos, toolbox talks, pre-task plans (JHA), safety incidents and corrective actions, project + schedule planning, automatic sub reminders, analytics and plain-English answers.

Subcontractor access is free, and general contractors see 95%+ sub daily report compliance. See why teams switch. Start with free onboarding and integration plus a one-month pilot on the general contractor plan, no contract lock-in, priced below Raken, Procore and ACC, guaranteed.

Request Access

Frequently asked questions

What does a good construction daily report look like?

It reads like a factual log: weather with times, manpower and hours by company, work performed with location and quantity, delays with cause and duration, safety items, visitors, and photos. Someone who was not on site should be able to follow it.

Should a daily report include opinions?

No. Write what happened and who said what. Opinions such as 'the electrician is incompetent' weaken the record and can be used against you. State the fact: 'Northline had 2 of 6 scheduled workers on site, third day this week.'

How detailed should work performed entries be?

Include the scope, the location using drawing language, the quantity when it can be measured, the crew, and the time window. 'Hung 42 sheets of 5/8 Type X on Level 3 corridor, gridlines 4 to 7' beats 'drywall on 3.'

Can I use a short daily report on a small job?

Yes. On a small job a few lines per section is fine as long as every section is covered and every entry is specific. Short and specific is better than long and vague.

Request Access

RESOURCES

See how your team reports by text.

Free onboarding and integration, a one-month pilot and no contract lock-in. Tell us about your jobsites.

EARLY ACCESS FOR PUGET SOUND GCS · SET UP IN DAYS · YOUR DATA STAYS YOURS