Milestones and site exceptions

Site milestones carry a name, due date, project, owner, notes and a status of Pending, Met or Missed. They are checkpoints in the project programme. The project manager uses them alongside packages and tasks to decide what needs action before a date passes. A milestone status is a concise delivery signal; the related evidence and review decision provide the detail when another team asks how it was reached.

The Site Exception Triage page draws together overdue milestones, overdue site tasks, fixed-but-unverified RF is and leading construction risks. Each item carries its owner, age and a path to the source record. This gives the site manager a single opening agenda while leaving the work in its proper project, task, milestone, issue or risk record. Clearing the queue means resolving the source condition, not dismissing a separate summary item.

• Milestone owner. Assign the checkpoint to a crew member who can report whether the work has reached its expected state.
• Exception queue. Start the daily review with overdue dates and unresolved verification, then open the underlying record for the next decision.
• Evidence beside status. Link inspection files to the relevant subject and record any review decision separately from the milestone label.

Agree which checkpoints matter for site delivery and how a milestone due date relates to the package schedule. Decide who may mark a milestone Met or Missed and what evidence the team expects before a Met decision. If a milestone feeds a payment handoff, name the separate commercial process and its owner; the milestone record itself is the site checkpoint. Establish who reviews fixed issues waiting for verification, because that queue should not become a resting place for closed-out work.

Bring a pilot project with a due milestone, a task approaching its due date, a fixed issue awaiting inspection and an open risk. Set owners for all of them. Walk each row from the exception page to its source record and check that the site manager can tell which person should act next.

The formwork checkpoint is due on Thursday. On Friday morning it still reads Pending, so it appears in the site exception queue. The site manager opens the milestone, checks its owner and notes, then follows the associated project tasks. One task is overdue because inspection evidence has not been reviewed. The quality inspector opens the linked file, records a decision against the intended subject and returns the result to the project manager. The manager can then decide whether the checkpoint is Met or Missed using the actual site evidence.

In the same queue, a drawing issue is Fixed but has not been Verified. That item stays visible until the quality inspector checks the correction. A separate high-rated risk remains with the project manager for mitigation. The team can discuss all of them in one meeting without treating one status field as proof that every other decision was made.

• Site Milestones At Risk — Pending and missed checkpoints by project, owner and due date.
• Site Exception Triage — Overdue milestones and tasks, unverified fixed issues and leading risks with links to their records.
• Blocked Site Tasks — Work held before it can reach the next checkpoint.

Milestone and exception review follows the daily queue. Review decisions and evidence follows the supporting files.