Find the job
Ask what the paragraph is supposed to do: define, persuade, summarize, compare, explain or transition. The rewrite must do the same job.
Paragraph rewriting is about structure, not wording. Each sentence should earn its place: setup, evidence, consequence, transition. A rewrite that loses that order reads worse — no matter how smooth it sounds.
What to do
A paragraph has a job, a spine and an ending. Check all three; most rewrites break at least one.
Ask what the paragraph is supposed to do: define, persuade, summarize, compare, explain or transition. The rewrite must do the same job.
Keep the main claim and its evidence close to verbatim, then rewrite the supporting sentences around them.
A strong paragraph ends with a consequence, not a vague summary. If the last sentence restates the first, cut it.
Worked example
Remote work offers numerous benefits for organizations. It can improve employee satisfaction and reduce overhead costs. Many companies have adopted flexible policies. Overall, remote work represents an important trend in the modern workplace.
Remote work cuts two costs at once: office space and attrition. Companies that kept flexible policies after 2023 report lower turnover in exit surveys, and smaller leases show up directly in operating expenses. That is why the policy debate is really a cost debate.
The rewrite keeps the claim but gives it a spine — two named costs, one source of evidence, and an ending that states a consequence instead of “overall, this is important”.
Prompt
Rephrase this paragraph. Its job is to [persuade / explain / summarize / compare]. Keep the main claim and all evidence exactly as written. Improve flow and cut filler, but keep the logical order: setup, evidence, consequence. End with a consequence, not a summary. Paragraph: [paste paragraph]
Paragraph jobs
Diagnose the job first — each one has a shape the rewrite should respect.
| Job | Shape | Rewrite focus |
|---|---|---|
| Define | Term → plain meaning → boundary case. | Cut history and etymology; keep the boundary case, it does the real work. |
| Persuade | Claim → strongest evidence → objection handled → consequence. | One claim per paragraph. If there are two, split the paragraph. |
| Summarize | Conclusion → the two facts that carry it. | Kill list-like recitals; a summary ranks, it does not enumerate. |
| Compare | Criterion → A → B → verdict on that criterion. | Organize by criterion, not by item — otherwise readers do the comparison themselves. |
| Transition | One sentence: close the old thread, open the new one. | If a transition needs a full paragraph, the document order is wrong. |
Flow
AI rewrites usually connect sentences with additive glue: “additionally”, “furthermore”, “moreover”. Additive glue is a sign that the sentences are stacked, not linked — you could shuffle them and nothing would break. Human paragraphs run on causal and adversative glue: because, so, but, instead, which is why. After any rewrite, check the joints. If every sentence could trade places with its neighbor, the paragraph has no argument yet, only content.
The quickest repair is the old-to-new pattern: start each sentence with something the reader already knows from the previous one, and end it with the new information. “The pilot cut ticket time by 22%. That 22% came almost entirely from auto-drafted replies. Auto-drafting, however, only works when the knowledge base is current.” Each sentence hands the next one its opening. When a paragraph reads smoothly aloud, this pattern is almost always why.
One more check that catches subtle damage: count the claims before and after. A four-sentence paragraph making three claims should still make three claims after the rewrite — not two (something got smoothed away) and not four (something got invented). Claim-counting sounds pedantic and takes fifteen seconds; it is the cheapest integrity test there is for paragraph-level editing.
Second example
Customer feedback is essential for product development. We have received various feedback from our users over the past quarter. Some feedback was positive while other feedback highlighted areas for improvement. We plan to incorporate this feedback into our roadmap going forward.
Q2 feedback clustered around one theme: export. Forty-one of sixty tickets asked for scheduled exports, and two enterprise renewals named it a condition. We moved scheduled exports to the top of the Q3 roadmap and told both accounts a date. The rest of the feedback was positive but low-signal — nothing else appeared more than four times.
The draft had a shape (“feedback exists, some good, some bad, we will act”) that said nothing. The rewrite keeps the same job — summarize feedback, state the action — and fills the shape with counts, a decision and a consequence.
FAQ
It is when a rewrite turns a structured argument into a list of equally-weighted smooth sentences. The words improve but the logic — this, therefore that — disappears.
No. Identify the main claim and its evidence first, keep those nearly verbatim, and let the rewrite change only the connective tissue around them.
Summarize both versions in one line each. If the summaries differ — or the rewrite is harder to summarize — the argument got lost.
Models like to close with a vague summary sentence. Delete it, or ask for an ending that states a consequence: what changes, who acts, what happens next.
Related