A token-gated field surface with no login. It shows the checklist for the stage the person is clocked into, reading the same sources the office Gantt reads. Ticking a checkpoint goes through the same server writer, and completing the last one fires the same customer email as a desk-side completion.
Also called: crew app · field checklist · mark it done on site · no login for crew
The crew opens a link. There is no app and no password.
Each crew member gets a token link that opens straight onto the job they are clocked into — no account to create, no password to reset, nothing to install. That is the whole difference between a crew that reports progress and a crew that does not. The screen is built for a phone in direct sun: near-black on white, one action at a time, targets big enough for gloves.
A box ticked in the field is the same box the office ticks
The crew's tick runs through the same server writer as one made at the desk, and completing the last one sends the customer the same email. There is no separate crew app with its own rules to keep in step, and no retyping texted photos and updates into the schedule on Friday afternoon. Where the progress was recorded is not a difference the rest of the system can see.
The crew can say a thing is done; undoing it stays in the office
Completing the last checkpoint on a stage messages the customer, and no phone screen can un-send that. So the field link only ticks forward. If something was closed too early the office reopens it, and finishing the stage again notifies the customer properly the second time.
By default only crew leaders can mark work complete
Every man with the link can clock in, add photos and see what is left, but closing a stage — the act that emails the customer — is limited to crew leaders until you decide otherwise. One switch opens it to the whole crew when you are ready. Someone without the permission is told why, rather than tapping something that silently does nothing.
The field list shows exactly what the office list shows
The crew screen reads the same places the schedule reads, so the two cannot argue. Checkpoints the office marked not applicable appear struck through and are not tappable, and a checkpoint that has since left the stage answers “That's not on this stage any more. Pull down to refresh.” rather than writing to something that no longer exists.
- 1The stage is never sent by the client — it is the stage the man is clocked into
- 2Checkpoint writes go through the same milestone writer the office uses
- 3A stage with no checklist can be closed via the same atomic completion function, whose 'stage just completed' guarantee is enforced in the database, so a double-tap on a laggy phone cannot fire the customer's notification twice
- 4Checkpoints marked N/A by the office are shown struck through and are not tappable
- 5A checkpoint that has left the stage returns 'That's not on this stage any more. Pull down to refresh.'
- 6Rate-limited per IP
A crew lead standing in a finished building had to phone the office and have somebody else tick the box — and that call happened at the end of the week, if it happened at all, so customers heard about Tuesday's work on Friday. Crews tick the work off from their phones, and a crew ticking the last box means exactly what the office ticking it means, down to which email the customer receives. Ticking is one-way: the crew can say a thing is done, and undoing it stays in the office, because completing a stage messages the customer, and a portal that could quietly reverse that would be lying about what has already been sent.
- Field progress not reaching the office until later
- Crew apps that behave differently from the office view
- A field mistake un-sending a customer message
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →