City and County Fleet Divisions: Agenda Thresholds and Cooperative Contracts

Every jurisdiction sets its own thresholds and we do not pretend to know yours, but the shape is always the same. Below one figure a supervisor buys against a requisition. Above it, purchasing runs a process. Above a second figure, the award goes to a council or a board of supervisors, and at that point the packet deadline rather than the meeting date becomes the real constraint.

Two habits make this manageable. Ask for the written quote early, before anybody has decided to proceed, so the number is known rather than estimated when the route is chosen. And tell us the ceiling you are working to, because we would far rather write a scope that fits inside an authority you already hold than one that quietly pushes a nine day repair onto a public agenda six weeks out.

• Written quote first, so the route is chosen against a real figure
• Tell us the ceiling you can authorize without escalating
• Packet deadlines usually sit a week or more before the meeting
• A tabled item costs a full cycle, not a few days

Where another public agency has already competitively awarded a contract for the same category of work, many jurisdictions permit riding it rather than running a fresh solicitation. Cooperative purchasing organizations exist for exactly this, and joint powers arrangements between neighboring agencies do the same job at a smaller scale. It is comfortably the fastest legitimate route into an outside body shop.

What we need in order to be usable that way is the contract or cooperative reference, whatever documentation the sponsoring agency requires from a vendor, and confirmation of which categories the award actually covers. Whether your jurisdiction may rely on a particular award is a question for your purchasing officer and your counsel, and we take no position on it. We simply supply the paperwork the process asks for.

Most cities of any size run fleet as an internal service fund: the division pays the outside vendor, then charges the using department through a journal entry or an internal billing run. The charge only survives scrutiny if it can be traced to a unit, a date and a department, which is why the four fields we ask for at intake are not bureaucracy for its own sake.

Where a department disputes a charge months later, what settles it is an invoice naming the unit and the division it was assigned to, plus the gate photographs from arrival. We keep both. Tell us at intake which department the unit belongs to rather than which department reported the damage, because those are frequently not the same and the second one is not who pays.

Most purchasing codes carry an emergency provision for situations where waiting for a process would cause harm or serious operational failure. Whether a damaged vehicle qualifies is entirely a matter for your purchasing officer, and it is not a determination anybody at a body shop should be offering an opinion about.

What we can say is that the provisions we have seen used all involve documentation after the fact, usually a written justification and a ratification at a subsequent meeting. So the paperwork still has to exist, it just arrives in a different order. If that is the route being taken, tell us, and we will produce a dated quote and a written scope on the day rather than a verbal figure that later has to be reconstructed.

A shared fleet hides its own risk. Two identical pickups can look like redundancy on a spreadsheet while actually serving code enforcement and building inspection, so taking both in the same fortnight stops two functions at once and neither supervisor was consulted. We see this happen most often when a division decides to clear a backlog efficiently.

Send the list with the assigned department against each unit and we will stage arrivals so no single function goes dark. It usually costs nothing, because the constraint is bay time rather than calendar time and the same total work simply lands in a different order. Where the same department owns several units on the list, we will say so before anything is booked.

Assigned units across several departments sharing one fleet fund. Agency downtime is absorbed rather than invoiced, so it shows up as service levels slipping in whichever department lost the unit. Where a rental covers it, the rental is the visible cost and the internal charge follows it.

• A repair tabled at a meeting for want of a written quote in the packet
• A solicitation process longer than the repair it was meant to authorize
• A department disputing an internal charge four months after the fact
• Two divisions losing the only two units of the same type in one week