Most programs send weekly team updates. Most of those updates land somewhere between ignored and skimmed. The director writes the message, sends it Sunday night, and within a week is fielding the same questions that the message already answered. Communication is happening without actually working.
The instinct most directors have at this point is to write better messages. Add more information. Make them shorter. Make them prettier. None of that addresses the actual problem: families haven't been trained to look for program communication on a predictable cadence in a predictable place with a predictable structure. The weekly routine has to do that training work before it can do anything else.
What follows is a concrete weekly framework with four functional sections that families learn to expect. The real work is filling a known template with the week's specifics each week, sending it on a known schedule, and watching families develop the habit of checking the official channel because they've been conditioned to find what they need there.
Why the Routine Beats the Message
Before the template, a quick note on why predictability matters more than content quality. Families develop habits around information sources. A weekly communication that arrives at a different time each week, with a different structure, covering different topics in a different order, never becomes a habit. Families have to actively decide whether to engage with it each time, and they often won't.
A weekly communication that arrives at the same time, in the same place, with the same structure, becomes background scaffolding for the family's week. It stops being a decision and starts being a default. The family has already made space for it, because the routine is part of the texture of how they experience the program.
This is the foundation everything else in your communication system rests on. A solid weekly routine gives the rest of your communication infrastructure somewhere to anchor, while a sporadic one forces every other communication you send to fight for attention against a background of inconsistency.
The Four-Part Template
The template has four sections that each serve a different functional purpose. The sections should appear in the same order every week, with the same headers, in the same place in the message. Predictability of structure is more important than elegance of structure.
1: The Recap
The week opens with a brief look back at the previous week. What happened. What stood out. What the team accomplished or worked through. This section is short, usually two to four sentences, and it accomplishes two things at once.
The first is acknowledgment. Families know the program saw what happened the previous week. The tournament that wrapped on Sunday. The hard practice on Thursday. The team dinner on Saturday. A few sentences carry the signal that the program is paying attention to the same events families experienced.
The second is anchoring. By starting with something families already lived through, the message earns their attention for the rest of the content. That shared starting point makes the rest of the message land more easily.
The recap should not include analysis, criticism, or coaching commentary. Those belong in coach-to-family communication rather than in the weekly team update.
2: What's Ahead
The second section is the practical preview of the week ahead. This is usually the most operational part of the message and the part families come for. Practice times, locations, what to bring, weather considerations, special events, any schedule changes from the published calendar.
Format this section for scannability. Day-by-day, with the most essential information at the top of each day's entry. Families should be able to find the answer to "what time is practice Tuesday and where" in three seconds without reading prose. Tables, bullets, or short stacked lines all work; what matters is that the information is visible at a glance rather than buried inside sentences.
The discipline in this section is to include only what's actually changing or noteworthy. The published calendar already exists. The weekly message references it but doesn't reproduce it. If Tuesday practice is at its normal time and place, the entry can be one line. If Thursday's practice has moved fields, that's where the detail goes.
3: The Development Note
The third section is the one most programs skip and the one that produces the most retention value when included consistently. This is a short note from the coach or director about what the team is working on developmentally that week.
Two or three sentences. What's the team focus this week. What skill, concept, or habit are they building. What does success look like. Treat this section as a thread that runs through the season, helping families understand what their kid is working on at any given moment and how the work fits into the larger arc.
The reason this section matters is that families who can articulate what their kid is working on feel invested in the season in a way that families who can't never do. The development note gives every family a shared narrative about what's happening on the field, even families who can't attend practices or watch games live. Over a season, this narrative compounds into a sense of forward motion that wins-and-losses reporting can never provide.
4: The Ask
The final section is a single specific ask. Something the program needs from families that week. RSVP for the team dinner. Confirmation of tournament travel plans. A volunteer slot to fill. A waiver to sign. A piece of equipment to bring.
The discipline here is one ask per week. Not three. Not five. Not a list of everything outstanding. One. Families will respond to a single clear ask at a meaningfully higher rate than they'll respond to a message that contains six asks competing for attention.
When there's nothing to ask, this section can be replaced with a single appreciation note. A team member's birthday. A parent who helped with logistics. A volunteer who covered a shift. This keeps the section in place structurally even when the program doesn't need anything operationally, which preserves the routine for the weeks when an ask matters.
How to Run the Routine
The template is the easier part. The harder part is running it consistently for a full season without it degrading into something the director cobbles together at 9pm on Sundays.
Same Day, Same Time, Same Channel
The routine has to land the same way every week. Sunday evening between 6 and 8pm is the most common slot because it positions the message at the moment when families are mentally preparing for the upcoming week. Whatever slot you choose, hold it. Drift between Tuesday one week and Sunday the next produces two disconnected messages rather than a routine.
The channel matters as much as the timing. The weekly message goes through the official platform every time, with no exceptions for "quick" updates that route through text or email. Families need to learn that one source has the weekly rhythm, and any drift in channel breaks the pattern.
Build the Template Once, Use It Every Week
The four-part structure becomes a literal template file you start from every week. Date at the top. The four section headers fixed. Empty fields below each one. The work becomes filling in the fields, which usually takes twenty to thirty minutes once the routine is in motion.
This matters operationally because the alternative is writing a weekly message from scratch every Sunday, which is the single most common reason weekly routines collapse mid-season. Directors get tired. Sundays get busy. The message gets skipped. Once it's skipped once, the routine is broken, and rebuilding the habit is harder than maintaining it would have been.
Source the Content Across the Week
The development note is the section most likely to feel hard to write on Sunday evening. The fix is to capture the content during the week rather than reaching for it at the moment of writing.
A short note from the coach after Tuesday's practice, captured in whatever way is easiest (a quick voice memo, a text to the team manager, a note in a shared doc), gives the writer of Sunday's message something concrete to work from. The coach knows what the team worked on this week; the director or team manager doesn't always. The handoff during the week takes the development note from a hard write to an easy one.
The same principle applies to the recap and the ask. Both can be captured progressively during the week rather than retrieved from memory on Sunday night.
Track the Open and Response Rates
A weekly routine that nobody reads functions more like a personal habit the director maintains alone than a communication system anyone else participates in. Most official communication platforms track open rates. Track them. Track whether they're climbing over the first six weeks of the season, which is what should happen as families learn the routine. Track whether response rates on the section four ask are above 60%, which is roughly the threshold above which the routine is working as intended.
If open rates aren't climbing or response rates are low, the issue is usually one of three things. Inconsistent timing breaks the pattern, overly long content makes families skim, and vague asks make families bypass them entirely. Each of these is fixable, but you can't fix what you don't track.
The Cumulative Effect
A weekly routine run well across an entire season changes the texture of the program in ways that compound. Families develop a habit of expecting the message. They learn the structure and start to find the sections they care about quickly. The development narrative builds week over week, giving families language for what their kid is working on and why. The ask gets answered because it's the only ask. And the official channel becomes the trusted source for everything else, because the weekly rhythm has trained families to look there first.
By the end of a season, directors who ran the routine consistently have communication infrastructure most programs spend years failing to build. The ones who skipped the work spend that same season answering the same questions in week twelve that they answered in week three, still wondering why their families don't engage with program communication.
The work lives in the routine more than the writing. Build the template, hold the schedule, run it for ten weeks, and the system starts running itself.
