Coaching at almost any level — youth soccer through high school basketball through adult rec leagues — generates more documentation than people expect. The game plan for Saturday. The scouting notes from the team you're playing next. The practice plans for the rest of the month. The per-player notes about what each kid (or adult) is working on. The conversation with the parent who emailed about playing time. The roster, the contact list, the league rules, the field permits.
Most of it lives in a folder on your laptop, a stack of notebooks in your bag, the photos on your phone of the whiteboard from yesterday's practice, and a group chat with the assistant coaches. Three days before a game, you're rebuilding the picture from scratch.
A vault that holds all of it in one searchable shape — with the agent pulling what you need when you need it — turns coaching admin into something that fits around the actual coaching. Below is the shape we'd suggest.
One vault, one parent page per season, child pages from there
In Docapybara, the season gets a top-level page: 2026 Spring Soccer, 2026-27 Basketball. Underneath sit child pages for Roster, Practice plans, Game plans, Scouting, Players (a tree, one child per kid or adult), Parents/comms, Logistics, and Reflections.
Pages nest indefinitely, OneNote-style. So Players > Maya > Skill development is a valid path; so is Game plans > Week 4 vs. Tigers. The agent searches across the whole tree regardless of how you've organized it.
If you also coach a separate team or run private training on the side, each gets its own top-level parent. The vault holds all of them, the agent searches across or within as you ask. (For private coaching as a small business, the Running a Side Hustle Out of Your Notes App shape applies — coaching is a service business with the same admin needs.)
Practice plans — the page you actually open in the parking lot
The Practice plans page is the one you'll re-read most. One child page per practice, dated, with the warm-up, the technical work, the small-sided games, the scrimmage, and the cool-down. Roughly the structure you already use; just typed once instead of redrawn each week.
The agent can fork from past practices: "Take last Tuesday's practice plan, adapt it for this Thursday with more focus on transition defense — keep the same warm-up structure." You get a draft you tweak quickly instead of starting from blank.
For the running picture across the season, an inline database via the :::database::: directive captures every practice: date, focus theme, what worked, what didn't. The agent can summarize: "Across the last six practices, what topics did we cover, and which ones still need more attention before the [opponent] game?"
Voice works for the post-practice debrief. Walk to the car, tap record, talk for thirty seconds about what went well and what to fix. Audio recording in-app gives you a transcript with speaker labels. Lands on the practice's page.
Game plans — the document the team actually plays from
The Game plans page tree has one child per game. The starting lineup, the formation, the substitution rotation, the set pieces, the matchups to watch, the things you've told the team to focus on. Whatever level you coach at, the document doesn't have to be fancy — it has to be findable on the morning of the game.
The agent can pull from scouting and from past games against the same opponent. "For this Saturday's game against [opponent], pull last season's notes against them, the recent scouting notes, and draft a starter game plan I'll edit." You get the synthesis in seconds; you do the actual coaching judgment.
For post-game reflections — what worked, what didn't, what needs to change before the next game — drop a quick voice note. The agent can summarize the season's reflections later: "What patterns have shown up in my post-game reflections this season?" Useful for the end-of-season review.
Scouting — what you saw, what you'd run against them
For competitive coaching, Scouting is its own page tree. One child per opponent, dated entries. What you saw when you watched their games, what their strongest and weakest matchups looked like, what their set-piece tendencies are, who their key players are.
For coaches who film games, the videos can be referenced from the scouting notes (links, timestamps, with your written observations). For PDF scouting reports from leagues or programs, drop the PDF on the page. Docapybara converts uploaded PDFs to markdown via docstrange, so the agent can actually read them and pull specifics: "What did the scouting report say about [opponent] in transition?"
Across a season, the agent can build the picture: "Look at scouting notes for the four teams we still play this season — who's the toughest matchup, and what should we work on in practice to be ready?"
Players — the per-kid (or per-adult) context that matters
The Players page tree is where most of the coaching memory actually lives. One child per player. Strengths, weaknesses, what they're working on, recent progress, what motivates them, what you've talked about in 1:1s, any context the parents have shared, injury history, position preferences.
For longer-form per-player notes, voice is the right tool. After a practice or game where a player did something noteworthy, walk to the car and talk for a minute. "Maya's footwork in the back is getting noticeably better — the work we did last month is paying off. She's still hesitant on long switches; want to set up a small-sided game next week that forces them." Transcript lands on Maya's page.
The agent can summarize at evaluation time: "For Maya, summarize the last six weeks of notes — what's improved, what's still a focus, what should I tell her parents at the end-of-season meeting?" Comes back with a clean summary you'd otherwise spend an hour rebuilding from memory.
For the broader per-person tracking shape — same mechanic, different content — the How Account Managers Keep Client Context From Slipping approach applies; coaches and account managers both run page-per-person.
Parents and communications — the part most coaches dread
Parent communication is its own category. The page captures the running thread with each parent (when relevant), the team-wide communications you've sent, the things you've committed to address.
For the email-from-Maya's-mom that arrived at 10 p.m. on Friday — "why isn't Maya playing more in the midfield?" — drop the email on Maya's page or on a Parents/comms page. The agent can help draft the response: "Draft a reply to Maya's mom about midfield playing time. Use my notes on Maya's positional fit and the conversation we had with her at the start of the season — keep the tone warm and direct, not defensive." You edit and send.
Across the season, the agent can summarize: "What are the recurring themes in parent communications this season?" Useful for the team meeting where you address things that keep coming up.
Logistics — the field permits, the rosters, the league emails
Logistics holds the boring-but-essential stuff. Field permits, league contacts, the official roster, registration deadlines, tournament dates, equipment inventory, the league's rule clarifications.
For league rules and schedules, drop the PDFs. The agent reads them: "What did the league say about substitutions in the last rules update?" Comes back with the answer. Same for tournament rules, which always vary slightly.
For the running schedule, an inline database with date, opponent, location, time, and field works. The agent can pull the next month: "What games and practices do I have in May, with locations?" Useful when you're texting an assistant coach who can't remember.
A starter shape for week one of the season
A small but underrated page is Reflections. End of season, walk around for ten minutes, talk into the recorder. What worked this season. What didn't. What you want to do differently next season. What you learned about coaching that you didn't know before. Across multiple seasons, the agent can pull patterns: "Looking at end-of-season reflections from the last three seasons, what are the recurring lessons?" Most coaches improve by repetition; the vault makes the lessons compounding instead of episodic. (For the broader long-arc personal-archive shape, see Turn Casual Captures Into a Searchable Life Archive.)
If you're moving from notebooks and group chats to a vault, this is what we'd suggest:
- [Season name] — top-level parent
- Roster — inline database with player info
- Practice plans — page tree, one child per practice
- Game plans — page tree, one child per game
- Scouting — page tree, one child per opponent
- Players — page tree, one child per kid
- Parents/comms — running notes per parent or family
- Logistics — schedule database + permits/rules
That's it. Nothing template-perfect. The vault grows with the season.
The point isn't to turn coaching into an admin job. It's that the small amount of structure means the next practice is easier to plan, the next game is easier to prep for, and the conversations with parents and players are grounded in actual notes instead of memory.
Try Docapybara free — start with the Practice plans page and the Players page tree, and the next time you're driving to practice, the plan will be in one place.