FieldPass Match
What is FieldPass Match?
FieldPass Match is the opportunity-discovery layer of FieldPass. It connects student-athletes with brands by ranking real campaign opportunities against the athlete's profile — using engagement metrics, geography, sport-to-industry affinity, and semantic fit to the campaign brief.
Match is live. Athletes and agents can browse ranked campaigns, apply, and message brands today.
How is Match different from FieldPass Clear?
FieldPass Clear is the compliance engine — it structures, documents, and compliance-checks deals you've already found.
FieldPass Match is the discovery layer — it surfaces the right-fit deals in the first place, particularly for athletes who have strong local or regional value but don't have nationally recognized names.
The two products connect: when a Match thread leads to an agreement, you can convert it to a FieldPass Clear deal in one click without re-entering data. See Converting a thread to a Clear deal below.
The opportunity feed
The opportunity feed (/match) shows all active brand campaigns ranked by match score. Each card displays:
- Brand name and industry
- Campaign title and description
- Match score (0–100%)
- Compensation range
- Geography (city, state, and radius — or "national" for geography-agnostic campaigns)
- Deal type
- Application deadline (if set)
- Bullet-point reasons explaining why this campaign matched
Campaigns are sorted highest match score first.
How is the match score calculated?
Match uses a two-layer scoring model:
Layer 1 — Structured scoring
| Signal | What is measured |
|---|---|
| Geography | Distance between the athlete's school and the brand's city; closer = higher score |
| Division | Whether the campaign targets the athlete's division (D1/D2/D3/NAIA/NJCAA) |
| Engagement rate | Engagement percentage on the athlete's social profiles, not just raw follower count |
| Deal type preference | Alignment between the athlete's preferred deal types and the campaign's deal type |
| Sport affinity | Affinity between the athlete's sport and the brand's industry (e.g., cross-country → outdoor brands) |
Layer 2 — Semantic re-ranking
Where available, the engine uses embedding-based cosine similarity to score how well the athlete's profile text matches the campaign brief. Layer 2 refines Layer 1 scores rather than replacing them.
The match score and the reasons bullets on each campaign card reflect the combined result of both layers.
Applying to a campaign
Athletes and agents can apply to any campaign from the campaign detail page.
- Open the campaign from the feed
- Click Apply to campaign
- Optionally add a note (up to 140 characters) introducing yourself or explaining your fit
- Click Submit application
Submitting an application creates a message thread for that campaign and redirects you to it. See Message threads below.
You can also click Save for later to bookmark a campaign. Saved state is local to the current session.
Message threads
When an application or brand invitation is accepted, FieldPass opens a persistent message thread between the athlete (or their agent) and the brand (via their ORG_ADMIN).
Inside a thread you can:
- Read the full message history, including the opening note from the application or invitation
- Send new messages (up to 1,000 characters each)
- See who sent each message (role label and timestamp)
- Convert the thread to a FieldPass Clear deal (see below)
Thread access is participant-based: only users who are part of the thread can view or message it. ORG_ADMIN users have access to all threads.
Converting a Match thread to a Clear deal
Once negotiation in a thread reaches a point where you're ready to document the deal formally, click Create Deal in FieldPass Clear from the thread page.
FieldPass automatically pre-fills a new Clear deal with:
- Deal title (brand name + campaign title)
- Deal type (mapped from the campaign)
- Counterparty information (brand name, contact placeholders)
- Compensation (set to the campaign minimum; update to the agreed amount)
- A default 30-day term starting today
- A starter deliverable (update to reflect the actual agreed deliverables)
After the deal is created, you land on the Clear deal detail page. Review and complete all fields — especially compensation and deliverables — before generating the compliance packet.
Brand-side: viewing athlete matches
ORG_ADMIN users can view the ranked athlete results for any campaign by clicking View brand-side athlete matches on the campaign detail page.
The athlete results page shows:
- Athlete name, school, sport, and division
- Match score and match reasons
- Engagement rate and follower count
- Distance from the brand's location (or "National campaign" for national campaigns)
- Preferred deal types
Filtering athlete results:
| Filter | What it does |
|---|---|
| Division | Show only athletes from the selected NCAA/NAIA/NJCAA division |
| Preferred deal type | Show only athletes whose preferred deal types include the selected type |
| Max distance | Slider to limit results to athletes within a specified radius of the brand location |
Inviting athletes to a campaign
ORG_ADMIN users can send a campaign invitation to any athlete in the results list.
- Click Invite to campaign on an athlete card
- Optionally enter the athlete's FieldPass email address (creates or links their account)
- Write a message to include with the invitation
- Click Send invite
Sending an invitation creates a message thread, identical in structure to an application thread, with brand_invite as the initiator. If you provided the athlete's email, they are added as a thread participant automatically.
Who can use FieldPass Match?
| Role | What they can do |
|---|---|
| Athlete | Browse campaign feed, view campaign details, apply to campaigns, message threads they're a participant in, convert threads to Clear deals |
| Agent | Same as Athlete — can apply and manage threads on behalf of athletes they represent |
| ORG_ADMIN | Browse feed, view athlete match results for campaigns, invite athletes, access all threads |
What is the "Data: Fallback" badge?
On Match pages you may see a small badge reading Data: Fallback. This means the Match database tables are not yet connected in the current deployment, and the feed is showing seeded sample data instead of live campaigns.
When connected to the live database, the badge reads Data: Persisted and shows real, active campaigns.