Life · July 2026 · 6 min read

Five Calendars, Two Kids, One Brain: How I Put AI in Charge of My Family's Sports Schedule

What I build

A Family Briefing Layer

This is what I build for you: a family briefing layer. A direct connection between the apps that run your family — the team app, the school app, the shared calendar — and an AI assistant that folds every change into one daily briefing, conflicts already flagged.

About fifteen minutes per app. We start with the noisiest one.

Talk to me about a Briefing Layer

Count your calendars

Do the math with me.

One kid plays club soccer — that's a team app with games, practices, tournaments that eat entire weekends, and a coach who posts schedule changes at 9 p.m. Another kid swims — different app, different login, meet warm-ups at hours that shouldn't legally exist. Then there's your work calendar, which is its own full-contact sport. Your partner's calendar, which you coordinate mostly through texts that say "wait, I thought YOU had Thursday." School calendars. Doctor appointments. Your own life — remember that one?

I counted mine: five calendars, three apps, two kids in two different sports, one consulting practice, and one household where two working parents pass the baton daily like a relay team that never gets to leave the track.

Here's what nobody says out loud: the games and the meets aren't the hard part. We love the games. What's not to like? You're hanging with other parents for long weekends, trauma bonding.

The hard part is the monitoring — the low-grade, always-on scanning across all of it so nothing collides and nothing slips. Checking the soccer app "just in case." Cross-referencing the swim meet against the client call. Watching the school app to make sure your kid didn't miss a project or a Hawaiian shirt day, heaven forbid. One time, I forgot to dress my youngest in his PJs for pajama day. Boy, did I get an earful when I picked him up at carpool about the fact that he was the "only kid" not in pajamas. Sorry, I digress.

The point is: being the one human router every schedule flows through. That's not parenting. That's a logistics job. And nobody hired anyone for it. Now you know why I'm always telling my kids "I don't work for you." But the truth is, maybe I do. I decided there was a better way.

So I hired someone. Sort of.

What I actually did

I connected TeamSnap — the app my son's soccer club runs on — directly to Claude, the AI assistant that already manages my calendar and email. Not a copy-paste arrangement. A real connection: Claude can see the team schedule, the roster, the coach's announcements, and the RSVP list, and it folds anything new into the morning briefing it writes me every day at 7 a.m. — right next to my client meetings, my husband's commitments, and everything else it already watches.

The morning the fall schedule drops — coaches always post it in August, usually while you're at work — I won't find out from a push notification I swipe away at a red light. It will be in my briefing, with the conflicts against work and the other kid's schedule already flagged. Tournament weekend collides with a client deadline? I find out in August, not the Thursday before.

Total setup time: about fifteen minutes. My part was three clicks and two copy-pastes. Claude did the technical work while I made tea.

The setup, step by step

What you need: a TeamSnap account — the free one your club already made you counts — and Claude's desktop app, which can install and run these connections for you. Ask Claude to set up "the TeamSnap MCP server" and it will walk you through exactly this.

Step 1 — Claude does the plumbing. I told Claude I wanted TeamSnap connected. It downloaded the open-source connector, checked the code for safety, and installed it. My job at this stage: nothing.

Step 2 — Tell TeamSnap it's allowed. TeamSnap has a free developer page (auth.teamsnap.com/oauth/applications — no paid plan needed) where you create an "application," which is just TeamSnap's word for a permission slip. Name it anything, paste in the callback address Claude gives you, and submit. My first name choice was taken — worth knowing app names are unique across all of TeamSnap, like usernames.

Step 3 — Copy two codes to Claude. TeamSnap shows you a Client ID and a Secret. Paste both into your Claude chat. (Blur these in any screenshot you share — treat them like a spare house key.)

Step 4 — Click Authorize, paste one last code. TeamSnap asks "allow this?", you say yes, and it hands over a short code. Mine appeared inside a Safari error page — which turned out to be the finish line wearing a disguise; the code was right there in the address bar. Pasted it to Claude. Done.

A note for the security-minded (I see you, fellow data people): the access Claude gets is read-scoped — it can see schedules and announcements, not spend money or change your account. The credentials live encrypted on my own computer, not in someone's cloud. And you can revoke the whole thing anytime with one click on that same TeamSnap page.

What it means for your household

Here's the reframe I want you to sit with, because it's the same one I use in coaching sessions.

You already know how to do this. You do it at work every day.

No working executive personally monitors every system in the company. You build an operating rhythm. You delegate the watching. You get a briefing, and you spend your attention on what only you can do: the decisions, and the showing up.

At home, we abandon all of that. We become the operating system. Soccer app, swim app, school app, two work calendars, two personal calendars — every schedule routes through one overloaded human, and then we wonder why Sunday-night planning feels like a second job and why "what are we doing this weekend?" is a loaded question.

One connection changed the physics in my house. The soccer schedule now reports to us — one briefing, conflicts pre-flagged, both parents reading from the same page instead of reconciling apps over breakfast. The "wait, I thought YOU had Thursday" texts are becoming extinct. And multiply the effect: the same fifteen-minute pattern works for the swim team's app, the school's communications, the family calendar itself. Each connection retires another app from your check-it-just-in-case rotation.

Handing the monitoring to an assistant that never sleeps doesn't make you less involved with your kids. It makes you more involved — because you're at the game instead of managing the game's metadata. You're deciding, not scanning.

That's not a productivity hack. For working parents holding a career, kids' schedules, a household, and often aging parents at the same time, that's recovered capacity. That's the meeting you're present for, the bleacher seat where you're actually watching, the eight minutes of quiet before anyone needs you.

The fix

Start with one app. The noisiest one. Give away the monitoring, keep the mothering. Want the checklist version of this setup, plus the other connections I've made — email triage, school comms, family calendar? It's part of what I build with coaching clients.

Book a conversation

Know a parent doing the rounds of five apps? Forward them this.