Review project margin often enough to act before the next material delivery or commercial commitment. Weekly reviews suit active, volatile work; fortnightly reviews may suit steadier delivery; monthly reviews can support portfolio governance. The right cadence also requires complete actuals, a defined cut-off, a named owner, and an exception process between scheduled reviews.
Terms used in this guide. cost: the expense included in the stated project model; margin: revenue left after the included costs; margin percentage = that amount / revenue × 100; baseline: the approved original plan kept for comparison; forecast: recorded actuals plus the remaining plan, a calculation and not a prediction.
In plain words
Review cadence is how often you check a project’s margin. The right rhythm depends on how fast the project can go wrong: weekly for a fast, fixed-price job; every two weeks for steady work; monthly for a portfolio view. Reviews only help if the hours and costs are up to date when you hold them.
Who this helps: Project managers, delivery leads and finance partners who set up reviews.
Questions this guide answers:
- How often should you review project margin?
- What should a margin review cover?
- Weekly or monthly project reviews: which is better?
Margin words: gross, contribution, managed margin, budget, forecast and the roles named here are defined once in the margin vocabulary.
Start with a PMO lead and twelve projects
A PMO lead is responsible for twelve projects and cannot review them all weekly. She sorts them: a few fixed-price jobs that are changing quickly, most that are steady, and a few long, stable ones. Each group gets a different rhythm, with an extra review when staffing, scope, rates or dependencies change. The matrix below is that sorting rule.
A project margin review cadence matrix
| Project condition | Starting cadence | Trigger for an interim review | Primary participants |
|---|---|---|---|
| New, short, or rapidly changing fixed-price delivery | Weekly | Material staffing, scope, rate, or dependency change | Project manager, delivery lead, finance |
| Steady delivery with reliable weekly actuals | Fortnightly | Threshold alert or missed milestone | Project manager and finance |
| Long, stable project with formal monthly close | Monthly | Unplanned cost, approved change, or significant hours variance | Project and portfolio governance |
| Paused or low-activity work | Milestone-based | Restart, new commitment, or new cost | Project manager (accountable owner) |
Treat the table as a starting framework, not a benchmark. A small but strategically sensitive engagement may need closer review than a larger, predictable one. Local accounting, contract, regulatory, or client obligations can also set minimum requirements.
What should happen before, during, and after the review?
| Stage | Control | Output |
|---|---|---|
| Before | Close hours through the cut-off; capture supported costs; identify missing inputs. | A labelled data set and exception list. |
| During | Compare the same period and cost basis; trace resource and cost drivers; read spend beside progress. | Material explanations and decisions. |
| After | Record action, owner, due date, and any approved baseline change. | An auditable decision record and next review date. |
A weekly agenda (30 minutes for a project with changes; 15 minutes when nothing material moved)
- Five minutes: confirm data completeness and the cut-off.
- Ten minutes: inspect planned and actual hours by resource and period.
- Five minutes: reconcile non-labor costs, budget consumption, and completion context.
- Five minutes: explain material project margin variance.
- Five minutes: record decisions, owners, and exceptions that need escalation.
A review can be shorter when nothing material changed. Preserve the discipline by documenting that the cut-off and checks were completed rather than holding a meeting only to fill a calendar.
Use exceptions between scheduled reviews
Cadence and alerts solve different problems. The meeting provides a regular interpretation and decision forum; a threshold or material event can prompt review sooner. An alert should route attention, not declare a root cause or take an automatic commercial action.
When should the cadence change?
Reassess the interval when the project enters a new phase, replaces a key resource, receives an approved scope change, misses a milestone, changes its cost profile, or repeatedly arrives at review with incomplete actuals. A shorter interval may be temporary while a risk is active. A longer interval should follow evidence that delivery and data are stable, not meeting fatigue.
Track whether reviews lead to timely decisions, whether material issues are first found between meetings, and whether the data is complete by the cut-off. Those observations are more useful for tuning the cadence than the number of meetings held.
How cadence should shift across a cloud-migration project
A cloud-migration project is a useful test of the matrix above (how volatile the work is, how much money is at stake, how good the data is and how soon a decision is needed) because its volatility and materiality change sharply from one stage to the next, even though the contract and team stay the same.
- Discovery and planning. Set the cadence from the decisions and uncertainty in this engagement. Predictable, low-spend investigation may fit milestone reviews; an expensive or uncertain discovery phase may need weekly or more frequent checks. The phase name alone does not establish low risk.
- The first migration wave. Once cutover of the first application group starts, undiscovered dependencies and rework can quickly change effort and role mix, even when the contracted scope has not changed. Move to the weekly cadence the matrix recommends for new or rapidly changing fixed-price delivery, before the first wave, not after problems appear.
- A mid-program scope change. The client adds two more applications to the migration list partway through a wave. That is exactly the kind of material scope change the matrix lists as a trigger for an interim review—do not wait for the next scheduled meeting to reconcile the budget and plan.
- Cutover weekend. Materiality spikes sharply for the hours around the actual go-live, even on an otherwise fortnightly project. A short, focused check-in through the cutover window is proportionate; it does not need to become the project's new standing cadence.
- Post-migration hypercare. Once applications are stable in the new environment, lengthen the interval back toward monthly or milestone-based review, following the guidance above on evidence of stability rather than meeting fatigue. Where several migration waves or client environments are being tracked together, portfolio-level margin rollups become more useful than another individual project meeting.
Limitations and implementation checklist
- A frequent review cannot compensate for missing or late actuals.
- Portfolio cadence should not erase the need for project-level resource detail.
- Actual-to-date figures do not predict the final margin.
- Manual percent-complete context is not the same as formal earned value.
- Meeting frequency is not a substitute for clear decision authority.
Document the cut-off, input owner, reviewer, materiality threshold, participants, decision rights, and exception trigger. Revisit the cadence after a major scope, staffing, or delivery-phase change.
How Managed Margin supports the rhythm
In Managed Margin, weekly timesheets are recorded and approved, expenses are posted, and the baseline, actual to date and forecast are recalculated. Guidance cards flag time that still needs recording or approval, and a margin that is falling behind plan; the product does not make the decision for you. Start with the planned-versus-actual margin method, then use the project margin review checklist and project margin tracking software.
- Project Budget Consumption: Formula and What It Tells You
- How to Manage Fixed-Fee Project Margins in Consulting
At the office: Hye-jin sets the rhythm
An illustrative story with invented figures, to show how the idea works in a real office.
Hye-jin, a PMO lead, manages 12 projects. She sorts them: three are fixed-price and changing quickly, six are steady time-and-materials work and three are long, stable projects.
She sets weekly 15-minute reviews for the fixed-price three, fortnightly reviews for the steady six and a monthly check for the long, stable three. Every review starts with the same question: are the hours up to date?
After a month she changes one project from fortnightly to weekly because its variance jumped. The rhythm is not fixed; it follows the risk.
Who sets the review rhythm, and who attends?
| Step | Owner | Checkpoint |
|---|---|---|
| Sort the projects | PMO lead | Each project is classed by volatility and materiality |
| Choose a starting cadence | PMO lead with delivery heads | Weekly, fortnightly or monthly, with the reason |
| Define triggers | Delivery head | A staffing, scope, rate or dependency change brings an interim review |
| Run and improve | Project managers | Missing actuals are fixed first; the rhythm is revisited when risk changes |
Frequently asked questions
How do you choose the review interval?
By how fast the project changes and how soon the next commitment arrives. Shorter when risk is high.
Does cadence change over a project?
Often. Review more often at stage gates, after changes and when variance appears.
How often should a project margin review happen?
As often as it takes to act before the next commitment: weekly for new, short or fast-changing fixed-price work, less often for stable work, plus an extra review whenever staffing, scope, rates or dependencies change.
Continue the sequence: guides to read next
- Weekly Project Margin Review: Checklist and Actions: what to do in the review
- Project Margin Variance: Formula, Example and Causes: how to read what it shows
- Project Margin Rollups: Formula & Example: the portfolio view of the same rhythm
- Budget Consumption vs Percent Complete: Reading Both: why budget used and work complete are different measures
Sources and methodology
- U.S. Department of Energy, Earned Value Management System and Project Analysis Standard Operating Procedure. Used as an example of a governed monthly assessment process and its data-validity-first analysis sequence; it is not presented as a universal cadence.
- Cadence recommendations and the decision matrix are Managed Margin editorial frameworks, not research benchmarks. Product statements were reviewed against the current Managed Margin application on 26 September 2026.