Piggyback contract
A piggyback contract is one public agency's purchase made under a contract another public agency competitively awarded. Done properly it saves a district a full solicitation. Done casually it produces an award with no competitive basis and a finding attached.
| Condition | What breaks it | Who confirms it |
|---|---|---|
| Your state authorises the practice | A statute limiting purchases to in-state awards, or to awards by like entities | Your counsel and board policy |
| The original solicitation contemplated other agencies | No cooperative or piggyback clause in the original bid documents | The bid documents, not the contract summary |
| Scope and terms match your need | You are adding services, quantities or products outside the awarded scope | The awarded scope of work |
| The vendor agrees to extend the terms | Vendor offers "similar" pricing rather than the awarded price | Written vendor confirmation, kept in the file |
How it differs from a co-operative
Both let a district buy without running its own solicitation, and they are not the same instrument.
A co-operative contract is competed from the outset to serve many agencies. The solicitation says so, the pricing anticipates volume from members, and an organisation administers participation and collects a fee.
A piggyback is a district adopting a contract that another agency competed for its own requirements. Nobody administers it, no fee is collected, and the entire defensibility of the arrangement rests on the original solicitation having contemplated other users and on your state permitting it.
The audit risk distributes differently as a result. On a co-operative ride, the lead agency's process is the thing being relied on and it was designed to be relied on. On a piggyback, your district is relying on a process run by someone with no obligation to you and no reason to have documented it for your benefit.
The five findings auditors write
- No piggyback clause in the original solicitation. The contract may mention cooperative use; the underlying bid documents are what count, because competitors priced against those.
- Scope expansion. The original award covered a licence; your purchase adds migration services, a second module and training days. Professional services are the usual culprit.
- Term problems. The original contract has expired, or is running on an extension that was never properly executed. A contract nobody renewed is not a contract you can ride.
- Price divergence. Your quote does not match the awarded price sheet. Even a better price is a problem, because it demonstrates the price was negotiated rather than inherited — and a negotiated price has no competitive basis.
- Unlike entity. A school district riding a city or county award where state law requires the awarding agency to be a comparable entity. This is jurisdiction-specific and is exactly what counsel is for.
The file that answers all five. Keep the original solicitation including the cooperative clause, the award document and board minutes, the awarded price sheet, written vendor consent to extend the same terms to you, and your own determination that the scope matches. Five documents, assembled in an afternoon, and the difference between a defensible award and a finding.
The privacy parallel worth knowing
The same mechanism exists on the data-protection side. Under the National Data Privacy Agreement structure, a vendor can make a general offer of the same privacy terms to any other district in the state, and those districts countersign rather than negotiate. One district does the work; the rest inherit it.
It has the same dependency. If the first district negotiated a weak data privacy agreement, every district that adopts it inherits the weakness, and a general offer looks identical whether the underlying terms are strong or terrible. Read the exhibits before countersigning, particularly the deletion, secondary-use and sub-processor clauses.
Kastr holds no piggybackable award and no signed general offer today, because we are pre-launch with no customers. When we sign a first district's agreement, that district's terms become the terms everyone else inherits, which is a reason for us to negotiate that one carefully rather than quickly.
This entry describes what the rule says. Whether and how it applies to your district is a question for your own counsel, not for a vendor.
Questions people actually ask
Is piggybacking legal in every state?
No. Authority varies, and some states restrict it to in-state awards, to awards by comparable entities, or prohibit it outright for certain categories. The authority is in your state's procurement code and your board policy, and it is a question for counsel rather than for a vendor.
Does the original contract need a piggyback clause?
Generally yes, and the clause needs to be in the original solicitation rather than added to the contract afterwards. Competitors priced against the solicitation, so a right that appeared later was not part of what they bid on.
Can a district piggyback on a contract from another state?
Sometimes, where state law permits it and the original solicitation contemplated out-of-state users. Several states restrict this, and some permit it only through a recognised co-operative rather than agency to agency. Confirm before relying on it.
Who is responsible if a piggybacked contract is challenged?
The purchasing district. The lead agency competed for its own needs and owes nothing to a district that rode its award. That asymmetry is the main practical reason to keep a complete file of the original solicitation, award and price sheet.
One price. Every feature. Locked for three years.
$3.50 per student per year under 5,000 students. No tiers, no add-on modules, no per-message fees. Published on the site because you should not have to book a call to learn a price.