Revenue Sharing Gave College Athletic Departments a Software Problem

On 6 June 2025, Judge Claudia Wilken granted final approval to the House v. NCAA settlement. Direct payments from schools to athletes began on 1 July. The first-year cap was set at about 20.5 million dollars per school, calculated as roughly 22 percent of average power-conference revenue from media rights, ticket sales and sponsorship, with increases of around 4 percent a year. The College Sports Commission reported about 21.58 million for 2026-27.

Most coverage treated this as a legal and competitive story. Inside athletic departments it immediately became an operations story, and a lot of them were not ready for it.

What the settlement actually requires of an athletic department

A school that opts in has to track every direct payment against an annual cap, across every sport, through a year of roster changes, injuries, transfers and mid-season renegotiations. It has to allocate that pool across sports and justify the allocation internally and, potentially, under Title IX scrutiny.

Separately, athletes must report third-party deals worth 600 dollars or more to NIL Go, the clearinghouse built with Deloitte, within five business days of signing. Those deals are reviewed for valid business purpose and fair market value, with disputes going to arbitration and then the College Sports Commission. The Commission, led by former MLB executive Bryan Seeley, enforces these rules independently of the NCAA.

Read that as a system specification rather than a legal summary and the shape of the problem is obvious. You need a ledger with a hard cap, a workflow with deadlines measured in business days, an audit trail that survives external review, and reporting across a dozen roles who all need different views of the same data.

The spreadsheet stage, and why it ends badly

The first season was run in spreadsheets almost everywhere, which was a reasonable response to a rule set finalised weeks before it took effect.

The failure modes are predictable. Two versions of the cap tracker circulating with different numbers. A commitment made verbally in a recruiting conversation that never reaches the file. A deal signed on a Friday and reported on the following Thursday because nobody was tracking the five-day clock. No record of who approved what and when, which is precisely what an enforcement body asks for first.

None of these are exotic. They are what happens to any process with hard deadlines, multiple approvers and real money when it runs on shared files.

What a usable system looks like

A single ledger that is the only source of truth for committed and projected spend against the cap, visible in real time to the people making commitments. Not a monthly report. If a coach can verbally commit money without seeing the remaining balance, the cap will be breached by accident.

Deadline tracking from the moment a deal is signed, with automatic escalation as the five-day window closes. An immutable approval log recording who approved each payment, when, and under what authority. Integration with the systems the department already runs for compliance, financial aid and the student record, because re-entering the same athlete into four systems is how the data drifts apart.

Very little of this is novel software. It is contract lifecycle management and budget control applied to a new domain under an unusually tight deadline regime. Departments building it usually find that custom business software and automation sized for forty users costs considerably less than the staff time currently lost to reconciliation.

Title IX adds a second dimension to every allocation decision. A department weighting its pool heavily towards football and men’s basketball, which most do, needs the reasoning and the figures recorded at the time rather than reconstructed later under review. A system that captures the rationale next to the number is doing compliance work a ledger alone cannot.

The part that will keep changing

This framework is not stable. Proposed federal legislation would alter the cap substantially and change the enforcement structure, appeals continue, and the Commission is still establishing precedent through its decisions. Anything built now has to assume the rules move.

In practice that means configurable caps and reporting thresholds rather than hard-coded values, and the ability to add a deal type or an approval step without rebuilding. The schools that treated this as a permanent build are the ones that will pay for it twice. Staying current with how the rules are being applied, through college sports coverage and the Commission’s own published guidance, is part of running the system rather than a separate research task.

The honest summary for an athletic director

You now run a capped payroll with external reporting obligations and an independent enforcement body. That is a finance and compliance operation, and it needs the systems one gets, not a shared drive and a determined compliance officer.

The departments that accept this in year two will spend a modest amount on tooling and move on. The ones that wait will find out what it costs when a reporting failure reaches the Commission, and that bill is not measured in software licences.

Similar Posts

Leave a Reply

Your email address will not be published. Required fields are marked *