Emergency Purchasing Rules for Field Technicians

A compressor contactor fails on a 94-degree Saturday. The technician is standing in a customer's garage, the nearest supply house closes in forty minutes, and the owner's phone is face down at a kid's soccer game. What happens next is decided by whatever the technician believes the rules are.

In most owner-run trade businesses, the rules are a mix of habit, memory and one angry conversation from three years ago. One tech buys the $380 part on his personal card and waits to be reimbursed. Another drives 40 minutes back to the shop to avoid spending anything. A third calls the owner four times and gets no answer.

None of those outcomes are the technician's fault. The owner never wrote the decision down.

Emergency purchasing rules fix this. They aren't paperwork for its own sake. They are one operating decision, made once, in writing, so the 9 pm phone call never has to happen. This post walks through what to put in the policy: spending tiers, a safety exception, approved vendors, receipt requirements, escalation and review. Every dollar figure below is a hypothetical example. Replace it with your own.

Why emergency purchases are an operating decision, not a technician judgment call

Calling an emergency purchase a judgment call sounds respectful of your people. It's actually a handoff of a decision that belongs to the owner.

Think about what the technician is weighing in that garage. Cash exposure, customer patience, whether the part will be reimbursed, whether the owner will grumble about the price. You are asking a field employee to guess your risk tolerance with incomplete information and a customer watching. Some will guess too tight and lose the job. Some will guess too loose and buy a $1,200 part that sat in the truck stock two bays over.

The cost of leaving it unwritten shows up in three places. First, margin: unplanned retail-price parts bought at the closest counter instead of your account vendor. Second, speed: technicians stalling on the phone while a no-heat call sits unresolved. Third, accountability: when a purchase goes sideways, nobody can say whether the technician followed the rules, because there were none.

Treat this like pricing or hiring. You decide it deliberately, you write it down, and you revisit it on a schedule. The owner's job isn't to approve each purchase. It's to decide, ahead of time, what the business will pay for on its own authority and what needs a second set of eyes.

A good policy has one test: can a technician with two years of tenure make the right call without calling anyone, at 9 pm, in under a minute? If not, it isn't finished.

That moves the owner from approver to rule-writer. You give up the 9 pm phone call and get a document that works while you sleep.

Set the spending limits yourself: a tiered approval ladder (hypothetical example, not a standard)

There is no industry standard for how much a technician can spend without asking. The right number depends on your average ticket, your margin and how much cash you can tolerate being wrong about. So pick the numbers yourself, and build them as a ladder rather than a single cap.

Here is a hypothetical example. Treat every figure as a placeholder.

• Tier 1, up to $150: The technician buys and proceeds. No call. Covers fittings, capacitors, fuses, small supplies.

• Tier 2, $151 to $500: The technician buys and proceeds, but texts the dispatcher or service manager before checkout with the part, the price and the job number. A reply isn't required to continue.

• Tier 3, $501 to $1,500: The technician must get a yes from the service manager or owner before buying. The dispatcher can approve if the manager is unreachable (see the escalation section).

• Tier 4, over $1,500: Owner approval only, and usually this is a quote and a return trip, not an emergency purchase.

The ladder has two jobs. It lets most purchases happen with zero friction, because most emergency buys are small. It also concentrates your attention on the few that actually move margin.

Two rules make the ladder work. First, set it per job, not per day, so a technician can't split a $900 part into three transactions. Second, state what counts as one purchase: parts plus freight plus any rental equipment on the same ticket.

Pick your Tier 1 number by looking at the last 90 days of receipts. If 70 percent of emergency buys fall under a number, that number is a candidate. Write the ladder on one page. A technician should be able to read it in 30 seconds.

Write the safety exception so it protects people first and spending second

Every spending rule needs one sentence that overrides all the others. It should say that when there is an active safety hazard, the technician acts first and reports after.

Gas leak. Exposed live conductors. A flooding supply line that will damage a finished basement. Carbon monoxide from a cracked heat exchanger. In those situations nobody should be reading a policy or waiting for a callback. The technician makes the site safe, buys what is needed to do it, and documents it.

Write the exception narrowly enough that it can't be stretched. A good version has three parts:

1. What qualifies: an immediate threat to life, health or property that can't be controlled without the purchase. A warm house in January is uncomfortable. A failed gas valve is a hazard.

2. What is allowed: the technician may exceed any tier limit for the minimum parts or materials needed to make the situation safe, not to complete the repair.

3. What follows: the technician notifies the on-call contact as soon as the situation is stable and files the incident note by next business day.

The last line matters most. Say plainly that a technician will never be disciplined for spending money to protect a person. If technicians believe they might be, they will hesitate at the exact moment hesitation is expensive.

The OSHA general duty clause already puts the burden of a safe workplace on the employer (OSHA, 2026). Your policy should make clear that the business backs its people when they act in good faith.

Keep the exception short. If it's a full page, technicians will remember the page and forget the intent.

Approved vendors and payment methods: where technicians buy and how

A spending limit without a vendor list is half a policy. Where the technician buys matters as much as how much they spend, because the same compressor can cost 30 percent more at a retail counter than at your account supplier.

Build a short approved vendor list, ordered by preference. For a typical HVAC or plumbing shop that might be:

1. Your primary account supplier (net terms, contractor pricing)

2. A backup account supplier (see supplier concentration risk for why you want one qualified before you need it)

3. A named big-box store, for fittings and consumables only

4. Anyone else, only under the safety exception or with dispatcher approval

Then decide how technicians pay. You have three realistic options, and you should pick one as the default:

• Company card issued to each technician, with the Tier limits set at the card level where your card provider allows it.

• Vendor account with a technician PIN or job number, so purchases bill to the shop and tie to a ticket automatically.

• Personal card with reimbursement, which you should treat as a last resort. It creates cash-flow friction for the employee, slow reimbursements breed resentment, and it makes your spending harder to see.

My position: vendor accounts first, company cards second, personal cards only when nothing else works. Account purchases carry the job number from the start, which makes the receipt step almost automatic.

Write the list on the same page as the ladder. Update it when a supplier changes terms or a branch closes. A stale vendor list sends a technician to a counter that no longer takes your account.

Receipts and the incident note: what a technician submits by next business day

Technicians will follow a receipt rule only if it's small. Ask for a form and a paragraph, and you'll get neither. Ask for two things and you'll get both.

The policy should require two items by the end of the next business day:

1. The receipt or invoice, photographed and sent to a single destination (a shared inbox, a field-service app field, or a dedicated text number). Not three places.

2. A short incident note, three to five lines, answering the same questions every time.

The incident note is the part most shops skip, and it's the part that makes the system worth running. Standardize it:

• Job number and customer

• What failed and what the technician found

• What was bought, from where, for how much

• Why it couldn't wait (safety, customer on-site, no stock on truck, supply house closing)

• Whether the part was installed or returned

That note takes two minutes at the end of a call. It also turns every emergency purchase into a data point. Over a quarter, you will see which truck is missing which parts, which technician keeps paying retail, and which supplier is out of stock most often.

Hold the deadline firmly but fairly. Next business day is realistic, because Friday-night emergencies shouldn't require weekend paperwork. Say so in the policy, and say what happens at 48 hours with nothing submitted: the dispatcher follows up, and repeated misses are a coaching conversation, not a payroll deduction.

If a purchase also affects the customer's invoice, route the receipt to whoever bills the job. A $400 part that never reaches the invoice is a $400 margin leak you won't notice until the monthly review.

Escalation: who answers the phone, and what happens when no one does

The ladder says when to call. Escalation says who picks up, and what the technician does if nobody does. Most policies skip the second half, and it's the half that fails at 9 pm.

Name people, not roles. A policy that says "contact management" is a policy that gets ignored. Write an escalation chain with first and second names and a response window:

1. On-call service manager, responds within 10 minutes

2. Dispatcher or office lead, can approve up to Tier 3 if the manager doesn't respond

3. Owner, reached only for Tier 4 or for a safety event that is still unresolved

Then write the rule for silence. If nobody answers within the window, the technician follows a default. A reasonable default, in hypothetical terms: for any purchase at or under Tier 3, buy it, document it and proceed. For anything over Tier 3 with no safety issue, secure the site, tell the customer you'll return with the part, and log the call. A missed call shouldn't force a technician to choose between an angry customer and an unauthorized purchase.

Publish the on-call rotation weekly so technicians never wonder who is covering. If you are the on-call contact for everything, that's a signal. It often means the business needs someone between the owner and the field, which is the situation covered in hiring your first operations manager.

Test the chain once a quarter. Call the dispatcher line at 8 pm on a Tuesday and see who answers. One failed test call will teach you more than a page of policy language.

Next-day review and a monthly look at patterns, then put the policy in your decision record

Rules that nobody reviews decay within a quarter. Build two review habits into the policy itself.

The next-day review. Each morning, the dispatcher or service manager scans yesterday's emergency purchases against the ladder. The check takes five minutes: Was the tier respected? Is the receipt in? Is the incident note complete? Did the part reach the invoice? Anything unusual gets a short conversation that day, while the memory is fresh and the tone can be curious rather than punitive.

The monthly pattern review. Once a month, the owner or operations lead looks at the aggregate. Questions worth asking: How many emergency purchases happened, and in which tiers? Which parts show up repeatedly (a signal for truck stock)? Which technicians buy most often, and is that a training gap or a stocking gap? What is the total, and what share of revenue is it? Is the safety exception being used, and used appropriately?

A repeated $180 purchase of the same capacitor isn't an emergency. It's a stocking decision you haven't made yet. Fixing it saves money and a Saturday call. This kind of review fits naturally into your monthly business review agenda as a standing five-minute item.

Then write the policy down where it will outlive your memory. The ladder numbers, the safety exception, the vendor list, the escalation chain and the review cadence are all operating decisions with a date, an owner and a reason. When you change a limit from $150 to $250, record why. Six months later, nobody will remember, and the next hire will ask.

This is the kind of decision Finnus is built to hold. A Finnus Board meeting gives you an experienced outside partner to pressure-test the limits, and the decision lands in Business Memory, the lasting record, so the rule is written once and stays findable.

Conclusion

Pick one afternoon this month and write the one-page policy: your ladder, your safety exception, your vendor list, your escalation chain and your review cadence. Use the hypothetical numbers above as a starting draft and replace every figure with your own. Then test it by asking your newest technician to explain it back to you in two minutes.

If you want an outside view before you commit, bring the draft to a free 30-minute intro call with Finnus. Bring the decision, leave with a sharper set of limits, and have the final version recorded in Business Memory with Finnus Board at $999/month if you want it reviewed monthly. My prediction: the first 9 pm call you don't get will be worth more than the afternoon you spent writing the policy.