Your firm's lost time

Every firm on site has its own ledger of its own position: the Your firm's lost time view, behind the Lost time tile on the Commercial surface (I) — and on the phone at /blockers/my-firm. It needs no special grant beyond ordinary Blocker visibility: the tile is a resolving door, and a firm membership without the site-wide lost-time grant lands here, with Your firm written in the header so the scope is never in doubt. The server binds the figures to your firm, always — and it exists because most of what the site's Lost time figures need from you happens here: the counts only your firm can give, the closes only your firm can declare, and the record of what's being said about your work.

This page is written for the foreman, supervisor or contractor's QS who opens that view. The site-wide read surface is the ledger; the counting rules are on How lost time is counted.

The header — your position in one line

The view leads with a sentence like:

5 records · 3 confirmed (38 crew-hours · 1 no count) · 1 awaiting triage — 6 days · 1 rejected · 2 without a count

Read it left to right: how many records are about your firm's work, how many a coordinator has confirmed (and what they add up to — with a rider whenever a confirmed record contributes no figure yet), how many are still waiting on triage and how long the oldest has waited, how many were rejected, and how many still carry no crew count. A "0 confirmed (— crew-hours)" is deliberately never hidden: it is exactly the signal that your claims are sitting undecided.

The three sections

1. Needs your count — records about your work that carry no crew figure yet: a raise that named no work, another firm's declaration about your crew, a record minted from an injury. Each row hosts your complete affordance and says plainly why the figure is missing ("no basis — nothing bounds this window"), plus whether anyone has chased it.
2. Raised about your work — records someone else raised about your firm (another firm, a coordinator, or the system from an injury). You can read them at any state — including rejected — because they are about you. A record somebody messaged in rather than saw wears that on its face: who told the desk, how it reached them (WhatsApp · email · a phone call · in person) and when they sent it, labelled as told to us, beside the declaration stamp. A first-hand record — which is every phone raise — carries none of those three and says nothing.
3. Raised by us — your own firm's raises.

Every row wears its band word — confirmed, awaiting triage, rejected — and two disclosures beside it: a quiet still stopped while the record is open (the crew has not restarted and the record still owes a restart instant), and, on a rejected row, the reason the coordinator gave. Both are there to be read, not acted on: the close is on the Still stopped tile (see below), and the recourse against a rejection is a fresh raise.

A fourth listing, Blamed, sits outside that split: records that name your firm as responsible for someone else's loss — count, crew-hours, and how many you've contested. Its empty state ("No records name your firm responsible") always renders, because the absence of blame is a fact you're entitled to read.

Answering for a count

When a record about your work carries no figure, completing it is one gesture:

1. Open the record from Needs your count and attach the work it stopped — your crews, plant or areas. Picking a permit or a Work line expands to the crew placed under it, pre-ticked and strikeable.
2. Answer the two questions — the gang (defaulting from what you attached, each piece showing its contribution; typing over it makes it your declared figure), and the send-home count.
3. Add evidence — photos, documents — on the same sheet, and save. The figure lands wherever the record is read.

Two things you'll notice are deliberate:

• The count controls only wake up once at least one piece of your work is attached — a number has to rest on something.
• Another firm can propose work but never a count. A safety adviser or coordinator reaching your record may attach your work to it as a proposal — each proposed chip says who proposed it and when — but how many of your people stopped is your firm's answer alone. Your completion is also the endorsement: the refs that survive it become your firm's own word.
• There is exactly one way a count arrives without you typing it, and you are in the room for it. At the coordination meeting a coordinator may record your firm's count only with a named representative of your firm present at the sitting — and it stores as your firm's word, with their name, your firm and the meeting's date on the count's own timeline event, which the record reads back as "spoken by ⟨rep⟩, ⟨firm⟩, at the ⟨date⟩ meeting". A count somebody wrote — in a WhatsApp message, in an email — is never that: it is prose in the description, and the record sits in Needs your count until your firm speaks. Correcting it afterwards is an ordinary later act on your own record.

Closing, and the honest ways out

Work restarting is your firm's fact, so closing is yours too. On the phone the close has its own launcher door — Still stopped, in the My work band right beneath this view, badged with how many of your records are waiting on your word; on the desk it stays on the record's properties panel and the ledger. This view marks which rows are still stopped but offers no verb: one gesture, one home.

• We're moving again closes the record at now (the exact time is editable behind a tap).
• Some are back closes it and opens a follow-on slowdown with a freshly-asked count — a partial return is two different records, not an edit.
• If the closed window spans time your crew wasn't on site — an overnight, a weekend — the close offers to split it into one record per on-site stretch, showing each stretch dated, with set the real end time and no, we ran straight through as first-class alternatives.
• Nothing to declare — we never restarted is a stated control, not an emptied box: the record closes with no restart recorded and contributes no hours, and it says so before you tap.

Mistakes are corrected on the record — window, counts, attached work, evidence — through the same sheet, at any state; a correction to a confirmed record marks it changed since confirm and tells the people who signed it off. Nothing is silently rewritten.

When you're blamed, and when you're rejected

• Contest — if a confirmed record names your firm responsible and you disagree, contest it from the record. The mark travels everywhere the figure does ("…of which 61 contested") but subtracts nothing: it is your firm's voice on the record, not an appeal that freezes the number.
• Re-raise — a rejected record's recourse is a fresh raise, and the rejection notice offers it pre-filled (window start, work, cause). The count is deliberately not pre-filled — a re-raise speaks its numbers afresh. Both records stay readable, linked in both directions, so nobody adjudicates the same claim twice unknowingly.
• Split proposals — if a coordinator had to close your record in your silence, the presence-based split arrives as a proposal with one-tap accept/decline; nothing is accepted for you.

The nil return — saying "we lost nothing"

When the work plan's accounting flags one of your late lines as having no loss record behind it, the view mirrors that flag with a remedy line: file a record, or record that nothing was lost against this line. The second option is the nil return — a dated, signed statement that your firm lost no time against that line. It changes no figure and blocks nothing; it exists so that an empty week reads as an answer you gave, not paperwork nobody got round to.

---

Next: Raising a blocker · Slip & nil returns · Lost time, scene by scene

Blockers & lost time guide: Overview · Reviewing & triaging · Raising · How lost time is counted · The ledger · Your firm's panel · Slip & nil returns · Standing cost · The register · Scene by scene · Reference