nilportal.ioExplain – Reason – Verify™

Every NIL evaluation should be documented, traceable, and tamper-evident.

nilportal.io is built for compliance teams that need structured agreement review, clear reasoning, and audit-ready evidence. This page explains how the system works, what it produces, and how you can use it.

How it works

nilportal.io uses a structured three-stage framework called Explain, Reason, Verify. Each stage produces a documented output. Nothing is hidden. Nothing is assumed.

EXPLAIN
Identify applicable policies

The system identifies which governed authorities — federal, CSC, and state — apply to the deal. It surfaces the exact clauses tied to the agreement. You see what rules are in play before any evaluation begins.

REASON
Apply structured logic to deal inputs

The system evaluates the agreement against three gates: associated entity status, valid business purpose, and range of compensation. Each gate produces a clear result with supporting rationale. The reasoning path is fully documented.

VERIFY
Generate a documented record

The system produces a structured compliance record that includes policy citations, timestamps, assessment scores, and a SHA-256 hash for tamper evidence. Every output is traceable back to the inputs and rules that produced it.

Common questions

How is this different from CSC submission or other tools?

CSC submission is the reporting step. Agreements are submitted to the College Sports Commission for review. nilportal.io evaluates deals before submission. It surfaces what was flagged, why it was flagged, and which policies apply. It produces the reasoning and evidence the institution needs before a deal reaches the CSC submission process.

Where do the scores come from?

Scores are generated by a deterministic rules engine that evaluates agreement inputs against three gates: associated entity status, valid business purpose, and range of compensation. Each gate applies specific policy criteria. The scoring logic is consistent and repeatable. The same inputs produce the same score every time.

How does the platform support an audit?

The platform is designed to support your institution's audit response. Every evaluation produces a documented record with policy citations, reasoning traces, and a SHA-256 hash for tamper evidence, exportable as a structured evidence pack that shows what was evaluated, which rules were applied, and what the system found. Whether that record is accepted in any particular proceeding is determined by the tribunal and your institution's overall compliance process — the platform provides documentation and tamper evidence; it does not by itself establish evidentiary weight or legal defensibility.

Does this replace legal review?

No. nilportal.io does not provide legal advice. It provides structured analysis and documented evidence to support your compliance review process. Your institution makes all final decisions. The platform is designed to inform your judgment, not replace it.

What happens if policies change?

The system maintains a governed corpus of official primary sources — the federal Executive Order, the CSC framework, the House settlement, and governed state NIL statutes. Conference NIL policy is consolidated under the CSC framework post-House. The corpus is versioned and hash-frozen; each evaluation records the corpus version it ran against. Previous evaluations retain their original policy references for audit purposes.

How do you prevent unsupported outputs?

Every finding links to a specific policy citation. If the system cannot identify an applicable rule, it does not generate a finding. Scores are produced by deterministic logic, not generative text. The reasoning path is documented and verifiable.

What data do you send to third-party services?

By default, none: regulatory retrieval runs in-process against the governed corpus, uploaded documents are stored as sealed evidence without machine extraction, and all compliance scoring is performed by the nilportal.io deterministic engine. If your institution explicitly enables the optional Document Processing intake feature, documents are processed by Google Cloud services under your institution's control, with pattern-detectable identifiers tokenized first; sensitive contact details and government identifiers are never extracted — see the Privacy Policy for details.

What an assessment looks like

Here is a simplified example of how nilportal.io evaluates an agreement.

Sample Assessment
Input

A university in Texas submits a $12,000 social media endorsement agreement between a football quarterback and a local energy drink company. The sponsor has made $75,000 in donations to the athletics program over the past three years.

Assessment Score
68Flags Identified
Reasoning Summary

Gate 1 flagged the sponsor as an Associated Entity based on the institution-disclosed donor relationship ($75,000 in cumulative donations to the athletics program) — Associated Entity deals receive the highest scrutiny tier in CSC review. Gate 2 found no warehousing patterns. Deliverables are specific: four social media posts and two personal appearances. Gate 3 found compensation within the estimated fair market range for a Power 4 quarterback in Texas.

Authorities
House Settlement (In re College Athlete NIL Litigation), Exhibit B
Texas Education Code §51.9246
CSC framework — Associated Entity review (collegesportscommission.org)
For institutional reference only. This assessment does not constitute legal advice or a compliance determination.

Policy and compliance insights

nilportal.io tracks regulatory changes across federal, CSC, and state authorities in its governed corpus. Here are examples of what the system monitors.

Policy updates
When a state changes its NIL statute or the NCAA updates its framework, the regulatory reference database is updated. Active evaluations can be re-assessed against the new rules.
Common agreement risks
The most frequent flags are lack of valid business purpose, warehousing (reserving rights for unspecified future work), and compensation above fair market benchmarks. These are the most common categories flagged in CSC review.
State-level differences
NIL rules vary significantly by state. Texas requires disclosure before entering into the agreement; Michigan requires disclosure at least 7 days before committing; California conditions NIL activity on team-contract conflict rules. For deals in a state with a governed statute in the current corpus, the system retrieves that state's own statutory text — not a paraphrase; where a state is not yet in the governed corpus, that is disclosed on the assessment and federal/CSC authorities are applied.
Federal oversight
The April 2026 Executive Order ties federal grant eligibility to NIL compliance enforcement. Institutions now need documented evidence of systematic oversight. The system generates SHA-256 hashed evidence bundles to support this requirement.

See how your current process compares.

Request a demo to evaluate a sample agreement against your institution's policies. See the reasoning, the citations, and the evidence your team would receive.

Request Institutional Briefing

nilportal.io provides automated compliance analysis for institutional review. This platform does not provide legal advice or compliance determinations. Final decisions remain the sole responsibility of the subscribing institution.

Patent Pending · Explain – Reason – Verify™ · Built on Google Cloud Platform

Back to home