How to Run a Book Club or Writing Group on Discord

A Discord book club or Discord writing group lives or dies on its weekly rhythm, not its channel list. Pick one clear format, publish a schedule people can plan around, and keep every meeting, thread, and feedback round predictable. If you still need to build the server itself, start with the guide to building a Discord server for writers and readers; this post covers what happens after it exists.

1. Choose one core format (book club, critique group, or writing sprints) and add the others only when members ask.
2. Set a reading or submission pace you can sustain, and post the whole schedule up front.
3. Give each chapter or submission its own thread, with spoiler rules that are easy to follow.
4. Use short, regular voice meetups, sprints, and check-ins, and enforce critique etiquette consistently.

Choose a format before you choose a schedule

Groups stall when they try to be everything at once. Decide what the group does most often, because that decides your calendar.

A reading-focused online book club needs shared pace above all. A critique group needs fairness above all, meaning everyone gives roughly as much feedback as they receive. Writing sprints on Discord need almost nothing except a start time and a room, which makes them the easiest format to add later. Start with one, run it for a month, then add a second format only if members ask for it.

Set a reading schedule and pace

For a book club, the schedule is the product. Before the first meeting, post the full plan in one pinned message: title, author, reading sections by date, and the day of each live discussion.

• Pick a pace for the slowest regular reader. One or two chapters, or roughly 50 pages, a week suits most casual clubs.
• Leave a catch-up week. Every four to six weeks, skip a section so people who fell behind can rejoin the conversation.
• Choose books by poll. Collect nominations in a thread, then use Discord's built-in poll: up to 10 answers, with a duration from one hour to one week. A week-long poll gives slow readers time to vote.
• Post times with timestamps. The Discord timestamp generator produces a time that shows in each member's own time zone, so nobody converts a meeting time by hand.

Discord timestamp generator

Treat the schedule as a promise. If the group keeps moving the date, regular members stop planning around it.

Give every chapter its own thread, with spoiler control

One thread per reading section keeps discussion findable and keeps spoilers from leaking into general chat. Discord threads let a topic grow in its own space without becoming a new channel, and they hide themselves after inactivity: the default is three days, with one hour, 24 hours, or seven days also available. For a weekly club, seven days is the setting that matches the rhythm.

Discord's Threads FAQ explains creating, closing, and reopening threads

A simple structure:

• A weekly "Chapters 4–6" thread, opened by the host on the day reading starts. Name it with the section, never "Discussion".
• A starter post with two or three open questions so the thread does not begin empty.
• A "caught up" rule: members who have not finished reading stay out of the thread, or post only under a spoiler tag.

For spoilers, use layers. Keep the main #book-club channel safe for general talk, turn on a Spoiler Channel (Edit Channel > Overview > Content Visibility) for ending-level discussion, and ask members to wrap small reveals in double bars like ||this||. Put one sentence about this in your pinned schedule so new members see it before they type a word.

Run voice meetups and Stage events

Text discussion fills the week; a live call gives the group its energy. Keep the meetup short and structured so people actually come back.

1. Create a Scheduled Event for the meetup. Discord events can take place in a voice channel, a Stage channel, or at an external location, and members who tap Interested get a notification when it starts.
2. Write the agenda in the description: for example, five minutes of check-in, thirty minutes on the section, ten minutes on next week's reading.
3. Use a normal voice channel for a small group where everyone speaks freely.
4. Switch to a Stage channel for a hosted reading, an author Q&A, or a larger club where a few people speak while the rest listen and raise a hand. Stage channels require a Community server.
5. Post the decisions afterwards: next book, next date, any homework.

Rotate the host. A club that depends on one organiser stops when that person gets busy.

Hold writing sprints and accountability check-ins

A sprint is a timed block where everyone writes at once. The most common shape is 10 minutes to share a goal, 25 to 45 minutes of quiet writing with mics muted, and 10 minutes to report back. Post the schedule in an event so it repeats on the same days, and have the host name the start and end times aloud.

Pair sprints with a light check-in thread. Each Monday, members post one goal for the week; each Friday, they reply with what they finished or what blocked them. Reward showing up rather than word count, so people who write 200 words feel as welcome as people who write 4,000.

Members who get stuck between sessions can use an AI book writer to outline a chapter or test a plot idea, then bring the draft back to the group for feedback. Whatever you allow, say so in the rules: some critique groups want every submitted page to be the member's own writing, while others only ask that AI-assisted work is labelled.

Set critique etiquette and feedback rules

Critique is where groups succeed or fall apart, so write the rules before the first submission. Adapt the Discord rules template and add these writing-specific points.

Discord rules template

• Critique the work, not the writer. Say what the page does for you as a reader, then suggest one change.
• Ask what feedback the author wants. Every submission names its type: big-picture, line edits, or "just tell me what you felt".
• Use a give-to-get rule. Members give feedback before they request a new critique, which stops lopsided exchanges.
• Set a size limit and a deadline. For example, 1,500 words per submission and feedback within seven days.
• Lead with what works. One genuine strength first makes the next comment easier to hear.
• Keep work private. Nobody copies, quotes, or shares another member's draft without permission.
• Authors respond last. Thank reviewers and ask follow-up questions; do not argue with feedback.

Assign roles and moderate lightly

A small team keeps the group running without turning it into an organisation.

• Host: runs the meetup and opens the weekly thread. Rotate it.
• Schedule keeper: posts timestamps, updates the pinned plan, and creates events.
• Critique coordinator: tracks who owes feedback and nudges gently.
• Moderator: removes spam and enforces the rules.

Give moderators the Manage Threads permission so they can lock a thread that has run its course or gone off the rails, and avoid handing out Administrator. Add slowmode only where it helps, such as a fast-moving sprint channel. When two members disagree about feedback, move the conversation to a private message or a moderator thread rather than letting it grow in public.

Use bots for scheduling, reminders, polls, and timers

You do not need many bots; you need the right small set.

• Events and scheduling: Discord's built-in Scheduled Events cover most clubs. Bots such as Apollo and Sesh handle RSVPs and recurring sessions if you want more, though some recurring-event features sit behind a paid plan.
• Reminders: a scheduled-message feature, such as the one in Sapphire, can post "Chapters 4–6 discussion is tomorrow" without a human remembering.
• Polls: Discord's built-in polls handle book votes and time-slot choices.
• Timers: for sprints, use any bot with a timer command, or let the host post the start and end time and call it aloud.
• Custom commands: an all-round bot such as Carl-bot can answer "when is the next meeting?" with a stored message.

Compare options in the guide to the best Discord bots before adding one, and check each bot's permissions on the invite screen.

Keep members active

Most groups lose people in the second month, when the novelty fades. A few habits slow that down.

• Welcome new members by name and point them to the pinned schedule.
• Keep the same days and times so the group becomes part of members' weeks.
• Celebrate small finishes: a completed chapter, a first submission, a returned critique.
• Ask one easy question in the weekly thread, such as "Best line you read this week?"
• Message absent members once. A friendly "we missed you, we are on chapter 7" brings back more people than a public reminder.

Grow the group on purpose

Grow only as fast as you can host. A book club works well with 8 to 20 active members; a critique group works best when every member can read every submission.

Invite people from places where readers and writers already gather: your own newsletter, a blog, a social profile, or friends with similar tastes. Post a short description of the format, the schedule, and what you expect from members. Run an open "trial week" before inviting people in permanently, and consider an application question for critique access so everyone arrives understanding the give-to-get rule. When the group outgrows one thread or call, split it by genre or time zone rather than making the meetup bigger.

Frequently asked questions

How many people should a Discord book club have?

Eight to twenty active members is a comfortable range. Fewer than six makes discussion thin when two people miss a week; more than twenty calls for several threads or a Stage event.

How often should a critique group meet?

Weekly or fortnightly works for most groups. A submission window, a feedback window, and one live call per cycle is enough; any more and members start to burn out.

Should writing sprints be public or private?

Sprints can stay open because nobody shares pages. Keep critique areas private or invite-only since members post unpublished drafts there.

What should I do when a member stops contributing?

Message them once, privately and kindly. If they are still unavailable after a cycle or two, release their critique slot so the group stays fair, and welcome them back whenever they return.