Getting an edited draft back is a strange experience. The document looks like yours, but sentences have moved, paragraphs have shortened, and a phrase you liked has vanished without comment. Most writers accept the edits and move on, which wastes the best learning opportunity in the process: the edit itself is a personalised lesson in what was not working. Comparing your draft with the edited version, change by change, turns that lesson from a feeling into evidence.

Text and Document Comparison lets you place two drafts side by side and see every change highlighted. This post uses a fictional writer's drafts to show what an editor's changes reveal, and how to turn those revelations into better first drafts.

Start with the shape, not the sentences

Paste your original draft on one side and the edited version on the other, and begin with a broad comparison. Before reading any single change, look at the pattern: how much of the draft is unchanged, where the changes cluster, and whether whole passages moved, shrank, or disappeared. The pattern tells you what kind of edit you received.

Consider Tomas, a fictional blogger at example.org, who wrote a 1,500-word post about balcony gardening and received an edited version back. The comparison shows that the introduction and conclusion are almost untouched, while the middle third is heavily changed: several paragraphs are shorter, two have swapped order, and one long example has been cut entirely. That pattern already teaches something: Tomas's openings and closings work, but his middles wander. Without the diff, he might have concluded the whole draft needed work, or that it needed none. The pattern says something more precise: the middle is where his writing loses its thread.

Also note what was not changed. Unchanged passages are evidence of what already works. Writers tend to focus on corrections and ignore the stretches an editor left alone, but those stretches are the standard to match elsewhere. If your introductions survive editing untouched, study what makes them different from your middles.

Read the edits as a list of habits

Now read the changed passages at word level, and sort the edits into habits rather than treating each one as a separate event. Editors repeat themselves, because writers repeat themselves. Tomas's diff, read this way, shows four recurring edits: long sentences split in two, repeated words replaced, throat-clearing openings deleted ("It is worth noting that," "In today's world,"), and passive constructions turned active.

Each recurring edit names a habit. Tomas writes long sentences that carry two ideas; he repeats a favourite word until it blurs; he warms up with empty phrases before his real point; he hides the actor in passive sentences. None of these is a mystery once listed, and each one is fixable in the next draft by a simple check: one idea per sentence, a search for his repeated word, deleting the first sentence of each paragraph to see if it is needed, and asking "who does this?" of every passive verb.

This is the real value of comparing drafts. A single edit corrects one sentence. A list of repeated edits diagnoses the writer. Tomas's next draft will still have problems, but they are less likely to be these four, because he now knows to look for them before sending anything to his editor.

Worked example: one paragraph, before and after

Here is a fictional paragraph from Tomas's draft, and what the diff reveals about it. Original: "It is worth noting that in today's world, many people who live in apartments are increasingly finding that the utilisation of small balcony spaces for the growing of herbs is something that can be extremely rewarding and also very practical for everyday cooking purposes."

Edited version: "Many apartment dwellers grow herbs on small balconies. It is rewarding, and the herbs are useful for everyday cooking." The diff highlights the deleted throat-clearing, the replacement of "utilisation of small balcony spaces for the growing of herbs" with "grow herbs on small balconies," and the split of one long sentence into two shorter ones. The meaning is unchanged. The word count falls from 42 to 19, and every remaining word earns its place.

Tomas's lesson from this one paragraph generalises: his first drafts say things in the longest possible way, and his editor's job is largely compression. Knowing that, he can compress his own next draft before sending it, by asking of each sentence whether a shorter version says the same thing. The editor's time then goes to ideas and structure, which is what an editor is actually for, instead of sentence trimming the writer could have done himself.

For a related guide on making drafts easier to read, see how to improve readability.

Make the comparison a habit, not a one-off

A single comparison teaches you about one draft. A series of comparisons teaches you about your writing. Keep your original drafts — not just the published versions — and compare each one with its edited return. Over three or four articles, the recurring edits will stabilise into a short personal checklist, and that checklist becomes your pre-send routine: the five things you check before anyone else reads your work.

The comparison habit also changes how you receive edits emotionally. An edit stops feeling like a judgement on a particular draft and starts looking like data about a pattern. Writers who see their edits as data improve faster, because they stop defending individual sentences and start fixing the habit that produced them. It also makes you a better editor of your own work: once you have seen an editor split your long sentences five times, you start hearing the split point while you write.

One caution: do not chase your editor's style instead of your own. If an editor changes a phrase you deliberately chose — a rhythm, a voice, a joke — that is a conversation, not a correction. The diff shows you what changed; it does not tell you which changes to accept. Keep the ones that serve the reader, and push back on the ones that flatten your voice.

Honest limitations

A text comparison shows what changed, not why. It cannot tell you whether an edit improved the piece or merely changed it, and an editor's preference is not automatically a rule. Diff tools also work on text: if the drafts differ in formatting, headings, or images, those differences may appear as noise alongside the wording changes, and ignoring whitespace helps only partly. Finally, comparing drafts is a learning exercise, not a substitute for editing judgment — a draft can be heavily edited and still be good, or lightly edited and still miss its point.

FAQs

Should I compare every draft with its edited version?

For the first few pieces with a new editor, yes — that is when the patterns are most instructive. Once your personal checklist stabilises, you can compare selectively, when a piece comes back more heavily edited than usual.

What if my editor changes things I disagree with?

Treat the diff as a list of questions, not verdicts. Accept the changes that serve the reader, and discuss the ones that affect voice or meaning. An editor expects that conversation; it is part of the job.

Can a diff show me my repeated words?

Indirectly, yes. If the same word is repeatedly replaced in the edited version, the diff makes that pattern visible across the document. A dedicated repetition check, though, will find repeats the editor missed as well.

Does comparing drafts work for non-fiction only?

No. Fiction, essays, reports and emails all benefit. Any writing that passes through another person's hands carries the same diagnostic information in its edits.

If your drafts are data files rather than prose, JSON Studio compares JSON structures, and Word Counter checks length and keyword density before you send a draft out.

human review pending client designation