Session 8.6: Stage 5: Editing and Refinement

Course → Module 8: The Pipeline

Session 6 of 10

Editing Is Not Writing

AI-assisted editing is fundamentally different from AI-assisted writing. In Stage 3, you generated prose from specifications. In Stage 5, you are directing targeted revisions against a specific list of issues identified in Stage 4. The AI is not creating. It is fixing. And every fix gets re-approved by a human before it stands.

The annotated draft from Review contains tags: [FACT], [VOICE], [STRUCTURE], [ARTIFACT], [MISSING]. Each tag becomes an edit instruction. The instruction must be specific enough that the AI can execute it without guessing.

Writing Effective Edit Instructions

Bad edit instructions are vague. Good edit instructions are surgical.

Bad Instruction	Good Instruction	Why It Matters
"Fix this paragraph"	"Replace the opening question with a declarative statement that directly states the main argument"	The AI knows exactly what to change and what to change it to
"Make it sound more natural"	"Shorten sentences in paragraph 3 to an average of 12 words. Remove the hedging phrase 'it is worth noting that'"	Measurable, verifiable changes
"Fix the facts"	"Replace the claim '73% of companies' with the verified figure from Source 4 in the research brief: '61% of Fortune 500 companies, per the 2025 Deloitte survey'"	Provides the correct information, not just a complaint
"Remove AI artifacts"	"Delete 'it is important to note that' in paragraph 2. Replace the tricolon 'efficient, effective, and engaging' with a single specific adjective"	Points to exact locations and exact fixes

The Edit Cycle

Editing is iterative. One pass rarely catches everything. The standard cycle has three steps.

flowchart LR A["Annotated Draft"] --> B["Write Edit Instructions"] B --> C["Execute via AI"] C --> D["Human Re-Review"] D -- "Issues remain" --> B D -- "Clean" --> E["Advance to Stage 6"] style A fill:#222221,stroke:#c47a5a,color:#ede9e3 style B fill:#222221,stroke:#c8a882,color:#ede9e3 style C fill:#222221,stroke:#6b8f71,color:#ede9e3 style D fill:#222221,stroke:#8a8478,color:#ede9e3 style E fill:#222221,stroke:#c8a882,color:#ede9e3

Pass 1: Fix flagged issues. Work through every annotation from Stage 4. Write a specific edit instruction for each. Execute the edits via AI (or manually for small changes). Re-read the edited sections.

Pass 2: Check for introduced errors. AI edits sometimes fix one problem and create another. A rephrased sentence might fix a voice break but introduce a factual inaccuracy. Read the edited sections again, specifically looking for new issues.

Pass 3: Polish. This is the fine-tuning pass. Transitions between sections, paragraph rhythm, the opening sentence, the closing sentence. Small adjustments that take the content from "correct" to "good."

When to Edit Manually vs. When to Use AI

Not every edit needs AI. Some are faster by hand.

Edit Type	Use AI	Do Manually
Removing a specific phrase		Find and delete. Faster than explaining.
Rewriting a paragraph for voice	Provide the paragraph + voice spec + instruction.
Inserting a verified fact		Copy from research brief. Exact data, no AI involvement.
Restructuring a 500-word section	Provide section + new structure + constraints.
Fixing a transition between sections	Provide both sections + desired connection.
Deleting an entire section		Just delete it. No API call needed.

The rule of thumb: if the edit requires generation (new text, rephrased text, restructured text), use AI with specific instructions. If the edit is mechanical (delete, move, copy, replace with known text), do it manually. Manual edits are faster and introduce zero risk of new AI artifacts.

Tracking Edit Volume

Count the edits per draft. This number matters for two reasons.

First, it tells you whether your upstream stages are working. If every draft needs 30 edits, your research, outline, or voice spec has a gap. Fix the input, and the edit count drops. A well-tuned pipeline produces drafts that need 5 to 10 edits, not 30.

Second, it tells you your editing cost per piece. If each edit takes 2 minutes of human time plus one API call, 15 edits cost 30 minutes and roughly $0.10 to $0.30 in API fees. Multiply that by your production volume, and you have a real cost number for Stage 5.

The quality gate for Stage 5: all review annotations resolved, no new issues introduced, and the content passes the publication test. If you would not put your name on it, it goes back.

Assignment

Take the annotated draft from Session 8.5. For each annotation, write a specific edit instruction following the patterns in this session.

Execute the edits using AI (for generative changes) and manual editing (for mechanical changes).
Re-read the edited sections to check for introduced errors.
Count: how many edits were needed? How many required a second pass?

Document the total edit count and the time spent. Compare the final output to the original draft. Is the difference worth the effort? (It should be. If it is not, your review process in Stage 4 needs recalibration.)

Stage 5: Editing and Refinement