How to build a project intake process

What project intake is

Project intake is the operating process for receiving, clarifying, evaluating, deciding, and starting proposed work. It creates a fair path from an idea or request to a funded and owned initiative, or to an explicit decision not to proceed.

Without intake, the loudest message often becomes the highest priority. Teams begin work before outcomes are clear, duplicate existing efforts, accept deadlines without capacity, and discover missing decisions after delivery has already started.

Begin with one front door

A single intake path does not require every request to use the same form. It means the company knows where a proposed commitment becomes visible and who owns the next decision. Email, chat, meetings, and customer conversations may still originate ideas, but durable requests should reach one governed queue.

Make submission easier than working around the process. Ask only for information the requester can reasonably know. The intake team can add analysis later. A form that demands a finished business case from every employee will drive important work back into private messages.

• The problem or opportunity in plain language.
• The people or customers affected.
• The desired outcome and why it matters now.
• Known deadline, constraint, dependency, or policy requirement.
• The requester and an available subject-matter contact.

Separate clarification from evaluation

First determine whether the request is understandable and belongs in the queue. Then evaluate whether the company should act. Combining those steps encourages reviewers to reject poorly written requests even when the underlying opportunity is valuable.

Clarification should produce a concise outcome statement, known constraints, affected systems or teams, and the smallest responsible next decision. If important information is missing, return a specific question instead of leaving the request in an ambiguous pending state.

Use decision criteria, not a secret score

Evaluation criteria should reflect company strategy and operating reality. Common dimensions include expected value, urgency, risk reduction, customer impact, regulatory need, strategic fit, effort, opportunity cost, and confidence in the evidence.

A numeric score can support comparison, but it should not replace judgment. Small differences in speculative inputs do not create objective truth. Record the reasoning and the trade-off, especially when leaders choose a lower-scoring request because of a constraint the model does not capture.

• Value: what improves if the outcome succeeds?
• Urgency: what changes if the work begins later?
• Evidence: how confident are we in the need and expected result?
• Effort: which people, skills, money, and time are required?
• Opportunity cost: what will not happen if this request is accepted?
• Risk: what new exposure or reduction does the work create?

Give every request a decision owner

The intake coordinator may manage completeness, but someone with the right authority must own the accept, defer, reject, or investigate decision. Define decision rights by cost, risk, strategic scope, or affected area so requests do not circulate between reviewers.

Set a service expectation for the decision, not necessarily for delivery. Requesters should know when they will receive an answer and what each answer means. Deferred work needs a review condition or date; otherwise defer becomes a polite word for forgotten.

Turn acceptance into an operating record

Approval is not the end of intake. An accepted request must leave with an accountable owner, outcome, initial scope, decision history, relevant evidence, and a next planning action. Creating an empty project and forwarding the original form transfers ambiguity to the delivery team.

Preserve the connection between the request and the resulting initiative. That link lets the company later compare the promised value with the delivered result and improve its intake decisions.

Measure whether intake improves choices

Queue length and decision time matter, but they do not reveal quality. Track how often accepted requests start without an owner, return for missing context, conflict with capacity, duplicate existing work, or fail to produce the intended outcome.

Review rejected and deferred requests too. Repeated themes may reveal an unmet product need, a policy problem, or a capacity constraint. The intake queue is not only administration. It is evidence about what the company is being asked to become.

Close the feedback loop with requesters. Explain important decisions, publish recurring criteria questions, and improve the intake form when the same clarification appears repeatedly. A process becomes credible when people can predict how responsible choices are made.

Frequently asked questions