How to Coordinate Shared Worldbuilding Before Multiple Authors Add Conflicting Lore

A disagreement about lore can be a process problem: one writer treats a brainstorm as binding, while another assumes nothing is official until it appears in a published story. Decide what counts as canon in this project and record the answer where everyone can find it. For example, you might say that approved setting facts and released stories are binding, while pitches and private drafts are proposals. A collaborative writing project, Federation 54, makes a similar distinction between a member’s personal canon and Fleet canon, and describes approval as the step that makes a proposal shared canon. Federation 54’s “Get involved” guide

Keep the policy proportional to the project. A small group may decide together; a larger one may assign a continuity editor or rotating reviewers. The important point is to settle the decision route before a contested idea arrives. Clarify who can approve a new fact, who can revise an established one, and whether silence counts as approval. If writers are unsure, the safe default is to label the idea provisional and ask before using it as a premise for another author’s plot.

A lore bible is useful when it helps writers make decisions during drafting. Start with facts that could cause scenes to contradict one another: the timeline, geography that affects travel, rules and limits of unusual technologies, established character histories, important institutions, and names or terms with agreed spellings. Add only the detail needed to answer recurring questions. A long encyclopedia can wait until contributors need it.

For each entry, include the fact, its status, and its source. “The eastern pass is closed in winter” is more actionable when the record also says whether this is established canon, a local belief, or a new proposal, and points to the story or decision that supports it. That distinction matters because an unreliable narrator, disputed history, or regional custom can create apparent disagreement without changing the underlying world. The reference should preserve those differences rather than flatten every statement into an unquestioned fact.

A useful guide marks both boundaries and freedoms. List a small set of fixed rules that other stories depend on, then identify what contributors may invent without prior approval: a village’s local festival, for example, may be open while the founding history of the capital is fixed. Assigning regions, characters, or story periods to individual writers can also reduce accidental overlap, as long as the guide explains which shared facts still apply.

The point is to prevent collisions that would change another writer’s work, not to settle every detail in advance. In a collaborative project described by Campfire Writing, contributors’ stories sometimes led the team to adjust details or ask authors to elaborate, and the team prioritized consistency with the anthology in at least one case over an earlier lore-bible detail. That example supports a practical lesson: the reference needs a way to handle conflicts and revisions, because its first version will not anticipate every story. Campfire Writing’s “Managing a Collaborative Worldbuilding Project”

Ask writers to submit a brief note before they draft lore that affects shared history, established characters, major rules, or another contributor’s planned story. The note can answer four questions: What is the proposed fact? Which existing facts does it touch? Which stories or contributors could it affect? Is the detail meant to be fixed canon, a character’s belief, or an open question?

This small checkpoint catches conflicts while they are still easy to resolve. A proposal that a rare substance grows on trees, for instance, should be checked against existing descriptions of how it forms and who can access it. Perhaps the new detail can fit a particular region or a mistaken account; perhaps it requires changing the earlier description. Either way, the writers can choose deliberately instead of discovering the mismatch after both drafts depend on incompatible versions.

When a proposal conflicts with the reference, pause the affected draft and identify the exact statements that disagree. Then decide whether the difference is a factual contradiction, a viewpoint within the fiction, or a gap the new story can fill. If it is a contradiction, choose among revising the proposal, changing the earlier fact, narrowing where or when each version applies, or keeping the material provisional. Record the reason and update affected entries so the same debate does not recur.

For groups, match the review route to the impact. A low-impact local custom might need a quick check from the relevant contributor; a change to a shared historical event may need the designated editor or group discussion. Federation 54 describes a workflow in which members submit new canon for approval, after which it becomes available to the wider group and is written into its shared Codex. That is one workable model, not a universal requirement: the right level of review depends on how many stories rely on the fact and how the group makes decisions. Federation 54’s canon process

Choose one canonical location for the current reference and name someone responsible for recording approved changes. After a decision, update the entry promptly, include a date or version marker if the project needs it, and notify writers whose drafts depend on the changed fact. Keep a brief change log for consequential revisions: what changed, why, and which stories may need checking. Avoid maintaining parallel “final” documents that can quietly drift apart.

Writers should also be able to find the relevant entry quickly. Use consistent headings, a searchable document, and links from timeline or character entries to related facts. If the project has too much lore for a single file, divide it into indexed sections but keep the status labels and decision rules consistent throughout. A practical test: can a contributor confirm the status of a disputed fact in a minute or two? If not, improve navigation before adding more material.

Before an author builds a plot around a new world fact, check the parts of the reference most likely to constrain it: chronology, location, character knowledge, and any rule the story uses. Ask what must already be true for the proposed scene to work, and whether another writer’s established material rules that out. For a character arriving at a city before a festival, for instance, check the date, travel time, and whether the character could know the route. The check should focus on dependencies, not every detail in the setting.

Close the loop by marking the proposal’s status and telling affected writers the decision. If a detail remains unsettled, authors can avoid making it load-bearing until the group resolves it. A compact canon policy, a living reference, and an early review step give a shared world a stable frame while leaving plenty of room for each author’s story.

• “Managing a Collaborative Worldbuilding Project” — Campfire Writing

• “Get involved” — Federation 54