Set Up a Recurring Weekly Check-In Reminder in Slack
How do I set up a recurring weekly check-in reminder for a Slack channel?
In the channel, send /remind #team-checkins to post your weekly check-in in the thread every Monday at 10:00 AM. Slack then posts that text to the channel every Monday. Keep the reply template in the channel so people answer in the same format. Channel reminders repeat by day, not by hour, and cannot be edited, only deleted and recreated.
A weekly async check-in in Slack needs two pieces: a channel reminder that repeats on a fixed day, and a reply template people copy so every answer has the same shape. The reminder comes from the built-in /remind command. Slack’s reminder article names no plan restriction for it, unlike Workflow Builder, which is paid-only. The template is plain text you keep in the channel. Nothing here needs an app, a bot token or a paid plan.
Which /remind command posts a weekly check-in to a channel?
Slack’s Set a reminder article gives the channel format as /remind [#channel] [what] [when]. Its own example is /remind #marketing-team to submit expenses every Thursday. When the time comes, Slack sends a message to the channel with the reminder description.
For a weekly check-in, the command looks like this:
/remind #team-checkins to post your weekly check-in in the thread under this message (template is pinned) every Monday at 10:00 AM
To set it up:
- Open the channel where the check-ins should happen. Slack’s steps start from the message field, and on mobile they say to start from a channel or DM.
- Type
/remindand pick it from the shortcuts menu, or keep typing the full command. - Fill in the channel, the description and the schedule, then send. Sending the message is what schedules the reminder.
- Type
/remind listin the same channel and send it. Slack shows a message only you can see, listing the channel reminders you can delete. If your new reminder is in that list, it is scheduled.
A few rules from the same article shape how you write the command. Reminders repeat by the day, such as every Monday, but not in time increments, such as every hour. Slack recommends American English date and time formats, so write 10:00 AM rather than 10h00 or 10.00. If you name a day but no time, the reminder arrives at 9 a.m. in your time zone, or at a different default if you changed it in Preferences. Guests cannot create channel reminders, so a full member has to set this up.
Keep the description short. It is one line in a channel, read by people who are skimming. The template does the real work, and it lives in its own message.
What should each person post when the reminder fires?
Each person replies in the thread under that week’s reminder, using the same five lines. A fixed template makes answers fast to write and fast to scan. It also makes it obvious when someone is blocked, because the blocked line is always in the same place.
Post this template once in the channel and pin it, or put it in the channel canvas. Then the reminder text can point to it.
Weekly check-in - week of [Monday's date]
Done last week:
- [one to three outcomes, not activities]
Planned this week:
- [one to three outcomes, with a day if it matters]
Blocked or waiting on:
- [what, and who can unblock it] (write "Nothing" if clear)
Need a decision from:
- [name and the decision, with a date] (write "Nothing" if clear)
Out of office this week:
- [days and hours, in your time zone] (write "None" if not)
A filled-in reply from a sample team member looks like this:
Weekly check-in - week of 2026-11-16
Done last week:
- Sent the Q4 supplier price list to Avery Example for sign-off
Planned this week:
- Close the October expense report by Wednesday
Blocked or waiting on:
- Card statement for October; Morgan Sample can request it
Need a decision from:
- Avery Example: approve the new courier contract by Friday
Out of office this week:
- Thursday afternoon, 1:00-5:00 PM London time
The rules that make this work:
- Reply in the thread, not the channel. One thread per week keeps the channel readable and gives each week its own record.
- Outcomes, not activities. “Closed the October expense report” tells the team something. “Worked on expenses” does not.
- Write “Nothing” instead of deleting a line. A missing blocked line is ambiguous. “Nothing” is not.
- Name the person who can unblock you. That turns the check-in into something the owner can act on today.
- Set a reply-by time in the reminder text if you need answers before a meeting, for example “by 2:00 PM”.
If decisions keep showing up in the “Need a decision from” line, they probably need a proper home with a deadline. The guide on setting up an async decision log with an explicit response deadline covers that.
Reminder phrasings and what Slack does with each one
These lines use the format and rules in Slack’s help article. The table describes the behavior that article documents. It does not cover every phrase Slack’s parser accepts, so after any change, run /remind list and check that the reminder appears.
| You type | What Slack does |
|---|---|
/remind #team-checkins to post your weekly check-in every Monday at 10:00 AM |
Posts the text to #team-checkins every Monday at 10:00 AM |
/remind #team-checkins to post your weekly check-in every Monday |
Posts every Monday at your default reminder time, 9 a.m. in your time zone unless you changed it |
/remind #team-checkins to post your end-of-week wrap-up every Friday at 3:00 PM |
Adds a second, separate weekly reminder for Fridays |
/remind #team-checkins to post your check-in tomorrow at 10:00 AM |
Posts once, the next day, and does not repeat |
/remind #team-checkins to post an update every hour |
Not supported; channel reminders repeat by day, not by time increment |
/remind list (sent in the channel) |
Shows only you a list of the channel reminders you can delete, each with a Delete option |
Two practical notes. First, Slack’s article describes reminder times in terms of the person setting them (“your time zone”). For a team spread across time zones, pick the hour that works for most people and state the time zone in the reminder text so nobody has to guess. Second, if you want both a Monday prompt and a Friday wrap-up, they are two separate reminders. Each one is listed and deleted on its own.
How do you change, pause, or remove a channel reminder?
You cannot edit a channel reminder. Slack’s article says to delete it and create it again. That applies to every change, including a new time, a new day or a typo in the text.
To replace the weekly check-in reminder:
- In the channel where the reminder posts, type
/remind listand send it. - Find the check-in reminder in the private list and select Delete.
- Send the corrected
/remindcommand. - Run
/remind listagain to confirm there is exactly one check-in reminder.
There is no pause option in the article, so a holiday week means deleting the reminder and setting it again when the team is back. For a single skipped week, it is simpler to post “No check-in this week” under that week’s reminder than to delete and recreate it.
Keep the command you used in the channel canvas next to the template. Since you cannot edit the reminder, having the exact text saved means the next change is a copy, a small edit and a paste, rather than a rewrite from memory.
When is a Workflow Builder scheduled workflow the better fit?
Slack’s reminder article itself says channel reminders work best for simple team reminders. For more complex messages, it recommends a workflow built from the scheduled message template, or a Slackbot task.
Check your plan before you plan around Workflow Builder. Slack’s Guide to Slack Workflow Builder lists the feature as available on paid plans. By default, full members can create workflows, and members and guests can use them. A workspace on the free plan should stay with /remind.
On a paid plan, the workflow template article describes the steps. From the desktop app, open Agents & tools in the sidebar (Slack notes it may show as Tools instead), go to Workflows, select Templates, choose a template and click Set Up. Then fill in the highlighted inputs and publish. The Workflow Builder guide also says workflows built to start on a schedule start automatically.
Consider a workflow when:
- The check-in prompt needs formatting or more text than a one-line reminder carries comfortably.
- Several people should be able to manage the schedule. A published workflow can have workflow managers, while a channel reminder has to be deleted and recreated.
- You want to collect answers in a form instead of a thread.
For a team that only needs “post your check-in, here is the template”, the /remind command is enough and has fewer moving parts.
Where a weekly reminder falls short
A reminder only prompts. It does not chase people who skip a week, and it does not summarize the thread. Someone still has to read the replies, follow up on blocked lines and carry decisions somewhere they will be tracked.
Watch for these limits:
- Nobody owns the thread. Name one person, usually the team lead or office manager, who reads every reply by an agreed time and follows up on each blocker.
- Status lives in two places. If the team already tracks work in a spreadsheet, a Slack thread duplicates it. Pulling the updates into one written digest may suit you better, as in turning Google Sheets status updates into an async weekly digest.
- Notion-based teams. If the weekly record should live in a document rather than a channel, see automating a weekly report page in Notion for remote teams.
- Sensitive content. Anyone in the channel reads every reply. Keep performance or personal issues out of a shared check-in thread.
- Daily rather than weekly. If the real need is a daily list of stuck work, a scheduled script fits better than a reminder. The guide on posting a daily blocked-tasks summary from Google Sheets to Slack shows one approach.
For more routines like this one, browse the remote operations guides.