What Makes a Good Project Request? A Practical Guide for Business Units

TL;DR

Most project requests fail at intake or get funded with weak strategic grounding, not because the underlying idea lacks merit, but because the submission does not answer the questions the PMO governance process requires. A strong project request does three things: connects to a specific strategic outcome with a verifiable mechanism, articulates the business problem and solution hypothesis clearly, and provides enough financial context for early-stage evaluation. This guide shows business unit leaders exactly what that looks like.

You have an idea for an initiative that would genuinely improve your function’s performance. You are confident it would deliver measurable value. You submit it to the PMO intake process.

And it either fails to advance, gets deprioritized against proposals you believe are less impactful, or advances but receives less resource commitment than you requested.

The frustrating reality: the idea may have been exactly right. The submission may have been the problem.

PMO intake processes are governance systems, not systems for evaluating ideas. They are designed to assess whether a proposed initiative is strategically aligned, financially justified, and executable within the portfolio’s resource constraints. A request that does not answer those questions, even if it describes a genuinely valuable initiative, provides the PMO with no basis to advocate for it at the portfolio level.

This guide tells you exactly what a strong project request looks like from the perspective of the governance process evaluating it. Most project requests that fail PMO review are not bad ideas. They are good ideas, but the submissions are weak. Here is the difference and how to close it.

What the PMO Is Actually Evaluating

Understanding what the PMO is looking for changes how you write a request.

Most business unit leaders approach the intake form as a description exercise: describe the initiative, explain why it is valuable, and attach supporting material. The governance process is evaluating something more specific and more structured than a description.

The PMO intake review is answering four questions from your submission:

1. Strategic Linkage
Which specific strategic outcome does this initiative support, and how exactly will the proposed solution drive that outcome?

2. Problem Clarity
Is the business problem clearly defined, with evidence that demonstrates its scale, urgency, and impact?

3. Solution Viability
Is the proposed solution realistic and capable of solving the problem within a reasonable level of investment?

4. Portfolio Fit
Does this initiative add value to the existing portfolio, or does it duplicate efforts already in progress or approved?

A strong project request answers all four questions. A weak one answers one or two and leaves the others to the PMO reviewer’s inference, which is both a governance risk and a competitive disadvantage relative to submissions that answer all four explicitly.

The Four Components of a Strong Project Request

1: Specific Strategic Linkage: Not Generic Alignment

The most common reason a project request fails at intake is not that it lacks strategic relevance; it is that the strategic relevance is claimed generically rather than demonstrated specifically.

What generic alignment looks like: “This initiative supports our strategic objective of improving operational efficiency.”

What specific alignment looks like: “This initiative advances Key Result 3: reduce end-to-end invoice processing time from 14 days to 3 days by Q3. It does this by automating the three manual handoff steps between Accounts Payable and vendor onboarding that currently account for 9 of the 14 days.”

The second statement is verifiable. The mechanism is specific. The PMO reviewer does not need to infer the connection; it is explicitly stated and can be evaluated against the declared key result target.

A 2024 Gartner case study of IndigoPillar found that when organizations required specific outcome linkage rather than objective-level alignment claims, the accuracy of strategic alignment improved measurably and the quality of intake submissions doubled.

How to write your strategic linkage:

Element	Example
The outcome you are advancing	“Key Result 3: Reduce invoice processing time from 14 to 3 days by Q3”
The mechanism of contribution	“By automating the three manual handoff steps that account for 9 of the 14 days”
The measurable signal of success	“Invoice processing time below 3 days for 90%+ of transactions by end of Q3”

2: A Clear Problem Statement, With Evidence

The business problem your initiative solves should be stated as a problem, not as a solution description. Many intake submissions describe the solution in detail while leaving the problem implicit. The governance process requires the problem to be explicit because the problem statement is what the PMO uses to evaluate whether the proposed solution is the right response.

Weak problem statement: “We want to implement an automated invoice processing system.”

Strong problem statement: “Our current invoice processing workflow takes an average of 14 days from Invoice-to-Pay authorization. The industry benchmark for our sector is 3–5 days. This creates two measurable impacts: we are losing early payment discount eligibility on approximately $2.3M of annual vendor spend, and vendor satisfaction surveys rank payment speed as the top friction point in our supplier relationships.”

The strong version defines the problem, quantifies its scale, and establishes why it matters, giving the PMO everything needed to evaluate the proportionality of the proposed solution and investment.

3: A Solution Hypothesis: Not a Project Plan

At the intake stage, the PMO does not need a detailed project plan. It needs a solution hypothesis: a structured statement of your proposed approach and why you believe it will solve the stated problem.

The solution hypothesis has three parts:

1: What do you propose to do?

The proposed solution in plain terms, not technical specifications, not vendor names, not implementation methodology. What the initiative will do, at a level of specificity that allows evaluation.

2: Why do you believe it will work?

The causal logic connecting your solution to the problem. Not evidence that the solution exists, but evidence that it addresses the specific problem you have defined.

3: What success looks like.

The measurable outcome that would confirm the initiative delivered on its intent is expressed in the same terms as the key result it advances, so that the benefits realization connection is established from the submission stage.

4: A Financial Estimate: Rough Is Fine, Absent Is Not

Most business unit leaders either over-engineer the financial section of an intake submission, producing a detailed business case at the intake stage when it is not yet required, or omit financial context entirely on the grounds that it is too early to know.

The intake process needs neither a full business case nor a zero. It needs a rough order-of-magnitude investment estimate that allows the PMO to assess whether the initiative is in the right cost bracket for the outcome it claims to advance.

What the financial section needs at intake:

Element	What to Include
Investment range	Low-medium-high banding or rough order-of-magnitude ($50K–$200K, $200K–$500K, $500K+)
Resource requirements	Internal headcount estimate and any external vendor or contractor dependency
Time horizon	Expected duration from approval to delivery of the primary outcome
Benefits estimate	Rough quantification of the outcome — cost reduction, revenue impact, risk reduction, time saving

A submission with a rough investment range and a rough benefits estimate allows the PMO to run a proportionality check: is the investment in the right order of magnitude relative to the outcome being claimed? A submission with no financial context forces the PMO to make that assessment without data, which disadvantages your request relative to ones that provide it.

The Intake Submission Checklist

Before submitting, verify that your request answers each of these:

#	Check	Your Submission
1	Have you selected a specific strategic outcome or Key Result, not just a broad objective?
2	Have you explained the mechanism by which your initiative advances that outcome, not just asserted relevance?
3	Have you defined the business problem in terms of measurable impact, not as a solution description?
4	Have you provided a solution hypothesis with causal logic connecting your approach to the problem?
5	Have you stated what success looks like in measurable terms consistent with the outcome you selected?
6	Have you provided a rough order-of-magnitude investment estimate and a rough benefits quantification?

A submission that answers all six is not a guarantee of approval.

Portfolio prioritization involves trade-offs that may defer a well-written submission in favor of a higher-priority one. But a submission that answers all six gives the PMO everything needed to advocate for your initiative at the portfolio level, and that is the best position you can put yourself in at the intake stage.

Frequently Asked Questions

What is the most common reason project requests fail at PMO intake?

Generic strategic alignment claims, linking a request to a broad objective without explaining the specific mechanism by which the initiative advances a measurable outcome. The PMO cannot verify generic alignment claims and cannot advocate for submissions that require inference rather than evidence to establish relevance. A specific, verifiable linkage to a key result or defined outcome is the single most important improvement that most business unit submissions can make

How detailed should a project request be at the intake stage?

More detailed than a concept note, less detailed than a business case. The intake submission needs: a specific strategic outcome linkage with a mechanism explanation, a clear problem statement with measurable impact, a solution hypothesis with causal logic, and a rough financial estimate. Full business case development, detailed financial modelling, implementation planning, and risk analysis are appropriate after a submission has cleared the intake governance stage.

What is a solution hypothesis?

A solution hypothesis is a structured statement of the proposed approach, the causal logic connecting it to the stated problem, and the measurable outcome that would confirm success. It is not a project plan or a technical specification. It is the answer to the question, “What are you proposing to do, why do you believe it will work, and how will you know when it has?”

Why does the PMO need a financial estimate at the intake stage?

To assess proportionality, whether the investment range is reasonable relative to the outcome being claimed. A $2M investment to reduce invoice processing time by 2 days requires more scrutiny than a $50K investment to achieve the same result. Without a rough financial estimate, the PMO cannot make that proportionality assessment and cannot position the request accurately in the portfolio prioritization process