A short daily log can prevent a long search later.
Messages, photos, delivery slips, and verbal updates are easy to lose when they live in different places. A consistent daily record connects them to one date and one project.
The log does not need to be complicated. Complete it near the end of each workday, use observable facts, and link photos or documents by a stable file name. It can help owners, contractors, and property teams remember sequencing, decisions, access interruptions, and open questions. It does not replace the contract, approved drawings, permits, formal change orders, inspection records, or required safety documentation.
1. Start with the same header every day
Record the project, address or unit, date, person completing the log, arrival and departure window, weather when it affects exterior work or deliveries, and general site conditions. For an occupied property, note the approved access window and whether the area was returned to the agreed condition at the end of the day.
| Field | Example entry | Why it helps |
|---|---|---|
| Date and log owner | Sept. 11 · site lead | Shows who can clarify the entry |
| Conditions | Dry; elevator booked 9–11 | Explains access or delivery limits |
| Work areas | Kitchen and main hall | Keeps the record location-specific |
2. Record people, work, and deliveries
List the companies or trades present and a simple headcount; personal information is usually unnecessary. Describe completed work by location and outcome: “kitchen east wall boarded and first coat applied” is more useful than “drywall worked on.” Note material and equipment deliveries, quantities when relevant, visible damage or shortages, the packing-slip number, and where items were stored.
3. Give photos useful names
Take overview photos before close-ups so another reader can understand the location. Use a simple naming pattern such as date-room-subject-number. Link each image to a log entry instead of leaving it in an unlabelled camera roll. Avoid photographing residents, personal papers, access codes, keys, or security details unless there is a legitimate project need and an approved way to store the image.
4. Separate observations, issues, and decisions
- Observation: a factual condition that may not require action.
- Issue: a condition that blocks work, affects scope, creates risk, or needs follow-up.
- Decision required: the exact choice, responsible decision-maker, options or supporting reference, and needed-by date.
- Decision made: who approved it, when, and where the written approval is stored.
Do not treat the daily log as authorization for extra work or cost. If a condition changes the agreed scope, price, product, or schedule, connect the entry to the project’s formal approval or change-order process.
5. Note interruptions and protection
Record planned and unplanned shutdowns of water, electricity, heating, alarms, elevators, parking, or access routes. Include the actual time, affected area, notice provided, restoration check, and any follow-up. Note daily protection, cleanup, dust control, waste removal, locked doors, and any area intentionally left isolated.
6. Close with tomorrow’s plan
List the next planned tasks, expected trades, deliveries, inspections, access needs, and decisions due. A next-day plan is not a promise that concealed conditions or approvals cannot change; it is a shared coordination snapshot. Carry every unresolved item forward with the same identifier until it is closed.
7. Review weekly and at closeout
Once a week, scan open items, missed decisions, pending documents, and repeated delays. At project closeout, keep the logs with approved changes, inspection records, warranties, manuals, product information, and the final punch list. A clean archive is much easier to use than hundreds of disconnected messages.
Pair this template with the change-order checklist and renovation punch-list checklist. JT can help turn an existing condition and desired result into a coordinated scope for GTA renovation work.