Site conditions, daily report printing, and a legal hold for the day you get served

Somebody slips on a floor you finished at 11:40, and six months later the only question is whether you can prove the signs were up. This release is built around that question: the record you make at the time is the one that holds, so STrOp now makes the right record the easy one — and keeps it from changing afterwards.

On the daily report, for the foreman:

• Site conditions — nine rows inside the Daily Report, above Photos: work area closed off, signs up, client contact told, alternate route posted, lighting adequate, the mid-shift walk, the area stayed clear, the floor dry-tested, the area released. Tap a row and it stamps the time; most rows have a Camera button that drops a Safety photo on the report captioned with the row. An unchecked row is part of the record too.
• Print daily report — one link on the card lays the whole day out on your letterhead: who was there and their hours, the narrative, areas worked, weather, delays, deliveries, every site-condition check with its time and photo, and the photos themselves with capture time and location. Submitted-by and approved-by are printed on it.

On approvals, for the PM:

• A submitted day now locks. If something genuinely has to change, a PM or super taps Reopen on the card on Timecards and types the reason — the reason is recorded against the card for good. Foremen can't reopen, not even their own day. A quiet edit was never defensible; a stated correction is.
• Approved days accept one change only — voiding — and voided days accept none; the database refuses everything else, from anyone, including us.
• The Approvals queue shows each pending day's narrative, how many site-condition checks were made, how many photos, and a link to the printed report.

On the project, for the org admin — the day a notice arrives:

• Legal hold. Open the project → Edit → Legal hold, give the reason, and every field record on that job — timecards, daily reports, photos, T&M tickets, documents — freezes against edits and deletes, for everyone, until an org admin releases it. Only an admin sees that card; if that isn't you, your job is getting one to set it the same day. The hold is enforced at the database and in storage, not just on the screen: documents are frozen at the database and the file store refuses to delete them while the hold is on; photos are frozen in storage against both delete and overwrite. Setting and releasing it are both on the audit trail. An amber pill on the project header says it's on.

The crew guide was rewritten around all of this — Daily site photos and the daily report — and it surfaces in the How-to panel on timecards, and on the project Photos tab too (the daily-report photos it describes live on the day's report, not in that tab). General guidance, not legal advice: your counsel decides what the record needs. This gives you the record.