Requisition, RFQ, and budget routing

Purchase Requisitions should capture category, quantity, delivery need, site, cost center, expected timing, and urgency in a way that eliminates guesswork later. Procurement loses time whenever requesters submit demand without enough context for comparison or approval.

The requisition is not just a request form. It is the first control point in the procure-to-pay chain, because poor demand context will show up again as unclear RFQs, weak supplier quotations, and avoidable invoice disputes.

Evidence should come from supplier state, requisition context, RFQ response, quotation comparison, PO approval, receipt, invoice, debit note, or settlement posture. For Structured demand capture, a strong answer names the visible cue, record, status, or reference that supports the next step and states what would pause the learner.

Routing should follow spend policy and budget responsibility rather than informal escalation. The right approval path makes procurement smoother because it removes the need to rediscover who is accountable after the request is already waiting.

Turn the section on Budget routing with ownership into a realistic example. Ask the learner to describe the situation they are responding to, the first surface they would open, the cue they expect to find, and what they would do if that cue is missing.

For Budget routing with ownership, the learner should point to the specific page, record, status, or note that separates evidence from assumption before moving to the next step.

The RFQs tab turns approved demand into a supplier-facing sourcing request. Users should confirm the requisition is approved, the scope is clear, suppliers are eligible, dates are realistic, and response expectations are visible before the RFQ is sent.

Teach the handoff plainly: requisition captures internal demand, RFQ asks the market for a response, and supplier quotations become comparable only if the RFQ gave each supplier the same decision context.

Use this section to confirm the learner understands more than the page label. They should connect RFQ only after demand is ready to the business state, owner, and consequence behind it.

Run the lesson as a requisition-to-settlement control exercise. Start with the practical task: identify the fields required for an actionable purchase requisition. Ask the learner to name the role, surface, evidence, and state they would inspect before taking action.

Evidence should come from supplier state, requisition context, RFQ response, quotation comparison, PO approval, receipt, invoice, debit note, or settlement posture. The practice should end with the learner connecting the action back to the lesson summary: teach procurement teams to turn raw demand into governed requisitions and then into RFQs with enough context for fair supplier response.

Close the exercise by asking the learner to restate the objective in operational terms: identify the fields required for an actionable purchase requisition. They should name what changed, what remains uncertain, and which surface or owner takes the next step.

Do not let procurement become a chain of disconnected documents. Each step should preserve supplier context, budget posture, policy evidence, and the next accountable owner. In this lesson, watch for that risk while learners work on this objective: identify the fields required for an actionable purchase requisition.

Do not mark the lesson complete because the learner can repeat terms. Completion means they can name the minimum information every requisition should include and describe why the lesson matters in real work.

Review the answer for skipped ownership, missing evidence, or vague next steps. If the learner cannot name the minimum information every requisition should include, keep the lesson in practice mode before marking it complete.