Designing intake so good ideas survive the committee.
The eight signals every committee should see on every paper, and the intake structure that surfaces them without turning submission into a research project.
PulsePMO IQ · Field guide for PMO and portfolio leaders
Committees rarely reject good ideas on purpose. They reject them because the paper in front of them doesn't answer the questions the committee actually needs answered, so the safest response is to defer, ask for more information, or quietly let it die on the agenda. The fix is not a better pitch — it's an intake format that forces the eight signals a committee needs to exist before the paper ever reaches the room.
The eight signals
These are not a checklist to fill in after the fact. They are the fields your intake form should require before a submission is even eligible for committee review.
Strategic alignment
Which specific strategic pillar or objective this serves — named, not implied. "Improves efficiency" is not alignment; "reduces cost-to-serve in the segment we committed to grow margin in" is.
Sponsor commitment
A named executive sponsor who has reviewed the paper and will defend it in the room — not just an author who submitted it on their behalf.
Cost and benefit range
A range, not a false-precision single number, with the confidence level stated. A committee can work with "$800K–$1.2M, medium confidence." It cannot productively interrogate "$947,000."
Capacity and resource ask
What this actually requires in the units the portfolio is constrained on — specific roles, specific vendor capacity, specific budget line — not a headcount-equivalent abstraction.
Dependencies and risk
What else has to be true or has to happen first, and what breaks if a dependency slips.
Time-to-value
When benefit realization actually begins, distinct from when the project completes. A committee weighing two requests needs to know one pays back in month four and the other in month eighteen.
Fit against stated evaluation criteria
A direct, submitter-completed mapping against whatever criteria the committee has published — forcing the submitter to make the case in the committee's terms, not their own.
Kill criteria
The specific condition under which the sponsor agrees the project should be stopped or re-scoped. A paper with no kill criteria is asking for an open-ended commitment, whether or not that is the intent.
Committees default to “defer” when a paper is ambiguous, because deferring feels lower-risk than approving on incomplete information. Requiring these eight fields up front removes the ambiguity that makes deferral the safe choice — the committee is now choosing between funding, not funding, or asking one specific follow-up question, not guessing at what's missing.
Structuring the one-pager
The intake document itself should fit on one page. Length is not a formatting preference — it forces the submitter to commit to the range and the sponsor to actually engage with what they're signing, rather than skimming a ten-page deck. A workable structure:
- Header block — title, sponsor, submitter, date, requested committee date.
- The ask, in one sentence — what is being requested, and by when a decision is needed.
- The eight signals, each in two to three sentences, no appendices required to understand any of them.
- Alternatives considered — including the alternative of doing nothing, and why it was rejected.
- Sponsor sign-off — a literal signature or system approval, not an email forward.
Running the committee session
A well-structured paper still needs a committee mechanic that doesn't waste it. Three practices consistently improve decision quality without adding meeting time:
- Pre-read, not present-live. Papers go out 48 hours before the session. Committee time is spent on questions and the decision, not a first read of the material in the room.
- Three decision outcomes, not two. Approve, decline, or approve conditional on a named follow-up with an owner and a date — eliminating the vague “let's revisit next quarter” outcome that is functionally a decline without the accountability of saying so.
- Timebox by ambiguity, not by agenda slot. A paper that generates no questions should take two minutes. One that generates real debate should get the time it needs, even if that means deferring the next item — a fixed ten-minute slot per paper optimizes for the agenda, not for decision quality.
Common failure patterns
Two patterns account for most intake processes that quietly stop working:
- Scope creep in the form itself. Every quarter, someone adds one more required field to catch a problem from a specific past project. Within a year the form takes longer to complete than the analysis it's meant to summarize, and submitters start routing around it informally.
- No visible record of declined or deferred papers. If rejected ideas disappear rather than remaining visible with the reason they didn't proceed, the same ideas resurface repeatedly under new sponsors, and the committee re-litigates decisions it already made.
Demand pipeline, scoring, and stage-gated triage — in the product tour.
This guide reflects general intake and governance practice patterns and is not specific to any named customer.