Government purchasing for non-procurement staff: five steps from threshold check to audit file

Non-procurement municipal staff without specialist expertise can handle government purchasing correctly by working through five steps: check your threshold and authority, document informal quotes below it, choose between a solicitation and a cooperative contract at or above it, record the reason for the award, and build the audit file as you go.

We understand the situation this describes. A department head, facilities manager, or IT lead at a city or county buys something once or twice a year, has no procurement training, and does not want a finding in next year's audit report. None of what follows requires that training. It requires knowing which questions to answer before you contact a Supplier, and what to keep once you do.

Civic Marketplace Platform is one practical option for occasional buyers managing the quote and evaluation stages of that sequence. It does not replace your Entity's legal authority or procurement office approval, and it does not resolve situations where statutory requirements are unclear.

Step 1: determine the threshold, authority, funding source, and purchase type before you contact Suppliers

Your threshold is not a universal number. Thresholds are set by state statute and by your own Entity's written purchasing policy, which means a figure that applies to a Texas city may bear no relationship to the rules binding a Washington county or a Montana school district. The Washington State Auditor's Office notes that public bidding dollar thresholds can be specific to each type of government rather than universally applicable, so the only reliable source is your own policy document and the state code it references. MRSC's contracting-requirements tool provides a useful starting point for Washington local Entities looking up applicable rules by government type.

Before contacting any Supplier, answer four questions:

1. What are we buying? A tangible good, a service, professional services, or construction work each triggers different procedures. Scope bundling creates risk: software plus implementation, equipment plus installation, or a lease with a purchase option can shift a purchase into a different legal lane. As MRSC guidance on purchasing materials and equipment explains, a purchase connected to public works may need to follow public-works requirements entirely.
2. Who can approve it? Check your Entity's delegated-authority schedule. An approval that sits inside your own budget authority is straightforward; one that requires governing-body action is not.
3. What funds are paying for it? Local funds typically follow state statute and local policy alone. When federal dollars are involved, 2 C.F.R. §§ 200.317 to 200.327 apply under the Uniform Guidance, as revised on 22 April 2024. Those rules key off two federal figures that were raised effective 1 October 2025: the micro-purchase threshold rose to $15,000 and the simplified acquisition threshold to $350,000. Both are ceilings for federal-award procedures, not permissions under your own policy, and your local threshold may well be lower. The Washington State Auditor advises following the strictest applicable requirement when federal, state, and local rules overlap.
4. Does the total scope change the lane? Calculate the full anticipated value, including the whole contract term, installation, freight, maintenance, and renewals. Leases require a full-term calculation before you determine which procedure applies.

Classification errors create more audit exposure than form errors. Getting the lane right at the start protects everyone downstream.

When to stop and escalate to procurement or legal

Some conditions mean the purchase is no longer yours to run alone. Stop and escalate when any of these is present:

• Federal funds are involved and you have not confirmed the applicable rules
• The purchase may be public works
• A Supplier is proposed without competition
• An emergency or sole-source exception is being claimed
• A conflict of interest concern exists
• The dollar value exceeds your delegated authority

These situations need your procurement office, legal counsel, or both before you proceed. Escalating costs you a few days. Discovering the problem in an audit costs considerably more, and by then the remedy is not yours to choose.

Step 2: if you are below your Entity's formal threshold, run an informal quote process that leaves a usable record

Below-threshold purchasing does not mean no process. Policy still governs how many quotes to seek, how to request them, and what to retain.

"In a small city, you don't have somebody that is that well versed in those rules because they are a jack of all trades," said Angie Smith, City Manager of Gun Barrel City in Texas. That reality is common across small Entities, and it is a pattern Civic Marketplace has documented across small cities. The answer is not improvisation. It is a documented, repeatable process that any reviewer can reconstruct.

What your intake brief should contain before asking for prices:

• Plain-language scope of work and acceptance criteria
• Budget code and funding source
• Total anticipated value and contract term
• Timeline, including required start date
• Any qualifications, licensing, or insurance the Supplier must hold

With that brief in hand, reach out to Suppliers and record each response. MRSC's guidance for Washington Entities says agencies using a vendor list should secure quotes from at least three vendors on the list, if possible, with quotations recorded immediately and made available for public inspection. Your own policy may require a different number or method. What matters for the file is that you document which Suppliers you approached, what each offered, and the date, so a reviewer sees the process and not only the result.

How Quick Quote handles the mechanics of an informal quote round

Civic Marketplace Platform's Quick Quote workflow addresses this directly. A buyer describes the need in plain language; Quick Quote matches the request to Suppliers by category, sends the request, and collects responses. Staff can compare offers side by side, then export the decision record, with approvals and timestamps, for the audit file. The workflow is designed for purchases below formal bid thresholds where three documented quotes are still required but a formal solicitation is not.

Quick Quote does not replace policy judgment about how many Suppliers to contact or whether a particular purchase qualifies for informal competition. It handles the mechanics of sending requests, collecting and comparing responses, and producing an exportable audit history with approval tracking, so documentation exists from the moment responses arrive rather than being reconstructed after the fact.

Step 3: at or above threshold, choose between a formal solicitation and a pre-competed cooperative contract

Once a purchase reaches your Entity's formal competition lane, two paths are available. The first is running your own solicitation: a sealed invitation to bid, a request for proposals, or a request for qualifications, depending on whether price alone or price plus other factors governs the award. The second is using an existing cooperative contract that a lead public agency competitively bid and awarded on behalf of participating Entities.

The cooperative route can remove the need to run a new solicitation. But it does not remove the documentation obligation.

A cooperative contract carries authority because a lead public agency ran the competition, not because the cooperative says so. That distinction is what your file has to evidence. Civic Marketplace Platform hosts TXShare Cooperative Contracts, competitively procured through the North Central Texas Council of Governments (NCTCOG). In June 2026, NCTCOG and the Alliance for Innovation (AFI) signed a reciprocal interlocal agreement giving members of either organization access to more than 500 competitively awarded contracts spanning technology, infrastructure, public safety, water and utilities, and professional services, through one agreement rather than a separate one per cooperative. Entities can search, filter, and compare contracts directly in the platform, including local and historically underutilized Suppliers.

Solicitation or cooperative contract: what each route puts in the file

The two routes differ less in difficulty than in who owns the evidence. Running your own solicitation means your Entity produces the whole document set. Using a cooperative contract means the lead agency produced most of it and you have to obtain and retain the parts that prove it applies to you.

Civic Marketplace's model cooperative purchasing policy, developed using best practices and guidance from the National Institute of Governmental Purchasing (NIGP), sets out three things staff must confirm before a purchase order issues. First, that the lead agency used a competitive process, advertised publicly and evaluated against published criteria. Second, that the contract term is active and your Entity is named as an eligible participant. Third, that a price reasonableness review compares the cooperative pricing against recent bids or market data.

The most frequent cooperative compliance problem is treating utilization as automatic. Scope mismatch, missing approval records, and weak pricing documentation create more risk than the cooperative contract itself.

Step 4: compare offers on more than price and write down why the award makes sense

Price is always in view. But below-threshold informal quotes, requests for proposals, and cooperative contract evaluations all permit, and sometimes require, consideration of additional factors such as fit to scope, delivery timeline, technical approach, implementation support, references, and total cost of ownership over the contract term.

The rule is simple and often missed: factors must be stated before responses are received, and the award record must show how those published factors were applied. An award memo written after the fact to justify a Supplier you already preferred is not evaluation documentation.

What a defensible award memo contains

A practical award memo contains six elements:

1. The requirement and method used
2. Which Suppliers were contacted or submitted proposals
3. The factors considered, in the order they were stated
4. Why the selected offer met the need better than the alternatives on those factors
5. Any price reasonableness determination
6. The approvals obtained before award

Bake Off, Civic Marketplace Platform's AI-assisted proposal comparison capability, supports the comparison stage. Paired with the Quick Quote workflow, it lets an Entity run a bake-off among qualified Suppliers without launching a new RFP, and keeps evaluator scoring records showing how offers differed on the factors in view, available at the point of award rather than assembled afterward. What it does not do is decide the award or supply the reasoning; the memo is still yours to write.

Departments doing this for the first time consistently underestimate one thing. Writing the award reason down while the decision is fresh takes ten minutes. Reconstructing it eighteen months later under audit pressure takes much longer, and the result rarely satisfies a reviewer.

Step 5: build the audit file while you buy, including post-award records

The audit file is not a project you start when an auditor calls. It is the natural output of a purchase done correctly at each step, as described by the Washington State Auditor's Office guidance on procurement accountability. A reviewer works backward from the award, so the file must show the full sequence.

Accountability is split. The department buyer owns: a clear scope from the start, approvals routed before commitment, receiving and acceptance evidence, immediate change alerts when scope or cost shifts, and file completeness for the department's portion. The procurement office handles: policy interpretation, formal process management, required public notices, forms review, and final compliance review where applicable.

Outside help can supply legal, technical, or construction-management expertise. But outsourcing does not transfer accountability: the local government remains responsible for compliance and contractor oversight even when a consultant manages the process. That responsibility sits with the Entity, not the contractor.