How to structure a 12-week coaching programme that actually finishes

Most 12-week programmes lose half their members by week five. This guide — built from what we see work across coaches, therapists, and team leads running programmes inside Bitir — explains the week-by-week structure that keeps a cohort together to the end.

The 12-week dropout curve — and where it bites

If you run enough 12-week programmes you will see the same curve every time. Members arrive full of intention. They attend week one. They do the first assignment. They attend week two. By the end of week four, about 15% have quietly disappeared. By week five or six, another 15–20% follow them. The remaining 60–70% make it to the end.

The second drop — between weeks four and six — is the one worth fighting for. It is the point where the initial excitement has worn off, the first quick wins have already happened, and the final outcome is still too far away to pull on. Without a deliberate structural intervention, a significant chunk of your cohort will silently quit during this window.

The structure below is designed around this.

Week 1: The contract, not the content

Week one should contain almost no content. It should contain a contract.

• A written group agreement posted as a manager note, covering confidentiality, tone, and what "showing up" means in this programme. Every member clicks an acknowledgement reaction.
• One group goal, set by you, that defines what success looks like at week twelve.
• One individual goal per member, written by the member in their own words, not prescribed by you.
• The weekly rhythm, explained explicitly: poll on Monday, assignment due Saturday, session midweek, recap by Sunday night.
• Nothing else.

If you give week one a dense content load, you set an expectation that every week will be that heavy, and members will start budgeting time against that expectation. They will then fail to meet it, feel bad, and disengage.

Weeks 2–5: The boring middle

The weeks from two to five should be deliberately identical. Same ritual, same day, same structure. If week two's poll has five questions, week five's poll has five questions. If week two's assignment is a one-page reflection, week five's assignment is a one-page reflection.

This sounds like bad programme design. It is actually the opposite. Predictability is how members budget their week. Variety is how they lose track.

Each week should have exactly three things, and nothing more:

1. A weekly check-in poll, posted the same day each week at the same time.
2. A weekly assignment with a clear deadline and a maximum time cost.
3. A weekly recap from you, posted within 24 hours of the live session.

The check-in poll is the most important of the three. It is the ritual that tells members "I am noticing you", even when they didn't come to session. Inside Bitir you can set this up as a recurring poll that fires automatically every Monday and stays open for 72 hours.

Week 6: The mid-programme re-engagement

This is the week where most programmes leak members. So this is the week that should look different from all the others.

Week six should contain:

• A half-way goal review. Every member looks at the individual goal they wrote in week one and answers three questions: are you still working toward this, has it changed, and what would you change if we reset now?
• A private reflection. Using Bitir's private-by-default member posts, each member writes a short note to you (not to the group) about what is working and what is not.
• A celebration of something small. Somebody in the group has done something worth noticing. Publicly celebrate it.

If you do this week well, your drop-out curve flattens for the second half.

Weeks 7–10: The same ritual, with higher stakes

Return to the weekly rhythm from weeks two to five, but start adding explicit references to the end of the programme. "This is week eight of twelve." "We have four weeks left." Members who lose track of where they are in a programme stop seeing the finish line.

Around week nine, start asking members what they plan to do after the programme ends. Not as a formal exercise, just as a question in the weekly recap. The members who answer this question are the members who will show up in week twelve.

Weeks 11 and 12: The celebration arc

The final two weeks should feel like a landing, not a cliff.

Week eleven is about consolidation. Ask every member to look back at their own check-ins from weeks one through ten and write one paragraph on what changed. This is also the week to publicly celebrate anyone who has completed every weekly assignment — Bitir's celebration feature works well here, because it is visible and it marks the moment for the whole group.

Week twelve is the closing session and the written farewell. Members write one final private reflection to you, and one public message to the group. You post a written farewell of your own and, critically, you explicitly close the group rather than letting it drift.

What to put in your weekly assignment

Assignments are the single highest-variance lever in a 12-week programme. A good assignment takes under 20 minutes, produces something the member can re-read later, and is close enough to real life that it is hard to fake.

We have a full write-up of the seven assignment patterns that reach above 80% completion: Assignment design for group coaching.

What to leave out

More content is almost never the answer. Things to specifically not do during a 12-week programme:

• Do not add a bonus week. It will become a mandatory week, and the programme will feel 13 weeks long, which is worse than 12.
• Do not add a second weekly assignment. One is enough.
• Do not change the check-in format partway through.
• Do not use a side channel (WhatsApp, email) for "urgent" updates. If it's not in Bitir it does not exist.

A real example

Dr. Amelia Richardson, a Bristol-based clinical psychologist, uses almost exactly this structure for her anxiety groups. Her 12-week drop-out rate fell from 31% to 14% after she adopted it. Read the full case study: Dr. Amelia Richardson — anxiety groups on Bitir.