How to rewrite a sentence without changing what it says

You can rewrite a sentence safely as long as four things come out the other side unchanged: who does the thing, by when, how sure it is, and what you committed to. Everything else is yours to move: word choice, clause order, formality, length, rhythm. That is the whole difference between a paraphrase and a rewrite, and it is worth being precise about, because the two produce text that looks equally good and means different things.

Rewording is not rewriting #

A paraphrase preserves what the sentence asserts and changes how it is said. A rewrite is licensed to change what it asserts. Both are legitimate jobs. The problem is that one button often does either, and you cannot tell which you got by looking at the result. A rewrite reads as well as a paraphrase, sometimes better, because dropping a condition makes a sentence cleaner.

Take an ordinary work sentence:

“We can probably deliver the API docs by Thursday if the review comes back on time.”

A paraphrase of it:

“If the review returns on schedule, we should be able to deliver the API documentation on Thursday.”

Different word order, different vocabulary, one clause promoted to the front. The agent is still we, the deadline is still Thursday, the certainty is still hedged (probably became should be able to), and the condition is still attached. Nothing you would be held to has moved.

Now a rewrite, of the sort a “make it punchier” pass produces:

“The API docs will be delivered Thursday.”

Six words, and three separate things are gone: the condition, the hedge and the agent. The first version says we might, if. The second says it will. If the review is late, the first sentence was accurate and the second one was a broken promise. Nobody wrote a false statement on purpose; the tool was asked to be direct, and hedges and conditions are what stands between a sentence and directness.

What actually changes when you change register #

Register is not a coat of paint over fixed content. Shifting it moves three dials, and each one can carry meaning. Knowing which three is what turns “this feels off” into something you can check.

Hedging

Probably, should, roughly, I think, around, up to, in most cases. These are the smallest words in any sentence and the first to be cut, and they are frequently the only thing standing between an estimate and a guarantee. Formal registers tend to add hedges; concise registers strip them; confident registers strip them deliberately. Compare:

• Original: “The migration should take around four hours.”
• Confident: “The migration takes four hours.”
• Safe paraphrase: “We expect the migration to take approximately four hours.”

The middle one is a different claim. It is also the one that reads best, which is the trap.

Agency

Who did the thing, and who is on the hook for the next thing. Voice changes move this without touching a single fact:

• “We have not received your signed contract.”
• “Your signed contract has not been received.”
• “You have not sent the signed contract.”

All three describe the same missing document. The first puts the gap on the writer's side, the second on nobody's, the third on the reader's. A tool asked to make the sentence more direct will reliably hand you the third, and the third is the one that starts an argument.

Directness

In English, politeness lives mostly in grammar: a modal, a question mark, a past tense used as distance. That means a register change alters how much pressure the sentence applies, even when the request is identical.

Casual to formal, using a real pair FixMeBot returns: “Hey, just checking if you got a chance to look at the thing I sent?” becomes “I wanted to follow up on the document I shared and ask whether you have had a chance to review it.” Note what moved. The thing became the document, which is a small content addition if you had sent two things. Just checking is a minimiser doing real social work, and it disappeared. And the direct question became an indirect one, which lowers the pressure. The formal version is not the casual version in a suit; it applies less force and is more specific.

Verbose to concise, the other direction: “At this point in time we are of the opinion that it would probably be best if we were to postpone the meeting until next week” becomes “We would rather move the meeting to next week.” Twenty-eight words to eight, no facts lost. But probably is gone, and we are of the opinion that it would be best (a recommendation) became we would rather (a preference). Almost always fine. Occasionally that gap is the entire message.

The four ways a paraphrase loses the meaning #

Practically every meaning-losing rewrite is one of these four. They are worth memorising because they are what the four-question check below is checking for.

1. A dropped qualifier that was carrying the meaning

“We support up to 15,000 characters per request” becomes “We support 15,000 characters per request.” “Roughly 40 accounts were affected” becomes “40 accounts were affected.” The qualifier looked like padding to a shortening pass and was a ceiling and an estimate respectively. Numbers attract this failure more than anything else, because a bare number reads cleaner than a bounded one.

2. Inverted agency

“We were not able to reproduce the issue with the steps provided” becomes “The steps you provided did not reproduce the issue.” Same event, and the blame moved across the table. Watch for this specifically in customer-facing writing, where the passive was often deliberate.

3. A lost condition or commitment

Any if, once, assuming, subject to or provided that is load-bearing, and every one of them is a clause a concision pass can delete without leaving the sentence ungrammatical. This is the failure with actual consequences, because the resulting sentence is a promise in writing.

4. A term of art flattened into a synonym

Terminate is not end in a contract. A regression is not a problem in a release note. An invoice is not a bill in accounts payable, and indemnify has no synonym at all. General-purpose rewriting reaches for the more common word, which is the right instinct everywhere except inside a domain, where the rare word was chosen because it means something the common one does not. If you have highlighted a clause you are not sure about, ask what it means before you paraphrase it.

A four-question check before you send #

Run these against the new version and compare each answer with the original. It is quicker than reading both texts, and much more reliable, because reading two versions side by side makes you see what you meant rather than what you wrote.

1. Who does it? Name the subject of every action out loud. If a passive became active or an active became passive, someone changed places.
2. By when, and on what condition? Every date, deadline, if and once in the original should still be findable in the new version. Missing ones are not style edits.
3. How certain is it? Count the hedges in each version. The number does not have to match, but a drop from two to zero is a change of claim, not of tone.
4. What did I just promise? Cover the original and read only the rewrite. Write down the obligation it creates in your own words. If that sentence is bigger than the one the original created, do not send it.

A fifth question applies when the text was not yours to begin with: would the person who wrote it recognise their point in your version? Paraphrasing someone else's argument to summarise it is the one case where a rewrite is not just risky but wrong.

Length is a separate instruction #

Changing register changes length as a side effect, and side effects do not hit targets. A formal paraphrase is usually longer than the original because formality is built from modals, indirect questions and full noun phrases. A casual one is usually shorter. Neither will land on 200 characters for a bio or 280 for a post, and asking for “shorter and more formal” in one breath asks for two opposing things.

So split them. Get the register right with paraphrasing, check the four questions, and only then hit the ceiling with length adjustment, which changes the word count and leaves the register where you put it. Two passes you can verify beat one pass you have to trust.

None of this argues against rewriting. Rewriting is often exactly what a sentence needs, and a paragraph you have already redrafted four times is usually one where you have stopped being able to see the problem. It argues for knowing which one you asked for. The version that reads best is not always the version that says what you meant, and the gap between them is invisible until someone holds you to it.