Contracts, insurance, and buying right

You are holding a contract a vendor wrote. The board expects you to know whether its terms are fair before anyone signs it.

A proposal, a service agreement, a purchase order: something like it is sitting in your inbox right now. Reading it like someone whose money is on the line is part of the job now.

That expectation shows up the moment you move from running the plant to running the business. The dollars behind that contract are not yours. They came out of a rate bill or a tax account. A neighbor at the grocery store has every right to ask why you spent them that way.

Rung 4 of the manager track.

Buying right does not start with the signature. It starts with a process the board can point to, and a habit: read past the price line before you agree to anything.

Why every purchase is the board's business

Running the system as an enterprise means customer revenue gets spent on operating the system, paying its debt, and building its reserves. Nothing else. That single rule is why a purchase you would never think twice about at home draws a second look here.

Protecting the integrity of the utility's money is one of your core financial responsibilities as a board member or manager. So is setting the framework, planning ahead, adopting a budget, and watching performance month to month. A contract signed without a documented process behind it puts that responsibility at risk, even when the deal itself turns out fine.

That same enterprise-accounting rule limits what customer revenue can pay for in the first place: operating the system, servicing its debt, and funding the reserves the board has approved. A purchase that does not fit one of those buckets needs a harder look before it goes forward, not after the check clears.

Conflicts of interest get their own rule for a reason. A board member's own company is not normally treated as a qualified vendor for the utility. If unusual circumstances mean you use one anyway, write down the reason on the purchase paperwork and disclose it in full in the financial statements. That vendor gets no preferential treatment over anyone else who bid.

What bids and quotes are actually for

The point of comparing bids is not squeezing out the lowest possible number. Purchasing runs on a competitive, least-cost basis, but the board can weigh other factors too:

• payment terms
• whether the vendor can actually deliver on time
• warranties
• delivery and setup charges
• what the item costs to operate once you own it
• how reliable that vendor has been before

Getting quotes in writing, side by side, turns "I picked the contractor I know" into "here is why this vendor won." That comparison is the paper trail an audit wants to see. It is also the answer you give the neighbor who asks.

For a large or complex purchase, some systems separate the two questions instead of scoring them together. Rank the vendors on qualifications and references first, sealed cost proposals second. If the best-qualified vendor is not the cheapest, you at least know that going in, and you have room to negotiate the price with a clear reason why.

Matching the process to the size of the purchase

Not every purchase needs the same amount of paperwork behind it. One procurement schedule built for small utilities scales the process to the dollar amount. A $300 part and a $50,000 contract do not go through the same steps:

• Under $500: an open-market purchase, no quotes required.
• $500 to $1,000: at least three oral quotations before you buy.
• $1,000 to $5,000: at least three written quotations before you buy.
• Over $5,000: sealed, competitive bids from qualified vendors.

Treat that scale as one working model, not your system's actual rule. Your own thresholds live in your adopted purchasing policy.

That policy has to line up with your state law, your bylaws or charter, and any loan or grant agreement that applies to your system. Check your own policy before you rely on a dollar figure. If you do not have one, that is a gap worth closing with legal help before your next large purchase, not after it.

Before you sign

Read past the price line. Is the price locked, or can the vendor change it later? What happens if the work is late or the equipment does not perform? What warranty applies, and for how long?

Confirm a written purchase order or requisition exists before the vendor starts work, and that it is approved before any money moves. Confirm, too, that the person approving it is not the same person who wanted the purchase. Splitting that responsibility protects the utility and the vendor both; no single person's judgment is the only thing standing behind the money.

Routine bills like payroll and the electric bill do not need a fresh purchase order every month; they are expected and already in the budget. Everything outside that routine list does, no matter how well you know the vendor.

Once a bill is paid, mark it "paid" and initial it. Duplicate payments are one of the easiest mistakes to make on a small staff. They are also one of the easiest to catch if that habit is already in place.

Keep the whole file together: the requisition, the quotes you compared, the signed contract, and the paid invoice. Financial records generally need to be kept for at least seven years past the current fiscal year. A complete contract file is exactly what an auditor, a lender, or a curious ratepayer asks to see first.

When the emergency exception still needs paperwork

A burst main at two in the morning cannot wait for three written quotes, and the process allows for that. Emergency purchases can skip the normal bid and quote requirements.

That exception is not a blank check, though. Document the emergency on a purchase requisition with a written explanation. Get that explanation on paper within two working days of the repair. A year later, when someone reviews the file, "we had no choice, and here is why" needs to already be written down, not remembered.

Insurance and bonding, in short

Two kinds of coverage protect the system in different directions. Both belong in your purchasing conversation, even though neither is a purchase itself.

A fidelity bond protects the utility from its own people. Anyone who receives, handles, or spends system funds should be bonded. That way, no single person with access to money becomes a single point of financial failure. General insurance protects the system from everything else: property damage, liability claims, and losses that could otherwise wipe out reserves built up over years.

Picture the difference. A fidelity bond pays out if the person who handles deposits is the one who takes money. General insurance pays out if a storm floods the treatment building or a delivery truck backs into a hydrant. A small system carries both, not one or the other.

What coverage you need, and how much of it, is a question for your insurance agent and your attorney. It is not a number this guide can hand you. A quick legal review of an unfamiliar policy is worth the wait. It is the same wait a second quote asks for on a purchase over a few thousand dollars.

Where to go from here

Buying right is a process question: who reads the contract, who approves it, and what paperwork proves you did both. What your engineer negotiates on the technical side of a project is its own skill, covered in your engineer works for you. Once state or federal money is actually in the bank, a different set of rules kicks in, covered in after you win the money. For the rest of the manager track, the field guide picks up from here.