REQ-FUN-105
Schedule slippage detection vs approved baseline
What
For every activity in a project with an approved schedule baseline, system SHALL compute and expose schedule_variance_days (actual_finish - baseline_planned_finish) and slip_status (on_track / at_risk / slipped) via REST, MCP, and the web UI.
Why
established project management guidelines Control Schedule requires per-activity comparison against the baseline; slippage is the primary signal that triggers corrective action or a schedule-affecting Change Request.
How
Slippage view computed at read-time from current activity rows + most recent approved baseline; thresholds (e.g. >0 days late = at_risk, >5 days late = slipped) configurable per project via the config-merge system (REQ-FUN-100); slipped activities raise a row in the issue log.
Done when
Endpoint returns per-activity variance + status; web UI renders a slippage column on the schedule table; threshold change via project config re-classifies activities on the next read.
Out of scope
Predictive slippage (covered by REQ-FUN-110); slippage on milestones beyond activities.
established project management guidelines Mapping
established project management guidelines Control Schedule output - work performance information on variance.