Six Tables to Master Procurement Planning: From Annual Strategy to Exception Handling

Many companies treat procurement as constant firefighting, but the root cause is often a lack of structured procurement planning. Annual, monthly, and ad-hoc demands get mixed together without unified standards for timing, justification, inventory visibility, or approval authority.

The solution is to split planning into three layers: annual sets budget and direction, monthly sets purchasing rhythm, and ad-hoc handles exceptions. Six tables connect these layers into a complete chain: request → inventory check → demand balancing → approval → execution → receipt → exception review.

1. Annual Procurement Plan

Purpose: answer three questions — how much will we spend this year, which categories, and which resources need early preparation. It is not a detailed purchase list; listing every material a year ahead makes the plan obsolete when business changes.

Key fields: requesting department, procurement category, planned project, estimated amount, budget source, demand basis, procurement cycle, critical material flag, supplier readiness, notes. Focus on budget and category, not individual SKUs.

Example: Equipment department budgets ¥500k for spare parts, Production budgets ¥3M for packaging, Projects budget for outsourced processing. Management uses this to decide which categories need framework agreements, which long-lead items require early supplier locking, which purchases align with cash flow, and which demands are merely departmental wishes needing confirmation.

The plan must allow rolling correction: set budget and category framework at year start, then adjust quarterly or monthly based on actual consumption, order changes, and inventory status.

2. Monthly Procurement Demand Table

Annual plan sets direction; monthly plan drives execution. The biggest risk is demand without rhythm: late submissions, split orders for the same item, duplicate requests despite existing stock, and unrealistic lead-time expectations (e.g., supplier needs 20 days but department demands 7).

Required fields: using department, usage scenario, demand reason, planned use date, requested quantity, current stock, in-transit quantity, safety stock, suggested purchase quantity, expected delivery date, impact on production/project milestones.

Critical trio: stock, in-transit, and safety stock. Example: workshop needs 1,000 packaging boxes next month; warehouse has 400, 500 in transit, safety stock 300. Actual purchase quantity must be recalculated using the formula: Actual procurement demand = Demand quantity – Available stock – Covered in-transit quantity , then adjusted for safety stock and delivery timing.

Monthly planning cannot stop at department submission. The flow: department submits demand → warehouse verifies stock → procurement confirms lead time → finance/budget checks quota → company-level monthly plan finalized. Using a platform like 简道云 to link demand submission, stock check, and quantity confirmation in one workflow prevents scattered requests in WeChat/Excel and manual re-aggregation.

3. Ad-hoc Procurement Request

Unplanned needs are inevitable: equipment failure, rush orders, project changes, quality rework. The table must capture three dimensions:

Trigger cause — forecast miss, plan change, equipment breakdown, customer rush, or departmental omission. Genuine emergencies get fast-track; repeated omissions should not rely on the ad-hoc channel.

Urgency with business consequences — not just “urgent” but: will it stop the line? affect customer delivery? what is the daily delay cost? are substitute materials available? can stock or borrowing bridge the gap?

Special procurement conditions — sole-source, price premium, skipped bidding, purchase-before-approval. Record reason, approver, and outcome for later review to distinguish true emergencies from planning gaps.

Ad-hoc must not become a universal queue-jumping channel.

4. Procurement Demand Consolidation & Balancing Table

Having annual, monthly, and ad-hoc demands is not enough; departments request what they want, but the company must buy what is truly needed after balancing.

Three core actions:

Merge similar demands — different departments requesting the same material (office supplies, standard parts, PPE, packaging, common auxiliaries) are consolidated to reduce duplicate orders and enable volume pricing.

Deduct stock and in-transit — requested quantity ≠ purchase quantity. Apply the formula above, then factor in safety stock and arrival timing to avoid over- or duplicate purchasing.

Set procurement priority — not everything is “urgent.” Priorities based on business impact: protect production, protect customer delivery, safety/compliance, project milestones, general replenishment, deferrable. Priority should be jointly confirmed by business, procurement, warehouse, finance, and management — not decided by procurement alone. When supplier capacity, procurement resources, or cash flow are constrained, allocation follows rules, not lobbying.

5. Approval Workflow Table

A plan without a defined process fails. After submission: who reviews? who confirms stock? who checks budget? who judges urgency? what amount triggers higher approval? what causes rejection? All must be predefined.

Standard monthly flow: Department submits → Department head reviews → Warehouse confirms stock → Procurement checks lead time/supplier → Finance/budget verifies quota → Approver signs off → Procurement executes.

Branches based on real business:

By amount: small → department approval; medium → division head; large → senior leadership.

By type: fixed assets, production materials, office supplies, outsourced services each mapped to relevant reviewers.

By urgency: normal follows standard flow; urgent compresses nodes but adds post-hoc review.

By budget: within budget → normal; over budget → supplemental approval.

Using 简道云 to build the workflow strings nodes by business rules; exceptions (budget shortfall, missing docs, urgent buy) route back to the responsible step automatically instead of chasing approvals in chat groups. Clear return rules: which cases go back to department for补充, which to warehouse for re-check, which to procurement for re-quote, which are rejected outright.

6. Procurement Execution Tracking Table

Approval ≠ completion. Post-approval steps: PO issuance, supplier confirmation, delivery, inspection, put-away, plus delays and exceptions.

Fields: request ID, category, supplier, PO number, order date, promised delivery, actual delivery, received quantity, put-away quantity, exception reason, responsible party, resolution, business impact flag.

Focus on deviations and exceptions, not just completion counts. Track: which suppliers frequently delay? which departments often raise last-minute needs? which materials show large plan-vs-actual consumption gaps? which approvals are fast but delivery stalls? which exceptions remain open?

Especially for delivery exceptions, categorize root cause: supplier delay, late PO placement, late demand submission, approval bottleneck, or quality rejection. Only with documented causes and resolutions can future plans and supplier management be adjusted.

Closed-Loop Procurement Planning

The six tables are not extra paperwork; they link the critical nodes: annual sets direction, monthly sets rhythm, ad-hoc governs exceptions, consolidation balances, approval assigns accountability, execution tracks results. The complete chain: Request → Inventory check → Demand balancing → Approval → Execution → Receipt → Exception review .

Procurement shifts from passive order-taking to proactive visibility: seeing demand early, judging gaps, scheduling rhythm. Ad-hoc requests no longer prioritize by loudest voice but by documented cause, approval, and record. The core questions remain: should we buy, how much, when, who approves, who tracks, how to fix problems. The tables are merely the vehicle; the goal is a connected, executable, trackable, and reviewable management process.