Reviewing & Approving Work
Nothing the Engine produces goes live without you. Your reviews happen in three places: Mission Control’s “Waiting on you” card points you at anything needing a decision, the Tasks queue holds proposed work, and the Activity feed holds finished work.
Approving Proposed Work
Audits and plans don’t act on their own — they generate tasks that wait for your decision. Technical fixes can be approved right from the audit report (Approve task next to each finding); everything lands in the Tasks tab too. For each task you can:
- Approve — the Engine starts working on it.
- Revise — describe what to change about the brief and the Engine rewrites it (takes ~20–30 seconds).
- Edit — adjust the title or context yourself, or attach a brief.
- Dismiss — not worth doing; remove it.
Select multiple tasks with checkboxes to approve or dismiss in bulk, and set the destination or branch for the whole batch at once.
After an audit finishes, click Review & approve tasks on the audit card — it jumps you straight to that audit’s findings so you can triage them in one pass.
Reviewing Finished Work
When a job hits Ready for Review, its card in the Activity feed shows actions matched to where the work went:
- View PR — open the pull request on GitHub and review it there.
- View Changes — see before/after previews of CMS edits.
- View Report — read an audit’s executive summary and findings.
- View Content / Copy Content — for drafts delivered directly in the app.
The final step happens on your platform: publish the draft in your CMS, or merge the pull request on GitHub.
Requesting Changes
Don’t edit around the Engine — tell it what’s wrong. Ask in the command bar (e.g. “make the intro of that draft punchier”) and it revises the same draft in place: the same branch and pull request, the same Doc, or the same CMS post. Each revision keeps the history threaded together in the Activity feed.
When you request changes, the Engine extracts the durable rule behind your feedback and saves it as a learned rule in the Brand voice tab — so it stops making the same mistake. See Teaching the Engine.
Sending Work Onward
A draft delivered in one place can be pushed to another. Finished jobs offer buttons like Send to GitHub, Send to WordPress, or Create Google Doc — useful when a draft was reviewed in a Google Doc and is now ready to become a CMS draft or pull request.
If reviewers edited or commented on the Google Doc, the Engine picks those changes up when pushing onward — the Doc is the source of truth.