How I Edit My Manuscripts Step-By-Step 📚✨
Based on Mariana Vieira's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.
Use a dedicated physical “book notebook” per manuscript to store worldbuilding and characterization material that may not appear on the page but strengthens texture.
Briefing
Mariana Vieira’s manuscript-editing workflow is built around one goal: catch the kinds of problems that slip past fast drafting—structure gaps, consistency errors, and weak connections—by moving the work through multiple tools and reading modes. She starts with “book notebooks,” physical brain-dump notebooks for each manuscript, where she stores worldbuilding details, character backstories, political systems, and other material that may never appear directly on the page but still adds texture. When revision time comes—such as after receiving an agent’s notes—she scans the main topics needing attention and records them in the notebook to estimate the scope of the work.
From there, she transfers those revision conclusions into a spreadsheet designed for story-level tracking. The spreadsheet includes a “Beat Map plotter” that outlines story beats chapter by chapter, including when each beat occurs and how it lands in page and word-count terms. She also maintains a dedicated edits list, where each change is tied to a chapter and marked with a status (done, needs to be done, in progress, or cancelled). This structure matters because it makes revisions shareable with her agent—spreadsheets are easier to send than photos of paper notes.
Next comes the developmental editing pass inside Scrivener. She uses Scrivener’s binder to scan chapters and names them with one-line summaries of what happens in each chapter. For chapters requiring major revision, she adds a prominent red marker (a big red circle) so the heavy-lift sections stand out. She then works through the manuscript in order, even if that means revisiting chapters in between, to ensure the overall story still holds together.
Once the major edits are complete, she exports the manuscript to Microsoft Word using the manuscript format and Times New Roman. In Word, she performs a formatting check and then re-runs her spreadsheet checklist to confirm each planned edit actually made it into the document. This step often surfaces export-related issues—especially consistency problems or tie-pose errors—so she treats Word as a quality-control checkpoint before sending anything onward.
After that, she switches to a reader’s mindset by sending the Word document to her Kindle and reading the full manuscript like a leisure book rather than hunting for line-level fixes. She uses Kindle annotations to mark where changes should happen later, drawing lines and leaving notes that guide the next revision round. She also highlights sentences she believes can be cut to reduce word count without harming plot, dialogue, or flow.
Finally, she creates a buffer between the Kindle read and the correction pass on her laptop—typically a couple of days, or up to a week when possible, otherwise at least a few hours or the next morning. She then revisits the annotated pages, corrects typos and issues in Word, ensures everything is clean except Track Changes, and sends the updated file to her agent. The through-line is deliberate repetition: because she drafts and reads quickly, she builds in extra rounds to catch small problems and preserve smooth narrative flow.
Cornell Notes
Mariana Vieira’s editing system uses a physical “book notebook” for manuscript-specific brain dumps, then converts revision priorities into a structured spreadsheet and executes major developmental edits in Scrivener. She exports to Microsoft Word for formatting and checklist verification, since export can introduce consistency or tie-pose errors. To catch connectivity problems and typos without slipping into line-edit mode, she reads the manuscript on a Kindle like a normal reader, using annotations to flag what needs fixing later. After a short buffer period, she transfers those Kindle notes back into Word, cleans up errors, and sends the Track Changes document to her agent. The workflow matters because fast drafting requires multiple passes to maintain consistency and story flow.
Why does Vieira keep a separate “book notebook” for each manuscript, and what does it contain?
How does the spreadsheet function during editing, and what are its key components?
What role does Scrivener play, and how does she decide which chapters need heavy revision?
Why does she re-check the manuscript in Microsoft Word after exporting from Scrivener?
What’s the purpose of reading on Kindle, and how does Kindle annotation feed back into revision?
How does she manage timing between Kindle reading and laptop corrections?
Review Questions
- How do the “Beat Map plotter” and the edits checklist complement each other during revisions?
- What kinds of issues does Vieira say she often finds after exporting into Microsoft Word?
- Why does she avoid line-editing while reading on Kindle, and how do annotations change the next revision pass?
Key Points
- 1
Use a dedicated physical “book notebook” per manuscript to store worldbuilding and characterization material that may not appear on the page but strengthens texture.
- 2
Translate notebook conclusions and agent notes into a shareable spreadsheet with a Beat Map plotter and a chapter-linked edits list.
- 3
Mark high-impact chapters in Scrivener (e.g., with a red circle) so developmental edits focus where they’re most needed.
- 4
After exporting to Microsoft Word, run a formatting check and re-verify every planned edit from the spreadsheet to catch export-related consistency problems.
- 5
Read the manuscript on Kindle like a normal reader to detect connectivity and flow issues without slipping into line-edit mode.
- 6
Use Kindle annotations to create a concrete to-do list, then correct those items in Word after a short buffer period.
- 7
Build extra rounds into the process if drafting and reading happen quickly, since speed increases the need for repeated checks.