Filling in your round

This is the day's job: get the site diary filled in before the working period ends. The record publishes itself at the boundary whether or not you got to it, and whatever you left blank prints as a visible gap — so the pressure to write is the document, not a nag. Everything below happens inside the Site Diary surface — open it from its dock button or with the Y key. Concepts and law live on The site diary.

Before you start

You need the diary band on a site whose principal contractor is your own firm — that is the whole gate, and no role seniority substitutes for it (see The site diary). If you can see the dock button, you are in.

Task 1 — Walk your round

1. Open Site Diary from the dock — or, on a phone, tap Site Diary on the Home screen, which lands you straight on the round — and pick the My Round tile. The tile screen heads "Your round" with today's date, a summary line reading "{answered} of {answerable} answered · {holes} still to fill", and one tile per section carrying its fill state — All answered, Nothing to report, Still to fill or Automatic — plus the chips of whoever has already written into it, and a "You wrote this yesterday" hint where you did.
2. Press the start button. It reads "Start where the gaps are" when anything is unanswered — that is the default, and it drops you on the first gap rather than the first question — or "Go through the questions" once the round is complete and you are re-reading.
3. Answer the question in front of you. The runner shows one question at a time with ← Back, a {position} of {n} · {section} progress mark, and Done to leave. Anything already written for that question is shown above, read-only and attributed — "Entries can't be edited. Add another and both stand, in order."
4. Use the two footer buttons deliberately. "Nothing to report" writes an attributed entry that says exactly that; "Skip" writes nothing at all and leaves the question a hole. They are different facts and the published PDF prints them differently, so never use Skip to mean "nothing happened".

Note: There is no draft and no save-and-close: an entry is written the moment you save it, stamped with the server's clock and your name, and there is no edit or delete path anywhere. Two people answering the same question is normal — both entries render, in the order they were written, each attributed. That is the record working as designed, not a conflict to resolve.

Task 2 — Answer a suggested question

1. Where SimOps already holds evidence — the day's observations, the permits that started, the blockers, the deliveries — the question arrives as a pick-list under the lede "Tick what belongs in today's diary. Anything flagged is listed first."
2. Tick the rows that belong in the diary, and add a per-pick note where the bare row does not tell the story ("Add a note about this one (optional)"). Anything the registers do not know about goes in the free-text remainder underneath.
3. Choose "Save answer" (it counts your picks: "Save answer · 3 picked"). What is stored is the source rows and the text as it read at that moment — a permit edited tomorrow cannot rewrite what you signed today.

Note: A suggestion is only ever as good as the registers. If the feed is empty you get "Nothing on the registers for this question today…" and if it failed to load you get "Today's suggestions couldn't be loaded…" — in both cases you write the answer in your own words and it is recorded exactly the same way. An untouched suggestion is a hole, exactly like an untouched free-text box.

Task 3 — Confirm the permit tick-list

1. Open the "which works activities are we working at today?" step. It fills the screen with every permit issued and active for this working period, described first with a muted permit-number chip beside it.
2. Read the change strip before you touch anything: "{n} new today · {n} dropped off", then "Ticked to match {date}, the last published diary that recorded this. Change anything that isn't right." Rows carried over from that diary arrive pre-ticked with a "Carried over" badge; rows that have dropped off are listed struck-through so you can see what left.
3. Correct the ticks — untick what is not running, tick what is, add a per-permit note where it helps. On a long list use the filter box; hidden-but-ticked rows are counted and the page says so.
4. Press "Confirm 7 activities as my entry" (the count is yours). Nothing is recorded until you do: "Ticks aren't recorded until you confirm them." A pre-tick is a suggestion, and confirming it is the gesture that makes it your attributed answer.

Task 4 — Deal with photos

1. Open the photo tile from your round. Most of what appears there arrives on its own: every photo attached to the day's work is collected when the diary publishes, keyed to the work day it belongs to and not to when somebody got round to uploading it.
2. Add anything the tokens do not carry — a drone shot, a wide view — with "Add photos", giving each one a caption. That lands as your attributed entry.
3. Hide a photo that should not go to the client with "Hide from the diary". Read the warning first: "Hiding a photo is recorded as an entry, and can't be undone." The hiding is itself an attributed row in the record; it is accountable, not invisible.

Note: An empty photo section is not a hole — it prints a quiet "no photos" line, because "there are none" is an honest answer from a register rather than a question nobody answered. Upload after the boundary and the photo misses that diary permanently; the only route in afterwards is an erratum.

Task 5 — Record a correction after publication

1. Open The Document for the day and scroll to the Errata appendix. Press "Record a correction" (you need the same diary-write band; there is no window, and a correction weeks later is as admissible as one an hour later).
2. Pick what it is About — "The whole day" or one of the day's sections — and write what the record should have said. Photos may ride along.
3. Press "Record correction". Read the line beside it first: "Appended, never edited — there is no way to take one back."

Note: An erratum never touches the body. The published page re-renders from the same entries and the same computed values, with your correction added to the appendix and the revision letter stepped on — "Correction recorded — Rev C issued, superseding Rev B." Holes stay holes forever; the errata are the only thing that grows. The revision goes back out to the same audience flagged as a revision.

Gotchas

• The working day ends before you do. Once the period closes the runner says so — "The working day has closed, so the diary is no longer taking entries…" — and both footer buttons go dead. Finish inside the day; the erratum is a correction path, not a late-entry path.
• The day moved while you were writing. If the boundary passes mid-answer the save is refused with "The working day moved on while you were writing, so this entry wasn't recorded. Today's round is the one that's open now." Re-open your round and write it against the day that is actually open.
• Skip is not "nothing to report". Skip leaves a gap in a document the client reads tomorrow morning; Nothing to report is a signed answer. Reach for the second one whenever it is true.
• Nobody approves this. There is no submit, no sign-off and no publish button anywhere in the surface — the boundary sweep publishes the day exactly as it stands.

---

See also: The site diary — the concepts, the gate and what publishes · Defects — the contractual register — what the QA/QC counts are counting · Snags & work close-out. Terms: glossary — Site diary, Diary entry, Working period, Erratum.

Site diary guide: The site diary · Filling in your round · Defects register