Schedule, health and baselines

The Schedule page shows a health verdict worked out from your records by fixed, visible rules: overdue milestones, sequence contradictions, critical issues, high-scoring risks, at-risk milestones, blocked and overdue work. It is never AI, never guessed and never green on thin data, and it always lists its reasons. A health you set by hand is shown next to it, not replaced.

Each finding names the records and dates it rests on and links to them. Checks include a milestone dated before the milestone it depends on, work due after its milestone, dependencies arriving too late, overdue items, completed milestones with open work, high risks with no mitigation and at-risk milestones with no risk recorded.

Open a milestone and use Schedule dependencies to say which milestones must happen first. Loops and links across projects are refused. The timeline draws the links; a red dashed arrow means the order and the dates disagree.

Follows the links back from the latest milestone through the latest predecessors. It is not a formal critical path: the records hold no durations.

A project manager can take a baseline: a permanent snapshot of milestone dates and the budget. Later you can compare against it and see which milestones slipped and by how many days. A baseline can never be edited or deleted.