Inkshift Revision Analysis Overview

You tightened the pacing in Act 2, gave your villain more menacing beats, cut a subplot that wasn't pulling its weight. You hope the story is stronger for it. But hope only takes you so far. You can't go back to previous beta readers because they've already read your book, and you're the person least equipped to check it, because you're the one who just spent three weeks inside the manuscript.
A critique can tell you where your manuscript stands today. It's a snapshot in time. What it can't tell you is whether this version is an improvement, or whether fixing one thing quietly broke another. That's a different question, and it's the one most writers have no good way to answer. That's why we built Revision Analysis.
What Is Revision Analysis?
Revision Analysis is Inkshift's newest feature, and it does something no other tools can do: it looks at two full manuscript drafts instead of one. You upload your previous version alongside your new draft, and Inkshift compares them directly, evaluating how your plot, pacing, characters, and prose have shifted between versions.
Instead of another standalone critique, you get a report built entirely around change. It's priced separately from Critiques, at $25 for a single Revision Analysis or $100 for a five-pack if you know you'll be revising in multiple rounds.
Why a Snapshot Isn't Enough
Here's the thing about a single critique, even a great one: it's a moment in time. It's useful when you're trying to figure out where to start. But once you've made changes, once you're two or three drafts deep, a snapshot stops being the most valuable thing you can get. What you actually need to know is whether the changes you made worked.
This is a hard thing to self-assess. When you sit down to fix your villain, you're watching your villain. You're not watching what happens to the quiet subplot three chapters later, or the pacing in the section you didn't touch, or the secondary character whose one good scene got cut along with the material around it. You can't hold the whole manuscript in your head while you're heads-down inside one thread of it. Nobody can.
That's the gap Revision Analysis closes. It's not just telling you where you are, it's telling you how you got here and whether it worked, which is a far more useful question to answer once you're actually mid-process.
How It Works
The process takes two drafts and turns them into a single, structured report.
Step 1: Select Your Previous Draft
The best way to use Revision Analysis is to reference a past manuscript a critique. That way, the feedback from your last draft can be folded into the new analysis. But if you don't have a previous critique, you can also upload your previous version manually.
Step 2: Upload Your New Draft
Your latest revision, in .txt or .docx format. This is the draft you want evaluated against the one before it.
Step 3: Get Your Comparison Report
Within minutes, Inkshift generates a report that:
- Evaluates changes to plot, pacing, characters, and prose
- Shows what improved, what regressed, and what remains unresolved
- What new issues may have been introduced
- Gives you clear priorities for your next round of revisions
Rather than a generic "here's what's good and bad about this draft," every observation in the report is anchored to the fact that you changed something.
What You'll Discover
The results tend to fall into two buckets, and both are useful in different ways.
Confirmation. Sometimes Revision Analysis simply confirms what you already suspected: yes, the villain reads as more threatening now, yes, that pacing fix in Act 2 worked.
Discovery. The more interesting bucket is the stuff you didn't see coming. You cut a scene to fix pacing, and it turns out that scene was quietly doing setup work for a payoff two chapters later, one you now need to shore up elsewhere. You strengthened your protagonist's arc, and the antagonist, unchanged, now feels underpowered by comparison. You tightened dialogue across the board and, without meaning to, flattened one character's distinct voice along with it. None of these are things you'd catch by rereading your new draft in isolation. You'd only catch them by comparing it to what came before, which is exactly what a single-draft critique can't do and Revision Analysis is built for.
How to Use Revision Analysis Effectively
- Compare against a meaningful checkpoint, not yesterday's tinkering. Run it against the draft you last got real feedback on, whether that was a critique, a beta read, or your last major revision pass. Comparing against a draft from an hour ago won't tell you as much.
- Read the regressions as carefully as the improvements. It's tempting to skim past what didn't work in favor of what did. The regressions are usually the more actionable half of the report.
- Save your drafts as you go. If you opt to retain a manuscript for future comparisons, you build a version history you can check in against at any stage, not just the most recent one.
- Pair it with a fresh critique. Some point along the way, you'll need another fresh critique. Readers experience your book without prior knowledge, so while assessing changes can help you move through your drafts quicker, it's also important to periodically 'check in' from scratch.
Is This Available Anywhere Else?
There are document comparison tools, the kind used for legal contracts or academic papers, that will diff two versions of a text and tell you which words changed. And there are AI writing and editing tools that will critique a single draft of your novel. What doesn't exist anywhere else is a tool built for fiction manuscripts that puts two drafts side by side and evaluates how the actual story changed: whether your plot tightened, whether your pacing improved, whether your characters got stronger or lost something along the way.
Revision Analysis requires understanding both drafts as stories, and we're excited to help authors get from draft to done as quickly as possible.
Ready to see how your last draft measures up? Try Revision Analysis on Inkshift and find out what actually changed.

