Skills Drill 5 1 Requisition Activity

8 min read

You're staring at a blank requisition form. You've done this before. So again. *Am I picking the right thing? That said, will finance kick it back? But every time, there's that moment of hesitation. The dropdown menus blur together — account codes, cost centers, delivery dates — and you're not 100% sure which one actually matters for this purchase. Is this going to delay the project?

That hesitation? It's not because you're bad at your job. It's because nobody actually taught you the logic behind the form. They just handed you the template and said "fill this out.

Skills Drill 5-1 — or whatever your program calls the requisition activity — exists to fix exactly that gap. Let's walk through what it's actually trying to teach you, why most people rush through it, and how to make it stick.

Easier said than done, but still worth knowing.

What Is a Requisition Activity

At its core, a requisition activity is a structured exercise that walks you through creating a purchase requisition from start to finish. Not a purchase order — that comes later. A requisition is the internal request that says "we need this, here's why, here's the budget, please approve it.

In a training context, Skills Drill 5-1 typically gives you a scenario: *Your department needs 15 ergonomic keyboards by June 15. Budget code 6210. Vendor must be on the approved list. Go.

You're expected to:

  • manage the requisition system (or paper form)
  • Select the correct commodity codes
  • Attach supporting documentation
  • Route for appropriate approvals
  • Submit without errors that trigger rejection

Sounds mechanical. It's not. The drill is designed to expose the decision points that live inside every field — the ones that determine whether your request sails through or bounces back three times.

The Difference Between Requisition and Purchase Order

This trips people up constantly. A requisition is internal. And it's you asking permission to spend money. Even so, a purchase order is external — it's the legal document sent to a vendor after approval. On the flip side, the requisition creates the PO. If you skip steps on the requisition, the PO either doesn't get created or gets created wrong.

Why It's Called a "Skills Drill"

Because repetition builds muscle memory. Because of that, the first time you do it, you're thinking about every click. The fifth time, you're thinking about why you're clicking — the business logic, the compliance rules, the downstream effects. That's the shift the drill is designed to create The details matter here. That's the whole idea..

Why It Matters / Why People Care

Requisitions are the gatekeepers of organizational spending. Still, every dollar that leaves the company passes through one first. Get it wrong, and you're not just annoying the procurement team — you're creating real downstream problems And that's really what it comes down to..

The Cost of a Bad Requisition

  • Delayed projects — A rejected requisition adds 3–10 business days per cycle. Multiply that by 20 requests a month.
  • Budget misallocation — Wrong account code = expenses hitting the wrong department. Finance hates this. So does your manager when their budget looks blown.
  • Compliance risk — Missing sole-source justifications, missing quotes, missing approvals. Audit findings live here.
  • Vendor relationship damage — Late POs mean late payments. Vendors remember.

The Hidden Skill: Translating Business Needs Into System Language

The real value of the drill isn't learning the software. It's learning to translate: We need keyboards → Commodity code 43211604, account 6210, cost center 3300, delivery to Dock B by 06/15, three quotes attached.

That translation skill? Vendor negotiations. Budget forecasting. Here's the thing — it transfers. Audit prep. The drill is the low-stakes place to practice it No workaround needed..

How It Works (or How to Do It)

Most requisition activities follow a similar arc. Here's the breakdown, step by step, with the decision points called out.

1. Receive and Analyze the Scenario

Don't skim. In practice, read for constraints:

  • Quantity and unit of measure — "15 each" vs "15 boxes" changes everything
  • Delivery deadline — Is it a hard date or a preference? So hard dates require expedited processing
  • Budget availability — Does the cost center have room? If not, you need a budget transfer before submitting
  • Vendor restrictions — Approved list only? Sole source? Three quotes required over $X?

Pro tip: Highlight every number and proper noun in the scenario. Those are your data entry targets.

2. Log In and Select the Right Form Type

Systems often have multiple requisition types:

  • Standard goods/services
  • Capital equipment (different approval chain)
  • Emergency/urgent (limited fields, higher scrutiny later)
  • Blanket/release (for recurring orders)

Picking the wrong form type routes your request to the wrong approvers. That's a guaranteed rejection It's one of those things that adds up..

3. Header Information — The Easy Part That Isn't

Field What It Actually Controls
Requestor Who gets notified.
Currency Matters for international vendors. And
Deliver to Not just a building — dock code, room number, contact name. That said, who gets blamed if it's wrong. Warehouse needs this. Unrealistic dates = ignored requests.
Date required Drives the buyer's priority queue. Defaults to company currency.

4. Line Items — Where the Real Work Lives

Each line needs:

  • Item description — Specific enough for a buyer who doesn't know your project. So "Ergonomic keyboard, split design, USB-C, black" beats "keyboards. Practically speaking, - Quantity and UOM — Match the vendor's catalog UOM. If not, use the last PO price or vendor quote. "
  • Commodity code — UNSPSC or internal taxonomy. Also, ordering "1" when they sell by "case of 10" creates a mess. Also, - Unit price — Estimated. That's why split across codes if needed. - Account distribution — The budget hit. If you have a contract, pull the contract price. So this drives contract pricing, tax treatment, and reporting. Guessing here breaks downstream analytics. Percentages must equal 100%.

Some disagree here. Fair enough That's the part that actually makes a difference..

5. Attachments — The Evidence Package

At its core, where most rejections originate. Required attachments typically include:

  • Quotes — Three for competitive bids, one for sole source with justification
  • Sole source justification form — If you're not bidding it out
  • Specifications or scope of work — For services or complex goods
  • IT security review — For software/hardware
  • Legal review — For contracts, subscriptions, terms-heavy purchases

Name your files clearly: Quote_VendorA_Keyboards_20240515.pdf not scan001.pdf No workaround needed..

6. Approval Routing — Know Your Chain

The system usually auto-routes based on:

  • Dollar amount (tiered thresholds)
  • Commodity type (IT, facilities, professional services)
  • Cost center (manager, then director, then VP)
  • Special flags (capital, sole source, international)

But you often have to add

But you often have to add a manual override—especially when a request falls outside the standard thresholds or involves a new vendor. In those cases, you’ll need to:

Action When to Use How to Execute
Add a custom approver Project‑specific manager not in the default hierarchy In the “Approvers” tab, click Add and type the name/role. g.
Overrideांश limits Amount exceeds the pre‑set capproc Check Override and provide a brief justification in the comment box. Consider this:
Flag for audit High‑risk commodity (e. , weapons, pharmaceuticals) Select the Audit checkbox and attach the required compliance document.

You'll probably want to bookmark this section Small thing, real impact..


7. Submission & Immediate Post‑Submission Actions

  1. Double‑Check the Summary
    Review the auto‑generated summary PDF. Verify that all line totals, tax calculations, and account splits match your expectations Most people skip this — try not to..

  2. Send a Confirmation Email
    Even if the system auto‑notifies approvers, send a brief email to the requestor confirming receipt and expected timeline—this reduces follow‑ups.

  3. Set a Reminder
    Use the system’s calendar feature to flag the requisition. If no response within 48 hrs, the system will ping the approver automatically And that's really what it comes down to..

  4. Archive the Draft
    Keep a copy of the original PDF in a shared drive under Procurement – Drafts for audit purposes Turns out it matters..


8. Common Pitfalls and How to Avoid Them

Pitfall Why It Happens Quick Fix
Missing “Requested By” field Forgetting to fill mandatory fields Use the “Auto‑Fill” button; the system pulls your profile. Here's the thing —
Late attachments Uploading after approval begins Attach all required docs before hitting Submit.
Incorrect commodity code Typing errors or using a generic code Validate against the company’s code list before saving.
Over‑budgeting line items Not checking the current budget balance Click “Budget Check” next to the amount; adjust or request budget release.
Wrong currency Defaulting to local currency for international purchases Switch to the vendor’s currency in the header; the system will recalc totals.

9. Leveraging Technology for a Smooth Flow

  • Smart Suggestions – Enable the AI‑powered “Suggest Items” feature; it pulls the most frequently ordered items for your department.
  • Batch Upload – For recurring orders, use the CSV import tool and map columns to the required fields.
  • Mobile App – Approve or reject on the go; the app syncs with the desktop system in real time.
  • Analytics Dashboard – Review spend by category, vendor, and approval time to spot bottlenecks.

10. Training & Continuous Improvement

  1. On‑boarding Workshops – New employees should attend a 2‑hour hands‑on session covering the requisition workflow.
  2. Monthly “Ask the Buyer” Q&A – A live session where buyers answer real‑world questions.
  3. Feedback Loop – After every rejection, the requester should fill a brief survey; use the data to refine the form fields and guidance.
  4. Process Audits – Quarterly reviews of 10% of requisitions to ensure compliance and identify training gaps.

Conclusion

A requisition form is more than a bureaucratic hurdle; it is the first unequaled touchpoint between a business unit and the procurement engine. Remember that the key to acceptance is clarity, completeness, and adherence to the established thresholds. By mastering each field—header, line items, attachments, and routing—you transform a paper‑heavy process into a streamlined, data‑driven workflow. When you present a clean, fully‑filled requisition, you not only speed up approval but also reinforce trust in the procurement function and safeguard the organization’s budgetary health.

Treat every requisition as a professional contract in miniature—complete it meticulously, and the chain of approval will follow swiftly and smoothly.

Just Went Live

Fresh from the Desk

Along the Same Lines

A Few More for You

Thank you for reading about Skills Drill 5 1 Requisition Activity. We hope the information has been useful. Feel free to contact us if you have any questions. See you next time — don't forget to bookmark!
⌂ Back to Home