Mock product surfaces
The Divot Card loop, mocked end to end.
These pages show the beta and planned surfaces around the core card: practice history, retest proof, facility guest cards, coach review, data quality, and honest guardrails.
Preview group
Player loop
Mocked now so the product direction is visible without pretending every workflow is live.
Completed card timeline
Practice Passport
A running improvement history built from open, practicing, ready-to-retest, passed, and inconclusive Divot Cards.
Proof after practice
Retest Receipts
A short before/after result that says improved, unchanged, worse, or inconclusive with confidence and next recommendation.
Regression watch
Club Drift Alerts
Club-specific warnings when a repeatable pattern moves across multiple sessions.
Preview group
Facility
Mocked now so the product direction is visible without pretending every workflow is live.
Facility guest session mock
Bay Mode
A staff-friendly bay session flow for generating no-signup guest Divot Cards from one simulator export.
No-signup distribution
Facility Guest Cards
A facility workflow for branded guest cards that can be printed, shared, or claimed later by the golfer.
Preview group
Coach
Mocked now so the product direction is visible without pretending every workflow is live.
Reviewed assignment
Coach Stamp
A clear marker that a coach reviewed, edited, and approved the Divot Card before the student received it.
Approve before assign
Coach Review Queue
A coach workspace for reviewing AI/rule-drafted cards before students receive the final practice assignment.
Preview group
Trust
Mocked now so the product direction is visible without pretending every workflow is live.
Trust layer
Data Quality Score
A visible score and warning list that explains what DivotData can and cannot say from the uploaded file.
Product standard
Card Quality Guarantee
A product promise that every Divot Card must answer four questions before it is considered useful.
Anti-overclaim guardrail
Do Not Chase This Yet
A card section that protects golfers from changing the wrong thing based on incomplete simulator data.
Card quality rule
Every mock still has to answer the real product question.
What changed, why it matters, what to practice next, how to retest, and whether the work paid off.