Routed approvals with preferred-vendor catalogs
A 30-day operational improvement plan for routing purchase approvals and guiding buyers to preferred-vendor catalogs, with measures for requisition cycle time and supplier on-time delivery.
Trusted by frontline teams 15 years of frontline software
Built for: Technology And Software · Healthcare It · Higher Education · Manufacturing Operations · Professional Services
Overview
This operational improvement plan helps an IT or asset purchasing team change two connected parts of requisition handling: how requests reach approvers and how buyers choose suppliers. It is built around a 30-day measurement window and tracks two specific outcomes: requisition cycle time and supplier on-time delivery. The plan gives the team a starting point for defining preferred-vendor catalogs, assigning approval paths, and checking whether the new workflow improves purchasing flow without weakening controls.
Use it when routine purchases are delayed by unclear ownership, repeated supplier selection, inconsistent approval chains, or limited visibility into promised and actual delivery dates. It works particularly well for recurring hardware, software, accessories, maintenance items, and other IT assets that can be grouped into approved catalog categories. Adapt the plan to include spend thresholds, cost centers, budget owners, exception reasons, and supplier-specific rules.
Do not use this template as a substitute for a competitive sourcing event, a contract review, an emergency procurement procedure, or a detailed supplier scorecard. It also should not assume that a preferred vendor is always the lowest-cost or fastest option; exceptions need a documented path. Before rollout, agree on when the cycle-time clock starts and stops, how on-time delivery is calculated, and who owns catalog and routing maintenance. The recorded result belongs to the organization running the plan; any improvement should be verified from its own requisition and receipt data.
Standards & compliance context
- Align approval thresholds, separation of duties, supplier restrictions, and audit retention with the organization’s procurement and financial-control policies.
- For public-sector, education, or grant-funded purchasing, confirm that preferred-vendor catalogs do not bypass required competition, quotation, accessibility, or funding-source rules.
- Retain routing decisions, exception reasons, purchase records, and delivery evidence according to applicable procurement, contract, tax, and records-management requirements.
- Have legal, finance, or internal-audit owners review supplier eligibility and catalog governance where the organization operates under regulated procurement controls.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
How to use this template
- 1. Define the baseline and measurement rules by recording current requisition cycle time, promised delivery dates, actual receipt dates, approval stages, and the 30-day review period.
- 2. Build the preferred-vendor catalog by grouping common IT and asset purchases, confirming supplier status and pricing, and documenting which items require an exception.
- 3. Configure approval routes by spend threshold, category, cost center, and exception type, then name primary and backup approvers for each path.
- 4. Assign the plan to procurement, IT asset, finance, and budget-approval owners and brief requesters on how to select catalog items or submit non-catalog requests.
- 5. Run the routed process for the measurement window while logging approval timestamps, supplier commitments, receipts, delays, and approved exceptions.
- 6. Review requisition cycle time and supplier on-time delivery against the baseline, identify bottlenecks or catalog issues, and update routing, supplier rules, or follow-up actions.
Best practices
- Define requisition cycle time consistently, such as from submission to final approval or from submission to purchase-order release, and use the same definition throughout the review.
- Route routine catalog purchases through the shortest policy-compliant path instead of sending every request to a central procurement queue.
- Set primary and backup approvers with response expectations so absences do not create invisible queue delays.
- Keep preferred-vendor catalogs limited to current items, valid pricing, usable delivery terms, and suppliers that have passed the organization’s required checks.
- Record promised and actual delivery dates from the same source so supplier on-time delivery is not distorted by inconsistent date entry.
- Create a clear exception reason for urgent, unavailable, specification-sensitive, or contract-bound purchases and review those exceptions separately.
- Photograph or retain receiving evidence only where the asset process requires it, and reconcile partial deliveries rather than marking the entire requisition complete.
- Re-check the workflow after go-live because a shortened approval path can expose new delays in purchasing, fulfillment, receiving, or asset registration.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What purchasing process does this template cover?
This template covers requisitions that need review before purchase, including approval routing, preferred-vendor selection, and follow-up on supplier delivery performance. It is suited to recurring IT, equipment, software, and asset-related purchases. It does not replace a full sourcing event, contract negotiation, or emergency-buy procedure.
Who should run this improvement plan?
A procurement or IT asset manager should own the plan, with participation from budget approvers, requesters, accounts payable, and key suppliers. Assign one person to maintain approval rules and catalog content, and another to validate cycle-time and delivery data when possible. Keep finance or compliance stakeholders involved where purchasing controls require their review.
How often should the process be measured?
Use a 30-day measurement window to compare requisition cycle time and supplier on-time delivery before and after the routing and catalog changes. Review approval delays weekly during rollout, then inspect the two target metrics at the end of the window. Repeat the review after major catalog, supplier, policy, or organizational changes.
Does this template support regulated or controlled purchasing?
It can support purchasing controls when approval thresholds, separation of duties, supplier restrictions, and audit records are defined by the organization. The plan should be checked against applicable procurement policies, public-sector purchasing rules, contractual obligations, and financial-control requirements. It does not by itself certify compliance or replace legal, tax, or internal-audit review.
What is a common pitfall when implementing routed approvals?
A frequent pitfall is routing every request through the same approver chain, which can add delay instead of removing it. Define paths by spend level, category, cost center, and exception type, and provide a documented fallback for unavailable approvers. Also re-check catalog prices, availability, and supplier status so the preferred list does not become stale.
Can I customize the plan for different approval thresholds or catalogs?
Yes. Customize the routing rules, preferred-vendor categories, approval thresholds, exception reasons, owners, and review cadence to match your purchasing policy. You can also separate standard catalog purchases from non-catalog requests that require sourcing or additional justification.
Can this template connect to procurement or asset systems?
Use it alongside a procurement, enterprise resource planning, accounts payable, or IT asset-management system. Capture requisition creation, approval timestamps, supplier, promised date, actual receipt date, and exception status from the systems your organization already uses. If direct integration is unavailable, a controlled export or shared measurement log can support the 30-day review.
How does this compare with managing approvals ad hoc?
Ad hoc approval handling often leaves requesters unsure where a requisition is waiting and makes supplier performance difficult to compare. Routed rules create a repeatable path, while preferred catalogs reduce unnecessary supplier selection work. The template adds a defined measurement window so teams can distinguish a real process improvement from a short-term impression.
Related templates
Ready to use this template?
Get started with MangoApps and use Routed approvals with preferred-vendor catalogs with your team — pricing built for small business.
