Guides

A hare in a yellow cardigan looks at three winter landscapes and blank reply cards on a gallery wall.

How to Run a Discord Event Across Time Zones

If your members rarely have the same free evening, spread your Discord event across two windows. Give everyone time to add an entry, then start the feedback round once the submissions are in. Someone who posts near the deadline gets the same reply window as the first person through the door.

Here’s a worked plan for a winter screenshot exchange. Members share one scene from a game they already play, then respond to one other entry. The host matches people to posts after submissions close and checks that the quieter entries get a reply.

Choose a format that matches what members will do

For a small group that mainly exchanges reactions, one dedicated text channel is usually enough. For an exchange where every entry needs its own reply, use a forum post per entry if your server already has Community enabled. Each screenshot and its feedback stay together. Discord requires Community to create Forum Channels and supports guidelines and tags for organizing posts. Discord’s Forum Channels FAQ.

A plain text channel works without a forum. Ask people to send each entry as one message, then use Discord’s Reply action to respond to the assigned entry. When you publish the assignments, link to the original messages. Keep casual chat in the usual channel so people can scan the entries quickly.

Decide how much feedback you can cover before opening signups. In this example the host and a helper can each write up to four short backup replies, so the exchange starts with eight places. That leaves enough coverage if nobody completes their assignment. Use one signup message and have the host confirm places in order. If a place opens before submissions close, offer it to the next person only if they still have time to enter. If you want anyone to be able to post and you can’t cover every reply, call it an open gallery and invite optional comments. Give members the right expectation when they join.

Publish two time windows and one place to start

Choose a period that gives people more than one chance to log in. A Friday-to-Monday submission window includes a weekend and leaves a chance for people who can only check Discord on Monday. A second window gives members who enter late time to see the finished list. Tell them in advance when assignments will appear, including how much time the host needs to make them.

PhaseExample timing in UTCWhat happens
SubmissionsFriday, December 11, 2026 at 18:00 to Monday, December 14 at 18:00Each confirmed participant posts one entry. The host checks access and records its link
MatchingMonday, December 14 from 18:00 to 19:00The host makes the reply list from entries that arrived in time and links to each one
FeedbackMonday, December 14 at 19:00 to Thursday, December 17 at 19:00Participants leave one reply on their assigned entry. The helper checks in a day before closing
RecapFriday, December 18 at 18:00The host thanks contributors, shares entry links, and explains where any later discussion can continue

Put the format, calendar, and entry location in one announcement. Include an example such as “I took this on the way back from a quest. I like the reflection under the bridge. What detail did you notice first?” A text description can count as an entry if a member can’t attach a screenshot. Ask contributors to describe the main scene in a sentence so other members can join the discussion even if the image is hard to see.

You can show a deadline in each member’s local time with a Discord timestamp. For the example above, paste <t:1797271200:F> into your Discord announcement for the submission deadline and <t:1797534000:F> for the feedback deadline. Discord uses Unix seconds and displays the date and time according to the viewer’s locale and time zone. Use the codes as plain text in Discord, without backticks, and check the rendered dates before announcing. A UTC date and time in the announcement also gives members a stable reference. Discord’s message formatting reference.

Test the route as a participant

Have a regular member open the announcement from their phone, find the event space, post one sample entry, and reply to it from another member account. Test each action independently. A person may be able to open a channel yet have no permission to post, attach a file, or reply in a thread. Check the intended event roles and any overrides in that channel. Discord’s permissions guide.

For a forum, use its guidelines to show what belongs in the title and body. “Game name and scene” is enough for a title. A single event tag is useful if the forum serves several activities. Link directly to the entry posts when giving assignments, since inactive posts can move into Older Posts while feedback is still open. Discord’s Forum Channels FAQ.

If a member can’t get the screenshot uploaded, let them submit the description in the same place. If the event channel itself is hidden, fix the visibility issue before signups open. An invite to the server won’t establish that an ordinary member can use the intended event space. For help choosing between a forum and a thread in an existing channel, see Pinicon’s comparison of Discord forums and threads.

Assign replies after the submission window

Sort the eligible entries into a list, then assign each person the next entry on it. The last person replies to the first. With three entries, Ada replies to Ben, Ben replies to Cleo, and Cleo replies to Ada. Everyone has one job and each entry has one assigned reader. Use links in the assignment message so nobody has to infer which screenshot you mean.

Ask readers to mention one thing they noticed and, if the contributor invited it, ask a question about the scene. A person who wanted to share a quiet moment may welcome a specific observation about the lighting and have little use for advice about how to retake the screenshot. Let contributors say what kind of reply they’d enjoy in the entry itself.

Check coverage a day before closing and send a private reminder to anyone who asked for one. At the deadline, check again and split the unanswered entries between the hosts. If four remain, each host can take two before the recap. Keep the coverage list private.

If only two people submit, they can reply to each other. With one entry, reply as the host and keep the closing post small. If someone misses the submission deadline, offer a place to share in the recap or in the regular screenshot channel. Once assignments are out, keeping them stable lets people finish without checking for a new match.

Close the event while the links still make sense

Post a short recap with the original entries linked. Get permission before reposting images outside the event space. Give members one place for follow-up comments if you want to keep the conversation going. If you need to prevent new discussion in a forum post, Discord documents Close Post as a moderator-controlled closure. Moving into Older Posts through inactivity alone still leaves a post able to reopen. Discord’s Forum Channels FAQ.

Keep three counts for the next round: how many confirmed participants submitted, how many entries received a participant reply before the helper stepped in, and how many needed backup. If six people submit and the hosts cover four replies, you’ve learned something specific about the format. Ask whether the assignment was easy to find and whether the reply window was long enough before opening a bigger round.

If your members prefer sharing without assignments, use a simpler format next time. A comfort thread or year-end wall asks less of both hosts and participants. Pinicon’s Christmas Discord event ideas.