Designing a Tiered Intake Process: Because a Quick Fix Shouldn’t Require a 5-Page Form

I’ve seen teams use one enormous form for a label change and a two-year platform replacement. The small work escaped through chat. The large work learned to lie in smaller boxes.

Tiered intake changes the depth of review, not whether demand becomes visible.

Create three tracks

Use a quick-fix track for low-risk, reversible work under a small capacity limit. Use a standard track for cross-team changes. Use a strategic track for major investment, risk, or organizational change.

Repair the common foundation first with how to fix a broken business project intake process. Tiering comes after one door and one decision record work; otherwise it creates three better-labeled bypasses.

Every track begins with the same five facts in software project intake: current state, affected people, consequence, outcome, and owner.

Let evidence move the request

Do not let requesters choose the easiest tier permanently. Risk, dependencies, data sensitivity, cost, and affected teams can promote the request during review.

One “minor” field change that altered regulatory reporting. The work was small. The consequence was not.

Keep one capacity view

Quick fixes still consume people. Set a budget and show the total beside standard work. Work through the free Project Intake Evaluation Worksheet to find the small door that currently bypasses demand management.