
Test the diagnosis
Use crawls, search reports, release history, and page comparisons to check the explanation. Avoid treating one tool score as a complete diagnosis. Check the destination as well as the message that sends people there.
Specify the change, reason, owner, and acceptance check. Developers and editors need actionable instructions rather than broad labels. Choose the next task from the review rather than repeating the calendar.
- A written brief
- Named responsibilities
- Agreed review points




