Planview Blog

Leading the conversation on digital connected work

People of Planview

Who Decides When a Project Needs More Capacity Than You Approved?

A simple rule for who makes the call, and how to bring it to leadership.

Published By Jeffrey Yeager
Who Decides When a Project Needs More Capacity Than You Approved?

A project lead tells you on a Thursday that their estimate was off and the work needs a few more hours a week than planned. You find a gap in the team’s calendar and move someone over for a while. The project stays on track, nobody has to sit through a meeting, and you move on to the next item on your list.

Most resource managers and PMO leads have made that call, and in the moment it is usually the right one for the project. It also decides something for the whole portfolio, and the people who own the portfolio never hear about it. This post covers how to set up a simple rule for who makes that call, and how to bring the conversation to leadership when it belongs there.

What absorbing an overrun costs you later

Absorbing an overrun moves capacity from one project to another without anyone approving the move. The project that gave up people starts to slip, while the leaders who approved the roadmap are still looking at a plan that no longer matches the work. Runn’s 2026 research found that only 9% of organizations fully trust their resource data, meaning most leadership teams evaluate roadmap health with numbers they already doubt.

The bill can add up fast. In a Planview modeled example, a single approval that puts five projects on the same three engineers could cost roughly $345,000 in one quarter, spread across attrition, delayed revenue, sunk costs, and lost productivity.

The resource manager is often the first to see it building. A tripwire is how they make sure the capacity decision behind that cost goes to the right person.

A simple rule: the bigger the variance, the higher it goes

A capacity tripwire is an agreed-upon threshold that sends a decision to the right person once a change crosses it. For capacity, the threshold is measured in people’s time: forecast hours minus approved hours, divided by approved hours. A project approved for 200 hours a month that now forecasts 230 is 15% over.

Variance against approved hoursWho decidesWhat it looks like
Under 5%Resource managerMinor adjustments and small trade-offs, covered from internal contingency
5% to 10%PMO directorA change that needs a decision above the resource manager but short of the steering committee
Over 10%, or any impact on another projectGovernanceA trade-off that needs an explicit decision

What can governance decide once you escalate?

Governance has three options, and choosing one starts a deliberate decision. Which work slips, what gets cut, and where freed capacity goes all still need an owner.

  • Approve the extra resources and name the project that absorbs the trade-off. Which work slips, and by how much? That answer belongs in the room.
  • Deny the extra resources and decide what gets cut so the project can finish within what’s available. Reduced scope is a real outcome, and someone has to decide what it means.
  • Cancel, after checking whether what has been delivered is worth shipping, and direct the freed capacity somewhere. Stopping one project only helps if the capacity goes to work that matters more.

Absorbing the overrun quietly still makes a decision, and the work that slips gets chosen by default, with nobody owning it.

Want a clearer view of capacity before the next overrun?

Watch the on-demand webinar From Overcommitted to In Control: Optimizing Resource Management, a 45-minute session with Q&A on seeing capacity clearly and using it to guide approvals.

How do you bring it to leadership?

A specific decision with costs attached gives leaders something to act on. Before the meeting, pull together four things.

  1. The constraint, named specifically. Which person or skill is short, how much demand sits on them, and how much availability they have.
  2. Two to four modeled options. Give leaders scenarios to choose from, each with its cost and its effect on delivery dates.
  3. The strategic risk. Frame the overrun in terms leaders already track: stalled initiatives, missed delivery windows, and avoidable attrition. Economist Impact and Planview research found that only 20% of executives are confident that resources are properly allocated to execute strategy, and a clear capacity picture is how you help close that gap.
  4. Answers to the likely questions. Can the lost value be recovered later? Can anyone else step in? Is there budget for the fix?

Then put it in one message you can adapt:

[Project] is forecasting [X]% more hours than approved.
If we absorb it, [project] slips by [timeframe].
Here are [number] options with costs.
We need a decision by [date].

How often should governance look at this?

Two rhythms work together: a quarterly gate for planning decisions and a monthly or bi-weekly check for course corrections and tripwire responses. A mature strategic portfolio management practice builds both into the calendar, and this guide to enterprise project portfolio management shows how the planning side fits together.

Where should you start?

Three steps before your next steering committee:

  1. Audit how overruns are handled today. Where is capacity discussed, and are mid-delivery changes escalated or absorbed? Write down what you find, because that is your baseline.
  2. Name your critical constraint. Pick the skill or role your teams are always competing for, and make it visible.
  3. Run one what-if scenario. Model what happens if two competing priorities both go ahead, then what happens if one is deferred.

Agree on the tiers with your PMO director and governance before you need them, so the first overrun starts with a plan.

Cover of the ebook Don’t Plan What You Can’t Execute

Take it further

The full ebook, Don’t Plan What You Can’t Execute, covers the escalation path and the prioritization checks in more depth, and it is easy to forward to the leaders you report to.

Related Posts

Written by Jeffrey Yeager Content Strategist

Jeff Yeager is a Content Strategist with Planview supporting the Product Portfolio Management Solution. A storyteller at heart, he has over a decade of content marketing experience with various software companies spanning industries from publishing to healthcare to AI. With a knack for distilling highly technical topics into easily consumable narratives, he is grateful for the opportunity to help elevate the Planview platform and spread its message about the benefits of connected work.