# How to run a 21-day community challenge that people finish (template inside)

> A practical guide to running a 21-day challenge in your community: one outcome, 10–20 minute daily tasks, check-ins and proof, streaks, the day 8–12 dip, reminders, rewarding finishers and pricing a paid challenge. Full 21-day plan template included.

Published 2026-10-16 · updated 2026-10-16 · by Renu Rawat the Founder of prolaud.com · 20 min read
Source: https://prolaud.com/blog/how-to-run-a-community-challenge

Picture the same drawing challenge run twice. Same teacher, same audience, twenty-one days, one sketch a day. In the first run, each day's task takes most of an evening, check-ins go into a group chat where they scroll out of sight within the hour, and nothing changes in the second week. By day nine the chat is quiet and the teacher is posting to nobody. In the second run, each task takes fifteen minutes, every check-in lands in one place where people reply and cheer, and there is a short live session on day ten. The subject is identical. The design is what decides how many people reach day 21.

This guide is that design, step by step, for teachers, coaches and course creators running a challenge inside their own community. It works for a skill (sketching, speaking, coding, an instrument), a habit (daily practice, revision, movement) or a project (a portfolio, a chapter, a recorded talk). The complete 21-day plan template sits in the middle; copy it and swap in your subject. Where a tool helps with a step, we say how Prolaud does it, but every step works with whatever you already use.

## Step 1: Choose one outcome people can show

The most common mistake is promising a transformation. “Become a confident speaker in 21 days” is vague, huge and impossible to check. “Record a two-minute talk on camera, without notes, by day 21” is small, specific and visible. A good challenge outcome passes three tests: a member can show it (a photo, a recording, a page, a number), they can compare it with where they started, and it is reachable in 21 short sessions by someone at the level you are inviting.

Write the outcome as one sentence and put it at the top of everything: the sign-up page, the welcome post, the first day's task and the certificate. When people wobble in week two, that sentence is what you point back to. If you find yourself needing two sentences, you have two challenges; run the second one next month.

**Swap the vague promise for something a member can post on day 21 and hold up against day 1.**

| Subject | Vague promise | Outcome people can show |
| --- | --- | --- |
| Sketching | Get better at drawing | One finished drawing of an object you choose, posted next to your day 1 sketch |
| Speaking | Speak with confidence | A two-minute talk on camera, without notes |
| Language learning | Become fluent | A one-minute voice note describing your day, only in the new language |
| Writing | Write a book | A finished 3,000-word chapter |
| Exam prep | Master algebra | Ten past-paper questions solved in one timed sitting |
| Music | Learn guitar | One song played start to finish, recorded |

## Step 2: Design the daily tasks

A daily task should take 10 to 20 minutes and end in something postable. If it needs an hour, people will postpone it to the weekend, then skip it, then quietly leave. Small tasks are not a lower standard: twenty-one small reps add up to more practice than three ambitious evenings that never happen. Keep an optional “stretch” line on harder days for keen members who want more, so you never have to choose between the beginner and the enthusiast.

Write every day in the same three parts, so members learn the shape and stop having to think about it:

1. Why — one sentence on what today builds and why it matters for the outcome.
2. Do — one clear instruction with a time limit. Not a list of options; one thing.
3. Post — exactly what the check-in should be: a photo of the page, a link to the recording, or one line about what was hard.

> Day 6 — Shadows. Light is what makes a drawing feel solid. Put one object from your kitchen under a single lamp and draw it with its shadow, 15 minutes. Post a photo and one word for how it went.

### The rhythm: learn, practice, share

A good plan alternates three kinds of day. Learn days introduce one idea, through a short lesson, a demonstration or a worked example. Practice days repeat that idea with a small variation, which is where the skill actually grows. Share days ask members to show their work to the group, compare it with an earlier day, or ask a question in public. A fourth kind, the catch-up day, has no new content at all: its task is to finish one day you missed or redo one you rushed.

The rhythm matters because each kind of day does a different job. Learn days give people something new, which keeps the challenge from feeling like a chore. Practice days produce the visible improvement that keeps them going. Share days fill the community with work, which is what pulls the quieter members back in. Catch-up days stop one missed day from turning into a missed week.

## The complete 21-day plan template

Here is the full plan, day by day. The example tasks are for a sketching challenge, with the same day adapted for a speaking challenge alongside, so you can see how the structure carries over to any skill. Keep the task types and their order; replace the examples with your subject.

*Three weeks, four kinds of day. Week 2 carries the lightest tasks and two share or catch-up days, because that is where people drift.*

**Swap the example tasks for your subject. Keep the order of the task types and keep week 2 light.**

| Day | Task type | Example task: sketching | Same day: speaking |
| --- | --- | --- | --- |
| 1 | Share (start line) | Draw a mug from your table in 10 minutes, no erasing. Post it with one line on why you joined. | Record 60 seconds introducing yourself. Post the link and why you joined. |
| 2 | Learn | Watch a short lesson on continuous line. Draw three household objects without lifting the pen. | Learn three ways to open a talk. Record a 30-second opening using one. |
| 3 | Practice | Five continuous-line drawings of your hand, two minutes each. | Record the same opening three times; post the best one. |
| 4 | Practice | Draw one object from three angles. | Tell a 60-second story about your morning using a strong opening. |
| 5 | Share (first milestone) | Redraw your day 1 mug. Post both side by side. | Re-record your day 1 introduction. Post both links. |
| 6 | Learn | Lesson on light and shadow. Draw one object under a single lamp. | Lesson on pausing. Record 60 seconds with three deliberate pauses. |
| 7 | Catch-up | Finish a missed day, or redo the one you rushed. | Finish a missed day, or re-record the one you rushed. |
| 8 | Learn (short) | Five-minute lesson on texture. Sketch one rough surface. | Five-minute lesson on filler words. Record 30 seconds without any. |
| 9 | Practice (short) | Ten minutes: three quick texture studies. | Ten minutes: answer one question aloud in 45 seconds, recorded. |
| 10 | Share | Join the live session or post your favorite sketch so far with a question for the group. | Join the live session or post your best clip so far and ask for one tip. |
| 11 | Practice (tiny win) | One five-minute sketch of anything in front of you. Done counts. | One 30-second voice note on your favorite food. Done counts. |
| 12 | Catch-up | Catch up on one day, or redraw your weakest sketch. | Catch up on one day, or re-record your weakest clip. |
| 13 | Learn | Lesson on simple perspective. Draw a corner of your room. | Lesson on structure: point, example, point. Record 60 seconds using it. |
| 14 | Share (second milestone) | Draw the day 1 mug a third time. Post all three. | Re-record your introduction a third time. Post all three. |
| 15 | Learn | Lesson on combining line, shadow and texture in one drawing. | Lesson on ending a talk. Record an ending for your day 13 clip. |
| 16 | Practice | Draw one object using all three techniques. | Record a full 90-second talk with an opening, structure and ending. |
| 17 | Practice | Your choice of subject, 20 minutes. | Your choice of topic, 90 seconds. |
| 18 | Practice (stretch) | Draw a small scene with two objects and a shadow. | Record two minutes with notes, on a topic you care about. |
| 19 | Learn | Plan your final piece: choose the subject and do a quick thumbnail. | Plan your final talk: three points on a single card. |
| 20 | Practice | Make your final drawing. | Rehearse the final talk twice; record the second take. |
| 21 | Share (finish line) | Post your final drawing next to day 1, with what changed. | Post your two-minute talk without notes, next to day 1. |

> **Start from the template in Prolaud:** In Prolaud's Challenges builder, choose Start from a plan → 21 days and type one word for what members do each day (sketch, speak, write). Every day is written for you in this kind of rhythm, and you can change any of them before you start. See Run a challenge in your community (/help/community-challenges).

If you already teach a course on the subject, you may not need to write tasks at all. Prolaud can build a challenge from a course, one day per lesson: each day links its lesson, and finishing the lesson checks the student in for that day. It is a straightforward way to turn a self-paced course that people start and abandon into one they work through together, on the same days, with classmates watching.

## Step 3: Decide what counts as a check-in

The check-in is the engine of the whole challenge. It is how a member tells you they did the work, how they see their own progress, and how everyone else sees that the challenge is alive. Decide before day one exactly what counts, and say it in the welcome post.

- A photo of the page, the plate, the whiteboard or the screen. Best for anything physical, and the most motivating for others to see.
- A link to a recording, a document or a piece of code. Best for speaking, music, writing and anything digital.
- A few words about what they did and what was hard. Best for habits where the work itself is private, like a morning walk or a revision session.

Ask for one check-in a day, in one place. Two things make check-ins work far better than a stream of messages. First, they should be visible to classmates, so the community fills with people doing the work and each check-in can be cheered. Second, each one should be answered — a reaction, a short reply, or a spotlight on the best few. A check-in nobody responds to tells the member that nobody is watching, and people stop doing things nobody is watching.

![A student's phone showing the challenge card with today's task and a Check in button](https://prolaud.com/help/community-challenges/02-student-challenge.png)

*On a phone: today's task, the days so far, and Check in.*

In Prolaud, the challenge card sits at the top of the community with today's task and a Check in button. A check-in is a photo, a link or a few words, and it also appears as a post on the community wall (/help/community-wall), so classmates can cheer it. One check-in a day is allowed; a second the same day is refused, so the count means what it says.

### When proof matters

For most challenges, trust is fine: a member who posts “done” without doing the work is mostly cheating themselves. But when finishing earns something real, such as a certificate, a discount on your next course or a place in a selective group, ask for proof you can check. Make the proof specific (“a photo of today's page with the date written in the corner”) and review it each day. In Prolaud you can set check-ins to need approval; they wait for you, or a moderator, to approve or decline, and XP (/help/xp-levels-rewards) counts once a check-in is approved.

## Step 4: Streaks, and why missed days happen

A streak — the number of days in a row someone has checked in — is a simple, powerful motivator. Seeing “Day 9” next to your name makes skipping day 10 feel like breaking something. Show it, celebrate round numbers, and let members see their own row of completed days.

But people miss days, and it is rarely about motivation. A child is sick, a shift runs late, the internet goes down, a holiday lands in the middle. If one missed day means failing the challenge, the member who misses day 6 has no reason to show up on day 7, and you lose them for the rest of the run. Plan for missed days instead of punishing them:

- Let missed days be done later. A member who misses Tuesday can still do Tuesday's task on Thursday. The streak resets, but the day counts toward finishing.
- Set the finish rule below the full length. For example, finishing means 18 of 21 days checked in. One bad day no longer ends the challenge for anyone.
- Build in catch-up days. Days 7 and 12 in the template exist for exactly this.
- Talk about it in advance. In the welcome post, say plainly that missing a day is normal and the only rule is to come back the next day.

Prolaud has both of these as settings: Missed days can be done later, and a number of days needed to finish. A streak still counts days in a row, so the people who never miss a day get their recognition, while everyone else still has a real path to the finish line.

## Step 5: Plan for the mid-challenge dip (days 8–12)

*An illustration of the pattern to plan for, not measured data: energy runs high at the start, sags in the second week, and picks up as the finish line comes into view.*

Every multi-week challenge has a stretch where the novelty has worn off and the finish line is still far away. In a 21-day challenge it tends to arrive somewhere around days 8 to 12. The first-week excitement has gone, the tasks have started to feel like work, and real life has had a week to get in the way. You will see it on your progress grid as rows of ticks that start to break up. This is where most challenges are won or lost, so plan it before day one rather than reacting on day ten.

- Make week 2 lighter, not harder. Shorter tasks on days 8, 9 and 11, and a “done counts” tiny win. Save the stretch tasks for week 3, when the finish line pulls people through.
- Hold a live session around day 10. Answer questions, show your own work in progress, and celebrate how far people have come. It gives the middle of the challenge an event worth showing up for.
- Make progress visible. Day 14 in the template asks members to redo day 1. A post comparing a few members' day 1 and day 9 work does more than any pep talk.
- Reach out to the quiet ones. Anyone who has not checked in for two days gets a short, kind message: “Today's one is quick, ten minutes. Come back and do it with us.” Not guilt; an easy way back in.
- Spotlight people, not just work. A “member of the week” post on day 10 or 11 reminds everyone that real people are still in this.

![The teacher's progress grid: members down the side, days across, ticks for check-ins, and a Nudge button](https://prolaud.com/help/community-challenges/04-teacher-grid.png)

*The progress grid: every member, every day. Nudge reaches everyone who has not checked in today.*

Spotting who is drifting is much easier when you can see everyone at once. Prolaud's progress grid lists every member down the side and every day across, with a tick for each check-in. The gaps are obvious, and Nudge sends a reminder to everyone who has not checked in today in one click, so you can spend your time on the personal messages that need your own words.

## Step 6: Reminders without nagging

Reminders keep the challenge in people's day, but too many turn into noise they learn to ignore — or a reason to unsubscribe. A simple pattern works for most challenges:

1. Morning: the task. One message with today's task, early enough to plan around. This is the one reminder everyone should get.
2. Evening: a nudge, only if needed. One reminder for people who have not checked in yet. Anyone who already checked in should hear nothing.
3. Email: rarely. A daily email works for a five- or seven-day challenge. For 21 days, rely on notifications and keep email for the welcome, the halfway point and the finish.

Write reminders the way you would talk to a student in the hallway: short, warm, and specific to the day. “Day 9: three quick texture studies, ten minutes. Post them before bed.” is better than “Don't forget to complete today's challenge!” In Prolaud, members get the day's task as a notification each morning and a reminder in the evening if they have not checked in; a daily email is an option you turn on, best kept for short challenges.

## Step 7: Recognize finishers

People finish for something they can show. The finish line should feel like an event, not a quiet end to the notifications. Give every finisher at least one of these, and announce them on day 1 so people know what they are working toward:

- A certificate with their name, the challenge and the date — something they can share on a profile or send to family. In Prolaud, a certificate is issued automatically when someone meets the finish rule, with a public verify link anyone can open.
- A wall post celebrating the finishers by name, ideally with each person's day 21 work next to their day 1. It is the most persuasive thing you can show the people thinking about joining the next round.
- A badge or XP that stays on their profile in the community. Prolaud gives XP for each check-in and for finishing, and the challenge has its own leaderboard; see XP, levels and rewards (/help/xp-levels-rewards).

Recognize the near-finishers too. Someone who checked in on 16 of 21 days did a lot of work. A short note — “You did sixteen days; the next round starts on the 1st, and your progress carries into it” — keeps them in your community instead of feeling like they failed.

## Step 8: Price a paid challenge as an entry product

A challenge can be free, or it can be a product in its own right. A free five- or seven-day challenge is a strong way to introduce your teaching: people experience how you teach, get a small win, and meet your community. A paid 21-day challenge works well as an entry product, the first thing someone buys from you before your full course or coaching program.

When you price a paid challenge, three things help. Price it well below your main course, so it is an easy first yes rather than a big decision. Include something a free challenge cannot offer, such as live sessions, feedback on a few check-ins, or a smaller group where you know everyone's name. And keep your first paid round small enough that you can answer every check-in yourself; the results from that round are what you will show the next one. Look at what others in your field charge for something similar, start toward the lower end, and raise the price once you have finishers' work to show.

Then plan the step after. The last day of the challenge is when finishers are most motivated and most convinced they can do the work. Put your next course or program in front of them that day, with a clear reason it continues what they just started. In Prolaud you can sell a challenge on its own page through a store product, so buyers join the community and the challenge together, and On the last day, offer puts your next course in front of everyone who finished. Challenges come with every plan.

## Step 9: Run it again, better

Your first run is a draft. Before you plan the second, look at three simple counts: how many people checked in on day 1, how many on day 10, and how many finished. A big drop between day 1 and day 10 usually means the early tasks were too long or too vague. A big drop between day 10 and day 21 means the dip plan needs work. Write the three numbers down each round, so you can tell whether a change helped instead of guessing.

Then ask finishers one question: “What almost made you quit?” The answers tell you exactly which days to rewrite. Change those days, keep everything that worked, and run it again. A simple pattern is to run the same challenge on a regular cycle — once a quarter, or at the start of every term — with past finishers invited back as helpers who answer questions and cheer check-ins. Their day 21 work becomes the best promotion for the next round.

## Common mistakes, and what to do instead

- Tasks that are too big. If a task takes an hour, halve it and add an optional stretch.
- Silence after check-ins. Plan time each day to react and reply, or share the job with two or three keen members as moderators.
- Changing the plan mid-way. Write every day before day one and stick to it; members plan their days around yours.
- No “before” on day 1. Without it, nobody can see how far they have come on day 21.
- Treating a missed day as failure. Let days be done later and set the finish rule below the full length.
- Running it in a group chat. Check-ins disappear in the scroll and nobody can see who is keeping up. Use chat for reminders, and the community for the work.
- Ending with nothing next. Have the next step ready before the challenge starts.

## Checklist before you launch

- One outcome, in one sentence, that members can show on day 21.
- All 21 days written, each with why, do and post.
- A clear rule for what counts as a check-in, and whether it needs approval.
- A finish rule, and whether missed days can be done later.
- A dip plan: lighter week 2 tasks, a catch-up day, a live session around day 10, and time set aside for personal messages.
- One morning message and one evening nudge, and no more.
- Finisher rewards ready: certificate, wall post, badge, and the next-step offer.

For the wider picture of keeping students engaged between challenges, read how to build an online community for your students (/blog/build-online-community-for-students-india), or see what a community on Prolaud includes on the community feature page (/features/community).

[Start free](https://prolaud.com/signup) — Open a community, choose Start from a plan → 21 days, and invite your students. Challenges come with every plan.

## Frequently asked questions

### Should my challenge be 5, 7, 21 or 30 days?

Match the length to the job. Five days suits a free taster that shows your teaching and ends with an offer. Seven days covers one full week of a habit, with room for a live session in the middle. Twenty-one days is long enough for visible improvement in a skill, which makes it a good length for a paid challenge, but it needs a plan for the dip in week 2. Thirty days suits a sprint before an exam or a launch; treat it as four weekly blocks, each with its own small finish.

### Should a challenge be free or paid?

Both work, for different jobs. A free short challenge introduces your teaching to new people and leads into a paid course. A paid challenge is an entry product: price it well below your main course, include something the free version cannot (live sessions, feedback, a smaller group), and keep the first round small enough to answer everyone. One simple setup is a free five-day challenge that leads into a paid 21-day one.

### What if nobody checks in?

Start by checking the first few days: tasks that take too long, or a check-in that is unclear, stop people before they begin. Then make the first check-in effortless (a photo and one line), check in yourself on day 1 so the space is not empty, reply to every check-in within the day, and personally invite a handful of keen students to go first. A visible handful of early check-ins usually gives everyone else permission to post.

### What is the difference between a habit and a challenge?

A challenge has a finish line: a fixed number of days, an outcome and a celebration at the end. A habit has no end: members check in every day or every week for as long as they keep it up, and what they see is their history rather than a countdown. Run a challenge to build a skill or start something; run a habit for ongoing practice afterward. In Prolaud you can choose A habit (no end), and members see a heatmap of their days.

### Does it take 21 days to form a habit?

There is no single magic number of days for a habit; it varies by person and by habit. Twenty-one days is a practical length for a challenge rather than a scientific threshold: long enough for members to see real improvement, short enough to commit to. Present it as a strong start, then invite finishers to keep going, for example in an open-ended habit.

### How do I keep people going through days 8 to 12?

Plan the dip before day one. Make the week 2 tasks shorter, add a catch-up day, hold a live session around day 10, ask members to redo their day 1 task so progress is visible, and send a short, kind message to anyone who has not checked in for two days. Save your hardest tasks for week 3, when the finish line pulls people through.

### What should a check-in include?

Proof in a fixed format, posted in the same place every day: a photo of the work, a link to a recording or document, or a few words about what they did and what was hard. One check-in a day is enough. When finishing earns something real, ask for specific proof and review it before it counts.

### Can I turn an existing course into a challenge?

Yes. Treat each lesson as one day, add a short practice task and a check-in, and have the group work through it together on the same dates. In Prolaud you can build a challenge from a course with one day per lesson, and finishing the lesson counts as that day's check-in.