Co-writing is the smallest collaborative world: two people, one canon. It feels manageable precisely because it is small — surely two people can just keep each other posted. In practice, two is enough for the world to split into two copies, and the breaks show up exactly where the two writers' work meets.
And two is in some ways the most deceptive number. A full writers' room expects to need process; two friends writing a book together assume their constant texting is process enough. It is not — the things that drift are the small, settled-feeling facts that neither writer thinks to mention, precisely because each assumes the other remembers them the same way.
The craft of co-writing is managing the seams where two writers' work meets. Here is how to keep a shared world consistent when more than one hand is writing it.
Co-writing breaks at the seams
Within their own sections, co-authors are usually consistent — each is checking against the world as they understand it. The contradictions appear at the seams: the handoff where one writer's chapter meets the other's, where a fact one of them established was never seen by the other.
A character grieves a death in one author's chapter that the other author's chapter has not yet caused. A rule one writer treats as absolute, the other treats as flexible. A location is three days' ride away in your half and an afternoon's walk in mine. An object is introduced twice, by two writers who each thought they were introducing it. Neither author is wrong inside their own pages. The break lives in the gap between them — which is the part nobody owns.
The reason seams are so dangerous is that they are invisible during writing. You proofread your chapter against your understanding of the world and it passes cleanly, because of course it agrees with itself. The conflict only exists when your chapter is read next to your co-author's, and during drafting nobody is reading them next to each other — each writer is heads-down in their own half.
Agree on what's settled before you write
Most co-writing breaks trace back to a fact that felt too obvious to confirm. Before the drafting starts, the two of you should actually pin down the load-bearing facts in writing: the rules that cannot bend, the timeline's fixed points, what each major character knows and wants as of the start, the spellings and names. Not the whole world — just the parts a contradiction in would be expensive.
The point of writing it down is not formality; it is that "we both know how the magic works" is almost always two slightly different understandings that have never been compared. The act of stating it out loud surfaces the disagreement while it is still a five-minute conversation, instead of a chapter-thirty contradiction that forces one of you to rewrite a climax.
Two ways co-writers split a book
Co-writers tend to work in one of two modes, and each fails differently. In the divided model, each author owns whole chunks — you write the chapters from one character's point of view, I write the other's. The seams are few but deep: long stretches of independent writing meet at a handful of handoffs, and a fact that drifted has had a whole arc to compound before the two halves touch.
In the braided model, you trade passes over the same material — I draft, you revise, I revise your revision. The seams are everywhere but shallow: you are constantly reading each other's work, so drift is caught fast, but it is easy to overwrite each other's intentions and lose track of who decided what. Whichever model you use, the fix is the same underneath — one shared canon both of you write against — but knowing your model tells you where to look for the breaks: at the few deep handoffs, or in the churn of constant revision.
Divide the work, not the truth
It is fine, even efficient, for co-writers to own different parts of a project — chapters, characters, a region of the map. What cannot be divided is the canon itself. The moment each author keeps their own copy of what is true, the seams are guaranteed to drift, because each is writing against a slightly different world, and the differences are invisible until the halves meet.
One shared, live record of canon fixes the precondition: both authors are at least looking at the same world, updated the moment either of them changes something. Divide the writing however suits the book — but keep the truth single, in one place you both read from and write to.
Voice is a seam, too
Facts are not the only thing that drifts across a handoff. A character can stay factually consistent and still feel like two different people — wry and clipped in your chapters, earnest and verbose in your co-author's — because each of you hears them slightly differently. Readers register this as a continuity break even when no fact is wrong; the person does not hold together.
Capturing voice in the shared canon helps: a few lines on how each major character talks and what they would never say, agreed up front, gives both writers the same target. It will not make your prose identical, and it should not — but it keeps the character recognizably one person across the seam, which is its own form of continuity.
Check the seams before you merge
Sharing one canon stops the copies from drifting apart, but it does not catch the contradictions that are already on the page — a fact in your co-author's chapter that quietly disagrees with one in yours. Those need an actual check, run across both writers' material at once, before the chapters are stitched together.
A consistency pass over the whole shared world finds the disagreements neither author would catch alone, because neither holds both halves in their head. Run it at every handoff, settle the contradictions while the pages are still cheap to change, and the seams stop being where the book falls apart. This is exactly the kind of check CanonBoard runs: both of you build the world on one board, and the engine scans it on demand and surfaces the seam contradictions — both sides quoted — so the handoff becomes the place the book gets stronger rather than the place it breaks.
Frequently asked questions
- How do co-authors avoid continuity errors?
- By sharing one live record of canon instead of two private ones, agreeing on what is settled before they write against it, and checking the seams — the handoffs between who wrote what — where co-written contradictions almost always hide.
- Should co-writers divide the world or share it?
- Dividing the work is fine; dividing the truth is not. Co-writers can own different chapters, characters, or regions, but they all have to write against one shared canon, or their sections will quietly contradict each other at the edges.
- Where do co-written stories usually break canon?
- At the seams — the points where one author's material meets another's. A fact one writer established and the other did not see is the classic co-writing continuity error.
CanonBoard scans your whole world and tells you where it disagrees with itself.
Start free