Published September 7, 2026.
A refresh should begin with a reason a reviewer can inspect. An evidence ticket prevents teams from changing dates or prose merely because a page feels old.
State the trigger
Attach the source of the concern: a changed product screen, expired statistic, new official guidance, repeated reader question, declining query fit, or broken workflow. Include the observation date and affected passages.
Bound the proposed change
Specify whether the work is a correction, source replacement, structural rewrite, or expansion. Define what will remain untouched. Preserve the original publication date; use the site's truthful modification mechanism only when the revision warrants it.
Close with proof
After release, compare the intended diff, visible dates, structured data, canonical, links, and images. Record limitations such as noisy performance data or an unresolved expert judgment.
The operator may fix objective defects. Changes to claims, positioning, or audience belong with the content owner. This division keeps the routine fast without allowing maintenance to rewrite editorial history.
