FieldPassSupport
← All articles

Using FieldPass Clear

Generating & Downloading Packets

What is a packet?

A FieldPass packet is a versioned, audit-ready PDF that bundles everything needed for a NIL Go submission into one organized file. It is produced from your deal data and uploaded documents.

FieldPass is not NIL Go. The packet is the artifact you use to submit to NIL Go yourself (or to your compliance office).

What's inside a packet?

Every packet contains:

  1. Cover sheet

    • Packet ID and version number
    • Generation timestamp (UTC)
    • Policy library version and constraints profile version used
    • Submission readiness status (Pass / Warnings / Blocked)
    • List of any issues flagged by the policy check
    • Required evidence checklist with satisfaction status

  2. Deal summary sheet

    • Athlete legal name, school, sport
    • Counterparty legal name, address, and contact
    • Deal type, term dates, compensation, and deliverables
    • Exclusivity and usage/licensing terms (if applicable)

  3. Auto-generated NIL agreement

    • Parties, scope of work, consideration, and term/termination
    • Deliverables exhibit
    • Compensation exhibit
    • Compliance representations (no pay-for-play, no recruiting inducement)
    • IP/license section (for content licensing deals)
    • Signature blocks

  4. Athlete disclosures and attestations

    • Athlete attestation: accuracy of deal information, no performance contingency, no prohibited inducements
    • Counterparty attestation: no recruiting inducements, payment reflects services
    • Optional agent/representative attestation

  5. Supporting documents

    • All versioned uploads embedded (PDFs merged inline; non-PDFs referenced)

How do I generate a packet?

Once you have created a deal and uploaded any required documents, generate a packet from the deal page. The packet will be created within seconds.

The response includes:

  • The packet ID (for download)
  • The policy evaluation result (Pass / Warnings / Blocked)
  • A remediation list of blocking or warning items to fix
  • A diff from the previous packet version (what changed)

What does the packet version number mean?

Each time you generate a packet for a deal, the version number increments (v1, v2, v3, …). Version numbers let you and your compliance team track exactly which set of deal data and documents was used for each submission attempt.

The diff report shows what changed between the current and previous version — added documents, changed deal fields, updated compensation, etc.

How do I download my packet?

Download the packet PDF from the packet detail page. The download is authenticated — only the deal creator and ORG_ADMIN users can access packets. The file is delivered with a Content-Disposition: attachment header and includes a SHA-256 hash in the response headers for integrity verification.

What is the SHA-256 hash on my packet?

Every packet includes a SHA-256 hash of its ordered manifest (the list of all included files and their individual hashes). This hash:

  • Proves the packet has not been modified since generation
  • Lets you verify that what NIL Go received matches what FieldPass produced
  • Provides tamper evidence for audit purposes

You can verify the hash using any SHA-256 tool by hashing the downloaded PDF and comparing it to the value returned in the response header.

Why does regenerating a packet produce a different hash even if nothing changed?

If any deal field, upload, or timestamp changed between generations, the manifest changes and so does the hash. If you want to verify that nothing changed, compare the diff report — a "no changes" diff confirms the packet content is identical to the previous version.

I hit my 3-packet limit per deal. What do I do?

Free accounts are limited to 3 packet generations per deal. To generate more (for example, after multiple rounds of revision and resubmission), upgrade to a Pro plan. See Free vs. Pro Plans.

ORG_ADMIN accounts have no packet limits.