This article is general information, not legal advice. It summarizes the statute, publicly available Comptroller guidance, and case law as of September 2, 2026. Whether any specific contract qualifies for the piggybacking exception should be reviewed with your district's or municipality's counsel before you buy.

The short version

Since 2012, GML §103(16) has let New York political subdivisions skip their own competitive bidding and purchase through a contract another government already let, if, and only if, a set of conditions is met. The exception was always narrower than the sales pitch. After the Third Department's decision in Matter of Daniel J. Lynch, Inc. v. Board of Education of the Maine-Endwell Central School District, and the NYSED Building Aid guidance that followed it, it is narrower still: public works are out entirely.

What remains is a workable exception for apparatus, materials, equipment and supplies, and for services to install, maintain, or repair those items. But every word of the statute does work, and the Comptroller's guidance adds a consistency test with real teeth. Vendors will tell you their contract "qualifies for piggybacking in New York." That is a legal conclusion, it is yours to make rather than theirs, and this article is the framework for making it.

One more reason to have the framework straight now: the exception is scheduled to expire on June 30, 2027, the latest in a string of short extensions. More on that at the end.

What the statute authorizes, and what it no longer does

The scope sentence is precise: purchases of apparatus, materials, equipment and supplies, and contracts for services related to the installation, maintenance or repair of those items, through the use of a contract let by the United States or any agency thereof, any state, or any other political subdivision or district therein.

Two boundaries follow. First, the service authorization is tethered to the goods. Installation, maintenance, and repair of the things you are buying qualify; freestanding services do not ride along. Second, public works are outside the exception. The trial court in Lynch held that §103(16) is not available for public works contracts and projects, defining those as construction or repair projects undertaken by municipalities on their infrastructure, and the Third Department affirmed in May 2026. OSC's current bulletin carries the point. If the work is a public works contract, the piggybacking analysis ends before it starts, whatever the cooperative's marketing materials say. I covered what that means for capital projects, and the Building Aid consequence NYSED attached to it, in the article linked above.

Everything below assumes you are inside the surviving scope: goods, and their install, maintain, and repair services.

Prerequisite one: a government must have let the contract

The underlying contract must have been let by the United States or a federal agency, any state, or any political subdivision or district of any state. The Comptroller reads that list to include New York's own political subdivisions, so a qualifying contract let by another New York district or municipality can be used, alongside the separate county-contract pathway discussed later.

The disqualifier is just as important as the list. A contract developed for governmental use but actually let by a private party, a company, an association, a not-for-profit, does not fall within the exception, no matter how public-sector its branding. This is the first question to ask about any national cooperative: who, exactly, awarded the contract to the vendor? Some cooperatives are themselves units of government, and a contract they let can sit inside the list. Others are private entities administering contracts, and cannot. The answer is a matter of the letting entity's legal status, it is not always obvious from the website, and it is worth confirming in writing before anything else, because if this prerequisite fails, nothing downstream can save the purchase.

Prerequisite two: the contract must actually extend to you

The contract must have been made available for use by other governmental entities, which in practice means the contract itself contains a clause extending its terms to other governments. Read the clause. Some extend only to entities within the letting government's state, some require the vendor's consent per order, some have expired.

And note what the Comptroller says does not count: a unilateral offer by the vendor to extend the contract's pricing and terms to you. "We honor that contract for New York schools" is a sales representation, not an extension clause. If the availability lives in the vendor's email rather than the government's contract, prerequisite two is not met.

Prerequisite three: lowest responsible bidder or best value, consistently with §103

The contract must have been let to the lowest responsible bidder or on the basis of best value in a manner consistent with §103. Consistent does not mean identical; the other government's procedures need not mirror New York's. But OSC identifies four elements that should be present, and they function as your checklist when you request the procurement history:

1. Public solicitation of the bids or offers, serving the same ends as §103's advertising requirement.
2. Sealed submissions, or analogous procedures preserving the integrity of the process and the confidentiality of what was submitted until opening.
3. Specifications, or a similar common standard letting bidders compete fairly; for a best value award, this should include how offers would be evaluated and the relative weight of price and non-price factors.
4. Award to the lowest responsive, responsible bidder, or in a best value process, to the responsive and responsible offerer optimizing quality, cost, and efficiency on objective and quantifiable analysis.

Then the sentence that disqualifies more cooperative contracts than any other: a contract awarded through a negotiation process is not consistent with these requirements. A solicitation that produced proposals which the entity then negotiated into a contract, however sensible commercially, is not a §103-consistent award. When you ask a cooperative for the underlying solicitation, evaluation record, and award documentation and the answer is slow, vague, or proprietary, that is itself information.

The best value authorization trap

Here is the condition that lives on your side of the transaction rather than the contract's, and it is the one I would check first.

A political subdivision, other than New York City, that wants to piggyback a contract let on a best value basis must first have authorized best value for its own purchase contracts: by local law for municipalities, or by rule, regulation, or resolution for school districts, BOCES, and fire districts. One resolution suffices, and it covers future use. But if your board never adopted it, a best value cooperative contract is not available to you, even if the contract passes every other test in this article.

Most large national cooperative contracts are best value awards. Which means for many districts, eligibility for the modern cooperative marketplace turns on whether a one-page resolution exists in the minutes. Check before you rely; adopt it properly if you intend to; and note the parallel to the electronic bid receipt resolution I have written about before. New York keeps making useful authority contingent on a board action nobody remembers to take.

The file: cost-benefit and documentation

Unlike the county and federal contract pathways, §103(16) does not expressly require a cost savings finding. OSC's advice is to do one anyway, and I would treat that advice as binding in practice: a cost-benefit analysis before using the exception, considering all pertinent factors, including the administrative expense you avoid by not running your own bid. That last factor is legitimate and real, and it is also the one that turns into hand-waving if it is not quantified. Estimate the hours honestly.

The file OSC describes for this exception is: a copy of the contract, your analysis of the three prerequisites, and the cost savings analysis including consideration of the other procurement methods available. That is three documents. A district that assembles them at the time of purchase has an answer for the auditor, the board, and the losing local vendor. A district that assembled a vendor's one-page "piggybacking justification letter" has assembled the vendor's legal conclusion.

Two more items for the same file. The purchase creates a contractual relationship with the vendor on the underlying contract's terms, and those terms were written for someone else's law. A term lawful where the contract was let can conflict with New York law, and a conflict can make the contract unusable for you regardless of the prerequisites; that review belongs to counsel before the order, not after. One obligation sits above this whole analysis, and the current bulletin says so expressly: §103(16) does not relieve the district of applicable preferred source obligations under State Finance Law §162, or of any M/WBE mandates that apply to the procurement. If a preferred source can supply the commodity or service, that duty comes before any competitive method, piggybacking included.

And if the purchase is below the bidding threshold in the first place, this exception is not what governs it: your §104-b policy is, and OSC's own sample policy lists piggybacking in the policy's exemption paragraph, which is where your board should have placed it.

A caution when federal money is involved

Piggybacking is a state law exception, and federal funds do not care about state law exceptions. If the purchase will be charged to a federal award, the procurement must independently satisfy the federal standards in 2 CFR 200, and a cooperative contract qualifies there only if the underlying procurement meets the federal competition requirements, which is a separate analysis with different elements. The two frameworks overlap heavily in spirit and imperfectly in detail. Run both before charging a piggybacked purchase to Title I, IDEA, Child Nutrition, or any other federal source.

What piggybacking is not: the other four pathways

The exception gets asked to do jobs that belong to its neighbors. Side by side, because I have never seen anyone lay them out together:

County contracts, GML §103(3) and County Law §408-a. The original piggybacking, older than §103(16) and untouched by Lynch as to its own scope. Purchases through your county's contracts, on the county's terms, with its own statutory conditions.

State contracts, GML §104. Purchasing through OGS centralized contracts. Its own eligibility rules, its own procedures, no dependence on §103(16), and no June 2027 sunset.

Cooperative bidding, GML Article 5-G, §119-o. Two or more local governments jointly running one solicitation. This is the one to remember post-Lynch, because joint bidding is not piggybacking: the participating governments are letting the contract themselves, together, and it remains available for public works. A BOCES-coordinated or multi-district joint bid is this pathway, not §103(16).

Below-threshold purchasing, GML §104-b. Under the aggregation-tested thresholds, §103 does not apply at all, and your own policy governs. No exception needed, which also means no §103(16) analysis rescues a purchase your policy required quotes for.

The practical sequence: determine which framework the purchase actually sits in first, then apply that framework's conditions. Most piggybacking mistakes I have seen were really classification mistakes, an analysis run under §103(16) that belonged somewhere else in this list.

The sunset: June 30, 2027

Section 103(16) has always been temporary, extended repeatedly since 2012. The current extension was signed on June 29, 2026, one day before the prior expiration, and runs to June 30, 2027. Last-minute extension has been the pattern, and it may well repeat. It is not guaranteed, and a district planning a purchase that will not be ordered until summer 2027 should have a fallback pathway identified now, most likely OGS, a county contract, or a joint bid.

One research caution worth passing along: as of this writing, at least one widely used statutory database still displays a pre-extension expiration annotation on §103(16). When the citation matters, verify against the session law, not the annotation. I will publish a fuller piece on the sunset, and what to do if it lapses, as the date approaches.

If you are not in New York

Nearly every state authorizes some form of cooperative or piggyback purchasing, and the variation runs along three axes worth locating in your own code. First, scope: many states, like New York now, confine the exception to goods and exclude construction; some extend further. Second, the qualifying contract: whether the underlying award must have been competitively let, and whether it must mirror your state's own procedures or merely resemble competitive principles. Third, the authorization architecture: whether your governing board must opt in generally, per contract, or not at all. The failure mode is identical everywhere: treating a vendor's assertion that a contract "qualifies" as the analysis, rather than as the thing the analysis tests.

Disclaimer. This article is provided for general informational purposes only and does not constitute legal advice, nor does it create any advisory or professional relationship between the author, BidLogiQ, LLC, and any reader. It reflects the statute, publicly available guidance, and case law as of September 2, 2026; statutes, regulations, agency guidance, and case law change, and this article may not reflect subsequent developments. Application of these authorities depends on the specific facts of a given procurement and the specific contract at issue. Readers should consult their own counsel and, where applicable, the Office of the State Comptroller before making procurement decisions. The author and BidLogiQ, LLC disclaim any liability for actions taken or not taken in reliance on this article. The views expressed are the author's own and are not those of any employer or client.