Why do emergencies break procurement?
A flood, an outbreak or a displacement changes the clock. Normal procurement can take weeks: request, quotations, approval, order, delivery. People in the field cannot wait that long, so they buy on the phone, pay in cash, and write it up later. Some of that is right. The risk is that “emergency” becomes the reason for every shortcut, and the file is thin when the donor or auditor looks at it.
The aim is not to slow the response. It is to know in advance which steps may shrink, and which must stay.
What can you relax, and what must you keep?
| Relax in an emergency | Keep in an emergency |
|---|---|
| Number of quotations (for example one or two instead of three) | A written request naming the project and budget line |
| Time allowed for bidding | An approver who is not the requester |
| Formal tender documents | A record of why speed was needed |
| Waiting for the full committee | A record of who was paid and for what |
| Pre-qualification of new suppliers | Proof the goods arrived |
The left column saves days. The right column is what lets you defend the purchase later. If you have to choose between speed and the right column, find a faster way to do the right column, such as a phone approval confirmed by message within a day.
How to prepare before an emergency
Preparation is where most of the speed comes from.
- Write an emergency rule. One page: what counts as an emergency, who declares it, what is relaxed, what approval is needed, and how long it lasts.
- Pre-select suppliers. Keep a list of suppliers already checked for common emergency items such as water treatment, tarpaulins, fuel, transport and food. See when to use framework agreements for the next step.
- Set emergency approval limits. Name who can approve what, including a back-up when the usual approver cannot be reached.
- Agree cash rules. If suppliers only take cash in the first days, set a ceiling and a recording method.
- Brief the team. The rule helps only if the field officer who needs it has read it.
What does a good emergency purchase file contain?
Make it short enough that busy people will finish it. For each emergency purchase:
- The declaration of emergency, with the name of the person who made it and the date.
- A short request: what is needed, how much, for which project and budget line.
- The reason normal steps were not followed.
- The quotations you did get, even if only one, and a line on why the supplier was chosen.
- The approval, with the approver’s name, role and time.
- The delivery note or receiving record.
- The invoice and payment evidence.
An honest note such as “Only one supplier had fuel in the town” is far better than a file with invented quotations.
How do you stop emergency rules from spreading?
Three habits keep the rule narrow.
- Time-box it. The emergency rule ends on a stated date unless a named person renews it in writing.
- Split urgent from ongoing. A tent now is an emergency. A monthly tent supply is a normal contract. Move recurring needs to the normal process as soon as you can plan.
- Review afterwards. Within a few weeks, someone not involved in the buying looks at the emergency purchases. They ask: Was speed really needed? Was the price fair? Was anything bought twice? Was any link to a supplier left unspoken?
Our article on managing conflict of interest in procurement explains why the review matters most when speed is high and pressure is strong. Emergencies are when people’s ties to suppliers are most likely to go unmentioned.
What about splitting and repeated orders?
Emergency rules attract a particular trap: several small purchases from the same supplier that together are large. Each looks fine alone. Together they would have needed a tender. Check purchases by supplier and by week, not only one by one. If you see a pattern, treat it as a single purchase and approve it at the level its total requires.
What should the debrief ask?
After the response settles, hold a short lessons session. Useful questions:
- Which delays came from the process, and which from the market?
- Which suppliers performed well, and should be pre-approved?
- Which steps did staff skip that they should not have?
- Did the rule’s time limit work?
Feed the answers into your procurement policy and your supplier list before the next event.
Where EMPOBase fits
EMPOBase Procurement records requests against a project and budget line, routes them through approval levels L1 to L5 that your organization sets, and keeps a record of who approved, when and any note. The requester cannot approve their own request. Purchase orders keep committed funds visible against the budget, and approved requests post to the ledger exactly once. EMPOBase does not make bank transfers or record proof of payment, and a goods received note does not move stock. Your emergency rule, and who may declare one, stays with your organization. See the procure-to-pay workflow.