How to run a daily log on construction and remodel projects

The ServFlo team
Sep 25, 2026
How to run a daily log on construction and remodel projects

A daily log is a short, dated record of each day on a project: the weather, who was on site, what got done, what was delivered or inspected, and anything that delayed the work or changed the plan, with photos. Have the lead write it before leaving the site each day, keep it to a few minutes, and share the parts that matter with the client.

Large commercial builders treat daily logs as standard practice. Small remodelers often skip them, then regret it the first time a client disputes a delay or a change. The good news is that a useful log takes five minutes.

Why bother with a daily log?

A daily log pays off in a few ways:

  • Memory. Three weeks later, nobody remembers which day the tile arrived cracked or when the inspector came.
  • Change orders. When the client asks for something new on site, the log records when and what. That makes the change order conversation easier.
  • Delays. Weather, late deliveries, failed inspections and the client's own decisions all push schedules. A log shows the cause.
  • Client communication. Sharing a short update with photos answers "how's it going?" before the client calls.
  • Disputes. If a disagreement does arise, contemporaneous notes are far stronger than recollection. If you're ever in a legal dispute, your attorney can tell you how records like these are used.

What should a daily log include?

Keep the same structure every day so it's quick to fill in and easy to read later:

  1. Date and project.
  2. Weather. Conditions and temperature, especially for exterior work, concrete, paint and roofing.
  3. Who was on site. Your crew, subcontractors and how many people from each.
  4. Work completed. In plain words: "Set base cabinets on north wall, ran water lines to island."
  5. Deliveries. What arrived, what was missing or damaged.
  6. Inspections and visitors. Inspector, client, designer, utility company.
  7. Delays and issues. What held things up, and why.
  8. Client requests and decisions. Anything the client asked for or decided on site.
  9. Safety notes. Near misses, hazards found, anything reported.
  10. Photos. A few wide shots and close-ups of today's work.

Not every field gets filled every day. A quiet day of drywall finishing might be three lines and two photos. That's fine.

Who should write the daily log?

The lead on site, every day the project has activity. Not the owner from memory at night, and not the office from text messages. The person who was there writes it before they leave.

When subcontractors are working and your lead isn't there, ask the sub's lead to send a short note and photos, and add them to the log. Our guide to managing subcontractors covers setting those expectations up front.

How do you make the habit stick?

Writing it is easy. Remembering to do it every day is the hard part. A few tactics:

  • Make it the last task of the day, right before packing up, like locking the site.
  • Use a phone, not paper. Typing or dictating a few lines and snapping photos is faster than a notebook.
  • Keep the format short. Leads will skip a log that feels like homework.
  • Review logs weekly. When the owner reads them and asks questions, they get written.
  • Use them. Pull a photo from the log into a client update, or quote it when explaining a delay. When people see logs being used, they keep writing them.

What photos are worth taking every day?

Photos are often the most valuable part of the log. Aim for:

  • A wide shot of each work area from roughly the same spot each day. Over the project, these become a timeline.
  • Anything about to be covered: plumbing and electrical in open walls, blocking, waterproofing, insulation.
  • Problems found: rot, old wiring, uneven subfloor, anything that changes scope.
  • Deliveries, especially damaged ones, with packing labels visible.
  • The site at the end of the day, showing it was left clean and secure.

Photos of what's inside the walls also help future you, and the homeowner, years from now.

Should the client see the daily log?

Usually some of it. Clients love seeing progress, and frequent updates reduce anxious phone calls. But the internal log may include things that aren't for the client: notes about a sub's performance, internal cost concerns or frank remarks about the client's decisions.

A practical approach:

  • Keep one internal log.
  • Share selected days, or a summary with photos, with the client.
  • Write anything you share in a calm, factual tone.

What should you avoid writing in a daily log?

A daily log is a business record, and it may be read later by clients, partners or, in a dispute, people outside your company. Write it that way:

  • Stick to facts. "Tile delivery arrived at 2 PM, two boxes cracked" rather than "supplier messed up again."
  • Leave out opinions about people. Notes about a sub's attitude or a client's taste don't belong in the log. Handle those conversations directly.
  • Don't guess at blame. Record what happened and what you did. If the cause isn't clear yet, say so.
  • Don't backdate. If you forgot to write yesterday's log, write it today and note that it was added late.
  • Avoid sensitive details like alarm codes or the client's personal information in anything you might share.

Calm, factual logs are more useful and far easier to share.

How does the log help with delays?

When a delay happens, record:

  • What happened ("rain all day," "countertop template delayed by fabricator," "failed framing inspection, missing hurricane ties")
  • Which work it affected
  • What you did about it

When you later explain why the project's end date moved, you have a day-by-day account rather than a general "there were delays." That's also the basis for adding schedule days through a change order when the cause is a client change.

A daily log checklist

  • Same format every day: weather, people, work, deliveries, inspections, issues, requests, safety, photos
  • Written by the lead on site before leaving
  • Photos of each area, hidden work and problems
  • Subs' work added when your lead isn't there
  • Reviewed weekly by the owner or project manager
  • Selected logs shared with the client

FAQ

How long should a daily log take? On most days, five to ten minutes. If it takes longer, the format is probably too detailed.

Do I need a log on days when nobody works? A one-line note helps when there's a reason, like weather or waiting on an inspection. On normal days off, it isn't necessary.

Are daily logs required by law? Some public and commercial contracts require them. For residential work it's usually your choice. Check your contracts and any local requirements.

What's the difference between a daily log and a timesheet? Timesheets record hours for pay and costing. A daily log records what happened on the project. Many crews do both from the same app.

How ServFlo helps

In ServFlo projects (Grow and Pro plans), each project has one daily log per day with fields for weather, who was on site, work done, and delays or issues, plus photos. The first save fills in the weather from the forecast at the property. Your crew can write the log from the technician app, even offline, and the office can share a log with the client in the customer portal one day at a time, with its photos. The same project holds phases, change orders, budget versus actual, subcontractors and files. See pricing for plan details.

Photo by Ernys on Unsplash.