61Players, Coaches, Admins, Treasurers

Player Statistics & Profile Analytics — GoClubPro

Training Module 61 | Understanding What Data the Platform Tracks and How to Use It


What This Guide Covers

GoClubPro accumulates data about every player over the course of a season — attendance, payment history, RSVP responsiveness, injury records, and (if enabled) Fantasy League scoring events. This guide explains what is tracked, where to find it, and how different roles use this data to make better decisions.

Primary audience: Players (own profile), Coaches (squad analytics), Club Admins (club-wide patterns), Treasurers (payment behaviour)


SECTION 1: WHAT DATA IS TRACKED

Per-Player Data Points

Data TypeUpdated ByVisible To
Attendance % (matches)Admin/Coach after each matchPlayer (own), Coach (squad), Admin
RSVP historyPlayer (RSVPs)Coach, Admin
Blockout datesPlayerCoach, Admin
Injury historyPlayer, Coach, AdminPlayer (own), Coach, Admin
Payment historyAuto (fees) + TreasurerPlayer (own), Treasurer, Admin
Registration statusAuto (payment)Coach (registration state only), Admin, Treasurer
league platform data (if linked)schedule syncAdmin (profile view)
Fantasy League scoring eventsAdmin/CoachAll members (if Fantasy League enabled)
Selection historyAuto (Squad Builder)Coach, Admin

What is NOT Tracked

  • On-field performance metrics (unless manually entered via Fantasy League scoring events)
  • Fitness data (no integration with wearables or fitness apps)
  • Disciplinary history (fines are recorded in Fines module but not a "disciplinary record")
  • Psychological or mental health notes
  • Training attendance (tracked separately from match attendance; not in Squad Builder)

SECTION 2: PLAYER PERSPECTIVE — YOUR OWN PROFILE

What You Can See in Your Profile

Profile → [Your Name] → Summary shows:

  • Personal details: Name, photo, DOB, contact details, emergency contact
  • Teams: Which team(s) you're assigned to this season
  • Payment summary: Outstanding fees, payment history
  • Attendance: Your match attendance percentage for the current season
  • Injury status: Current active injuries / return dates
  • Blockouts: Your registered unavailability periods

Reading Your Attendance Data

Attendance % = matches attended ÷ matches selected × 100

Example: Selected 12 times, attended 10 → 83% attendance

What coaches see: Your attendance% is visible in the Squad Builder when coaches are building their squad. Consistently low attendance may affect selection.

What affects attendance records:

  • Only matches where you were confirmed in the squad count
  • A RSVP'd "yes" that you then missed (no-show) counts against you
  • Injury absences: if recorded as an injury absence rather than a no-show, they are noted but handled per coach's policy

Managing Your Blockouts

Blockouts communicate extended unavailability (holidays, work commitments, rep duties):

  1. Profile → Blockouts → Add Blockout
  2. Enter: start date, end date, reason (optional)
  3. Save

Effect: Any Squad Builder session covering that date range will show you as unavailable. The coach won't include you without manually overriding.

Best practice: Add blockouts as soon as you know about them — don't wait until the week before. Coaches plan weeks ahead.

Remove a blockout: Profile → Blockouts → find the blockout → Delete


SECTION 3: COACH PERSPECTIVE — SQUAD ANALYTICS

Using Attendance Data for Selection

Squad Builder → select fixture → player list shows:

  • RSVP status (Going / Not Going / No Response)
  • Blockouts active for this fixture (shown as unavailable)
  • Injury status (injury badge if active injury)
  • Attendance % for the season (visible as a data point)

Using this data:

  • High attendance % + RSVP'd yes → reliable pick
  • Low attendance % + no RSVP → follow up before confirming; consider risk
  • Active injury → include only if cleared and coach judges it safe

Attendance % as a selection signal: It's a data point, not a rule. A player with 70% attendance may have had legitimate absences (work, family, injury). Context matters. Use it to identify patterns worth investigating, not to automatically exclude.


RSVP Response Rate

Coaches can see RSVP response rates over time:

  • Players who consistently RSVP early → reliable to plan around
  • Players who consistently don't RSVP → coach must chase every week → consider a team culture conversation
  • Players who RSVP yes then no-show → attendance record reflects this

Coaching insight: RSVP responsiveness often correlates with commitment level. A team where all players RSVP by Tuesday is easier to manage than one where the coach is chasing responses on Friday.


Tracking Development Over a Season

While GoClubPro doesn't have a formal player development tracking module, coaches can use the combination of:

  • Selection history (who's been in the squad each week)
  • Attendance % (who shows up)
  • Fantasy scoring events (if enabled) — who's scoring, assisting, being awarded best-on-ground
  • Coach's own notes (external to the platform)

For junior development tracking: Module 50 (Junior Development Pathways) covers how to use this data in a development context.


SECTION 4: ADMIN PERSPECTIVE — CLUB-WIDE PATTERNS

Identifying At-Risk Members

Admin Panel → Members → sort or filter by various criteria

At-risk signals:

  • Low payment compliance (Treasurer → Aging → members with long-overdue fees)
  • Blocked by injury for multiple consecutive rounds
  • No RSVP to 3+ consecutive fixtures (disengagement signal)
  • Profile incomplete (no photo, no emergency contact) — may indicate a uncommitted member

Module 48 (Member Retention & Growth) covers a full at-risk protocol. The data sources are in GoClubPro; the intervention happens through personal contact.


Comparing Season Data Year-on-Year

GoClubPro doesn't auto-generate year-on-year reports, but you can compare manually:

  1. Export current season data: Treasurer → Accounting → Export (financial) + Admin Panel → Members → Export (membership)
  2. Compare with previous export (saved externally)
  3. Key comparisons: member count growth, total fees collected, outstanding debt ratio, RSVP engagement

Best practice: Export at the same point each season (e.g., "end of Round 10") to make comparisons meaningful.


Using Payment History for Policy Decisions

Treasurer → Accounting → member history

Useful questions:

  • "Has this member paid consistently in previous seasons?" → relevant for waiver decisions
  • "Is this member's late payment a one-off or a pattern?" → relevant for committee escalation
  • "What's the overall outstanding debt ratio as a percentage of total fees?" → relevant for AGM reporting

This data doesn't generate automatically as a report — the Treasurer must query it by looking at individual records or the Aging view. For a structured financial overview, use the AGM reporting workflow in Module 34.


SECTION 5: FANTASY LEAGUE AS A STATS SYSTEM

Fantasy Scoring Events as a Proxy for Performance

If your club runs Fantasy League, the scoring events entered after each match constitute the closest thing GoClubPro has to a player performance database:

  • Who scored goals/tries
  • Who was awarded best-on-ground
  • Who made assists
  • Who scored in consecutive rounds

Using this data:

  • End-of-season awards: "most goals scored this season" can be derived from Fantasy scoring events
  • Coach's player of the year: supported by best-on-ground tally from Fantasy events
  • Player development: if a junior is regularly appearing in Fantasy scoring events, their development is visible

Export Fantasy data: Fantasy League → Leaderboard → Export (if available) to get the season's scoring event summary.


SECTION 6: DATA YOU CAN'T SEE AND WHY

Privacy Constraints on Player Data

A player can always see:

  • Their own full profile, payment history, attendance, and injury records

A coach can see:

  • RSVP status, availability, injury status, attendance% for their squad members
  • NOT: individual payment details, personal contact info beyond what's shared

A treasurer can see:

  • Payment history and financial position for all members
  • NOT: injury records, selection history, personal coaching-related data

The separation is deliberate: Financial data is sensitive — not every coach needs to know who's behind on their fees. Injury data is medical — not everyone needs access. GoClubPro's role-based access enforces these separations.


VISUAL: Who Sees What

DATA TYPE PLAYER COACH TREASURER ADMIN
─────────────────────────────────────────────────────
Own payment ✅ ❌ ✅ ✅
history

All members' ❌ ❌ ✅ ✅
payment history

RSVP/availability ✅ ✅ ❌ ✅
(own squad)

Injury records ✅ ✅ ❌ ✅
(own squad)

Attendance % ✅ ✅ ❌ ✅
(own squad)

Fantasy scoring ✅ ✅ ✅ ✅
(all members)

TOOLTIPS & HINTS

  • Attendance % resets each season — it only reflects the current active season, not historical
  • Blockouts protect both player and coach — a player who adds blockouts in advance prevents being selected and then having to withdraw
  • Fantasy events = your only performance database — if you want end-of-season stats, Fantasy League scoring events are the data source
  • RSVP no-responses are a signal, not a fact — follow up before assuming availability
  • Export before archiving — when a season is archived, export member and financial data for your records

FAQ

Q: Can I see my attendance record from previous seasons? A: Attendance % reflects the current active season. Previous season data may be accessible in archived season views if your admin has preserved it.

Q: Why can't coaches see whether a player has paid their fees? A: By design — payment information is financial/sensitive data restricted to Treasurer and Admin roles. Coaches receive a "registration status" signal (registered/not registered) without the dollar details.

Q: Is there a way to export all player statistics for the end-of-season awards night? A: Fantasy League scoring events can be exported if Fantasy League is enabled. Attendance data is visible per player but no bulk export of attendance across all players exists as a single report. Manually note top attendance from the Admin Panel member view.

Q: Our club wants to track training attendance separately from match attendance. Where does this go? A: Training attendance is tracked per-session if the coach records it (Admin Panel → Schedule → training fixture → attendance). This is separate from match attendance% in the Squad Builder. There's no combined "total training + match attendance" report.


COMMON MISTAKES

MistakeConsequencePrevention
Assuming no RSVP = not availablePlayer gets excluded without noticeFollow up no-responses before confirming squad
Not recording injury absences properlyAttendance% unfairly reflects injury absences as no-showsAlways record injuries so absences are attributed correctly
Forgetting to remove expired blockoutsPlayer appears unavailable after they returnPlayers: remove blockout when returning; coaches: verify if player seems incorrectly blocked
Not exporting data at season endYear-on-year comparison impossible next yearScheduled export at same point each season
Using payment status to make selection decisions without treasurer checkCoaches acting on assumptions not factsCoaches check with Treasurer if payment policy affects selection

SHORT ONBOARDING SCRIPT

"GoClubPro tracks attendance, RSVP behaviour, injuries, payments, and (if Fantasy League is active) scoring events. Players see their own data in their profile. Coaches see their squad's availability and attendance in Squad Builder. Treasurers see payment history. No one role sees everything — the separation is intentional. The most useful habit: players add blockouts early, coaches check RSVP + attendance before confirming squads, and admins export data at end-of-season before archiving. The platform accumulates data all season; the value comes from using it to make better decisions."


MICRO-TRAINING QUICK TIPS

  • Attendance % = matches attended ÷ selected — resets each season
  • Blockouts: add early (Profile → Blockouts → Add) — protects player and helps coach plan
  • Coaches: RSVP + blockout + injury = full availability picture in Squad Builder
  • Fantasy scoring events = your only in-platform performance database
  • Export member + financial data at end of each season before archiving
  • Payment status: coaches don't see dollar details (Treasurer/Admin only)

Training Module 61 | See also: 05 Selection Board · 08 Player Profile · 41 Injury Management · 48 Retention & Growth · 54 Fantasy League Admin