
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. Ask customer-facing staff which details people need before deciding.
Specify the change, reason, owner, and acceptance check. Developers and editors need actionable instructions rather than broad labels. Verify the next step while there is still time to correct a problem.
- A written brief
- Named responsibilities
- Agreed review points




