A service ticket for a system change
Frontline support, access requests, and catalog items belong on a ticket. A software change needs a problem, people, and an owner before anyone files a work item.
IT project intake
IT project intake that turns a department ask into a reviewable request
IT project intake is how a department asks for a software change and gets IT involved before discovery. Precision Foundry collects the current process, then an IT Owner recommends the appropriate discovery path and any specialist reviews. It is not a service ticket and Ready for Discovery is not funding approval.
IT project intake should
- Let the person closest to the process submit the ask
- Put an IT Owner in Intake Review before discovery
- Keep discovery readiness separate from investment approval
IT project intake fails when the only door is a ticket or a hallway yes
Department managers know what is broken. They do not know how to file an epic. When IT project intake is a service portal or a shared inbox, reviewers reconstruct the ask from a title. The request then jumps into a demand list or a board before anyone can understand it.
See how routed requests enter the broader IT demand management software pipeline without becoming tickets.
For the full front-door workflow, review software project intake from submission through the later investment decision.
A hallway promise that skips the record
A sponsor yes in a meeting spends capacity. IT project intake exists so the ask is written down before anyone treats it as approved work.
A demand list with no complete request
Ranking incomplete asks is theater. Intake finishes one request. Demand management compares a pipeline of finished requests.
The four IT project intake routes
Standard Discovery handles substantial or uncertain work. Lightweight Discovery keeps small, understood changes lean. Existing Solution Review checks whether configuration, licensing, or an existing capability solves the need. Not an IT Project returns business-process, policy, staffing, training, or operational work to the right owner.
One BA facilitates discovery after IT triage
Precision Foundry does not require Business and IT respondents to run the questionnaire simultaneously. One BA facilitates the selected discovery path, records answers from the appropriate perspective, and keeps the shared request moving. The early IT-triage record supplies the technical signoff and routing context.
Executing IT project intake for one department request
IT project intake makes a single software ask reviewable and routes it with IT before discovery begins. It does not score the portfolio, approve the investment, or open a sprint. Those jobs happen later on the same record.
- 1
Let the department write the current process
The requestor describes what happens today and who is stuck—without Agile vocabulary or a preferred architecture.
- 2
Attach an owner IT can call
Name the business person who can answer follow-up questions while the story is still fresh.
- 3
Triage the request with IT
An assigned or company IT Owner flags Security, Vendor, Data, or Architecture reviews and recommends Standard Discovery, Lightweight Discovery, Existing Solution Review, or Not an IT Project.
In the product
Readiness prepares the review—it does not approve the project
Portfolio Readiness checks whether the business context is understandable. Intake Review and IT Triage still determine whether and how discovery begins.
Results
IT project intake benefits
When IT project intake works, department asks arrive as stories instead of ticket titles. IT reviews the request early, an Approver can mark it Ready for Discovery, and a BA facilitates the selected path without requiring several people to complete the questionnaire at once.
- Department managers submit what they already know
- IT recommends discovery depth before questions begin
- Specialist reviews are added only when the request needs them
- Investment approval waits for discovery and both estimates
Common questions
Questions from IT and department leads
What is IT project intake?+
IT project intake is how a department submits a software change request to IT. A useful submission explains the current problem, the people affected, a reachable owner, timing, and known constraints. It is not a service ticket and it is not a ranked demand list.
How is IT project intake different from IT demand management?+
Intake collects and completes one request. Demand management is the pipeline: every complete ask, reviewed together, with a recorded yes, no, or not yet. You cannot rank a list you never finished collecting.
Who should submit an IT project request?+
The person closest to the broken process submits the initial request. They do not need project-management training. An IT Owner participates during Intake Review, and one BA later facilitates the shared discovery questions and records the Business and IT answers. Leaders make the investment decision after both estimates exist.
Should IT project intake live in the service desk?+
No. A service desk is for frontline support, access requests, service catalogs, and SLAs. A software change still needs a story and a decision before anyone spends delivery capacity.
Put one department software ask through IT project intake
See how a business lead submits a complete IT request without a ticket portal or a steering-committee deck.
Request Private Alpha