Site diary

Every construction site keeps a daily record, and on most of them it is a form somebody types up at the end of the day from memory and half a dozen WhatsApp threads. SimOps carries it as a Site diary: one record per site per working day, filled in as the day happens by whoever is at a screen, auto-answered wherever SimOps is already the system of record, and published at the day's boundary — by a sweep, never by a person — as the immutable PDF the client opens with their coffee.

What it does for you

• The record writes itself as the day goes. Answers land one at a time, from a phone, attributed to whoever wrote them and stamped with the server's clock. There is no end-of-day typing-up, because there is no draft to type up.
• SimOps answers its own questions. Cranes on site, inspections run today, open and closed Defects and snags, the day's photos, the weather — all computed from the registers at publication and attributed to SimOps itself, never to a person who would carry the blame for a machine's arithmetic.
• Nobody presses publish. The working period's boundary is the deadline, and the day publishes exactly as it stands. Empty and half-filled days publish too, with their gaps printed as gaps — that visible hole in a document the client reads is the only enforcement, and it works better than a nag.
• The record cannot be quietly rewritten. Entries are append-only and never edited; a published day admits only an Erratum, which lands in an appendix while the body stays byte-for-byte what it was.
• It is the main contractor's document. The gate is the principal-contractor link, not seniority — subcontractors get nothing, and the client's copy is the email.

The shape of a day

A day runs [boundary, boundary) in the site's own timezone — a Working period, six in the morning by default — so a night shift finishing at 01:00 is still writing yesterday's diary. Human answers are Diary entry rows: append-only, attributed, grouped into shift subsections, and storing what they rendered so a later edit upstream cannot rewrite a signed answer. Blanks are three distinct facts — a hole, an attributed nil-report, and a register's honest zero — and the PDF prints all three differently.

At the boundary the Publish sweep computes every automatic cell, renders the crane snip, renders Rev A, and mails it out with the PDF attached. Every later revision renders from the same entries and the same frozen values: the body never moves, holes stay holes, and only the errata appendix grows.

Three panes, one surface

The diary is the third full-screen citizen of the dock, beside Health & Safety and Commercial, opened from its dock button or the Y chord.

• My Round — the writing path: one question at a time, opening on the first gap, with one-tap "Nothing to report", Skip, and a full-screen permit tick-list that pre-ticks from the last published diary and waits to be confirmed.
• The Document — the reading path: the whole day in form order, exactly as the PDF will print it, with holes shown as "publishes as a gap" slots; after publication, the revision list and the errata composer live here too.
• Distribution — who the morning email reaches: the derived audience read-only beside the bare addresses somebody added by hand.

See it / try it

Where to go next

• The site diary — the concepts: the working period, the gate, holes vs nil-reports, publication, errata and distribution.
• Filling in your round — the how-to: walking the round, the tick-list, photos, and recording a correction.
• Defects — the contractual register — the register the QA/QC counts read.