Procurement: preparing comparable requests

A need must become specific

Office equipment requests lack quantities, usage, deadlines and acceptance criteria. Intake should obtain requester-supplied details, not invent technical specifications. Category-specific fields distinguish materials, services and subscriptions. Clear capture reduces follow-up and identifies specialist review needs before approaching suppliers. Ask the requesting area to explain the intended use and acceptable outcome when a specification is unclear. Procurement can coordinate that clarification without choosing technical requirements on the requester’s behalf. Keep the response associated with the request so suppliers and reviewers work from the same assumptions rather than separate interpretations.

Quotes with matching scope

Prices mean little when suppliers quote different deliverables. Preserve request versions and a common scope. Track changes requiring updated quotes. Review units, taxes, timing and exclusions extracted from documents. Comparison tables must retain meaning-changing notes, with explicit decision criteria and accountable review.

Separate approval from execution

Recommendations, authorization and sent orders are different states requiring ownership and evidence. Amount or scope changes may trigger renewed review. Supplier messages must follow actual status. This supports later reconciliation of requested, approved and received work rather than relying on informal conversations as commitment evidence. The approval record should identify the version reviewed, not only the name of the person who approved it. If quantities, conditions or deliverables change later, the team needs to determine whether the existing approval still applies under internal rules. This makes exceptions explicit rather than allowing an old approval to cover a different purchase silently.

Track dependencies

Delays may involve requesters, suppliers or internal approval. Generic pending states hide actionable causes. Show next action and owner. Receipt closure should include required review and documentation. Measure incomplete specifications, incomparable quotes, post-approval changes and decision waits without blaming procurement for every delay. When a supplier responds with a condition that differs from the request, flag it as a decision for the appropriate owner. A comparison table should make those differences visible instead of treating every quotation as equivalent. Follow the selected proposal through receipt to test whether the original acceptance criteria are usable in practice and whether the required evidence can be found without reconstructing scattered messages.

An initial example

Review three historical requests in one recurring category. Identify repeated questions, comparison-changing exclusions and missing approvals, then turn findings into fields and checks before expanding automation.

Common mistakes when preparing quote requests

Quotes that are hard to compare almost always stem from a request that left room for interpretation. These are slips that tend to repeat.

• Sending the request to each supplier in slightly different wording, so the replies rest on different assumptions.
• Answering one supplier’s question only to the one who asked, without sharing the clarification with the other participants.
• Leaving out delivery, support or warranty terms and discovering them as extra costs after the choice is made.
• Comparing a unit price against a total without verifying that quantity, validity period and taxes are expressed the same way.
• Accepting a scope change after the quote without recording who approved it and why.