5.3 · Reviewing and editing
Highlight a passage and say what is wrong. Annotation is what makes the next draft better.
Review is the step where GrowthOS earns compound interest on your time. When you highlight a passage and say what is wrong, 2 things happen: this draft gets rewritten with your note applied, and notes you mark Yes, learn it become training signal for every draft after. Same minute of effort, paid out twice. That is why review deserves the time that polish does not: this is the step that teaches.
Marking up the draft
Open the Review & Train step. The mechanics are 2 moves:
Highlight and note
Select any passage and write an annotation: a note saying what is wrong with it, or what is right, since positive notes teach the agent (the automated worker that drafts) what to do more of. After you write the note, the composer asks Should we learn from this for next time? Leave it on Decide for me, the default, to let the agent learn the note once the same point repeats; pick No, one-off to keep it to this article; or pick Yes, learn it to mark feedback that should apply across your drafts. Each saved note shows its scope underneath.
Rewrite with Feedback
When your pass is done, click Rewrite with Feedback. Add an overall direction if the draft needs steering beyond the individual notes, and optionally have it fix coverage gaps in the same pass. The agent rewrites in about 1 minute, applying your notes. Once you run the rewrite, the article moves on to the Polish stage.
The coverage rail alongside the draft shows what the page needs to address: must-cover topics, reader questions, term suggestions. It is a checklist for your read, not homework; note what is genuinely missing and skip what is not.
How to annotate well
- Say why, not only what. "Too salesy for a comparison page" trains; "reword this" does not.
- Go after patterns. If the same tic appears 5 times, annotate it once and name it as a pattern. The rewrite applies it everywhere, and so does the training.
- Accuracy notes are gold. They often reveal a context gap; fix big ones in Context too, so they stay fixed.
The training half of the loop
Notes fix drafts immediately, and they accumulate as pending feedback for your Writing Profile, the compiled version of how you sound.
Annotations train nothing until their review is completed. Completing a review schedules the profile update on its own, about 10 minutes later, so there is nothing else to click.
A good rhythm: complete each review rather than leaving it open, then watch the drafts that follow. Fewer notes needed on each is the trend line that shows the training landing, and reviewing is how you bend it.
Bringing in teammates
The Invite feedback step adds reviewers without adding seats:
- Share a public link: generates a URL you can drop in Slack. Anyone with the link can annotate, no login.
- Invite a specific person: by email, optionally with the invite mailed for you.
Guest reviewers see the draft, highlight, and note, then send their review; their notes carry no scope, since guests cannot set it. Their notes come back to this step, where you stay in control: select which reviews deserve applying and click Rewrite from Feedback. The agent rewrites the sections those reviews touch and saves the result as a new version, with your current version kept for comparison or rollback.
This is the right tool for the subject-matter expert who reviews 1 article a month. If someone reviews weekly, give them a seat.
You are done when every passage you would have rewritten carries a note saying why, and the rewrite comes back reading like something your team could have drafted. 1 article reviewed this way is worth 5 skimmed.
Common questions
How long does a review take? 15–30 minutes for early articles, dropping as the profile converges. If reviews are not getting faster after several completed cycles, the notes may be too vague to train on: more why, fewer rewordings.
Do guest annotations train the system too? They join the same feedback stream. You decide which reviews get applied to the draft; what trains the profile follows the same rule as your own notes left to Decide for me: they teach once their review is completed and the same point repeats.
Can I edit the text directly instead of annotating? Not here, and it is deliberate: review is annotation-only so your fixes become signal instead of silent edits. The place for hand edits is Polish, one step later.