portal players, Euro prospects, and HS recruiting cycle targets
Back to proof
Sports Analytics / Recruiting Workflow
BYU Transfer Portal Evaluation Workflow
A staff-facing evaluation workflow that turns roster criteria, player data, fit notes, and value tradeoffs into repeatable candidate briefs.
Outcome: The workflow moved from one-off analysis into staff use: 30+ portal players, Euro prospects, and high-school recruiting cycle coverage, with daily report usage during active evaluation windows.
The evidence
Problem, system, review loop, result.
Public proof
This case study shows AI implementation ability through criteria design, prompt/context systems, repeatable evaluation output, staff adoption, and daily operator use.
Public visuals use app screens built from public player data. Private staff notes, strategy, private evaluations, and non-public recruiting context stay out.
reports integrated into staff workflow during active windows
criteria adjusted by position and roster need rather than rebuilding the system
Ownership
Clear about the judgment. Clear about the assistance.
Problem definition, workflow design, evaluation criteria, source selection, validation, rollout, user feedback, adoption, and outcome framing.
Code, app structure, scripts, UI wiring, parsing, tests, and iteration support. I stayed accountable for whether the workflow was useful and honest.
Artifacts and proof
Look at the work.
Screenshots and artifacts are public-safe by design. Private strategy, records, credentials, and customer data stay out.
Local app view using public player data, with filters, role archetypes, status, impact score, and core box-score context.
Real player profile showing RAPM, skill dimensions, role classification, and similar-player context.
Role-based team-fit search that ranks available portal players against selected roster needs.
Public version shows app UI and local portal data, while private staff notes, strategy, and evaluation context stay out.
Why it matters