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.
How do you choose the review interval?
There is no universal interval for every services project. The practical question is not "How often can we produce a dashboard?" but "How long can this project change before a decision becomes expensive or irreversible?" A team making weekly staffing commitments needs a shorter feedback loop than a stable project reviewed at monthly milestones.
Formal programmes often define their own reporting rhythm. The U.S. Department of Energy's EVMS project-analysis procedure supports its monthly project assessments and begins with data validity before variance and trend analysis. That is evidence of a governed monthly process in a specific context, not a universal rule for professional-services teams.
Use four decision factors
- Delivery volatility: How quickly can role mix, hours, scope, or dependencies change?
- Decision latency: When is the next staffing, client, or commercial commitment?
- Data readiness: When are weekly hours and supported costs complete enough to trust?
- Materiality: How much cost or margin can move between reviews?
Cadence is a management design choice based on these facts. Shorter is not automatically better: reviewing incomplete data daily can create noise, while waiting a month on a fast-moving fixed-price project can delay a useful decision.
An original project margin 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 lead, delivery owner, finance or commercial owner |
| Steady delivery with reliable weekly actuals | Fortnightly | Threshold alert or missed milestone | Project lead and finance owner |
| 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 | Accountable project 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 30-minute weekly agenda
- Five minutes: confirm data completeness and the cut-off.
- Ten minutes: inspect planned and actual hours by resource and period.
- Five minutes: reconcile non-labour 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 four decision factors above 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. Before any servers or applications move, delivery volatility and materiality are both low. A milestone-based cadence, as in the matrix above, fits this stage—reviewing weekly would mostly repeat the same open questions.
- The first migration wave. Once cutover of the first application group starts, undiscovered dependencies and rework routinely change scope and role mix within days. 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
An authorised user manually records weekly actual hours. Managed Margin recalculates supported current figures and can surface configured budget-consumption or margin signals; it does not import timesheets, run external integrations, or make decisions. Start with the planned-versus-actual margin method, then use the detailed weekly review guide and delivery margin workflow.
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 implementation on 24 August 2026.