Many projects do not fail because of one big event. Progress slows gradually: deadlines move, responsibilities blur, unresolved risks pile up, and scope expands. Project management guidance stresses monitoring performance, spotting variances from the plan and correcting course before small issues become big ones (Hayes Munson). A monthly review is a simple way to do that.
Monthly sits between the weekly check-in, which tends to focus on immediate tasks, and the quarterly review, which can let problems run for too long. The U.S. Government Accountability Office describes a reliable schedule as a basic management tool because it lets you measure performance against the plan, see variances and judge the effect of changes (U.S. Government Accountability Office).
Why a monthly review helps
- Patterns. One delay may not matter; repeated delays can point to a systemic problem (Hayes Munson).
- Priorities. It is a regular point to ask whether current projects still fit your goals and resources.
- Visibility. A record of completed milestones shows progress against plan.
- Risk. Regular assessment surfaces schedule, resource, budget and dependency risks early (U.S. Government Accountability Office).
Before the review
Hold it on the same day each month. Gather schedules and milestone reports, task records, budget reports if relevant, meeting notes, the risk and issue log, and last month’s review. Keep them in one place.
The six steps
1. Review accomplishments
List milestones, deliverables and major tasks finished last month, and compare them with what was planned.
2. Assess milestone status
A simple traffic-light system keeps it consistent: green means on schedule, yellow means emerging risk or delay, red means off track and needing correction. PMI guidance notes that monitoring tells you when corrective action is needed and when a project can continue as is (Hayes Munson).
3. Identify risks and blockers
For anything yellow or red, name the specific cause: a pending approval, a late vendor deliverable, a resource shortage, a technical dependency, an unmade decision. Assign an owner, a target resolution date and an escalation path. GAO recommends updating schedules with actual progress so risk analysis rests on real data (U.S. Government Accountability Office).
4. Check scope, schedule and budget
Has work been added? Are hours or spending running over estimates? Do changed requirements affect delivery? GAO notes that schedule slippage often affects cost (U.S. Government Accountability Office). Document approved changes.
5. Reprioritize
Rank active work against goals, obligations, resources and expected outcomes. Decide whether to accelerate, maintain, defer or close each item.
6. Set next month’s priorities
Pick three to five measurable objectives, each with a defined outcome, an owner, a target date and the immediate next step.
A simple template
- Wins: completed deliverables, milestones reached, process improvements
- Status: green, yellow or red, with notes
- Risks and blockers: issue, owner, resolution date
- Scope, schedule and budget: approved changes, variances, resource concerns
- Decisions: started, paused, stopped, resources moved
- Next month: three to five outcomes, owners, dates
Common mistakes
- Reporting without deciding. A review should end in decisions and actions.
- Skipping it when busy. Busy periods are when slippage is most likely.
- Tolerating a long-running yellow. It is often a problem developing slowly.
- Too many priorities. Fewer objectives get done better.
- Not checking last month’s decisions. PMI guidance recommends capturing and applying lessons throughout a project, not only at the end (Rowe and Sikes).
Making it a habit
Same time each month, the same template, a short summary to stakeholders, tracking whether decisions were carried out, and adjusting the process itself as you learn (Rowe and Sikes). In my experience, a repeatable review does more to keep work on track than any amount of last-minute problem-solving.