Every district procurement office has a version of the same story: a vendor made a confident pitch, the contract got signed, the login credentials went out — and eighteen months later, nobody can say with any confidence whether the product actually moved the needle, or whether anyone from the company still picks up the phone. Outcomes-based contracting (OBC) is a direct response to that story. Instead of paying for a promise, a district pays most of a contract up front for access and support, and holds back a meaningful share of it until agreed student results actually show up.
What Actually Changes in an Outcomes-Based Contract?
In a typical edtech contract, a district pays for a license, a seat count, or an implementation period. What the vendor delivers is access to the product and some amount of support — not a guarantee about what happens to student learning. OBC changes the payment structure itself: a defined portion of the contract is contingent, meaning the vendor only collects it if specific, pre-agreed outcome targets are met.
A rigorous evaluation of OBC published by WestEd in July 2026 puts a number on that structure: at least 40% of total contract value has to be contingent payment, released only when the agreed targets are hit. That threshold matters because it’s high enough to change vendor behavior. A small holdback that a company can absorb as a rounding error doesn’t create real accountability. A holdback that large means a vendor’s revenue depends on the same thing the district cares about — whether students actually improve.
The shift in one sentence: OBC doesn’t ask a vendor to prove their product works in general. It asks them to say, in writing, before the contract is signed, exactly what result they’re promising — and to accept less money if that specific result doesn’t happen.
Who Sets the Rules, and Where Is This Actually Happening?
OBC isn’t a single district’s invention — it’s being coordinated as a field. The Center for Outcomes Based Contracting (COBC), backed by the Southern Education Foundation, runs a Standards of Excellence framework that defines what a legitimate OBC agreement has to include. COBC coordinates with Digital Promise and the National Student Support Accelerator, two organizations edtech companies are more likely to already recognize from ESSA certification and evidence work. As of the WestEd evaluation, OBC arrangements are being piloted in school districts across California, Florida, Mississippi, and Texas — a geographically and politically varied enough spread that this isn’t a niche experiment in one state’s procurement office.
| Domain | What It Requires |
|---|---|
| Defined Population | Exactly which students the contract covers — not “our users,” but a named, bounded group. |
| Defined Outcomes | A specific metric and assessment the contract will be judged against, agreed before implementation starts. |
| Contingent Payments | At least 40% of contract value held back until the outcome targets are verified as met. |
| Mutual Accountability | Both sides — vendor and district — have defined obligations, not just the vendor being on the hook. |
| Continuous Improvement | A process for adjusting implementation mid-contract if early data shows the target is off track. |
The Number That Actually Has to Exist Before Anyone Signs
Here’s what makes OBC different from a company simply pointing to a past efficacy study: a study tells you a product worked somewhere, for someone, under some conditions. A contingent-payment contract requires something much more specific — a number a district can hold a vendor to. How many minutes a week, or sessions a month, does a defined group of students need in order to produce a defined gain on a defined test?
That’s not a rhetorical question in an OBC negotiation. It’s the number the contingent-payment clause is written around. If a vendor can’t answer it with real data — not a marketing claim, not a single case study from a friendly district — the contract has nothing concrete to hold either side accountable to. And a vendor who has only ever measured that number for one population, on one assessment, is in a weaker position than a vendor who has checked it across the several student groups and outcome measures a skeptical district is actually likely to ask about.
Not just a product, but a vendor’s commitment to stay engaged with implementation — because their payment depends on the product actually being used enough to work.
A specific dose-to-outcome relationship, defined for a specific population, that a third party could independently check against real usage and assessment data.
This is why OBC is spreading: it directly targets the “sell and disappear” pattern districts are most tired of, by making ongoing vendor support and fidelity of implementation a financial interest for the vendor, not just a customer-service promise.
Your Published Implementation Research Decides Whether You Get the Contract
Everything above assumes a vendor can say what result it is promising, for which students, at what level of use. A district won’t take that answer from a sales deck. It will look for it in your research. Before a district puts a large share of a contract at risk, it will ask to see the study behind your claim, read what was actually done in it, and then either buy what the study describes or model its own contract on it.
That second step is the one vendors tend to underestimate. A district reads a study as a description of what a successful implementation looks like: which students took part, how much they used the product, how long the program ran, what training and support schools received, what assessment measured the gain, and what the comparison group was doing instead. Whatever the study documents becomes the blueprint. The district either purchases that implementation as it was run, or writes its own targets to match it.
| What the District Reads in Your Study | What It Becomes in the Contract |
|---|---|
| Who the students were | The defined population the contract covers |
| How much the product was used | The usage level the payment depends on |
| Which test measured the gain | The outcome target and the assessment used to verify it |
| What support schools received | The training and implementation help the vendor is expected to provide |
| Who the comparison group was | The benchmark for deciding whether the gain is real or just ordinary growth |
This works against a vendor in two ways. If the study never recorded usage, support, or fidelity, the district has nothing to model the contract on, and the vendor has nothing to point to when targets are negotiated. And if the study was run with a different population, a different dose, or a different assessment than the district’s, the district will notice the mismatch and ask why the results should carry over.
The research also has to be public. A study that sits in a private folder can’t be checked. A district evaluator should be able to find the report, read the methods for themselves, and compare it against an independent listing, without relying on your summary of it. Publishing to ERIC and ResearchGate, and earning a rating on a review site such as Evidence for ESSA, are what make a study something a district can verify.
ESSA Tier III Is Implementation Research, and It Needs Your Tier IV Model
Districts are focused on implementation right now. After years of adopting tools and replacing them a couple of years later, many want their teachers to use what they already have well, and to stop changing programs every other year. Outcomes-based contracting fits that mindset, because it ties payment to whether a product is actually used well enough to work.
This is where ESSA Tier III research earns its place. A Tier III study is correlational: it looks at how outcomes vary with how the product was actually used, which makes it implementation research. It shows districts what results look like at different levels of use, in real classrooms, without a randomized design. That is the kind of evidence a usage level in a contract has to come from.
But a Tier III study only means something if it measures a clearly described model. That is what the ESSA Tier IV logic model supplies. It spells out what the program is, what teachers and students are supposed to do, and how that is expected to lead to results. The Tier IV model says what implementing the program well should look like. The Tier III study shows what outcomes actually look like when schools do it. Each needs the other: a logic model with no outcome data is a plan nobody has tested, and a correlational study with no documented model leaves a district unsure what exactly was implemented.
| Evidence | What It Tells a District |
|---|---|
| ESSA Tier IV | The model: what the program is and what good implementation looks like. |
| ESSA Tier III | The outcomes: what results look like at different levels of use, in schools that implemented it. |
| Together | Something a contract can be built around: a described model, with outcome data tied to how it was implemented. |
The most useful implementation research reports dosage impact in plain terms: 20 sessions gets you this many assessment points, and 40 sessions gets you this many, broken out by benchmark profile, meaning where students started relative to grade-level benchmarks. That is the form a district can write a contingent-payment clause around, and it is more usable than a single correlation coefficient, which shows that use and outcomes move together without saying what a given amount of use buys.
For a vendor heading toward outcomes-based contracting, that suggests a practical order. Document the model first, then study how outcomes vary with implementation, and, where a contract calls for a stronger claim, build toward Tier II from there.
The practical takeaway: get your implementation research in order, and get it published, before you pursue an outcomes-based contract. Document your model (Tier IV), study outcomes against how it was implemented (Tier III), and make both public. A study that plainly documents the population, the dose, the assessment, and the support is what a district will buy from or build a contract around. Without it, you are asking the district to take the contract on faith.
A good first step is to read your existing study the way a district would. Does it record usage? Does it name the population? Does it report results on an assessment a district would actually use? Our companion article, How to Get Ready for Outcomes-Based Contracting, covers how to turn that into a number a contract can use, and our published studies show what that documentation looks like in practice.
What Happens if the Target Isn’t Met?
This is where the “mutual accountability” and “continuous improvement” domains do real work. A well-structured OBC agreement isn’t a pass-fail cliff where a district simply withholds payment and walks away if a target is missed — it typically includes checkpoints during the contract period where implementation data gets reviewed and adjusted before the final outcome is measured. If usage is tracking below the level the vendor said was needed, that’s a signal to intervene — more coaching, a schedule change, additional support — while there’s still time to hit the target, not just a fact to discover after the school year is over.
That structure also protects vendors from a district that undermines its own success: if a school fails to actually implement the product at the agreed frequency, mutual accountability terms can specify that as a district-side failure, not a vendor-side one. Getting that balance right — protecting the district from an underperforming product, while protecting a vendor from a district that doesn’t follow through — is most of what a well-drafted OBC contract has to solve for, and it’s exactly why the underlying numbers have to be right before the ink dries.
Why Does “Continuous Improvement” Sound Familiar to Anyone Who’s Sat Through an MTSS Meeting?
Because it largely is that meeting, with money attached. Most districts already run some version of this cycle for their own locally-owned interventions: a screener flags which students need support, a team reviews progress data on a regular cadence, and instruction gets adjusted based on what the data shows. That’s not a new process OBC invented — it’s the same screen-diagnose-target-monitor-adjust loop behind MTSS and most data-driven decision-making routines literacy and math coordinators already run.
What OBC does is apply that same loop to a product a district is paying an outside vendor for, and attach a financial consequence to whether it works. The WestEd evaluation’s description of the districts that implemented OBC well reads almost like a description of a well-run MTSS team — dedicated point people on both sides, regular data-review meetings, and joint problem-solving when the numbers show a gap. It’s also consistent with something else the evaluation found: districts with more baseline organizational capacity for this kind of structured data review tended to have more success running OBC contracts, while districts without that muscle already in place struggled more, regardless of the product.
The practical version: pitching OBC to a district isn’t asking them to build brand-new infrastructure. It’s asking them to point their existing dosage-and-data-review muscle at an externally purchased product, and to put a real share of the invoice behind what that review shows. A district’s MTSS or data-team maturity may predict more about how smoothly an OBC contract runs than anything about the vendor.
Do You Know the Number Your Contract Would Be Judged On?
Before you’re in a room negotiating a contingent-payment clause, it helps to know your own dose-response numbers — how much usage, for which students, produces which result. LXD Research offers a free conversation to help you figure out what you already know, what your existing studies document, and what you’d need to check before signing.
Book a Free Conversation View Our Services