Demand management is the discipline of capturing every request that could become a project, assessing it on a consistent basis, and weighing it against the organization's real capacity to deliver, before anyone commits resources. It is the front door of a project portfolio. Get it right and the portfolio contains the work that matters most. Get it wrong and capacity leaks into whatever arrived loudest, and the strategic work never gets funded.
Most PMOs discover they have a demand problem before they have a delivery problem. Teams are busy, yet the initiatives leadership cares about are late or unstarted, because unmanaged demand let a hundred small requests crowd out the few large ones. Demand management is the control that stops that.
Key takeaways
- Demand management captures, categorizes, assesses, and prioritizes all potential work against capacity, before commitment. It governs what is allowed to become a project.
- It is broader than intake. Intake is the mechanism that receives a request; demand management is the discipline that decides, across all requests, what the portfolio should hold.
- Every request must land in one consistent pipeline. Demand that arrives through side channels and personal favors is the demand that breaks a portfolio.
- Demand is only half the equation. It is meaningless without a capacity figure to weigh it against, which is why demand and capacity planning are two halves of one decision.
- In portfolio management, demand management refers to project demand, not supply-chain demand planning or forecasting. They share a name and nothing else.
- The output is a prioritized, capacity-aware pipeline that feeds portfolio governance, not a pile of approved requests with no owner of the trade-offs.
What is demand management in project portfolio management?
Demand management in project portfolio management is the process of gathering all potential and active demand for an organization's delivery capacity, evaluating each request against strategy and against available capacity, and shaping it into a prioritized pipeline of work the portfolio can actually execute. It sits at the start of the portfolio lifecycle, upstream of selection and delivery, and its job is to make sure the portfolio is fed the right candidates in the first place.
The word demand is deliberate. It signals that requests are not automatically projects. They are demand on a finite supply of people, money, and time, and like any demand exceeding supply, they have to be prioritized and rationed rather than simply accepted.
What are the steps in the demand management process?
The demand management process runs in six steps, from a raw request to a decision that respects capacity:
- Capture. Route every request through one channel with a consistent minimum of information: the problem, the sponsor, the expected value, and a rough size. One front door, no exceptions.
- Categorize. Tag each request by type (strategic, run-the-business, maintenance, regulatory, unplanned) so like is compared with like and mandatory work is visible.
- Assess. Evaluate value, strategic fit, risk, and rough cost on a common scale, enough to rank, not enough to over-invest in ideas that will be declined.
- Prioritize. Rank the assessed demand using consistent criteria, so the order reflects value and fit rather than who asked most insistently.
- Weigh against capacity. Draw the line where delivery capacity runs out. Everything below the line is the honest backlog, not a promise.
- Decide and route. Approve, defer, or decline each item, and pass the approved, capacity-aware pipeline into governance for funding.
The mechanics of receiving and logging a single request, the forms, the triage, the request record, are covered in the project intake process, with the request form itself broken down in the project intake form guide. Demand management is the layer above that: what to do with all the requests once they are in.
What is the difference between demand management and intake?
Intake is the mechanism that receives, logs, and triages an individual request; demand management is the broader discipline that assesses and prioritizes the whole body of requests against capacity and strategy. Intake is a step. Demand management is the ongoing balancing act that intake feeds. Put simply, intake handles one request at a time, and demand management handles all of them together. The staged flow those requests move through, from idea to delivery, is the project pipeline.
The distinction is practical, not academic. A PMO can have an excellent intake form and still have terrible demand management, if every well-logged request is then approved without anyone asking whether the portfolio has the capacity to deliver the sum of them. The intake queue fills up, everything is technically approved, and delivery quietly falls apart. Good intake without demand management is an orderly path to overcommitment.
How is demand management different from demand planning in supply chain?
They share a name and nothing else. Demand management in project portfolio management is about managing requests for project and delivery capacity. Demand planning in supply chain is about forecasting customer demand for products so that inventory and production can be planned. One deals with which projects to do; the other deals with how many units to make. If you arrived here looking for forecasting, inventory, or sales-and-operations planning, this is the wrong discipline.
The confusion is worth flagging because search results mix the two constantly, and some PPM tools (ServiceNow's strategic portfolio management, for example) use "demand management" as a named module for exactly the project-request sense described here. In a PMO context, demand always means demand on delivery capacity.
What types of demand does a portfolio have to manage?
Not all demand is discretionary, and treating it as if it were is a fast way to lose credibility. A portfolio typically carries five types, and only some are genuinely a choice.
| Type | What it is | Discretionary? |
|---|---|---|
| Strategic | New initiatives that advance business goals | Yes, the real prioritization battleground |
| Run-the-business | Enhancements that keep existing capabilities current | Partly |
| Maintenance | Keeping the lights on, small fixes, upkeep | Largely not |
| Regulatory | Compliance and legal mandates with deadlines | No, non-negotiable |
| Unplanned | Urgent requests that arrive mid-cycle | Case by case, needs a reserve |
The insight most portfolios miss is that mandatory demand (maintenance and regulatory) consumes capacity first, and only the remainder is available for the strategic work everyone actually argues about. Show leaders that the discretionary budget is 40 percent of capacity, not 100 percent, and the prioritization conversation gets a lot more honest.
How does demand management connect to capacity?
Demand management is one half of a single decision, and capacity planning is the other. A ranked list of demand is worthless without a credible figure for how much the organization can actually deliver, and a capacity figure is worthless without prioritized demand to spend it on. The two have to be read together, at the same table, or the portfolio commits to more than it can do and calls the shortfall a delivery failure when it was really a demand failure.
The line where prioritized demand meets available capacity is the single most important number a PMO produces. Above it is what gets done; below it is the honest backlog. Setting that line requires real capacity data, which is the subject of resource and capacity planning, and the decision to fund what sits above the line belongs in portfolio governance, where leaders own the trade-offs on the record.
Why does demand management matter in a PMO?
Demand management matters because it is the earliest and cheapest point at which a PMO can influence the portfolio. Every control downstream, prioritization, resourcing, governance, is more expensive and more contentious than simply managing what is allowed to enter. A PMO that only manages projects after they exist is firefighting; a PMO that manages demand shapes which fires ever get lit.
It is also where the PMO earns its strategic seat. Anyone can run a status report. Being the function that can say, with data, "here is everything being asked of us, here is what we can actually deliver, and here is what that means we must not do," is what makes a PMO worth having. Demand management is the front end of the whole project portfolio management process, and it defines the shape of the project portfolio everything else then manages.