Ogden Division — On-Time Diagnostic: Root Causes

Job Scheduling & Milestone Info, Task Pay Info, Tasks General, and Unexpected Orders — Ogden Division, joined job-by-job

Methodology — where "on time" comes from

"Target End Date" is pulled from TrackVia's Job Scheduling & Milestone Info report (falling back to Original Target End Date when the current target isn't set) — this is Cascade's own internal schedule commitment, not the builder-facing Client End Date, which typically has a few extra days of slack built in. "On time" means the job's Major Tasks Completion Date fell on or before that target. Any overage, even a single day, is currently scored as "Late" — there's no grace window built in today.

Vinyl-primary houses excluded. 12 jobs were removed because vinyl is the actual exterior finish (a logged Vinyl task with no stucco or masonry base-coat task) rather than a minor accent — vinyl runs on a different process and was skewing the diagnostic. All 12 were in Railrunner (DAI Construction). Houses with a Vinyl task that also have stucco/masonry work (vinyl used only as a trim or accent material) are kept in.

1. How close are we, really?

Ogden's job volume ramped up steadily — the first sustained month with meaningful volume (10+ scored jobs) was 2026-01. Everything below uses 2026-01 through the most recent complete data (262 jobs) — earlier months are excluded because 1-5 jobs/month isn't a meaningful on-time rate.

125

On time (48%)

137

Late (52%)

10.5

Avg days late (late jobs)

Median days late

Verified again, with more history: since 2026-01, on-time performance has held in the 48% range essentially every month — this isn't a one-off bad quarter, it's the steady state. And it's not a "single day over" problem: only 17 of 137 late jobs (12%) missed by just 1-2 days. Most late jobs are late by a lot.

How late, when late?

Days over target	Jobs	% of late jobs
1-2 days	17	12.4%
3-5 days	33	24.1%
6-10 days	38	27.7%
11-20 days	32	23.4%
21+ days	17	12.4%

2. A data quality flag before the diagnosis

Your instinct about the hours-worked stat was right. 30% of all logged task duration records (Start Date/Time to Completed Date/Time) come back as exactly 0 hours — a strong sign that crews are logging the start timestamp at the same time as completion rather than when work actually began. That makes raw "hours worked per task" unreliable at the individual-task level. To work around it, the analysis below leans on completion-to-completion gaps (how much calendar time passes between one logged task finishing and the next one finishing) instead of task duration — that signal survives the bad start-time data because it only depends on completion timestamps, which crews log more reliably.

3. Where the time actually goes: idle time between tasks

For each job, this looks at when each task got marked completed — Housewrap done, then Siding done, then Soffit/Fascia done, etc. — and measures the calendar time between one completion and the next. Add those gaps up across the job and you get "idle time": days where nothing was crossed off, even though the job wasn't finished. Restricted to tasks completed on or before Major Tasks Completion Date, so warranty/VPO/ punch-list work weeks later doesn't distort the picture.

Example — Job 223, Riverside Estates (Fieldstone Homes), 29 days late (target Apr 8, finished May 7): Mar 19 Housewrap completed | 24.8 days pass — nothing else logged as done Apr 13 Siding completed | 14.9 days pass Apr 28 Soffit/Fascia completed | 9.2 days pass May 07 Gutters completed → Major Tasks Completion ~49 days of idle time, on a job whose whole visible sequence spans ~49 days. No single task ran long — the house just sat waiting between crews for most of the build.

42 days

Avg total idle time — Late jobs

25 days

Avg total idle time — On-time jobs

Late jobs spend about 17 more days sitting idle between task completions than on-time jobs do — this is the clearest, most consistent signal in the data. It's not that crews take longer on any one task; it's the waiting between tasks that adds up.

Handoffs with the biggest late-vs-on-time gap (min. 5 jobs each side)

Task handoff	Avg gap — Late	Avg gap — On time	Difference
Rock → Vinyl	13.9d (6)	8.5d (5)	+5.4d
Rock → Soffit/Fascia	7.2d (8)	2.6d (14)	+4.5d
Soffit/Fascia → Remove Tarps	5.4d (6)	2.5d (6)	+2.9d
Set Scaff → Siding	5.0d (5)	2.5d (6)	+2.5d
Siding → Set Tarps	5.2d (11)	3.1d (6)	+2.1d
Gutters → Paint	8.9d (5)	7.2d (8)	+1.7d
Soffit/Fascia → Stucco Color	3.7d (26)	2.2d (24)	+1.5d
Paper/Wire → Scratch Coat	5.6d (19)	4.1d (24)	+1.5d
Siding → Vinyl	1.5d (5)	0.0d (5)	+1.5d
Remove Scaff → Gutters	4.4d (45)	3.0d (18)	+1.4d

4. Common denominators checked

Factor	Late jobs	On-time jobs	Verdict
Avg # unexpected/will-call POs	6.0	4.6	Real signal — late jobs order more
Avg unexpected PO $ spend	$1,549	$987	Real signal — late jobs cost more in will-calls
Started later than originally planned	40%	39%	Not a driver — same rate either way
Started 8+ days later than planned	20%	22%	Not a driver — same rate either way
Idle time between tasks (core sequence)	42d	25d	Strongest signal
Jobs with a task at 2x+ typical duration	83%	82%	Inconclusive — duration data too noisy (see above)

Bottom line: the clearest common denominator on late jobs is idle time between tasks, not any single task running long. Extra will-call POs travel with lateness too — consistent with the Meritage Westwood Estates siding-reorder pattern you flagged earlier. A late start doesn't doom a job, and starting on schedule doesn't protect one — about 4 in 10 jobs start later than originally planned, and that happens at almost the same rate whether the job goes on to finish on time or late. What differs is what happens in the middle, once work is underway.