Urgency can justify faster procedures but should not eliminate authority, documentation or post-event review. The exact documents, authority limits, legal effect and terminology can differ between companies, institutions and governments, so this guide focuses on the operational principle rather than presenting one organization’s procedure as universal.
Key points
- The emergency should be genuine and time-sensitive.
- Only necessary scope should use exceptional processes.
- Price reasonableness still matters where practical.
- Repeated emergencies may indicate poor planning.
A practical way to handle it
- Start with the actual business or operational requirement.
- Identify the person or function with authority to approve and commit the organization.
- Separate confirmed facts from planning assumptions, estimates and supplier statements that still need validation.
- Record the commercial basis consistently so suppliers can be compared on the same scope.
- Keep changes, exceptions, receipt or acceptance evidence, and the final resolution in the procurement record.
Worked example
Questions worth asking
- Are quantity, unit of measure, scope and delivery expectations unambiguous?
- Is this planning information, a solicitation, a supplier offer, or an authorized purchase?
- What would make the supplier response non-compliant or commercially unattractive?
- What changes would require a new approval, revised quotation or purchase-order amendment?
- What evidence will show that the goods or services were actually received and accepted?
Common control failures
Procurement errors often come from blurred stages: somebody treats an estimate as a quote, a quote as an order, an order as proof of receipt, or an invoice as proof that the requirement was met. Good systems keep those events distinct and link them with a clear audit trail.
Keep the decision explainable
A good procurement file should allow another authorized person to understand what was needed, how the supplier was selected, who approved the commitment, what commercial terms applied, what changed, what was delivered and how any discrepancy was resolved. That does not require unnecessary paperwork; it requires the right evidence for the value and risk of the transaction.
An emergency may justify a faster sourcing route, fewer competitive steps or temporary approvals, but it does not make records unnecessary. The file should still explain the urgent need, why the normal process could not be followed, who authorized the exception, what was purchased, how price reasonableness was considered and what happened afterward. Once immediate risk has passed, organizations can review repeated emergency purchases to see whether better planning or standing arrangements would reduce future urgency.