FieldPassSupport
← All articles

Getting started

Getting Started with FieldPass

What is FieldPass?

FieldPass is a compliance workflow platform for NCAA Division I NIL (Name, Image, Likeness) deals. It helps student-athletes, agents, and collectives create submission-ready packets for NIL Go — the official NCAA clearinghouse — with fewer rejections and faster resubmissions.

FieldPass does not submit to NIL Go on your behalf. It produces the organized, compliance-checked packet PDF you need to make that submission yourself.


Who is FieldPass for?

User type How FieldPass helps
Student-athletes Guided deal setup, auto-generated agreement and attestations, compliance readiness check before submitting
Agents / representatives Enter deal details on behalf of athletes; manage multiple deals from one account
NIL collectives Scale compliant deal workflows across a roster of athletes
Compliance staff Faster review with structured packets and version diffs when resubmission is needed

What are the two FieldPass products?

FieldPass Clear — The compliance engine. It checks your deal against policy rules, generates a NIL Go-ready packet PDF, and tracks submission outcomes so you can fix and resubmit quickly.

FieldPass Match — The opportunity-discovery layer. It ranks brand campaigns against the athlete's profile using engagement metrics, geography, sport affinity, and semantic fit. Athletes apply, message brands, and convert matched threads directly into Clear deals. See FieldPass Match.


How do I create an account?

During the current pilot, accounts are created automatically the first time you access the platform. You do not need to sign up in advance. Contact the FieldPass team through the early access form to get started.


What does the FieldPass workflow look like?

  1. Create a deal — Enter athlete info, brand/counterparty info, deal type, dates, compensation, and deliverables.
  2. Upload supporting documents — Attach any files required for your deal type (e.g., campaign brief).
  3. Generate a packet — FieldPass checks your deal against compliance policy and produces a versioned PDF packet.
  4. Review the readiness status — Fix any blocking issues flagged by the policy check.
  5. Submit to NIL Go — Use the packet as your submission artifact.
  6. Record the outcome — Log whether the submission was accepted or rejected. If rejected, fix issues and regenerate the packet.