How to run a seven-day challenge in Skool

To run a seven-day challenge in Skool, define one deliverable and divide it into steps that can be completed independently. Explain the workload before inviting sign-ups and offer a catch-up option. Seven days describes this program's duration, not a promise of habit change or commercial results for participants.

Bound the result and participation conditions

Choose a small output, such as an interview guide or a portfolio page, and define what it must contain at the end. Publish prerequisites, an estimated workload based on your own rehearsal of the tasks, and review availability. Allow participation without exposing sensitive information. Prepare all materials before launch and decide who will handle questions if the owner is unavailable. If you use posts and Classroom, link each instruction to its specific resource; Skool describes both spaces in its official feature overview. 1

Example: seven steps toward a portfolio page

This hypothetical sequence ends with a reviewed draft, not a complete website. Each day adds one element and keeps the previous work. Publish instructions manually and collect the links in an index for late arrivals. You do not need to block progress until everyone finishes. If a task takes longer than expected, reduce its scope or turn the next day into a catch-up period. Preserving the number of posts matters less than allowing participants to complete work that makes sense.

1. Day 1: choose the project and intended reader.
2. Day 2: describe the original problem in three sentences.
3. Day 3: select one work sample you may publish.
4. Day 4: explain one decision and its rationale.
5. Day 5: arrange text and image in a draft.
6. Day 6: request a review focused on clarity.
7. Day 7: apply one improvement and save the final version.

Make catching up possible without penalties

Use a consistent submission format: a link or screenshot, the decision made, and one specific question. Review that day's criterion instead of correcting the entire project. Avoid public rankings based on speed because starting conditions differ. The following message makes returning possible without explaining an absence and reduces the need to chase participants individually. Do not promise unlimited reviews: specify what you can support and what will need a different format.

If you have fallen behind, continue from your last step. You do not need to explain your absence or repeat submissions. Share your draft in {location} with one question; we will review {criterion} by {date}.

Evaluate the output and workload

Count voluntary sign-ups, started drafts, and deliverables meeting the criteria. Note where people get stuck and how much review work each step creates. Do not confuse posting seven comments with achieving the result. Use this information to simplify the next edition without presenting observed changes as guarantees.