Orientation for a lane in staged rollout
The construction lane is on the roadmap: scope is set, and it opens by request in a staged rollout. This page describes the record discipline the lane is built around — and states plainly what is and is not available.
Enter once
Daily site logs, photos, and progress entries are captured in the field and sync directly to back-office accounting. One entry serves both worlds: the crew lead writes the day once, and the office reads the same entry. Approved logs flow into billing runs without re-entry.
Verify before dispatch
Subcontractor licensing and workers' compensation coverage are checked before dispatch is permitted. Verification is a gate with a record — who was cleared, against what documentation, when — so compliance is answered at the moment of assignment, not reconstructed during a claim.
Sign on site
Change orders draft, price, and capture signature from the field with the full audit trail attached. The ledger updates as the signature lands, so scope changes are priced as business decisions on the day they happen — not reconstructed from memory the following week. The field note the field day, entered once follows one day through the same discipline.
Weather-aware windows
Forecast triggers flag at-risk crew windows ahead of time — designed to protect safety and schedule together. Flags are signal for a named owner, not automatic rescheduling.
Availability boundary
The substrate underneath this lane — sign-on, per-brand isolation, approval gates, the shared ledger — is live in other verticals today. The field-workflow layer itself is staged and opens by request. Live job, dispatch, and change-order state belongs to the authenticated console; this page is orientation, not an availability statement.