Most community owners do not have a workload problem. They have a shape problem. The work gets done in unpredictable bursts — three hours on a Sunday night because guilt kicked in, then nothing until the next guilt cycle — and the community feels it, because members can tell when you are around out of habit versus when you are around out of panic.
A routine fixes the shape. The total hours barely change. What changes is that the important-but-not-urgent things (welcoming, saving fading members, actually reviewing anything) stop being the ones that get dropped.
Here is a cadence that works for a community in the low hundreds of members. Scale the numbers, keep the shape.
What does a whole week of running my community look like?
A week of running a Skool community breaks into six small jobs on fixed days, none of them longer than forty-five minutes:
| Day | Job | Time box |
|---|---|---|
| Monday | Main post of the week + reply to everything | 45 min |
| Tuesday | Welcome new joiners, one at a time | 20 min |
| Wednesday | Reply sweep + show up somewhere outside your community | 30 min |
| Thursday | Second post, lighter format + reply | 40 min |
| Friday | DM batch: fading members and unanswered people | 45 min |
| Saturday | Nothing. Genuinely nothing. | 0 |
| Sunday | 30-minute review + plan next week's two posts | 30 min |
That is about three and a half hours. If you have more time, put it into replies, not into more posts. If you have less, cut Thursday first and Sunday last.
What should I post on Monday, and when do I welcome new members?
Monday carries the main post of the week, and Tuesday is for welcoming everyone who joined since last Tuesday, one message at a time.
Monday: the post that sets the week
One substantial post, published in the window your members are actually online rather than the window that suits you.
The format that reliably earns replies is a question with a constraint. Not "what are you working on?" — too open, people freeze. "What is the one thing you are stuck on this week?" gives them a slot to fill. A poll works for the same reason: the cost of participating is one tap.
Then, and this is the part that matters more than the post: reply to the first comment fast. Within the hour if you can. The first reply is a signal to everyone else that this thread is alive and that saying something will be acknowledged. A post with three comments and three owner replies outperforms a post with eight comments and silence from you.
Time box it. Forty-five minutes, then close the tab.
Tuesday: welcome people individually
Take everyone who joined since last Tuesday and message each of them personally.
Not a template. One line about them — what they said in their intro, what their profile suggests, why they might have joined — and one easy question. The goal is a reply, not a warm feeling.
This is the highest-leverage twenty minutes in the week, because the first fourteen days decide whether a member ever becomes a participant. A member who has had one real exchange with the owner behaves differently from one who received a broadcast.
If you get ten joiners a week, this is genuinely twenty minutes. If you get sixty, you need a system, and that is what DMing at scale properly covers — build the list, personalise per person, approve every draft, send them yourself.
How do I stop the middle of the week going quiet?
Midweek splits in two: Wednesday clears every unanswered comment and takes you into one community outside your own, and Thursday carries a second, deliberately lighter post.
Wednesday: reply sweep, then leave the building
Two halves.
First, the sweep. Go through every post from the past week and make sure nothing has an unanswered comment. Unanswered comments are quiet damage; the person who left one and got nothing back is measurably less likely to leave another. Check your mentions too — if someone tagged you three days ago and you missed it, fix that first.
Second, go be useful somewhere else. Pick one external Skool community where your members already spend time and leave one genuinely helpful comment. Not a pitch. Not a link. A comment that helps the person who posted.
This is the growth half of the week, and it is the half owners skip, because it does not feel like running your community. It is. Your members are in other rooms; showing up in those rooms is how new people find you, and it is also how you learn what your audience is talking about when you are not in the conversation.
Thursday: the lighter post
A second post, deliberately smaller. A win from a member, a shoutout to the people who commented on Monday, a short observation, a resource, a behind-the-scenes note.
The point of Thursday is rhythm. Two posts a week from you means members have a reason to check twice, and it means the feed does not go silent for six days between your appearances. Consistency beats size — a small post every Thursday is worth more than an essay every third week.
Recognition posts are underrated here. Naming the five people who showed up in Monday's thread costs you nothing and does more for participation than most content does, because it demonstrates in public that participating gets noticed.
Who should I message on a Friday, and how many?
Friday is one small batch of direct messages: forty-five minutes, twenty to twenty-five people, and every name on the list is there for a reason you can state out loud.
Who is on it:
- Fading members. People who were active a month ago and have gone quiet since. Not dormant members — those have already decided. Fading members are mid-decision, and a message that arrives while they are still deciding is the one that lands.
- People who asked something and never got a proper answer. You will find these in Wednesday's sweep.
- Members who are prolific in other Skool communities and silent in yours. These are not disengaged people. They have the posting habit; they just have not built it with you. Ask them what would make your room worth their time and take the answer seriously.
Rules for the batch:
- Every message names a specific reason the person is hearing from you. If you cannot state the reason, they should not be on the list.
- Twenty to twenty-five is the ceiling. That is not arbitrary — it is roughly the number of conversations one person can actually follow up on. There is no point starting sixty.
- Reply to replies within a day. Otherwise the batch was theatre.
If you use Skoolgrades for this, the send limits are 25 a day and 100 a month on Grow ($19/mo), and 25 a day and 500 a month on Pro ($99/mo). Every draft is reviewed and approved by you, and you click send for each one from the extension panel. Nothing dispatches on its own — which is exactly why it does not get you flagged and why the messages stay worth reading.
One constraint to plan around: you can only message people you already have a DM channel with.
Do I need to be in my community at the weekend?
Saturday is genuinely off, and Sunday asks for thirty minutes of review rather than a working day.
Saturday: off
Take the day. Communities do not need their owner present seven days a week, and an owner who is always on eventually becomes an owner who is gone.
Sunday: thirty minutes of review
Not an audit. An audit is twice a year and takes an afternoon — that is a separate job. This is thirty minutes with four questions.
- How many distinct members actually did something this week? Commented, replied, voted in a poll. Write the number down. Watch its direction over eight weeks, not week to week.
- Which post got the most comments, and why?
- Who joined, and did I message them?
- Who went quiet that I did not expect?
Then plan Monday's and Thursday's posts. Write the headline for each, not the full post. Ten minutes. If you keep running dry here, the fix is a standing content calendar rather than more Sunday willpower.
On the participation number: it counts comments, comment replies and poll votes, not page loads, so expect it to read lower than a visit-based engagement rate (here is why).
Do I need a tool to run this weekly routine?
You do not need a tool to run this routine, and for a community of eighty members you should just do every step by hand.
The parts that stop scaling first are Tuesday and Friday: knowing who joined and who is fading, and having something to say to each of them. Those are list-building and drafting problems, which is where Skoolgrades sits — a ranked stack of concrete moves rather than another dashboard, cohorts that refresh weekly, and DM drafts you approve and send yourself.
The Sunday review is the other one. Reports are included on every Skoolgrades plan: participation rate, retention lanes, joins, top posts, timing, and a peer benchmark computed on posts that have had 72 hours to mature so it does not swing with fresh content.
But the routine is the thing that works, not the tooling. Run the cadence for a month with a spreadsheet before you spend anything.