I kept running into the same problem.
Someone would send me a draft — a blog post, a product description, a pitch. The writing was fine. But it was full of small inaccuracies: numbers slightly off, context missing, a claim that sounded plausible but wasn’t quite right.
I knew the correct version. I just needed to get it into the document.
The back-and-forth problem
The standard workflow is a loop: you read, you comment, you send it back, they revise, you re-read. Each cycle takes time and introduces new decisions. Half the time the writer doesn’t have enough context to make the correction precisely — so you end up rewriting it yourself anyway.
What I actually wanted was simpler: point at the sentence, say what’s wrong, have it fixed. No loop.
Corrections are different from edits
There’s a distinction that most writing tools ignore.
An edit is a judgment call — make this shorter, change the tone, restructure the argument. The writer is the right person for that.
A correction is a fact: the number is 35%, not “significantly.” The growth came from Instagram, not “new marketing channels.” The product launched in February, not Q1.
Corrections are precise. They belong to the person with the knowledge, not the person with the words. That’s usually the founder, the subject-matter expert, the client.
What Redraft does
You open the document and describe the correction out loud, at the exact point where it belongs.
“That number is wrong — it should be 35% quarter-over-quarter.”
“Mention that this came from the Instagram launch specifically, not a general campaign.”
“That’s not accurate — we didn’t reduce costs, we restructured how they’re allocated.”
Redraft applies the change in place. The surrounding text stays intact. You move to the next thing.
No comments thread. No re-send. No explaining context to someone who wasn’t in the room.
Try it on a real draft
Open the editor, load a document, and say what should change.
Why voice
When you’re reviewing text for factual accuracy, you’re not composing — you’re reacting. The thought arrives fully formed: that’s not right, here’s what it should say.
Voice matches that. You say the correction the moment you notice the problem. The document updates. You keep reading.
Typing breaks the flow. You stop, switch to keyboard, locate the sentence, select it, retype. By then you’ve lost the thread.
The underlying model
Documents in Redraft are stored as independent blocks — each paragraph, heading, and list item has its own ID. When you give a correction, it applies to the specific block you’re pointing at. Nothing else changes.
This matters because precision is the whole point. A correction to one sentence shouldn’t touch the sentences around it.
Who this is for
Anyone who reviews text written by someone else and needs to inject knowledge the writer didn’t have.
Founders reviewing copy. Experts correcting articles. Clients giving feedback on drafts. Anyone who knows the right answer and just needs to get it into the document.