Keep the evidence, the fix and the decision together.
Turn a finding into a task, follow its status and history, and collect the approval before the work is marked done. Keep the next decision visible instead of losing it across drafts and messages.
Free with an account. Sign in when you run it; this page stays open to read.
Move the work. Keep the decision visible.
Illustrative exampleAdvance an example task through review and approval.
A task history and approval inbox for the work.
Illustrative workflow. Done is a manual status, not a live-site check.
Make review a visible step
A draft can be prepared, sent for approval, approved or returned for changes. Keep the relevant evidence and revision history close to the decision so the reviewer knows what is being accepted.
Review approved brand facts before accepting draft language that describes your business.
Know what done means today
Tasks are marked done by hand. The current board does not fetch the delivered page or check that the fix is live. If an existing status says verified, it remains a person-set workflow status rather than independent publication evidence.
The beta publishing integrations prepare a draft or pull request after review; that handoff still does not verify publication.
How it works
- Create a task from a finding or prepared fix.
- Review the draft and collect the approval.
- Record completion and retain the task history.
What to know before you use it
- Completion is set manually.
- Publication and later persistence are not checked.
- Team seats are not built; do not imply a multi-user workspace.
Questions
Does done mean a change went live?
It means a person marked the task done. The app does not currently check publication.
Can a client respond without an account?
The client-share workflow supports a read-only report with approve or send-back actions, using an expiring revocable link.
Keep the work moving across teams.
Agree a senior specialist to direct priorities and review delivery within a defined monthly scope.