Outcomes-based contracting changes the questions districts need to answer about their student support programs.

It is no longer enough to know how many students were enrolled, how many sessions a provider delivered, or whether an invoice matches the contract. If a portion of provider payment is tied to results, district leaders need reliable data showing which students received the intervention, what they actually received, how consistently the program was implemented, and what outcomes those students achieved.

That makes data one of the most important foundations for successful outcomes-based contracting (OBC).

But the answer isn’t simply “more data.” Districts need the right data connected in the right way—from student eligibility and participation through implementation, outcomes, and ultimately payment.

For districts preparing for OBC, here are the key types of data to consider and the questions each should help leaders answer.

Why Is Data So Important for Outcomes-Based Contracting?

In a traditional contract, districts may be able to evaluate provider performance largely through invoices, service reports, utilization data, and periodic program reviews.

Outcomes-based contracting requires a more connected view.

The Center for Outcomes Based Contracting defines OBC as a contracting model in which a substantial portion of provider payment is contingent on achieving agreed-upon outcomes. That creates a much higher bar for the data used to evaluate performance.

Districts need to be able to determine not only whether an outcome occurred, but also which students should be included in the calculation, whether they actually received the intended intervention, whether the program was implemented as expected, and how those results translate into contract performance.

This is why OBC data infrastructure needs to connect three fundamental questions:

What was supposed to happen? What actually happened? What happened as a result?

Without that connection, districts can have plenty of data and still lack the evidence needed for meaningful accountability.

The 6 Types of Data Districts Need for Outcomes-Based Contracting

Although specific requirements vary by contract and intervention, most districts need to connect six categories of data to effectively monitor an outcomes-based contract.

1. Student Eligibility and Rostering Data

Before a district can measure outcomes, it needs a reliable definition of which students are part of the intervention.

That starts with accurate student eligibility and rostering data, which may include student identifiers, school, grade, demographic information, intervention eligibility, program assignment, provider assignment, and relevant baseline measures.

This sounds straightforward, but it can become complicated quickly. Students may enter or exit programs during the year, switch providers, change schools, or be assigned to an intervention without ever meaningfully participating.

That makes it important to distinguish between students who were eligible, students who were assigned, and students who actually received services.

Without that distinction, districts risk evaluating outcomes against the wrong student population.

2. Participation and Attendance Data

Once students are assigned to an intervention, districts need to know whether they actually participated.

For tutoring, this typically means capturing scheduled sessions, completed sessions, student attendance, cancellations, no-shows, and other participation information. Similar measures may apply to other student support programs.

Attendance is more than an operational metric under OBC. It provides critical context for interpreting eventual outcomes.

If a student demonstrates limited growth but attended only a small portion of the intended sessions, that tells a very different story from a student who participated consistently but still did not demonstrate the expected outcome.

Before asking whether an intervention worked, districts need to know whether students actually received it.

3. Dosage and Duration Data

Participation alone does not tell leaders how much of an intervention a student received.

Districts may also need to measure:

Sessions per week
Minutes per session
Minutes per week
Total hours of support
Number of weeks participating
Program start and end dates
Consistency of participation over time

These measures help districts understand dosage and duration, both of which can be important when interpreting student outcomes.

For tutoring specifically, research has consistently emphasized the importance of frequency and sustained participation. The National Student Support Accelerator at Stanford University identifies frequent sessions, adequate session length, and consistent participation among the design principles associated with high-impact tutoring.

Under an outcomes-based contract, this implementation context becomes particularly important. If students did not receive the intended level of service, leaders need to understand that before drawing conclusions about whether the intervention itself was effective.

4. Implementation Data

One of the biggest mistakes districts can make with outcomes-based contracting is focusing so heavily on the final outcome that they lose visibility into what happened along the way.

Outcome data tells you what happened. Implementation data helps explain why.

Depending on the intervention, implementation data might include tutor or instructor assignment, tutor continuity, scheduling, session location, virtual versus in-person delivery, curriculum or content used, time of day, student-to-tutor ratio, cancellations, substitutions, and whether services were delivered according to the intended program model.

This information allows districts to identify patterns that a final outcome measure alone cannot reveal.

For example, imagine two schools using the same tutoring provider. Students at one school consistently receive three sessions per week with the same tutor during a dedicated intervention block. Students at another experience frequent scheduling conflicts, tutor changes, and missed sessions.

If their outcomes differ, knowing the implementation conditions helps leaders understand what may have contributed to that difference.

This is also where OBC can become a continuous-improvement strategy rather than simply an end-of-year payment calculation. When districts can see implementation patterns while a program is underway, they have an opportunity to make adjustments before final outcomes are available.

5. Student Outcome Data

Outcome data is the piece most directly associated with outcomes-based contracting, but it becomes much more useful when connected with the implementation data that came before it.

Depending on the contract, outcome measures might include:

Assessment growth
Proficiency or benchmark attainment
Course performance
Attendance improvement
Chronic absenteeism reduction
Credit attainment
Other agreed-upon student measures

Districts and providers should establish these measures before implementation begins, including the assessment or data source, baseline, target, student population, measurement period, and rules for determining whether an outcome has been achieved.

The Center for Outcomes Based Contracting’s Standards of Excellence provide a framework for establishing outcomes and structuring accountability within OBC agreements.

But measuring the final outcome should not happen in isolation.

The more useful analysis connects student outcomes back to the intervention each student actually received. That allows districts to examine not only whether students improved, but whether outcomes differed based on participation, dosage, implementation conditions, provider, school, or student population.

6. Contract, Rate Card, and Financial Data

The final data layer connects program performance with the contract itself.

Outcomes-based contracts often use a rate card or similar payment structure that establishes how provider compensation changes based on achievement of agreed-upon outcomes.

To manage that accurately, districts may need to connect contract terms with student-level eligibility, participation, outcome attainment, performance thresholds, and payment calculations.

For each contract, leaders should be able to answer questions such as:

What portion of payment is tied to outcomes?
Which students qualify for each outcome calculation?
What performance thresholds must be reached?
Which outcomes have been achieved?
What payment does each result trigger?
Can the calculation be verified by both the district and provider?

When those calculations depend on manually reconciling multiple spreadsheets, provider reports, assessment files, and contract documents, OBC can create a significant administrative burden.

A standardized data foundation can make the process more transparent and auditable for both districts and providers.

How Should Districts Connect OBC Data?

Having all six categories of data is only part of the challenge. The bigger issue is whether they can be connected.

In many districts, the information needed for OBC lives across multiple systems. Student information may live in the SIS. Attendance and session data may come from providers. Assessment results may live in another platform. Contract terms may live in spreadsheets or procurement systems. If multiple providers are involved, each may deliver its data in a different format.

That leaves district teams trying to manually piece together the story.

A stronger OBC data model connects information at the student level so leaders can follow a consistent progression:

Eligible → Assigned → Participated → Received Intended Dosage → Experienced the Intervention → Achieved an Outcome → Triggered a Contract Result

That creates a much stronger foundation for understanding performance than looking at separate provider reports or aggregate outcomes.

See how Pearl helps districts connect implementation and outcome data for outcomes-based contracting.

Why Standardized Data Matters When Districts Have Multiple Providers

Data standardization becomes even more important when a district or state works with multiple tutoring providers or student support partners.

One provider might report “attendance” as a percentage of scheduled sessions. Another might report total completed sessions. One might measure tutoring dosage in hours, while another reports sessions. Student identifiers, cancellation rules, session duration, and outcome reporting can all differ.

Individually, each report may be accurate. Collectively, they may be difficult to compare.

Districts need a common definition of performance across providers.

That means standardizing important measures such as student identifiers, participation, attendance, session duration, dosage, provider assignment, implementation measures, and outcomes before comparing results.

A common data model allows leaders to evaluate programs using the same definitions rather than relying on each provider’s individual reporting structure. It also gives districts greater ownership of their data and a more consistent view of performance across the full student support portfolio.

Implementation Data Creates Accountability Before Outcomes Arrive

One of the strongest reasons to build an OBC data infrastructure is that districts do not have to wait for outcome data to begin managing performance.

Academic outcomes may take a semester or an entire school year to measure. Implementation signals emerge much earlier.

Within the first several weeks of an intervention, leaders may already be able to see whether students are attending, receiving the intended dosage, maintaining consistent tutor relationships, or experiencing scheduling and staffing problems.

Those are not final measures of effectiveness. But they are leading indicators that tell districts whether the conditions necessary for success are actually being created.

That distinction matters for accountability.

If leaders discover in the spring that students received substantially less tutoring than intended, there may be little they can do to change the result. If they identify the same pattern in October, there may still be time to adjust schedules, address attendance barriers, change staffing, or work with the provider to improve delivery.

OBC should not only create accountability at the end of a contract. The right data creates accountability throughout implementation.

How Does OBC Data Support Mutual Accountability?

Outcomes-based contracting is sometimes described primarily as a way for districts to hold providers accountable for results. But student outcomes are rarely influenced by a provider alone.

District decisions can affect student scheduling, rostering, attendance, assessment completion, space availability, family communication, technology access, and other implementation conditions. Providers may control staffing, tutor quality, curriculum, session delivery, and other aspects of the intervention.

That is why successful OBC requires mutual accountability.

Shared data gives both sides visibility into the conditions affecting performance. Instead of waiting until the end of the contract to determine who was responsible for a missed outcome, district and provider teams can identify issues during implementation and determine what each can do to address them.

Research into early OBC implementations has identified this increased communication and shared attention to data as one of the potential benefits of the model. A 2026 WestEd evaluation of Outcomes Based Contracting found that participating districts reported stronger district-provider communication, accountability, and data use as they implemented OBC.

What Should an Outcomes-Based Contracting Dashboard Show?

An OBC dashboard should do more than display final outcome measures.

District leaders should be able to move from high-level program performance into the implementation factors contributing to those results. Depending on the intervention and contract, that may include:

Program reach: How many eligible students were assigned and how many actually participated?

Attendance: Are students consistently attending scheduled services?

Dosage: Are students receiving the intended frequency, minutes, and duration?

Implementation: Is the intervention being delivered according to plan?

Provider performance: Are there meaningful differences across providers, schools, programs, or student groups?

Outcomes: Are participating students achieving the agreed-upon measures?

Contract performance: How do those results translate into OBC targets and payment requirements?

The goal is not simply to create another dashboard. It is to give leaders a connected view of what was delivered, what students experienced, and what happened as a result.

Explore Pearl’s approach to managing outcomes-based contracting across programs and providers.

Questions Districts Should Ask About Their OBC Data Infrastructure

Before entering or expanding outcomes-based contracts, districts should assess whether their existing systems can answer the questions the contract will require.

Start with these:

Can we identify every student eligible for the intervention?
Can we distinguish assignment from actual participation?
Can we measure attendance, dosage, and duration consistently?
Can we see whether the intervention is being implemented as intended?
Can we compare data consistently across multiple providers?
Can we connect implementation data with student outcome data?
Can we analyze differences by school, provider, program, and student group?
Can we calculate contract performance and payment using trusted data?
Can both the district and provider understand and verify the results?
Can we identify implementation problems early enough to act on them?

If the answer to several of these questions is no, the district may have a data readiness problem before it has an OBC problem.

From OBC Reporting to Student Support Evidence

The data infrastructure required for outcomes-based contracting can ultimately serve a much bigger purpose than calculating provider payment.

Once districts can connect who received an intervention, what was delivered, how it was implemented, and what outcomes followed, they have the foundation for asking more meaningful questions about every student support investment.

Which programs are reaching the intended students? Which implementation models are associated with stronger participation? Where is dosage falling short? Do outcomes differ across providers or student populations? Which interventions should the district continue, adjust, expand, or reconsider?

That is the larger opportunity behind OBC.

Visibility is the prerequisite. Building the evidence base is the opportunity.

Outcomes-based contracting creates a reason to build that visibility. But the value of the data extends far beyond the contract itself, helping district leaders understand what’s working, for whom, under what conditions, and at what cost.

Learn how Pearl connects intervention delivery with student outcomes.

Frequently Asked Questions About Outcomes-Based Contracting Data

What data is needed for outcomes-based contracting?

Districts typically need student eligibility and rostering data, participation and attendance data, dosage and duration data, implementation data, student outcome data, and contract or financial data. Connecting these data sources allows districts to understand both whether an outcome was achieved and what contributed to the result.

What is implementation data in education?

Implementation data describes how an intervention or student support program was actually delivered. Depending on the program, it may include attendance, dosage, duration, scheduling, staffing, tutor continuity, delivery model, cancellations, and other measures that help leaders determine whether students received the intended intervention.

Why is implementation data important for outcomes-based contracting?

Implementation data helps districts interpret student outcomes and identify problems before final outcome measures are available. It can help leaders distinguish between an intervention that was delivered as intended but did not produce the expected result and an intervention that students did not receive consistently enough to fairly evaluate.

How do districts measure accountability in outcomes-based contracts?

Districts can measure accountability by tracking agreed-upon implementation and outcome measures throughout the contract. This may include student participation, attendance, dosage, provider performance, outcome attainment, and the payment thresholds established in the contract.

How can districts compare multiple providers under OBC?

Districts need standardized definitions and a common data model across providers. Measures such as attendance, dosage, student identifiers, session duration, implementation, and outcomes should be normalized so leaders can compare performance consistently rather than relying on different provider reporting formats.

What should an OBC dashboard include?

An outcomes-based contracting dashboard should connect program reach, attendance, dosage, implementation, provider performance, student outcomes, and contract performance. Leaders should be able to move from high-level results into the implementation factors that may be contributing to those results.

Does outcomes-based contracting require student-level data?

Student-level data can be important when districts need to connect individual participation and implementation with student outcomes or determine which students qualify for specific contract measures. The exact data required depends on the intervention, outcome measures, contract structure, and applicable district data-governance and privacy requirements.