WorkFlow Wednesday · AI Pro Writers Studio

🔥

WorkFlow Wednesday

The Beta Reader Handoff: Sharing Only What You Meant To

Your draft is done. Before anyone reads it — human or otherwise — here's how to send exactly the book and nothing else, and how to know later which version they read.

---

Here's the moment this article is about.

The draft is finished. You want eyes on it. So you export the whole book, attach it to an email, and send it to four people. Then, somewhere around the second reply, you get a very polite question about a document called Character Notes — Tam (DO NOT USE, old version).

That's the failure. Not the formatting loss, not the version confusion — though both of those are real. The one that actually stings is discovering that "export the book" sent more of your binder than you meant to.

So this week: the handoff. How to send the book and only the book, how to mark which version you sent, and the option where you don't send a file at all.

There's one thing you need to know before any of the steps, and it's the thing I got wrong.

---

The important part: not every export obeys the same rule

Your binder rows each have three little boxes: B, S, and ¶.

The third one, ¶, is the print flag. It means this document is part of the book. Tick it on your chapters, leave it off your notes, and your export contains a manuscript instead of a filing cabinet.

That's true. It is just not true of every export format.

| Format | Obeys the ¶ tick? |

|------------------------|---------------------------------------------|

| EPUB | ✅ Yes |

| PDF | ✅ Yes |

| DOCX | ✅ Yes |

| Markdown | ❌ No — sends everything |

| Plain text | ❌ No — sends everything |

This isn't a bug, and the code says so out loud:

> export_enabled is deliberately IGNORED here — Markdown export doubles as a backup format and always carries every document.

Which is a completely reasonable decision for a backup. A backup that only saved the chapters you'd ticked would be a bad backup. But it means the Markdown and plain-text options are the wrong tool for handing your book to a person, and they're sitting in the same menu as the right ones.

The tell: EPUB, PDF and DOCX each stop and show you a confirmation box before they run, spelling out that only ticked items are included. Markdown and plain text just go. If no dialog appeared, you exported everything.

So: for a reader, use EPUB. (Or DOCX if they want to leave comments, or PDF if they're printing it.) Save Markdown for your own backups, where carrying everything is the point.

One note on that confirmation box, while we're here: its wording calls the print tick "the same checkbox you use to include scenes in AI context." Those are actually two different boxes — ¶* controls export, B controls AI context. The export itself gates on ¶, correctly. The sentence is just loose.*

---

Step 1 — Tick ¶ on the chapters, and nothing else

Go down your binder and make sure ¶ is on for every chapter or scene that belongs in the book, and off for everything else — story bible, character files, outline, research, notes, your Chapter 14 rewrite you're not sure about.

Why it's worth doing deliberately rather than trusting the default: new documents arrive with the box already ticked. Which is right for a chapter and wrong for the note you scribbled at 1am, so the drift is always in the direction of more in your export, never less.

Three things get a document excluded, not one:

1. Its type isn't exportable — folders and session logs never go, regardless.

2. Its status is Cut. A chapter marked Cut stays out even with ¶ ticked. Useful: you can retire a chapter without untangling anything.

3. ¶ is off.

The folder shortcut: the box works on a whole folder. Tick ¶ off on your Research folder and everything inside goes with it. One click instead of nine.

A two-minute check before you export: your word count. The binder totals only what's ticked for print, so if the number reads meaningfully higher than the book you think you wrote, something's in there that shouldn't be.

---

Step 2 — Mark the version you're about to send

Three weeks from now someone will send you notes on chapter nine. You will have rewritten chapter nine twice by then. You need to know which nine they read.

Version history gives you that, but it's worth understanding exactly how it works, because it's not a Save button.

Snapshots happen when you switch away from a document. Not on every keystroke — that's deliberate, so your history is one snapshot per editing session rather than a thousand slivers of the same paragraph. Click into chapter nine, work, click away: that's a snapshot.

You keep the last ten per document. Older ones drop off as new ones arrive.

So the trick for marking a handoff version is the least sophisticated thing in this article: click into each chapter and back out again before you export. That flush is what writes the snapshot. Do it once, on the chapters that matter, and the state you sent is now a row in the history you can open and read.

Where to find it: the 🕘 button in the editor toolbar, or right-click a document in the binder.

Two snapshots happen without you asking, and both exist so a mistake isn't permanent:

- Restoring an old version takes a safety snapshot of the current one first, so restoring to the wrong version is itself undoable.

- A find-and-replace across a whole book or series backs up every affected document before it touches anything.

---

Step 3 — Export the EPUB

📤 Export / Import in the toolbar → Export book as EPUB…

You'll get the confirmation box. Read it once, then confirm. You'll also be offered a cover — your book's own, one from the gallery, or skip it.

Why EPUB for readers specifically: it reflows. Your reader opens it on a phone, a Kindle, a tablet, whatever they actually read on, at whatever text size their eyes need. A PDF makes them pinch and scroll on a page sized for paper, and a reader fighting the file is a reader who stops. That matters more than it sounds when the entire question you're asking is where did you put it down.

DOCX if they want to leave tracked comments. PDF if it's going to a printer or a contest.

---

Step 4 — Or skip the file entirely: the Reading Room

Here's the option that changes the shape of this workflow. You don't have to wait three weeks for four friends to get round to it.

🛋️ The Reading Room. Five readers. One honest verdict.

This is not another editing room, and the distinction is the whole point. It doesn't edit, diagnose, or improve your prose. It answers a narrower and more commercially useful question: what happens inside a real reader's head while they read this, and where do they stop.

Five readers and a moderator:

- MIRA — your target reader. Dead centre of your audience, buys in this category, knows what she came for. She's watching expectation match, satisfaction, whether she'd buy the next one. She's barred from craft vocabulary entirely.

- THEO — the genre veteran. The only seat allowed to name genre, and the keeper of the promise ledger: what your genre promised and whether you delivered it. If you've set a genre on your book, that pack becomes his ledger verbatim.

- JUNO — the drift reader. Tired, distracted, reading with the telly on, quits easily. She's the abandonment sensor, and she's forbidden from charity. Her stop point is described as the single most valuable output in the whole report, and I'd agree — no friend will ever tell you the exact paragraph where they lost interest.

- RHYS — the hostile reader. He writes your two-star review so you can read it before a stranger does. He carries a standing quota: name a deal breaker with evidence, or state why this isn't a two-star book. A neutral shrug is not an acceptable answer from him. He's barred from cruelty aimed at you, from inventing flaws that aren't in the text, and from mocking your subject matter. You can mute him — and the mute gets recorded and disclosed in the report, which I think is exactly right.

- DELLA — the emotional reader. Attachments and losses, setups and payoffs, the scene she'd reread. No structural vocabulary, no plot-hole hunting.

- ARBITER — the moderator, who never reads the manuscript. Turns five reactions into findings. Forbidden from adding an observation no seat reported, from softening anything, and from inventing agreement between readers who disagreed.

What it hands you

Three things: a Panel Report (reader reports, consensus and divergence, genre fit and shelf placement, an engagement and DNF map, predicted reviews and a star forecast), a Revision Roadmap ordered by reader impact against cost to fix, and a Panel Ledger recording every measured value — so that when you come back after revising, the second read is a delta rather than a fresh opinion.

That ledger has a detail I liked: before it calls an old problem fixed, it compares a hash of the chapter. If the chapter didn't actually change, the finding is reader variance, not a fix. It won't let you take credit for a sentence you never rewrote.

The bit that catches people

The Reading Room reads B, not ¶.

Your export ships what's ticked for print. The panel reads what's ticked into AI context. Two different boxes, two different audiences, and getting them confused is how you either hand the panel half a book or hand it your outline as though it were chapter one.

So before you open the room: tick B on the chapters you want read, and off on everything else. Your Story Bible is worth leaving on — it helps ARBITER tell a dropped thread from a deliberate one. An Ideal Reader Profile is described as the single biggest quality gain available, because it's what aims MIRA properly.

Two practical limits

Word counts. A full panel read wants 10,000 words or more. Between 1,500 and 9,999 you get Chapter Mode — full reactions, but no DNF map and no star forecast. Under 1,500 words the panel declines to read at all rather than produce a watered-down report, which is a refusal I respect.

Alpha or beta emphasis. Alpha weights structure, premise, stakes and arc. Beta weights immersion, clarity, dialogue and payoff. It's a weighting, not a different product — every seat still reports either way.

And what it won't do: line edit, copy edit, rewrite, make any revision at all, report a number it didn't measure, or suppress a finding because you asked it to. The panel reports. You decide.

On plans: the Reading Room sits in the Pro tier, alongside the other reporting and critique rooms.

---

Step 5 — Bring feedback back as notes, never over the manuscript

Whatever comes back — a panel report, an email from your sister, tracked changes in a DOCX — the rule is the same.

Make a new document. Don't type it into your chapter.

Add a Note in the binder, one per reader, titled so you'll recognise it in six months: Beta — Dana — ch 1-12 or Reading Room panel, draft 2. Then:

- Leave ¶ off. Feedback is not part of the book, and an untidy ¶ is how a reader's comments end up in a file you send to someone else.

- Turn B on only while you're actually working the notes. The Writers Room and the Editorial Room can then see the feedback while you revise, which is the point — but a folder of eight old beta reports permanently switched on is just noise crowding out your actual chapters.

Why separate files rather than one big feedback document: readers disagree, and you need to see who said what. Two people bouncing off chapter three is a signal. One person bouncing off chapter three is a person. Merged into a single document, those look identical.

The Reading Room's own ledger follows the same logic — save it, and your next run measures the change instead of starting over.

---

The whole thing, compressed

1. Tick ¶ on chapters, off on everything else. Folders cascade. Check the word count matches the book you think you wrote.

2. Click into each chapter and back out before exporting — that's what writes the version snapshot you'll want when notes arrive three weeks late.

3. Export EPUB for readers. DOCX if they'll comment, PDF if it's being printed. Never Markdown or plain text for a person — those carry your whole binder, by design.

4. Or open the Reading Room and get five readers immediately. Tick the chapters into B first — that's the box the panel reads, not ¶.

5. Bring every response back as its own Note. ¶ off, B on only while you're working it.

The step people skip is 1, because the boxes are already ticked and it looks done. The step people don't know they need is 3 — not the exporting, the choosing, because two of the five formats in that menu will hand a stranger your story bible without a word of warning.

And if you only take one thing: the question a beta reader is uniquely able to answer isn't was this good. It's where did you stop. Everything above is in service of asking that cleanly.

6 comments

WorkFlow Wednesday