📚 How to co-write a book without conflicts

Writing a book alone is possible, but with two people or a small team it is usually faster and more reliable: you get a second pair of eyes, additional expertise, and shared responsibility for the result. The problem is that without rules agreed in advance, working on a manuscript together quickly turns into chaos: two versions of the same chapter, different ideas about structure, and endless rounds of edits. Below we will look at how to set up the process so the book comes out on time, without burnout, and with quality you are not embarrassed to show readers.

Where to start: agreements before the first line

The most expensive mistakes in co-authoring happen not in the middle of the work, but at the start, when everyone is inspired and does not want boring formalities. Yet it is precisely the roles, schedule, and feedback rules fixed in advance that determine whether the manuscript reaches publication.

💡 Quick overview:

• Step 1: Agree on the concept and structure of the book before the first line is written.
• Step 2: Assign roles using the RACI model so it is clear who writes, who edits, and who makes the final decision.
• Step 3: Break the work into stages with specific dates, not "we will write the book by fall."
• Step 4: Introduce a three-level editing system so feedback does not turn into an endless loop.
• Step 5: Choose the publishing route, self-publishing or a traditional publisher, before the manuscript is ready, since it affects the format and budget.

Why co-authoring works: numbers that change the picture

Co-writing books is no longer the exception. According to a WifiTalents report for 2026, the volume of self-publishing exceeds 2.3 million books per year, and more than 500,000 authors are actively working on Amazon KDP. In the academic segment, co-authorship has grown by 7 percent in recent years. The trend is clear: the publishing ecosystem is becoming increasingly collaborative.

The numbers also explain the motivation. It is easy to enter the game and hard to earn: the average self-published author makes less than $1,000 per year, while traditional publishers accept only 1 percent of manuscripts. Co-authoring partially solves this problem: two authors bring twice the expertise, share the costs of editing and layout, and reach a wider audience through the overlap of their reader bases.

Roles and areas of responsibility: the RACI model for authors

The most common cause of conflict in co-authoring is uncertainty: "I thought you were writing this." The solution is to assign roles before the work begins. The RACI model from project management works well for this: Responsible (does the work), Accountable (owns the result), Consulted (provides input), Informed (stays in the loop). For a book, it adapts as follows:

The key point: Accountable is always one person. There is no such thing as "we are both responsible for the final text." If two people are responsible, no one is. The person with the Accountable role gets the final say on their block.

When areas overlap (both edit the same chapter), a simple rule applies: Author B writes the draft, Author A leaves comments without direct edits, Author B applies the changes and marks the chapter as done. This eliminates the situation where edits are made simultaneously and the text turns into a layer cake.

Tools for collaboration: what you actually need

Tool choice affects speed more than it seems. The optimal stack for a writing duo, according to the PublishDrive co-authoring guide, looks like this:

• Google Docs for drafts and parallel editing: versioning and comments cover most scenarios.
• Notion for the project knowledge base: chapter outlines, research notes, character cards, and references.
• Slack or Discord for day-to-day communication. Decisions get recorded in the document, not left in chat.
• Scrivener for large manuscripts when you need to manage scenes and chapters as separate units.
• Hemingway Editor for the final readability check and cutting overloaded sentences.

A rule that will save you weeks: pick one source of truth. If a chapter's status lives in Notion, it should not be duplicated in Telegram. If edits are made in Google Docs, do not keep a parallel copy of the file labeled "final" and "final final."

A separate point: version control. Cloud editors have it built in, but when working in Scrivener or desktop tools, set up sync and agree on file naming like "Book_Chapter3_Draft.docx." This eliminates the "I edited the wrong file" situation.

Work schedule: from "someday" to concrete milestones

Vague deadlines kill manuscripts more often than lack of talent does. A realistic horizon for a nonfiction book of 50,000 to 80,000 words is four to six months. Here is a plan for a duo:

Separately, agree on what happens when a deadline slips. The mechanics are simple: one to two days late, the other author waits and moves the call agenda; three to five days late, revise the scope or redistribute the workload; more than a week late, meet to revisit the whole plan instead of hoping it will "sort itself out." This approach removes emotional tension: you are not angry at each other, you are following a scenario you agreed on in advance.

Feedback without conflict: a three-level editing system

Feedback is the point where co-authoring either gets stronger or breaks down. The problem is that authors often lump typos, stylistic complaints, and structural notes into one pile, and the recipient reads it as "everything is bad."

The solution, an edit classification system recommended by the PublishDrive practical guide, splits comments into three levels:

• Level 1 (must-fix): factual errors, missing sections, broken logic. Fixed immediately, without discussion.
• Level 2 (should-fix): clarity issues, weak transitions, repetition, poor examples. Discussed, but almost always fixed.
• Level 3 (nice-to-have): stylistic preferences and minor wording. Can be accepted or rejected without consequences.

When both authors label comments by level, the "everything is urgent" effect disappears: the author sees that some notes require immediate fixes, while the rest can be handled in order. The throughput of editing grows several times over.

For difficult cases where you cannot reach agreement, a "conflict script" works: pause, briefly summarize what you heard, offer several options, give the final say to the Accountable, and move on without relitigating the decision after the fact.

Practical breakdown: a duo's path from idea to publication

To keep the principles from staying abstract, let's walk through the steps of a typical nonfiction duo using the PublishDrive guide. One author owns the expertise and factual material, the second owns packaging and editing, and both lock in who owns what up front.

At the start they pick a topic and audience, then build a shared outline and a written agreement: royalty shares, expense split, and the process if one author leaves. Then comes the rough work: the expert dictates chapters, the editor turns the recordings into readable text. Edits are tagged at three levels, and the final style polish is always done by one person so the voice sounds consistent.

The result comes not from talent but from predictability: every chapter has an owner, every comment has a priority, and every dispute has a pre-agreed way to resolve it. That process ends with a finished manuscript and a launch, not an abandoned folder of drafts.

The key takeaway: roles stay separate for the entire project. One person doesn't touch style, the other doesn't touch factual material, and that is exactly what saves months of back-and-forth.

Publishing strategy: self-publishing or a traditional publisher

The route you choose determines format, budget, and timeline, so the decision is worth making before the manuscript is ready.

Traditional publisher. Pros: an advance, distribution, editing, and cover design paid for by the publisher. Cons: according to WifiTalents data, it takes 18 to 24 months from manuscript submission to the shelf, hardcover royalties run 10 to 15 percent, and only 1 percent of manuscripts get accepted. Co-authors face an extra hurdle because the publisher evaluates not one author but the pairing and the risk of the duo falling apart.

Self-publishing. Pros: royalties from 40 to 70 percent, full control over timeline and content, and a direct connection with readers. Cons: editing, cover, and marketing costs fall on the authors, and professional self-publishing costs on average $2,000 to $5,000 per book.

For co-authors, self-publishing is often the better deal: two people split fixed costs in half and earn higher royalties. With an average ebook price around $3.06 in the self-publishing segment, a joint project reaches break-even faster than a solo one.

A separate point is legal compliance. Before you start, put it in writing: how royalties are split, who owns the rights to the text, what happens if one author leaves, and how decisions are made on translations, audiobooks, and screen adaptations. You don't need a lawyer at the start; even a Google Docs document signed by both sides will eliminate most future disputes, as PublishDrive advises.

⁉️🤔 Common questions

Can you co-write a book remotely, from different cities?

Yes, and most duos work exactly that way. The key condition is a single cloud-based tool for the text and a weekly 30-minute voice call to sync up. Time zone differences don't matter much if you have an asynchronous channel and an agreed response time, for example within 24 hours.

What if a co-author loses interest in the project halfway through?

That is exactly what a written agreement signed before the start is for. It locks in what happens to the rights to the work already written and how an author exits the project without claims. Without that document you risk losing the entire book, so this clause is worth including in the agreement from day one.

How do you split the fee if the authors' contributions are unequal?

The simplest option is proportional: if one person wrote most of the volume and the other less, royalties are split in the same proportion. It gets harder with invisible contributions like editing, marketing, and networking. The principle that works here is to estimate the contribution in hours and agree on the share before starting, as the PublishDrive guide recommends.

Do you need an editor if the authors already edit each other?

Yes. Two authors inevitably develop blindness to the text and stop noticing logical gaps that are obvious to an outside reader. The minimum is beta reading by several readers from the target audience and professional proofreading before publication.

How does co-authorship affect the authorial voice? Won't it turn into a patchwork quilt?

The risk is real, and it is removed one way: one author owns the final polish of style and voice. That person goes through the entire text at the final stage and brings it to a consistent sound. That is why readers never guess that two people worked on the text.

Bottom line: co-writing a book is a technology, not a lottery

Co-authoring a book is not magic, it is a managed process. The trend is backed by numbers: co-authorship is growing by 7 percent in the academic segment, the self-publishing ecosystem counts more than half a million active authors on Amazon KDP, and tools for remote collaboration have long been available. The key points:

• Agree on roles before you start: the RACI model removes uncertainty and conflicts over "who is in charge".
• Break the work into stages with verifiable deliverables, not "we are writing a book".
• Put in place a three-level editing system, it speeds up the editorial process and takes emotion out of feedback.
• Put money and rights in writing before the first paragraph is written.
• Choose your publishing route at the start: self-publishing gives higher royalties and control, a traditional publisher gives an advance and distribution, but a long cycle.

A book written by two people is not a compromise between two voices, it is a product that is stronger than either author on their own. Start small: lock in the outline, assign roles, and hold your first working call this week, rather than putting off agreements until the first disagreements appear.