Relay Writing: A Dictation Workflow for Editors

A two-person edit room has a hidden structural flaw: both people do the same thing, which is why a dictation workflow for editors starts with changing the work rather than the furniture. Editor A drafts, editor B edits, then the roles swap for the next piece, and on a good week both hands end up with the same workload, the same grip, and the same evening ache. It is a perfectly fair arrangement and a perfectly symmetric disaster, because a workload split evenly across two identical hands is still the same workload twice. Each editor's individual risk is identical to a solo writer's, just with better conversation. The remedy is not to split the work evenly; it is to make the two halves different kinds of work.

The insight behind the relay is that drafting and editing load the hands in different ways. Drafting is long, continuous, and high-volume; it prefers speed and tolerates mess. Editing is short, precise, and varied; it wants accuracy and a close eye. Typing places both loads on the wrist, but dictation handles the drafting load beautifully while leaving the editing load exactly where it belongs, on a keen eye and a spare hand. When one team member speaks the draft and the other types the corrections, the pair covers both halves with half the typing each, and the hands get alternating rest periods instead of synchronized overtime.

The word symmetric is the point. Both editors develop the same injury at the same time, and the team often discovers it together, which means the production capacity drops in one stroke. The relay is designed to break that symmetry deliberately: at any moment, one editor's hands are carrying the load while the other's are recovering, and the load itself is smaller because the drafting voice does not need fingers at all. Team hand health, it turns out, is not a solo discipline. It is a scheduling problem, and scheduling problems have elegant answers. The relay's first week is the slow one; the second is the convincing one.

The rotation is simple to describe and needs discipline to run. Two editors, two roles: the drafter and the polisher. The drafter works from the outline or the brief and produces the full first draft by voice, block by block, with the hands doing nothing but clicking and occasionally correcting a word. The polisher takes each finished block, reads it, and applies the line edits on the keyboard: tightening, reordering, fixing the facts, adjusting the emphasis. When the article is done, the roles swap for the next piece. Each editor therefore spends half the day producing with the voice and half the day editing with the keyboard, and neither hand ever carries a full day of either job.

The block size is the design parameter that matters. Blocks of 800 to 1,200 words work well: large enough that the drafter gets into flow and the polisher gets a meaningful unit, small enough that the handoff happens before fatigue or drift. Set the cadence on the calendar rather than the mood: the drafter dictates the block while the polisher reads the prior block, then they swap at the marker. The sharing of a single document in a co-editing tool, or a simple versioned file handoff, keeps the relay seamless, and the handoff ritual below removes the quality gap that worries people most.

The one rule that keeps the rotation honest is that the roles must swap on every piece, not every day. If editor A always drafts and editor B always polishes, the system devolves into a rig where one person's wrists slowly improve and the other's inherit the whole problem. An article-by-article swap balances everything over a week: the same number of pieces drafted, the same number polished, the same total keystrokes, and the same rest, all without any heroics. Teams that try the relay report the first real benefit around the third piece, when the routine stops feeling like a test and starts feeling like the shape of the week.

The fear that kills the relay before it starts is the fear of quality: surely a dictated draft needs far more fixing than a typed one, and the polishing hours will swallow the speed gain. In practice the fix load is similar, because a typed first draft also needs a line edit, and the real difference shows up in specific, predictable places. The handoff ritual exists to catch those places at the moment they are cheap to repair rather than after the article is finished. Three rituals cover most of the quality surface, and together they take about five minutes per block.

Ritual one: the drafter reads the block back to themselves once before handing it over. Most dictated errors are homophone slips and odd punctuation, and hearing the sentence catches them instantly, better than staring at text. Ritual two: the polisher does a quick spoken-in-to-text pass, or simply reads the block aloud with the drafter listening, which is the fastest way both people agree on where the rhythm broke. Ritual three: every article closes with a shared read of the introduction and the conclusion, since these are the sections where the relay's two voices are most likely to leave fingerprints. Both editors read; the polisher types the final changes.

The deeper quality safeguard is the ownership question, and the relay answers it cleanly: the polisher owns the final version, not the drafter. That single sentence removes the diplomatic fog of co-created text, because someone is definitively responsible for what ships. It also gives the polisher the authority to ask for a re-dictated block rather than re-typing it alone, which protects the whole point. Teams that add a simple two-minute review at the end of each article, with both editors naming one fix that the draft needed, report the quality standard rises rather than falls, because the draft now gets a second full pair of eyes and a second full pair of hands instead of one exhausted set of each.

The trial that convinced most teams runs four articles: two weeks of normal solo drafting by both editors as the baseline, then four articles on the relay. The baseline matters more than the novelty. Count the standard article's drafting and editing time, note the evening hand score for each editor, and record how the last block of the day felt. Then run the relay and compare the same metrics, plus a new one that both editors will be surprised to appreciate: the time cost of the handoff itself. The first article on the relay is always the slowest, and it tells you nothing; treat it as the rehearsal, and start measuring from the second.

By article three, the reports converge on the same shape. The dictated draft comes out faster than the typed one, usually by a noticeable margin on long-form pieces. The polishing time is slightly longer than the old single-editor edit, because the polisher is the only one at the keyboard, but the combined time is still at or below par. And the evening hand score, the quiet metric, moves more than either: both editors report the ache that used to greet them at dinner is lighter, or gone, and the end-of-week hands feel like a normal week's hands rather than a delivery week's. That subjective report is the argument that keeps teams on the system.

The trials also surface the complaints, and they are rarely the ones predicted. The most common is the loss of the tactile private drafting feel, the sense that an idea is not real until it is typed; a few dictated drafts are required before that feeling fades. The second is the mismatch of editing styles, which the role ownership usually resolves. The most durable objection is logistical: the relay needs both people present, or at least responsive, so half-day overlaps must be protected on the calendar. Every team that solves those three practicalities reports the same conclusion, which is that the hand load halves for no output penalty, and the work feels less like a relay than like the only sensible way to share an edit room.

The relay scales by adding roles rather than by replicating the pair. A four-person team runs two pairs, but a smarter arrangement is chained: a drafter, a polisher, and a fact-checker, rotating the roles article by article so every person drafts, polishes, and checks across the week. The chain has the same property as the pair, that no single set of hands carries all the typing, while adding a third stage that solo teams never had: a read that is entirely separate from the writing. In larger units the constraint ceases to be the hands and becomes coordination, so the tooling matters more: a shared queue, a clear ownership marker on each article, and a visible timer on each block.

The second scaling rule is to keep the ratio visible. On a team of six, if three people befriend the voice and three keep typing everything, the symmetry simply re-forms inside the sub-groups, and the team's hand-health data moves in two directions. A simple weekly ledger, the number of articles drafted by voice versus typed, makes the imbalance visible and lets the lead rebalance before the quiet cohort starts complaining. Teams that publish the ledger find the competition solves the adoption problem better than any memo does, because nobody wants to hold the pen for the whole team's wrist load.

The third rule is that the relay is a training system, not a bureaucracy. When a new editor joins, they learn the voice drafting habits by rotating into the chain on their second week, which means the skill propagates by practice rather than by handbook. The relay also survives role changes gracefully: a promotion that pulls the lead into meetings leaves a chain that still runs, because no single person owns the critical handoff. For editorial teams, the relay is less a workflow trick and more a small piece of infrastructure, and like all good infrastructure it is invisible when it works, which is exactly what it feels like on those quiet, comfortable weeks.