Policy Checks & Compliance Status
What is the policy check?
Every time you generate a packet, FieldPass evaluates your deal against a set of policy rules and a constraints profile. The result tells you whether your deal is ready to submit, has warnings to review, or is blocked from submission.
This check runs automatically — you don't need to trigger it separately.
What do PASS, WARNINGS, and BLOCKED mean?
| Status | Meaning | Can you generate a packet? |
|---|---|---|
| PASS | All required fields, documents, and clauses are present | Yes |
| WARNINGS | Non-blocking issues detected; the packet can be generated but should be reviewed | Yes |
| BLOCKED | One or more required items are missing; the packet cannot be submitted as-is | Yes, but with a remediation list |
Even with a BLOCKED status, FieldPass will still generate the packet so you can see the full remediation list. Fix the blocking issues, then regenerate.
What causes a BLOCKED status?
Blocking issues arise when required fields, documents, or contract clauses are missing. Common causes:
| Blocking issue | How to fix |
|---|---|
| Missing deal term (start or end date) | Add term dates to the deal |
| Missing athlete identity (legal name, school, sport, or email) | Complete the athlete information |
| Missing counterparty identity (legal entity name or contact info) | Complete the brand/counterparty information |
| Missing compensation (amount or type) | Add compensation details |
| Missing deliverables | Add at least one structured deliverable |
| Social promotion deal missing platform or post count | Add the platform and post count fields |
What causes a WARNINGS status?
Warnings are non-blocking but indicate items that reviewers commonly flag. Examples:
- A document type is listed as recommended but not uploaded (e.g., campaign brief)
- A required contract clause is present but may need verification
- Compensation details are complete but unusually structured
You can generate and submit a packet with warnings, but it increases the chance of being flagged for review by the CSC.
What are required contract clauses?
FieldPass checks that the generated agreement includes specific compliance representations required for NIL Go submissions:
- No pay-for-play: Compensation is not contingent on athletic performance or enrollment decisions
- No recruiting inducement: The deal does not serve as an incentive to enroll at or remain at a particular institution
- Exhibits attached: Deliverables and compensation exhibits are present in the agreement
These clauses are auto-generated by FieldPass when you generate a packet. If the policy check flags a missing clause, it typically means a required field used to populate that clause is missing from the deal.
What is a sponsored content disclosure and why is it required?
Federal Trade Commission (FTC) guidelines and NIL Go policy require that sponsored content — social posts where an athlete is paid to promote a brand — include a clear disclosure (e.g., #ad, #sponsored).
FieldPass includes disclosure requirements in the deliverables structure. For each social promotion deliverable, enter the disclosure tag in the disclosure field. The generated agreement will reference this requirement.
What are policy rule versions and constraints profiles?
Policy rules are the core set of checks FieldPass applies to every deal (e.g., required fields, deal-type-specific requirements). These are versioned — the version used for each packet is recorded on the cover sheet.
Constraints profiles are configurable checklists of required uploads and clauses. The default constraints profile covers standard NIL Go requirements. Future Pro and org-tier features will allow institutions and collectives to configure custom profiles.
Both versions are recorded in every packet for a complete audit trail.