Daily Log

The Daily Log is the project's day-by-day account of what actually happened: who was on site, what the weather did, who visited, and what held the job up. It exists for the conversation six months later that starts "we lost four days to rain in March" — and it only helps if the record was written on the day and can't be quietly rewritten afterwards.

That's the whole design. A day is a draft while you're filling it in, and locked once you submit it.

The calendar

The Daily Log opens on a month calendar for the project. Each day carries a mark showing where it's up to:

→Nothing — no entry has been started. Days stay empty until someone chooses to create one; opening a day doesn't create a record.
→Draft — an entry exists and is still editable.
→Submitted — the day has been locked and is now a read-only record sheet.

Click any day to open it. From an empty day you can start a daily log entry, or go straight to a QA checklist inspection without filling in the rest of the day.

Filling in a day

The day form autosaves as you type — there's no Save button to forget, and a half-finished day survives a dropped connection or a closed tab. A day holds:

→Weather — filled in automatically from the project's location (see below), and overridable by hand.
→Subcontractors on site — company, crew count, and what they were doing. Company names resolve against your contractor directory as you type.
→Own staff & labour hire — per person: start, finish, meal break, and the worked hours derived from them. These are the lines that feed Timesheets.
→Delays / stoppages — kind, reason, and duration. The section that earns the log its keep.
→Plant & equipment — what was on site, owned or on hire.
→Visitors — name, company, in and out.
→Photos — day photos with captions, separate from any defect's photos.
→Day summary — the narrative line for anything the structured sections don't cover.
→QA Checklists — inspections run against that day. See Inspections.

Nothing is mandatory. A day with only a weather reading and a delay line is a valid record.

Copy the previous working day

Most days look a lot like the day before — same trades, same crews, same plant. Rather than retyping it, copy the previous working day and edit the differences. It skips back over weekends and non-working days to find the last day that actually had an entry.

Weather, filled in for you

Set a project's location once and the Daily Log fills in each day's weather itself — conditions, and the temperature range for the date. Recent days come from forecast data; older days come from the historical record, so back-filling a week you missed still produces real numbers rather than blanks.

You can override any of it by hand. Once you do, the system won't overwrite your figure on a later refresh — a manually entered reading is treated as the authoritative one, because you were there and the weather station wasn't. Each day records whether its weather came from the service, from a person, or not at all.

Submit and lock

Submitting a day converts it from a draft into a record sheet: the same content, rendered read-only. This is the step that makes the log worth keeping.

→One live entry per day, per project. You can't end up with two competing versions of the 14th.
→Submitting is separate from editing in the permission model — the people who fill a day in aren't necessarily the people who can close it.
→QA checklist answers lock along with the day.

Treat submission the way you'd treat signing a paper diary: it's the point at which the day stops being working notes and starts being evidence.

Who can do what

Daily Log permissions are their own set, separate from defects:

→Managers work across the organisation's projects.
→Users work within the projects they're a member of.
→Submit is a distinct permission from edit, so you can let the site team write the day up while sign-off stays with the supervisor.

Trades, tenants, and clients don't see the Daily Log at all.