Site Progress & Schedule Control
Find sustained progress shortfalls and approvals waiting too long. Trace each delay to its weekly records.
Delayed activities
Historical flags, ranked by longest streak then lowest mean ratio within that streak. “Weeks behind” means consecutive weeks below 0.85, not a forecast finish delay. Select any activity for its weekly evidence.
Activities without a qualifying delay
Stuck submittals
No approval date and more than 21 days open, ordered by age. Days open and status are shown exactly as supplied.
Definitions and validation
Progress ratio = actual % complete ÷ planned % complete for each weekly record. An activity is flagged when the ratio is strictly below 0.85 for at least two consecutive weekly dates, seven days apart, anywhere in its recorded history. Missing weeks or a zero planned percentage break a streak. Calculations use unrounded source values.
Latest planned and actual percentages refer to each activity’s latest recorded week. “Weeks behind” is the longest qualifying streak. For equal longest streaks, lower mean ratios rank first, followed by activity ID. Historical flags remain visible even when the latest ratio has recovered. This is a progress proxy, not an earned-value SPI or critical-path delay forecast.
Model accuracy is reported as precision (true positives / all flagged activities) and recall (true positives / all answer-key-positive activities). An activity is answer-key positive if any of its weekly row_id records has is_delayed = Y. Labels are used only for validation, never to generate predictions. These are in-sample synthetic checks, not held-out model performance.
The stuck-submittal rule uses approved_date and days_open; status is displayed for context and does not override that rule. No current-date recalculation is applied. Project IDs are used because no project-name dimension was supplied.