Introduction

Collaborative Writing 101 introduced shared authorship, the Brotherhood's main collaborative writing activities, and how to track and credit contributions. This course builds on those foundations by focusing on how people work together.

By the end, you should be able to invite a partner with clear expectations, choose a workable group structure, set up a shared drafting space, agree on editing boundaries, and respond constructively to delays or disagreements.

Every writer works differently. Some plan every detail, while others start with a situation and develop it as they write. Some contribute a little each day, while others draft whole scenes in one sitting. Agreeing on how to work together helps prevent these differences from becoming sources of friction.

Finding Writing Partners

Start with an activity, competition, or story idea, then look for someone who would enjoy working on it with you.

Writing partners can be found among friends, Clan members, regular RP participants, or members whose characters appear suited to a particular idea. You can ask in a relevant Discord channel, approach someone directly, or join an activity that is already looking for participants.

The invitation does not need to be elaborate. Explain the idea, activity, expected contribution, likely pace, and any deadline so the other person can decide whether it suits them.

It is also useful to be clear about what you are asking them to do. There is a difference between inviting someone to join an RP session, asking them to contribute scenes for a character in an event fiction, and asking permission to include their character in a solo story.

For example: "Would you like to write a short co-op fiction for this competition? I can draft the opening scene, and I'd like you to contribute your character's response. The deadline is next Friday. Does that fit your schedule?"

Make it easy for someone to decline or suggest a smaller role. Once you agree to work together, give each writer room to contribute and be honest about what you can complete.

Working Styles and Group Structures

People's preferences and availability change between projects. Discuss how much structure each person wants, how often they can contribute, and whether they prefer proposing ideas or responding to prompts.

Divide responsibilities according to the work: someone may coordinate scenes, someone may keep track of continuity, and someone may prepare the final submission. A writer with limited time can take a smaller, agreed contribution. A less experienced writer may appreciate a clear opening or a question to respond to.

Groups can organize their work in several ways:

• Led project: A Dungeon Master (DM), organizer, or small team sets the direction and coordinates contributions. Agree on which decisions need their approval.
• Outline with flexible drafting: The group agrees on the setup, major events, and responsibilities, then gives each writer room to develop their section.
• Shared direction: Writers decide together how the story develops, checking in when a new idea would affect the others. This can suit informal or social scenes without requiring a detailed plot.

Use the amount of structure the project needs. A relaxed scene may need little planning; a competition entry with a deadline may need assigned sections and time for a final review. Make sure everyone understands the arrangement, and revisit it if it stops working.

Shared Documents and Editing

Choosing Access Permissions

For a shared-document project, choose a space everyone can use and agree on who needs to write, review, or simply read the work. In Google Docs, the usual access roles are:

• Viewer: Can read the document.
• Commenter: Can leave comments and suggest changes without directly editing the text.
• Editor: Can change the text directly, leave comments, and accept or reject suggestions.

Give co-authors Editor access when they need to draft in the document. Commenter access is useful for a reviewer whose changes should be considered before they become part of the text. If you share a live document with a grader, as permitted for this course's practical, viewing access is sufficient; follow the activity's instructions about the actual submission format.

Check access before your partners need to write or your grader needs to read. Copying a document link does not by itself grant access. Share it with the intended people and confirm they can open it; you do not need to give everyone editing access or publish the document to the whole internet.

Account or organization settings can limit sharing options. For details, see Google's sharing guidance. If you use another writing tool, look for equivalent access controls.

Working Copies and Submitted Files

A shared document is useful for drafting and review, but its contents can change after you submit its link. Giving a grader viewing access does not stop the authors from editing the document after a competition deadline. Competitions therefore commonly ask for an exported document, such as a PDF, that records the version submitted for judging.

For this course's practical, an eligible entry in the Fiction Gallery is encouraged when your collaborative fiction is available there. A shared-document link is also accepted, including for fiction written outside competitions. In either case, the evidence must let the grader identify the prose you and your partners wrote.

Editing, Suggesting, and Comments

Access permissions determine what you can do; the document mode determines how your changes are made. In Google Docs, use the mode selector to choose Editing or Suggesting when your access permits it.

Editing changes the draft directly. Use it to write your own section or make changes the group has already agreed you may make, such as routine corrections during a shared proofreading pass.

Suggesting proposes additions, deletions, or replacements for an editor to accept or reject. Use it when offering a rewrite or changing another author's wording without assuming their agreement. Use a comment to explain a concern, ask a question, or discuss a plot change before drafting the replacement. See Google's suggested-edits guidance.

When you propose replacement prose rather than correcting the original wording, agree how the contribution will be attributed before preparing the submission.

Agreeing on the Scope of a Review

Before asking someone to review a draft, say what kind of help you want:

• Proofreading: Correct spelling, punctuation, grammar, and formatting without changing the intended meaning.
• Wording and clarity: Suggest changes to phrasing or sentence structure while preserving the author's meaning and voice.
• Story feedback: Discuss characterization, pacing, continuity, structure, or plot. Agree on substantial changes before rewriting.

These are descriptions of the work, not ranks of reviewer. The same person may help in several ways, but permission for one kind of review does not automatically cover all of them.

For example, "Please fix obvious typos directly, suggest wording changes, and leave comments on plot issues" gives a reviewer a clear starting point. Agree on who will review suggestions and prepare the final version, and leave time for that work before the deadline.

Communication, Planning, and Etiquette

Communication

When reaching out to someone about writing together, establish a reliable way to communicate. It is better if that line includes everyone involved and uses the most convenient method available. For many groups, this will be Discord.

Writers need a way to ask questions and discuss concerns. Without one, disagreements about characterization or the direction of the story become harder to prevent and resolve.

The group does not need to remain in constant contact, but everyone should know where questions are being discussed and where changes to the plan will be recorded. For larger projects, a dedicated thread or group message may be easier to follow than scattering decisions across several channels and private conversations.

Agree on as much as the activity needs. For a planned fiction, this might include the characters, opening situation, central conflict, and a likely ending. These decisions can help divide the work without settling every scene in advance.

A casual RP may begin with a simple interaction and develop without a planned conflict or ending. An official or cooperative fiction may benefit from a rough sequence of scenes and assigned responsibilities. Leave room for ideas that emerge as you write, and discuss changes that affect the other participants.

Character Details

When writing with other people, remember that it is not only your character's story. Everyone involved brings their own characters, loadouts, and motivations.

During planning, establish which characters are involved and share the relevant character sheets, equipment loadouts, or snapshots required by the activity. A snapshot provides a fixed reference even if a character's sheet or equipment later changes. Read enough of these details to portray the characters consistently.

You are not expected to know a character's entire backstory or read their complete wiki article, though a little reading rarely hurts. The character sheet should provide enough information to avoid the most obvious mistakes. When uncertain, ask.

Follow the activity's rules and agree with the character's owner on what you may write for them.

Continuity

Do not disregard another member's contribution or change established details without discussing the change and following the activity's rules. This includes adding material that treats their character's perspective as conveniently mistaken, changing important details that have already been written, or derailing an RP session or planned storyline simply because you dislike its direction.

Not every continuity error is intentional. Writers miss details, misunderstand descriptions, or work from an earlier version of a document. Most small errors can be corrected easily once they are noticed. The concern is less about making a mistake than about knowingly disregarding what another participant contributed.

Before writing a new post or section, review enough of the existing material to understand the current location, relevant character actions, and any information that has already been established.

Managing Time Constraints

Many collaborative activities take place within a limited window. The group will have a certain amount of time to plan, write, revise, and submit its entry.

Pre-planning should not consume so much of that window that participants are left without enough time to write. Nor should someone reserve a post for a substantial period if doing so prevents the rest of the group from continuing.

Real life happens, and members will not always be able to meet an intended posting schedule. When that happens, let the group know and agree on how to continue within the activity's rules. Another participant may be able to take the next post or a scene may be reassigned. Do not assume that a fixed posting order or another writer's character permissions can simply be overridden.

An absent participant is difficult to plan around because the group does not know whether to wait, alter the story, or continue without them. A brief message is usually enough to give everyone else a practical way forward.

Corrections

Genuine mistakes will be made, but it is generally better to give someone the opportunity to correct their own work than to overwrite it in your next post or section.

Let the writer know if they misunderstood an action, contradicted an earlier detail, or portrayed your character incorrectly. Where possible, explain what needs changing rather than simply saying that the passage is wrong.

If someone is temporarily absent because of something outside the club, give them a reasonable opportunity to respond. When that is not possible, especially near a deadline, the remaining writers may need to finish the story, reassign the posting order, or make necessary corrections. Keep these changes within the activity's rules and any permissions already agreed with the character's owner. Those changes should resolve the problem without reading as vindictive or punitive.

Use the editing boundaries agreed at the start of the project. An agreed proofreading pass may allow direct typo fixes; a substantial rewrite, characterization change, or plot alteration still needs discussion. For a posted activity, check whether its rules permit edits before changing a submitted post.

If a disagreement cannot be resolved through a correction request, pause before making further changes. Make sure everyone understands what is being disputed and give each person a chance to explain what they intended. When appropriate, ask the activity organizer or DM to help the group decide how to proceed. For an informal project, the writers may need to adjust the plan, remove the disputed material by agreement, or end the collaboration. Keep the discussion focused on the work rather than making it personal.

Patience

Not every story needs to be completed immediately, and some do not need to be completed at all. Informal stories can be paused and returned to later. Check the competition rules before submitting a partial story: an unfinished narrative may be acceptable if it meets the entry requirements, but do not assume that every activity allows one.

It may be reasonable to work more intensively as a deadline approaches, but that does not make it acceptable to pressure or rush another participant. Most members know little about what is happening in each other's daily lives outside the club, and collaborative writing should be treated as a hobby rather than employment.

Writers also differ in experience, speed, confidence, and fluency. A participant may have limited creative writing experience, difficulty with spelling or punctuation, responsibilities outside the club, or English as a second language. These differences may affect how quickly they work or how much editing their contributions require, but they do not make them less deserving of patience.

The practical expectation is not that every participant writes at the same speed or produces identical prose. It is that they communicate honestly, make the contribution they agreed to make, and treat the other writers reasonably while doing so.

Conclusion

Good collaboration depends on clear expectations and communication that fits the project. Agree on the contribution each person will make, choose a workable drafting space, and establish how you will handle edits and decisions.

Before writing, check the relevant character details and activity requirements. As the work develops, build on each other's contributions, raise concerns early, and let the group know when your availability changes. A delay or mistake is usually easier to resolve when everyone understands what happened.

For the practical assessment, use an eligible existing collaboration or arrange a new one. Check that your evidence is accessible and identifies each writer's contribution. The assessment asks you to demonstrate shared authorship, not to produce a polished literary work.