Back to playbooks

Procurement and Contract Guardrails

Civics | core | Updated 2026-03-01

Tags

playbook, core

Procurement and Contract Guardrails

Use when: the real leverage is buried in an RFP, vendor renewal, or contract amendment.
Goal: get boring guardrails into the contract before failure becomes normal.

Why this matters

A lot of public harm is not just bad policy. It is weak vendor terms, vague metrics, or a renewal process that assumes performance instead of proving it.

Contracts decide:

  • what gets measured
  • what gets published
  • what counts as failure
  • what happens if the vendor underdelivers

What good looks like

One contract ask that adds one or more of these:

  • performance metrics
  • audit rights
  • data transparency
  • cure periods and escalation steps
  • termination for non-performance

Quick targets

Pull these first:

  • current contract or renewal packet
  • RFP or procurement notice
  • board packet or approval memo
  • vendor scorecard if one exists
  • next renewal or amendment date

Core questions

  • What is the vendor required to deliver?
  • What metric proves they delivered it?
  • Who can inspect the data?
  • What happens if the vendor misses the mark?
  • When is the next real decision point?

Contract clauses worth asking for

Audit clause

The public entity can inspect records, performance data, and billing documentation on a defined schedule.

Performance metrics

The contract names 3-5 measurable outcomes, not just activity counts.

Data transparency requirement

The vendor must provide plainly usable reporting on a set cadence.

Cure and termination terms

If the vendor fails, the contract requires a correction plan and preserves the right to terminate for repeated non-performance.

Decision rules

  • If you cannot get a big rewrite, ask for reporting and audit rights first.
  • If the contract is already signed, target the renewal, amendment, or oversight review.
  • If staff say the terms are boilerplate, ask who controls the boilerplate.

Scoreboard

  • Contract located? (Y/N)
  • Performance metrics present? (Y/N)
  • Audit clause present? (Y/N)
  • Public reporting requirement present? (Y/N)
  • Next renewal or amendment date identified? (date)

Definition of done

Leave with:

  1. one contract guardrail ask
  2. one target map or owner list
  3. one follow-up date
  4. one log entry

Back to playbooks