Review delivery exceptions

Step by step

1. Open the exception review Project Manager

   Project Manager uses Exception Triage to inspect overdue milestones, overdue tasks, fixed-but-unverified issues and leading open risks. Follow the direct path to the underlying record before assigning the next action.

   • Select work needing attention
   • Updates Milestones, Tasks, Issues, Risks

2. Confirm ownership and impact Project Manager

   Check who owns the work and how it affects the project or work package. Delivery Lead examines material exposure while the manager distinguishes an overdue date from a reported fix that still needs verification.

   • Assign the next action and assess exposure
   • Updates Projects, Work packages, Team members, Risks

3. Record the actual outcome Project Manager

   Milestone and risk owners supply evidence of the outcome and mitigation work. Project Manager records milestone results and risk updates; QA Engineer verifies fixed issues. Keep original dates and earlier decisions available so the review can explain what changed.

   • Record milestone and risk updates; verify issue fixes
   • Updates Milestones, Issues, Risks, Record attachments

4. Replan where needed Project Manager

   Project Manager changes the working task plan when the evidence calls for another schedule. Submit the corresponding baseline revision for feasibility checking and obtain the work-package decision through the normal handoff.

   • Prepare a checked revised commitment
   • Updates Tasks, Schedule baselines, Review decisions

5. Inspect action evidence Project Manager

   Read failed and pending operation receipts against their referenced work. A visible status does not establish that every requested update succeeded; investigate the actual record and result before repeating an action.

   • Explain the recorded action outcome
   • Updates Operation receipts, Review decisions

Project Manager

, Delivery Lead, QA Engineer and Developer.