Crew schedule table

Crews ranked by average variance against baseline, with stages completed of started, on-time rate and total days over.

What it is

The tabular companion to the Field Performance charts, inside settings. Sorted best variance first. Stages read as completed/started so the sample is on screen. An (i) on the heading tells the reader to check the run count before drawing a conclusion. Work with no crew assigned gets its own row rather than being dropped.

Also called: crew on-time rate · which crew is behind · crew days over

See it
Crew schedule table
Apr
May
Jun
Jul
Ivy Brubaker — Hobby Shop
Framing
Ivy Brubaker — Hobby Shop
Concrete
Ivy Brubaker — Riding Arena
Trim
Marlin Hoover — Hobby Shop
Framing
Marlin Hoover — Hobby Shop
Concrete
Framing crewConcrete crewTrim crew
The 'Crews' table: Crew / Stages (12/17) / On time 71% / Avg variance +1.4d / Days over 9d. StageAnalyticsTab.tsx. Sample data — no customer information appears here.
How it works
  1. 1Stage logs are grouped by crew; only rows with a variance count toward the averages.
  2. 2On-time rate = stages with variance at or below zero ÷ completed stages.
  3. 3Days over sums only the positive variances.
  4. 4Crews with no stages in the window are filtered out.
Why we built it

The heading's (i): 'Ranked by average variance against baseline. Read the run count first — a crew with two stages behind it is an anecdote, not a trend.' Keeping the unassigned bucket visible matters because unassigned work is itself a scheduling finding.

The problem
  • Crew comparison required reading the Gantt job by job.
  • Unassigned stage work disappeared from every rollup.
Sound familiar?
What you get
On-time reliability per crew in one sortable table.
Unassigned work is visible as its own line rather than silently excluded.

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 →