The House v. NCAA settlement, approved June 6, 2025, is the most consequential structural change to D1 athletics in a generation. Most of the coverage has focused on the compensation numbers — $2.8 billion in back pay, a $20.5 million per-school annual revenue sharing cap, and the 22% ceiling tied to average Power Five conference revenue. But the compensation story is only half of what's changed.
The other half is the data problem the settlement created — and it lands directly on the desks of ADs and CFOs who are now responsible for reporting, tracking, and justifying numbers they've never had to produce before.
Revenue sharing isn't a check you write and forget. It's an ongoing compliance obligation — one with specific data inputs, external oversight from the College Sports Commission, and a March 1 annual reporting deadline that started in 2026. The programs that walk into that deadline with clean, centralized data will clear it. The programs that don't are discovering, right now, exactly what their data gaps cost.
The New Data Obligations: What Athletic Departments Must Track
Before the settlement, the reporting burden on athletic departments was primarily financial — MFRS submissions to the NCAA, annual audit compliance, Title IX expenditure tracking. Detailed enough, but manageable with a competent business office and standard accounting systems.
The settlement adds a new layer on top of that financial infrastructure, and it's one that most business offices weren't built to support.
The settlement caps institutional revenue sharing at 22% of average Power Five athletic revenue — currently $20.5 million for 2025-26, growing to $32.9 million by 2034-35. The calculation uses eight specific MFRS revenue categories: media rights, ticket sales, sponsorships, conference distributions, bowl revenue, and others. Every dollar distributed to athletes has to trace back to a defensible cap calculation.
That means the revenue data feeding your distribution decisions needs to be current, auditable, and aligned with the MFRS categories the settlement specifies — not just "close enough." Programs that have clean financial data systems can run the cap calculation as a quarterly check. Programs with fragmented accounting or informal tracking are doing it with spreadsheets, which is how you make avoidable errors in a compliance context.
Every NIL contract valued at more than $600 must be reported to the College Sports Commission's NIL Go clearinghouse within five business days of execution. The CSC — staffed with tools built by Deloitte and LBI — reviews deals for fair market value compliance and flags arrangements that look like disguised pay-for-play recruiting. The five-day window is not advisory.
This creates an intake workflow obligation that didn't exist before: legal review, finance entry, and CSC upload, all within a five-day window for every NIL deal above the threshold. NIL compliance officers managing CSC reporting mandates in 2026 are discovering that the institutions best positioned to meet the five-day window are the ones who built deal-tracking infrastructure before the settlement — not the ones scrambling to retrofit it into a compliance workflow after the fact.
The settlement replaced scholarship caps with sport-specific roster limits, and introduced the concept of "designated student-athletes" — players grandfathered above those roster limits because they were already enrolled or recruited before the settlement took effect. Institutions must track these designations, link them to financial aid records, and report them to the CSC on the settlement's prescribed calendar.
What this means practically: every athlete on your roster needs a data record that captures their enrollment date relative to the settlement timeline, their designation status, their financial aid package, and their revenue-sharing compensation — all linkable for audit purposes. That's a unified athlete record problem, and it runs directly through your performance data infrastructure if you've built one, or through a compliance patchwork if you haven't.
Starting March 1, 2026 — and every March 1 for the ten-year settlement term — participating institutions must submit annual reports to the CSC covering revenue-sharing distributions, NIL activity, and roster compliance. The CSC has enforcement authority and can sanction programs for incomplete or inaccurate reporting. The records backing those reports must be retained for a minimum of seven years.
March 1, 2026 has already passed. Programs either made that deadline with defensible data or they didn't. The ones that found gaps are spending the rest of 2026 closing them before the next cycle.
"Revenue sharing is not a line item. It's a data operation. The programs treating it like a check they write once a year are the ones who will fail their first CSC audit."
Why Performance Data Systems Become the Foundation for Financial Compliance
Here's the insight that most athletic department leadership is still working through: the data infrastructure that supports athlete performance tracking is the same infrastructure that supports revenue-sharing compliance. They're not separate problems with separate solutions.
A centralized athlete data system — one that maintains a unified profile for each roster member, tracks compensation, links to academic eligibility records, and documents performance history — already does most of what the settlement's compliance reporting requires. The extensions aren't architectural; they're additive. You're adding financial data streams to a structure that already exists.
The programs on the right side of that grid didn't build their infrastructure for the settlement. They built it to manage athlete performance, connect athlete data to donor revenue conversations, and give their S&C staff visibility across the department. The settlement compliance layer landed on top of existing infrastructure instead of requiring a ground-up build.
The programs on the left side are doing the ground-up build now — under compliance pressure, with a CSC audit cycle running in parallel.
The Data Readiness Gap: Who's Ahead and Who's Scrambling
The programs best positioned for revenue-sharing compliance share a common characteristic: they invested in centralized athlete data infrastructure before the settlement forced the issue. Not because they saw the settlement coming — most didn't — but because the underlying business case for centralized data was already there. Donor reporting, NIL documentation, recruiting proof, S&C visibility. The settlement just raised the cost of not having it.
The gap between those two columns isn't a technology gap. It's a data architecture decision that was made — or not made — before the settlement existed. Programs that had already invested in centralized athlete data found that their infrastructure absorbed the new compliance requirements without a major rebuild. Programs that hadn't are facing the compliance requirements and the infrastructure build simultaneously.
That's a difficult position. The settlement doesn't pause while your business office and IT team negotiate a data systems project.
What "Revenue-Sharing Ready" Data Infrastructure Actually Looks Like
Revenue-sharing readiness isn't a single platform or a compliance module you bolt on. It's a set of data capabilities that need to be connected — financial, performance, academic, and legal — around a unified athlete record that can serve as the source of truth for both operational decisions and regulatory reporting.
The programs that have built it share a few structural characteristics:
A unified athlete record as the anchor. Every athlete in the program has a single record that pulls together enrollment and eligibility data, financial aid and compensation history, performance metrics, NIL activity, and designation status. Not five separate systems that a compliance coordinator manually cross-references — one record, updated continuously, accessible to the compliance office and the business office with appropriate permissions.
Financial data aligned to the settlement's revenue categories. The cap calculation uses eight specific MFRS revenue categories. Programs with revenue data organized around those categories can run the calculation as a standing report. Programs whose financial systems use different categorizations have a translation problem they discover at reporting time.
NIL deal intake that's workflow-driven, not email-driven. The five-day submission window to NIL Go is tight enough that informal intake creates compliance risk. Programs that have built a structured deal intake workflow — legal review, athlete record entry, CSC submission, confirmation logging — meet the window as a matter of process. Athletic directors evaluating data vendors are asking whether the platform can support NIL intake workflows, not just performance dashboards.
Audit trail generation built in. The CSC has enforcement authority. When it reviews a program's revenue-sharing practices, it will ask for documentation of the decisions that led to each athlete's compensation — the cap calculation, the distribution methodology, the deal fair-market-value assessment. Programs that have built audit trail generation into their data workflows can produce that documentation quickly. Programs that haven't will reconstruct it from emails.
"The CSC audit is not a hypothetical. It's a scheduled accountability mechanism with enforcement teeth. Your data infrastructure is either ready to answer those questions or it isn't."
None of this is abstract. The same donor reporting infrastructure that connects athlete performance data to development officer conversations — unified profiles, standardized exports, cross-system visibility — is the infrastructure that makes CSC compliance defensible. The investment isn't compliance-specific. It's a foundational athletic department capability that the settlement has made mandatory to justify.
The Business Office's New Role in Athletic Data
For most of D1 athletics history, the business office and the performance staff operated in separate worlds. Finance tracked revenue, expenses, and financial aid. The S&C and sports science staff tracked GPS loads, force plate outputs, and training volume. They used different systems, reported to different people, and had no particular need to share data.
The settlement ended that separation. Revenue sharing compensation ties athlete performance data directly to financial reporting. NIL deal valuation — which the CSC reviews against market benchmarks that include performance data — links an athlete's documented production to whether their NIL deal passes regulatory scrutiny. Designated athlete status, which affects roster cap calculations and scholarship financial aid reporting, requires the business office to have real-time visibility into roster composition that historically lived with the compliance and athletic operations offices.
CFOs and athletic department business officers who haven't been part of the conversation about centralized athlete data systems need to be part of it now. The performance data isn't just an S&C tool anymore. It's a financial compliance input — and the business office owns the reporting obligation it feeds.
The programs managing this well are the ones where the AD, the CFO, the compliance director, and the performance staff have built shared data infrastructure instead of parallel systems. Not because they were visionary about the settlement — most weren't — but because they recognized that athlete data touches every department in ways that require a shared foundation to manage.
The settlement made that shared foundation mandatory. The programs that built it before July 2025 are compliant. The programs that didn't are in a controlled scramble — and 2026-27 will be the year that gap becomes visible in CSC reporting outcomes.