Run one methodology across every age band
Write the club's standards down once, apply them per age group, and put a real approval flow between a coach's idea and the club library. Development plans, evaluations and session history stay in the club workspace when the coach who wrote them does not.
Club library
Review queue
Rondo to third-man release
Approved v2A. Meyer · U12
Pressing triggers, wide trap
In reviewS. Okonjo · U15
Positional 8v8 + 3
Second reviewerL. Barros · U14
Finishing from cutbacks
SubmittedA. Meyer · U16
Standards check · AI estimate, advisory
78 / 100Five roles, and exactly what each one can touch
Access is scoped in the queries, not just hidden in the interface. Staff and viewer only ever see the teams they are linked to. There is no analyst role, no medical role and no parent role: families reach the club through the player portal rather than by holding a seat.
Owner
Every team- Everything an admin can do
- Holds billing and the seat count
- Transfers ownership, archives the club
- One per club, set at creation
Admin
Every team- Approves and rejects library submissions
- Edits methodology and age-group guidance
- Sends club announcements
- Invites people, sets roles and policy
Coach
Every team- Submits drills and sessions for approval
- Republishes an approved item as a new version
- Reads the activity feed
- No approvals, no methodology edits
Staff
Only linked teams- Works inside the shared staff workspace
- Submits to the library, reads what is approved
- Sees only the teams they are linked to
- No approvals, no activity feed
Viewer
Only linked teams- Reads the approved library
- Reads dashboards for linked teams
- No editing anywhere, no submissions
- For directors, physios and board members
Three workspaces, one path from idea to club standard
The reason coaches share is that private drafting stays genuinely private. Every drill and session is stamped with one of three scopes, and moving between them is a decision somebody makes rather than a side effect.
My Workspace
Yours alone. Nobody in the club sees it, and it survives if you ever leave. A coach on a club seat still keeps a private space to think in.
Staff Shared
The working floor. Any member with an editor role can open and edit it. This is where a session gets built before anyone argues about whether it is club standard.
Club Approved
Published, versioned and read-only. Everyone including viewers can read it. Changing it means republishing a new version, not quietly editing in place.
How a session becomes club standard
Five steps, with a real rejection state and a real version history. Approval snapshots the item, so what the club approved does not silently change under it.
Submit
A coach hits Submit to club library from inside the drill editor or the session builder, with a note on what it is for. Nothing else about their work changes.
Review
Owners and admins see it in the Library queue. They can run the AI standards check against the club's own written methodology before deciding.
Second review, if you want one
Turn on the two-reviewer rule and a session needs a second approval from a different person before it publishes. Off by default.
Approve, and version 1 is written
Approval snapshots the item into the club library as version 1. Rejection is a real outcome too, and it will not go through without written review notes.
Republish, or fork
A coach republishes an approved item as version 2 with a summary, or forks a copy into their own workspace to adapt without touching the club's version.
Three approval settings, all off until you turn them on
- Require two reviewers on sessions, from two different people
- Auto-version approved items each time the source changes
- Let head coaches self-approve their own submissions
Write the methodology once, apply it per age group
Four fields describe how the club coaches. Twelve settings per age group decide what that means for U10 as opposed to U16, and sessions built for a group pre-fill from them.
The club profile
- Methodology description
How sessions and drills should feel across age groups, in your own words. - Principles
The non-negotiables every session should plan around. - Session themes
Named themes coaches pick from, so a theme means the same thing at U12 and at senior. - Learning outcomes
What a player should be able to do differently afterwards.
Twelve settings, per age group
- Preferred game format
- 5v5 through 11v11, per group
- Default session duration
- Pre-fills the planner for this group
- Default principles
- Seeded into a new session for this group
- Default learning outcomes
- Seeded the same way
- Required dimensions
- Every development plan must carry a goal here
- Minimum goals
- Below this, a plan reads as thin
- Maximum goals
- Above this, a plan reads as overloaded
- Review frequency
- Weeks between formal player reviews
- Observation frequency
- How often evidence should be landing
- Require player voice
- A plan is incomplete without the player's words
- Require goal outcome
- Closed goals must record how they ended
- Rubric anchors
- What 1 to 5 mean in writing, per dimension
Every player carries a record, not a folder
Individual development plans, rubric evaluations and the evidence behind them, held to the standard your age-group guidance sets.
Five dimensions, one rubric
Technical, tactical, physical, psychological and social. All five have to be scored before a review can lock, so nobody submits a half-finished evaluation.
Plans built from goals, not prose
Four goal kinds with process as the default, an advisory ceiling of four active goals, and criteria written per goal. Your age-group guidance can force a required dimension and set the floor and ceiling on goal count.
Evidence that arrives on its own
When a coach names a goal on a session block, checked-in players get evidence against that goal automatically. It removes the second entry, not the coaching judgement. Match evidence is weighted twice as heavily as training evidence.
Submit is the publish
Submitting a review locks it and notifies the family. Unlocking one needs a written reason and versions the row rather than overwriting it, so the history of what was said stays intact.
A cadence you actually hold to
Review frequency comes from your age-group guidance, defaulting to an EPPP-informed 12 weeks up to U10 and 6 weeks from U11. A 14-day stale flag marks players nobody has observed lately.
Comparison held back until it helps
Squad averages only appear from U13 upward. Below that, a plan is read against the player, not against the group.
What the director sees on a Monday
Six checks that count what has slipped and link straight to where you fix it, plus a dashboard that answers whether the methodology is reaching the pitch.
Pending approvals
Drills and sessions waiting on club review
Overdue reviews
Players whose next formal review date has passed
Stale evaluations
Players with no evaluation for 30 days or more
Plans due review
Active plans past their target review date
Unlinked staff
Staff entered by name but never linked to an account
Missing ownership
Teams with no linked lead coach assigned
Weekend brief
Every fixture across every team this weekend, each with a readiness score built from availability, recent training attendance and a penalty for overdue reviews.
Methodology adoption
A score per team for how far the club's written standards actually reach: principles used, themes and outcomes referenced, age guidance followed.
Review queue
Drills, sessions and development plans waiting on a decision, with the overdue ones counted separately and approvable from the card.
Staff load
Who is carrying how much, by linked staff member, so the workload is visible before someone burns out.
Teams grid
One tile per team: lead coach, squad size, weekly load, recent form, next fixture, and a warning line when something is off.
Library workflow
The submit to approve funnel, approved counts per team, and the drill your club actually reaches for most.
AI that informs, never authors
Eight tools exist across the product. None of them writes a plan, scores a rubric, submits a review, picks a team or generates a session. These four are the ones an academy touches.
Club standards check
Library review
Scores a submitted drill or session against your own written methodology and age guidance, naming the standard each finding refers back to. The score and verdict are computed from the findings by rule, so the same submission scores the same twice.
Progress report
Player file
Reads evaluations, active goals, appearances and season context and writes the account you would otherwise write from scratch before a handover. Dimension averages are overwritten with server-computed figures.
Parent summary
Plan tab
The same record in plain language for a family, football terms explained rather than assumed. Sending is a separate click, it only reaches linked guardians, and the send is audited.
Review prep brief
Reviews tab
What changed since the last formal review, with counts and dates off the record, plus a talking point and a question per active goal. Read only: it cannot fill in the form or score a rubric.
Club includes 500 credits a month across the whole staff, with no daily cap. A generation holds the maximum it could cost and settles at what was actually used, a failed run releases the hold in full, and a repeat on an unchanged record costs nothing. Anything a model wrote is labelled where it renders, with the time and the credits it cost.
The paper trail an academy is asked for
Everything that has to leave the system as a document does, rendered server-side from the same pages you read on screen.
Eight print-ready PDFs
The session plan in a coach version or a player version, the training week packet, the development plan, the season report card, a single locked review, the full player journey, the club season report and the officials' team sheet.
CSV where a spreadsheet is wanted
Club attendance, the pathway export and a season summary, plus JSON snapshots and a GDPR account export delivered as a signed link that expires after 24 hours.
A handover in one file
The player journey collects every cycle, review and transfer into a single document. It is what you hand the next coach, or the next club, when a player moves on.
What families actually see
Sharing outward is controlled by which surface you share, not by hoping a field stays hidden.
The player and parent portal
Linked guardians get a read-only view built on an explicit whitelist of what it will ever expose. Pro and Club.
Announcements and reminders
One message to every squad and their families, with read receipts, a 24 hour fixture reminder and an RSVP chase for the ones who have not answered.
Availability without an account
One event, one page. A parent taps yes, no or maybe from a link. The team calendar also publishes as a subscribable feed.
Photos private until published
Match gallery items are private by default and published one at a time. Nothing goes public because a folder was shared.
What Teloframe deliberately is not
Every line here traces to something we chose not to build. Club operations is a different product, and pretending otherwise would cost you a migration later.
- No membership fees, subscriptions or payment collection from families
- No safeguarding or DBS register, and no qualification expiry tracking
- No trials or registration intake forms
- No single sign-on, SCIM or directory sync
- No chat: announcements go one way, and there is no thread to moderate
- No club-wide attendance ledger beyond the session-level record and its CSV
What the Club plan costs
One price for the shared workspace, with seats added as the staff grows.
- 5 staff seats included, extra seats $8 a month or $77.80 a year
- 500 AI credits a month, shared across the whole staff, no daily cap
- Live co-editing on the tactics board, which is Club only
- 180 second animation clips, against 90 on Pro and 15 on Free
What the workspace unlocks
The Staff Shared and Club Approved scopes, all eight club tabs, the director dashboard, the approval queue with versioning, the methodology and age-group standards, the club activity stream and the club-wide default board theme. Everything a single coach gets on Pro is included underneath it.
Go deeper
This page is the academy overview. These go feature by feature.
Club workspace
Roles, scopes, the approval queue, standards and the director dashboard in full.
Player development
Plans, evidence, rubric reviews, the portal and the handover record.
Training sessions
Blocks, load, the live session and the reflection that feeds next week.
AI coaching assistant
All eight tools, what each one reads, and where the guardrails sit.
Academy FAQs
The questions directors and heads of coaching ask before rolling Teloframe out club-wide.
Who owns the work, the coach or the club?
How many staff fit in one academy workspace, and what can each of them do?
Is this suitable for under-18 player data?
Can we export development plans and evaluations?
Does AI write our player reports?
How do we actually keep every coach on the same methodology?
Can we run our own review cadence per age group?
What does Teloframe deliberately not do?
Roll one methodology out across the academy
Open Teloframe to see the workspace, or go straight to the Club plan to see how shared seats, the library approval flow and the director dashboard work for a multi-coach academy.