See every
project before
it slips.
A live view of your fleet, captured by the people on site. Imported plan vs. actual, project trajectory, and the empirical numbers your office hasn't had.
On day one, why a project is behind.
Over time, where the time goes.
Know where
the delay came from.
Every behind-by is split three ways: plan gap (Discovered work and incomplete plan), execution gap (phases slower than estimated), external gap (Blocked time). Computed from the taps, never entered. Your office cannot produce this today.
Quantify
the fix.
A slipping project tells you the dose — "+2 for three weeks" — sized from the gap between resource demand and observed progress. Where those people come from (own crew, subcontractor, a project running with slack) is your call. The tool sizes the need; you make the move.
React in days,
not at the wash-up.
Every day the system projects each running project against its plan and surfaces the at-risk ones. Coordinators see the drift before the customer call — not in the wash-up two weeks later.
Build the
empirical record.
Every completed phase hardens a fleet-wide record per phase type. Over months, you see how work in your business actually behaves — durations, spreads, where it blocks. Phase by phase, project by project. The empirical reference your office hasn't had.
Two surfaces.
Five events.
One plan.
Supervisor signs in.
Team taps anonymously.
The site supervisor signs in once at the start of a project. The tablet sits on a stand on the day view; the team taps from there. Phase events carry no identity. Numeric entry is a stepper — never a keyboard.
Lunch and end-of-day auto-pause. A Block is specifically an external cause: materials missing, decision pending, access denied. Unplanned work is captured as a new phase — never folded into a planned one.
Back-office.
Fleet first.
Coordinators and leaders sign in. The default view is the whole fleet — every running project at a glance, with at-risk surfaced.
Drop in the Gantt your office already produces. Tag each phase to a canonical type from your catalog.
Live trajectory per project. Overrun split into plan / execution / external gap. Daily at-risk projection.
A slipping project tells you what it needs ("+2 for three weeks"). Where those people come from — own crew, subcontractor, a project running with slack — is your call. The tool sizes the need; you make the move.
Every completed project hardens a fleet-wide record per phase type. Over time, you see how work in your business actually behaves — empirical, not from memory.
No actor on phase events. Schema doesn't allow it. Tap reliability follows from trust.
Imported once. Never edited in the tool. Divergence stays measurable against what the office actually said.
Captured as its own phase, never folded into a planned one. The plan stays accountable to itself.
Alerts, inactivity, attribution — computed per project, never per supervisor.