How to Let Players Post Independently While Keeping One Shared Campaign Timeline
For an asynchronous narrative campaign, let players write their characters’ actions in separate posts, then use a single shared timeline to establish what has actually happened and when. The key is to separate independent choices from shared consequences: players can post without waiting for every other player, while a designated recorder or game facilitator resolves overlaps and updates a dated campaign log. This workflow suits recreational groups that want to contribute at different times without creating contradictory versions of the story.
Why independent posts need a shared timeline
Play-by-post lets people participate at their own pace. Role Gate, for example, describes tabletop play by chat where players can write as little as a short message a day, and it separates in-character from out-of-character text. That flexibility makes clear posting conventions useful: readers need to know whether a message is a character action, a question to the group, or an update to established events. (Role Gate)
A shared timeline solves a different problem. It gives the group one reference for the order of scenes, decisions, discoveries, and unresolved events. D&D’s campaign-journal guidance recommends organizing entries by date or session and using them to recall earlier events and carry details forward. That guidance is for tabletop campaigns generally; adapting it to a continuous post-based game is a practical procedure, not a built-in feature of any particular platform. (Your Campaign Journal, Roll20 Compendium)
Think of the timeline as a record of settled fiction, not a transcript of every message. Players can independently propose actions, reactions, and details. The shared record says which events are now part of the campaign and what remains open for others to affect.
Set the campaign’s posting rules before play
Agree on a few small rules before the first scene. Decide where in-character posts go, where coordination goes, who maintains the shared timeline, and what happens when one character’s action depends on another character’s response. Keep the rules short enough that everyone can remember them.
A useful default is: any player may post an action that does not decide another character’s response; actions that would change a shared scene remain proposals until the group’s agreed resolver settles them. The resolver might be the game facilitator, a rotating player, or a group vote for low-stakes details. Pick one method and state it in advance.
Also agree on an update rhythm. For instance, the resolver might consolidate the timeline after a scene reaches a natural pause or after a stated window for replies. A window is a coordination aid, not a demand that players be online at the same time. If someone misses it, the group can keep that character’s choices open, have the scene move around them, or use a previously agreed fallback. Make the fallback explicit rather than assuming silence means consent.
Separate posts into actions, reactions, and canon updates
Use simple labels or channel names to distinguish three kinds of writing. An action post describes what a character attempts or says. A reaction post responds to another character or to a new event. A canon update records a resolved fact in the shared timeline. The labels can be as plain as “In character,” “Out of character,” and “Timeline”; the goal is to reduce ambiguity, not add administrative overhead.
For example, in a fictional campaign about restoring a lighthouse, Mira posts: “I climb the western stairs and inspect the cracked lantern housing.” That is her character’s action. Another player can independently post that their character examines a weathered map elsewhere in the room. Neither post needs to decide what the other character discovers. The facilitator can then respond with the results and update the timeline: “Mira finds a loose brass panel; Tomas identifies the lighthouse on the map as Northwatch.”
Avoid writing another player’s major action or reaction for them. “Tomas agrees to follow Mira” takes away a choice; “Mira asks Tomas to follow” leaves him room to answer. This boundary lets players contribute at their own pace without turning parallel posts into competing versions of the same scene.
Use a timeline entry that records changes
A helpful timeline entry captures enough to restore context quickly without copying the whole conversation. D&D’s campaign-journal sheet includes a session or adventure title, session number and date, planned summary, earlier events with bearing on the session, and additional notes. For asynchronous play, adapt those categories into a compact entry organized by in-world time or scene. (Campaign Journal, D&D Beyond PDF)
A practical entry can include:
This format is an editorial recommendation based on the journal’s emphasis on session identity and relevant past events. It is not necessary to track every message timestamp as fictional time. A post sent Tuesday can describe an event that occurred earlier in the same in-world scene; distinguish real posting order from fictional chronology whenever they diverge.
Resolve overlapping posts without rewriting the story
Overlaps are normal when people post independently. Suppose Mira says she lifts the brass panel while Tomas posts that he removes it first. Do not silently delete one post or make both actions happen if they cannot coexist. Mark the overlap as unresolved, then apply the rule your group chose: ask the players to adjust, let the facilitator establish an order, or treat one post as an attempt that occurred before the other.
Keep the correction narrow. The goal is to settle the point of conflict and preserve the rest of each contribution. If Tomas’s post also includes a useful observation about the map, that part can still stand even if the panel action needs clarification. Once the group resolves the sequence, update the timeline with the final outcome and, if useful, a brief note that the earlier posts were proposals.
For choices with consequences, distinguish attempts from outcomes. “I search the desk” records an attempt; “I find a sealed letter” may require a facilitator’s response or an agreed resolution method. This keeps players free to describe intent without accidentally establishing facts that the game has not settled.
Keep private information and shared continuity distinct
Some campaigns use secrets, hidden clues, or private character goals. Keep private notes separate from the public timeline, and record only what the shared story establishes. A player may privately know that their character suspects the lighthouse keeper, while the public log records only that the keeper declined to open the storeroom. That preserves the difference between a character’s interpretation and an event everyone can rely on.
The same discipline applies to uncertain details. Write “the group suspects the bell is linked to the storm” rather than “the bell controls the storm” until the story confirms it. A log that labels theories as facts can create avoidable continuity disputes. Mark uncertain details as “theory,” “unconfirmed,” or “open,” and revise the entry when new information settles them.
Make the recap easy to resume
At the beginning of a new scene or posting cycle, share a short recap from the timeline: current location, what has just changed, and what decisions are open. D&D Beyond’s campaign-journaling advice notes that a journal can capture important events and help the group recall details that matter later; a concise recap applies that same purpose to players returning to a long-running thread. (Creating Your First Campaign Using the 2024 Dungeon Master’s Guide, D&D Beyond)
For the lighthouse example, a recap might say: “The group is in Northwatch’s lantern room on Day 4. Mira has found a loose brass panel. Tomas’s map identifies the lighthouse. The panel has not been opened yet; Mira and Tomas both posted attempts, and the group is resolving who acts first.” That recap tells a returning player what they can respond to without asking them to reread every message.
Adjust the workflow to the group’s pace
Start with the lightest process that addresses your group’s actual friction. If posts rarely overlap, a shared log and clear labels may be enough. If simultaneous actions often collide, add a short reply window or have the facilitator consolidate turns. If nobody wants one person to own the recap, rotate the recorder by scene or session; D&D Beyond’s guidance also recognizes that journaling can happen in different formats, from notebooks to computer files. (Creating Your First Campaign Using the 2024 Dungeon Master’s Guide, D&D Beyond)
A timeline cannot decide every creative disagreement or remove the need for group communication. It can make the current state legible: what happened, what is still undecided, and whose choice comes next. Keep entries brief, correct them when the group settles a disputed fact, and let independent posts remain independent wherever characters’ actions do not conflict. That gives players room to contribute on their own schedules while keeping one coherent campaign history.