AgencyOps
Agency Project Health Metrics You Should Track Weekly
Most agencies discover delivery problems when a client escalates—not when the data still allows a cheap fix. The shift is a disciplined weekly review built on agency project health metrics that connect milestones, burn, scope, and margin on the same project record. This guide lists the metrics worth tracking every week, how to define them, and how distributed teams keep signals honest across regions and timezones.
Why weekly project health metrics beat monthly reviews
Monthly finance closes are essential for P&L—but too slow for delivery intervention. Agencies searching for project health dashboard metrics, agency delivery KPIs, and weekly project status metrics usually need earlier warning while re-planning is still cheap.
- Lead time to fix: slipping milestones often show up 2–3 weeks before a missed client date.
- Scope containment: unapproved work accumulates daily; weekly review caps exposure before write-offs.
- Capacity rebalancing: overload signals need action this week, not next quarter.
- Cash alignment: invoice milestones tied to delivery reduce AR surprises when reviewed weekly.
The eight agency project health metrics to track every week
| # | Metric | What it tells you | Typical owner |
|---|---|---|---|
| 1 | Composite health status (RAG) | Roll-up risk for leadership scan | PM / delivery lead |
| 2 | Milestone hit rate | Schedule discipline vs. plan | PM |
| 3 | Schedule variance (days) | How far critical path has slipped | PM |
| 4 | Blocker age & count | Dependencies and decisions stalling work | PM + accountable owner |
| 5 | Burn vs. plan (%) | Effort trajectory vs. budget | PM + finance |
| 6 | Scope change exposure | Unapproved work and missing change orders | PM + account |
| 7 | Margin vs. plan (%) | Commercial health of the engagement | Finance + PM |
| 8 | Invoice–milestone alignment | Whether billing matches shipped checkpoints | Finance |
Below: definitions, thresholds, and how each metric fits a weekly project health review.
1. Composite health status (RAG)
A single RAG status (green / amber / red—or on track / at risk / delayed) lets leadership scan a portfolio in minutes. The rule: RAG must be driven by thresholds on metrics 2–8, not gut feel.
Suggested threshold rules
- Green (on track): milestone hit rate ≥ 90% for the period, schedule variance ≤ 3 days on critical path, burn within ±10% of plan, no scope items over threshold without change order.
- Amber (at risk): one dimension breached; mitigation owner named this week.
- Red (delayed / critical):client-facing date at risk, burn > 15% over plan, or margin below floor with no approved recovery plan.
2. Milestone hit rate
Milestone hit rate = milestones completed on or before baseline date ÷ milestones due in the period. Track rolling 4 weeks and current week. Agencies with dependency-aware planning should weight milestones on the critical path higher than internal housekeeping dates.
Pair with our project management guide for agencies for milestone design that maps to client commitments and invoice lines.
3. Schedule variance (days)
Measure schedule varianceon the next client-visible milestone: planned finish minus forecast finish (in business days). Positive variance means late. Flag any project with critical-path variance > 5 business days for leadership attention.
4. Blocker age and count
Blocked tasks are where agencies lose calendar time without losing utilization. Track:
- Open blocker count on critical path tasks
- Median blocker age (days since flagged)
- Blocker owner (must be a person, not a team name)
Weekly rule: any blocker older than 3 business days on a client-visible milestone escalates to amber; older than 5 days escalates to red unless a dated resolution exists.
5. Burn vs. plan (%)
Burn vs. plan compares actual effort (hours or loaded cost) to the approved budget curve for the same period. Use cumulative burn for fixed-fee work and period burn for retainers with monthly caps.
| Signal | Likely cause | Weekly action |
|---|---|---|
| Burn under plan, dates slipping | Wrong work prioritized; blockers hidden | Reconcile task board to critical path |
| Burn over plan, dates on track | Scope creep or inefficient staffing mix | Scope review + change order or reforecast |
| Burn over plan, dates slipping | Recovery plan required | Leadership decision: descope, add fee, or absorb |
Deep dive on budgets and burn cadence: project budget guide for agencies.
6. Scope change exposure
Scope change exposure quantifies work in flight that is not covered by baseline scope or an approved change order. Track:
- Hours (or points) logged to “client request” / unscoped buckets this week
- Open change orders pending client signature
- Deliverables added to the board without milestone linkage
Weekly target: zero net new unapproved scope on fixed-fee projects; retainers document scope band exceptions in the account record. Connect to hidden profit leaks when exposure persists month over month.
7. Margin vs. plan (%)
Delivery health without commercial health is incomplete. Margin vs. plan compares forecast contribution margin (revenue minus direct delivery cost at loaded rates) to the margin assumed at kickoff. Update forecast weekly when burn or scope shifts—not only at phase gates.
Flag projects forecast more than 5 points below plan for amber; more than 10 points for red unless a signed recovery path exists. Roll up to client level monthly; review project level weekly.
8. Invoice–milestone alignment
Invoice–milestone alignment checks whether billing events match delivery checkpoints: milestones marked complete should have corresponding invoice lines sent or scheduled within your billing SLA (often 3–5 business days).
- Completed milestones with no invoice queued
- Invoices sent before acceptance criteria met (dispute risk)
- Change orders approved in delivery but not reflected in billing schedule
Finance should join the weekly health review for the top 20% of projects by revenue or risk—not every standup.
GEO optimization: weekly health metrics for distributed delivery teams
Multi-location and follow-the-sun agencies need the same eight metrics with two GEO extensions reviewed weekly at regional pass, then rolled up firm-wide:
| GEO metric | Definition | Why it matters |
|---|---|---|
| Cross-region handoff quality | % of handoffs with required brief fields completed before shift end | Prevents duplicate work and invisible blockers across timezones |
| Timezone-adjusted blocker age | Blocker age excluding non-overlap hours | Stops penalizing APAC teams for US-only decision delays |
| Regional status consistency | Same RAG definition applied in each office | Avoids “green in London, red at HQ” for the same project |
| Local calendar adherence | Capacity plan respects regional holidays and leave | Stops false green health when teams are actually unavailable |
Search queries such as global agency project tracking, remote team project health metrics, and multi-office delivery reporting map to this layer: one KPI dictionary, regional slices, shared engagement record.
Weekly project health review ritual (45 minutes)
- 0–5 min: Confirm data freshness (milestones, time, blockers updated in last 5 business days).
- 5–20 min: Walk reds and ambers only—metric breach, owner, mitigation due date.
- 20–35 min: Review new ambers from greens; validate threshold rules, not narratives.
- 35–40 min: Capacity conflicts on red/amber projects (next two weeks).
- 40–45 min: Log decisions; sync invoice–milestone exceptions to finance queue.
Embed this inside the broader weekly operating review so pipeline and AR do not live in a separate conversation.
How to segment the portfolio so the weekly review scales
Not every project needs the same depth every week. Use tiers:
| Tier | Criteria | Weekly depth |
|---|---|---|
| Tier A | Top revenue, new logos, red/amber last week | Full eight metrics + client context |
| Tier B | Active delivery, green last week | RAG + milestone hit + burn spot-check |
| Tier C | Maintenance / low burn | Exception-only (auto-alert on breach) |
Implementing metrics without dashboard sprawl
- One project record linking client, milestones, time, and invoices (stable IDs).
- One KPI dictionary—definitions live in a doc everyone cites, not in hallway lore.
- Automate collection where possible; reserve the meeting for exceptions and decisions.
- Audit monthly: pick three projects and verify metrics manually—calibration prevents gaming.
FAQ: agency project health metrics
- What are the most important project health metrics for agencies?
- The highest-signal weekly set is composite RAG status, milestone hit rate, schedule variance, blocker age, burn vs. plan, scope change exposure, margin vs. plan, and invoice–milestone alignment. Add GEO handoff quality if teams are distributed.
- How is project health different from project status?
- Status is a narrative update. Health is a threshold-based view across schedule, effort, scope, and margin. Status without metrics tends to stay green until a date is missed.
- Who should own the weekly project health review?
- A delivery lead or PMO runs the session; project managers own metric accuracy for their engagements. Finance joins for margin and billing alignment on Tier A projects.
- What RAG thresholds work for most agencies?
- Start with the green/amber/red rules in this guide, then calibrate after two cycles against your actual slip and write-off history. Thresholds should be firm-wide, with regional slices using the same definitions.
- Can we track health in spreadsheets?
- Spreadsheets work for pilots under ~15 active projects. Beyond that, manual entry duplicates the tool sprawl problem. Prefer metrics pulled from the system where milestones, time, and invoices already live.
- How do project health metrics tie to profitability?
- Burn, scope exposure, and margin vs. plan are leading indicators of profit leaks. Weekly delivery review catches them weeks before month-end margin reports.