A procurement intake process is the set of steps that turns an employee's need ("we need X") into a complete, approved and correctly routed purchase request that procurement can order or source. It does four jobs: capture the need on one structured form, check budget and approval authority, sort the request onto the right path (catalog, existing contract, quotes or a full sourcing event), and hand it to the buyer who owns it. Intake ends where sourcing starts.
The test of good intake is simple. A buyer can act on the request without sending a clarifying question, and the requester can see where it is without sending a chaser email.
The intake-to-procure workflow, end to end
| Step | What happens | Owner | Target time (example) |
|---|---|---|---|
| 1. Request | Requester fills in one intake form | Requester | 5 to 10 minutes |
| 2. Completeness check | Required fields, valid cost center, attachments present | Form rules, then intake buyer | Same day |
| 3. Triage | Pick the path: catalog, existing contract, quotes, sourcing event or emergency | Intake buyer | 1 business day |
| 4. Approval | Budget owner first, then threshold approvers; IT, legal or security in parallel only when a rule triggers them | Budget owner, approvers | 2 business days |
| 5. Sourcing | Order against the contract, or run an RFQ | Assigned buyer | Depends on path |
| 6. Award and PO | Choose the supplier, raise the purchase order | Assigned buyer | 1 business day after award |
| 7. Receive and pay | Goods receipt, invoice check, payment | Receiving, accounts payable | Per payment terms |
Intake proper is steps 1 to 4. Steps 5 to 7 are the rest of procure-to-pay. The target times are illustrative; publish your own so requesters know what to expect.
Triage paths
Triage is where most of the time is won or lost. Not every request deserves the same process.
| Path | Use when (example rules) | What procurement does |
|---|---|---|
| Express | Under $1,000, catalog item or preferred supplier, within budget | Auto-approve, raise the PO the same day |
| Existing contract | A live contract or framework already covers the item | Order against it and check the price matches the contract |
| Quotes | $1,000 to $25,000 with no contract in place | Collect three written quotes, compare, award |
| Sourcing event | Over $25,000, multi-year, or high risk (data, safety, single source) | Formal RFQ or RFP, evaluation team, contract review |
| Emergency | Production stopped, safety issue, legal deadline | Verbal approval logged by name, PO within 2 business days, reviewed afterwards |
The dollar bands are examples. Set yours from your approval policy and from how many requests your team can handle each week.
Common intake bottlenecks and how to fix them
| Bottleneck | What you see | Fix |
|---|---|---|
| Email requests | Details buried in threads, no queue, nobody knows the status | One form as the only front door; auto-reply on the old inbox pointing to it |
| Incomplete requests | Buyers ask two or three questions per request | Required fields with examples; send back naming the exact missing item, not "need more info" |
| Serial approvals | Request waits for IT, then legal, then finance | Run independent reviews in parallel; trigger IT and legal only by rule |
| Approver overload | One director signs everything over $500 | Raise thresholds for budgeted spend, set delegates, escalate after 2 business days |
| Wrong category | Requests land with the wrong buyer | A short plain-language category list (10 to 15 options); the intake buyer corrects it at triage |
| No status | Requesters chase by email, chat and phone | Status visible to the requester, with a notice on every change |
| Bypass | Invoices arrive with no PO | An express lane fast enough that bypassing is not worth it, then a "no PO, no pay" rule with finance |
Most of these trace back to two causes: the form lets incomplete requests through, and the approval chain is longer than the risk needs. Fix those two first.
What information to collect on a procurement intake form
Ask for what the next person in the chain needs to act, and nothing else.
| Field | Why procurement needs it | Required |
|---|---|---|
| Requester, department | Routing and follow-up | Always |
| What is needed: description, quantity, unit | A supplier can quote without guessing | Always |
| Goods or services, category (pick list) | Routes to the right buyer, keeps spend data clean | Always |
| Business reason (one line) | Approval and audit trail | Always |
| Estimated cost and how it was estimated | Sets the approval tier and the path | Always |
| Cost center or budget code (validated list) | Budget check | Always |
| Needed-by date | Tells triage whether a full sourcing event is realistic | Always |
| One-off or recurring; contract length | Total value, renewal and contract review | Always |
| Relationship with any suggested supplier (yes/no) | Conflict-of-interest check | Always |
| Suggested suppliers and contacts | Speeds up the RFQ; flags existing vendors | Optional |
| Specs, drawings or scope of work (attachment) | Makes the request RFQ-ready | Goods with specs; services above your quote threshold |
| Delivery or service location | Freight, tax, site access | Goods and on-site services |
| Will the supplier access our systems or personal data? | Triggers IT security review | Software and IT services |
| Will the supplier work on our premises? | Insurance certificate and safety induction | On-site services |
Rules that keep the form usable:
- Keep the always-visible part to about ten fields. Use conditional logic for the rest: a services request hides shipping fields, a software request shows the security questions. This is what people mean by a guided intake flow: two or three questions first (what are you buying, roughly how much, do we already have a supplier), then only the fields that apply.
- Use pick lists for category, cost center and location so the data can be reported. Keep free text for the description and notes.
- Put an example under the hard fields. Bad: "laptops". Good: "6 x 14-inch laptops, 16 GB RAM, 512 GB SSD, delivered to the Dallas office by 15 March".
- Validate on submit: needed-by date in the future, cost center exists, attachment present when the category needs one.
- Have one front door, linked from wherever people already work: the intranet, the team chat tool, the ERP menu.
Intake system features that reduce approval delays
When you compare intake tools, or set up your own with a form builder and a tracker, these are the features that actually shorten approval time:
- Rule-based routing by amount, category and cost center, so nobody assigns approvers by hand.
- Parallel approval steps for reviews that do not depend on each other, such as IT security and finance.
- Reminders and automatic escalation to a delegate once an approval passes its time limit, for example 48 hours.
- Delegation and out-of-office cover, so one person on leave does not freeze a queue.
- Approve from email or phone with full context on one screen: what, how much, which budget, the quote.
- Pre-approval for budgeted catalog spend under a set limit, so small routine buys never enter an approval queue.
- A visible status and clock per stage, so you can see where requests are aging.
- An audit log of who approved what and when.
Example (illustrative): a $12,000 software request needs the budget owner, IT security and finance. If each approver takes two business days, a serial chain takes six business days. Run IT security and finance in parallel after the budget owner and it takes four: two for the budget owner, then two for whichever parallel review finishes last. Add a 48-hour escalation and no single step can stretch past two days without someone noticing.
What to automate and what to keep human
| Automate | Keep human |
|---|---|
| Required-field and cost-center checks | Choosing the path for unclear or new types of request |
| Routing by amount and category | Talking through requirements on large or complex buys |
| Reminders, escalations and status notices | Supplier selection and negotiation |
| Auto-approval of budgeted catalog spend under a limit | Reviewing exceptions: unusual amounts, new suppliers, orders that look split |
How to replace email purchase requests with a structured intake process
A practical four-week switch for a small team:
- Week 1: baseline. Pull the last 50 to 100 requests from email. For each, note what was missing, how many follow-ups it took and how long it took to reach a PO. This gives you your form fields and a before number.
- Week 1: draft the form from the field table above. Test it on five real past requests: could a buyer have acted on each one without asking anything?
- Week 2: write the rules. Triage paths, approval thresholds and target times on one page. Get finance to sign off the thresholds.
- Week 2: set up the queue. A form feeding a shared tracker is enough to start. Every request gets an ID, status, owner and submission date.
- Week 3: pilot with the one or two departments that buy most often. Fix the fields that confuse them.
- Week 4: switch over. Put an auto-reply on the old purchasing inbox. For two weeks the intake buyer converts stray emails into requests and replies with the form link.
- After that: agree "no PO, no pay" with finance, but only once the express lane is genuinely fast.
Auto-reply template
Subject: Purchase requests now go through the request form
Thanks for your message. Purchase requests now go through one form: [form link]. It takes about five minutes and asks what you need, the rough cost, your cost center and when you need it.
When you submit, you get a request number and can check the status at any time. Catalog items under [express limit] are normally approved the same day.
For emergencies (production stopped, a safety issue or a legal deadline), call [name] on [number].
Check requests against existing contracts and suppliers
Before any sourcing starts, the intake buyer answers three questions at triage:
- Is there a live contract, framework or preferred supplier that covers this? If yes, order against it.
- Do we already have it? Spare software licences, stock at another site, an unused subscription seat.
- Is the suggested supplier already in the vendor master, possibly under another name? Avoid creating duplicates.
Add one question to the form ("Do you know of an existing contract or supplier for this?") and make the three checks a required step in the tracker. Capturing estimated cost and category at intake also gives finance committed spend weeks before the invoice arrives, which is the main reason to move spend data capture up front.
Intake metrics to track
| Metric | How to calculate | What it tells you |
|---|---|---|
| First-pass acceptance rate | Requests needing no clarification ÷ requests submitted | Whether the form asks for the right things |
| Submission to approval | Median business days | Where approvals stall |
| Submission to PO, by path | Median business days for each triage path | Which path to fix first |
| Rework rate | Requests sent back ÷ requests submitted | Form and training gaps |
| Requests per buyer per week | Count | Workload balance |
| Off-intake spend | Invoice value with no PO or a PO raised after the invoice ÷ total invoice value | How much buying bypasses intake |
Use the median rather than the average for cycle times; one stuck request distorts an average.
Example (illustrative): in one month the team receives 120 requests. 78 need no clarification, so first-pass acceptance is 78 ÷ 120 = 65%. Invoices total $400,000, of which $36,000 had no PO or an after-the-fact PO, so off-intake spend is 36,000 ÷ 400,000 = 9%. Those two numbers tell you to fix the form first, then chase the 9%.
Handing intake off to sourcing and RFQs
Good intake produces an RFQ-ready request: an item list with quantities and units, specs or drawings attached, delivery date and location, and the evaluation criteria (price only, or price plus lead time and quality). Carry the request ID into the RFQ and the PO so the trail from need to payment stays connected.
If you run quotes in AuraVMS, that approved request becomes the RFQ: you invite suppliers by email, compare their quotes side by side and place the order with one click. On the Medium Team plan you can also attach documents to RFQ items and send reminders to suppliers who have not responded.
Setting up intake for a five-person procurement team
You do not need an enterprise intake platform to run this well. A workable setup:
- One form and one tracker. Tracker columns: request ID, date submitted, requester, department, category, description, estimated cost, cost center, path, approvers, status, assigned buyer, needed-by date, PO number, date closed.
- A rotating intake desk. One buyer owns triage each week and checks the queue twice a day. The other four own categories and pick up assigned requests.
- Written thresholds. Express, quotes and sourcing-event limits on one page, signed off by finance.
- A 15-minute weekly review of every request past its target time, and why.
- A monthly look at the metrics above, shared with the departments that buy most.
Controls to build into intake
- The requester, approver and buyer are different people.
- The approval tier is set by total value, including recurring and multi-year value, so splitting a purchase does not dodge a threshold. Flag several requests from the same requester for the same supplier within 30 days.
- A yes/no conflict-of-interest question on every request.
- Category triggers: software or data access goes to IT security; on-site services need an insurance certificate; regulated categories, such as anything touching health data under HIPAA, go to compliance.
- The request, approvals and business reason stay attached to the PO for audit.
Common questions about procurement intake
What is the difference between a purchase request, a requisition and a PO?
A purchase request is the need as the employee describes it. A purchase requisition is the internal, approved document asking procurement to buy. A purchase order is the commitment you send to the supplier. Intake covers the first two. "Order intake" usually means the opposite side: a supplier receiving and processing customer orders.
How do we get stakeholders to actually use the intake process?
Make it faster than the workaround. Publish target times and hit them, make the express lane same-day, and show requesters their status without them asking. After the first month, report back to each department how quickly their requests were handled. Turn on "no PO, no pay" only once the process is quicker than emailing a supplier directly.
How do we handle urgent requests?
Define what counts as an emergency (production stopped, safety, a legal or regulatory deadline), name who can approve verbally, and require the PO within two business days. Review emergencies monthly. If they become routine, the problem is planning, not intake.
Should we require three quotes at intake?
No. Intake captures the need; sourcing collects quotes. Asking requesters for quotes pushes them toward suppliers they already know. Capture supplier suggestions if they have them, and let the quotes path handle competition.
Should procurement and sales use the same intake in one platform?
One platform is fine; one form is not. Purchase requests and sales or deal-desk requests need different fields, approvers and data. Share what is common: request IDs, status tracking, the audit log and, where legal reviews contracts from both sides, a single legal review queue fed by both forms.
What does good intake look like for employees, compared with bad?
| Good intake | Bad intake |
|---|---|
| One place to ask, linked from where people work | Email, chat, hallway requests and personal cards |
| Under ten minutes, with examples on hard fields | Long forms full of procurement jargon |
| A request number and visible status | Silence, then a chaser |
| Clear target times by path | "It depends" |
| Questions arrive once, all together | Repeated back-and-forth |
How does AuraVMS fit into procurement intake?
AuraVMS is RFQ software. It picks up at the sourcing step: you create the RFQ from the approved request, invite suppliers by email, compare quotes side by side, see supplier performance comparisons and place the order with one click. Plans start at $4.99 per user per month billed annually.
Where to start
- Pull your last 50 email requests and count the follow-up questions each one needed.
- Build the form from the field table and test it on five of those requests.
- Write your triage paths and thresholds on one page, then switch the inbox over.
Request a demo to see how AuraVMS transforms procurement intake from bottleneck to competitive advantage. The platform's structured approach to request capture, approval routing, and RFQ generation addresses the intake challenges that slow procurement organizations worldwide.
Every purchase starts with a request. Make sure your intake process sets those requests up for success.