Rewriting a draft
The app is at rewr.it/write. Three rewrites a day without an account; more with one. See Plans and quota.
The loop
1. Paste the draft. Anything a model wrote, or anything of yours that reads like it did.
2. Pick a register. Slack, Email, Skip-level / charter, or LinkedIn. The register changes sentence length, formality, and what counts as a tell — em dashes are unremarkable in a charter and conspicuous in Slack. See Registers and modes.
3. Read the report before you press anything. The tells report scores the draft as you type, in your browser, with no network call. Each finding names a span and says what is wrong with it. See Tells and the report.
4. Rewrite. The result streams in. When it finishes you get three things beside it: the rewrite, a diff against your draft, and a fact audit.
5. Push it further, or pull it back.
- Try another — a second rewrite, deliberately different in sentence shape and ordering. Not a source of new facts.
- Closer to original — stays nearer your wording and order, still removes the mechanical tells.
Protecting a span
Select text in the draft and protect it. A protected span comes through the rewrite exactly as written: a product name, a quoted line, a legal phrase, a number you have already checked with someone.
- Up to 20 spans, 4,000 characters total.
- A span that no longer appears in the draft is dropped before the request.
Protect anything you would be annoyed to see paraphrased. It costs nothing.
Notes into prose
Switch the input toggle from Rewrite to Expand and the input stops being a draft and becomes notes. Bullets, fragments, half sentences.
The rule is the same rule in a stricter form: every claim in the output must come from a note. It writes the sentences; it does not supply the content. If a note says "shipped Tuesday", the piece says shipped Tuesday. If no note says who approved it, the piece does not say.
Expand is Pro. A non-Pro account gets 402 with code: "expand_pro".
Checking the facts
The fact audit lists numbers, names, and dates from the draft and shows whether each one survived. It exists because "it does not change your facts" is a claim, and a claim about software should be checkable in the software.
Read it. Especially on anything with a number in it.
The audit compares the draft with the rewrite. It cannot tell you the draft was right. If a model invented the number before you pasted it, the audit will faithfully confirm the invention was preserved.
When to stop
The score does not have to reach zero. A rewrite at "a few tells" that sounds like you beats a clean one that does not. The tells report is a reading aid, not a target to optimise against.