# Content Refresh Brief

Define a focused update from obsolete claims, changed reader needs, performance evidence, search intent, product changes, and maintenance risk.

## Usage note

Refresh a page because evidence shows a reader, accuracy, product, or maintenance need—not simply because a date is old. Preserve a versioned baseline so changed performance can be interpreted responsibly.

## How to use this template

1. Restate the page's intended reader task and collect current content, source, product, and performance evidence.
2. Diagnose accuracy, usefulness, intent, overlap, discovery, and maintenance problems separately.
3. Define the refresh's original contribution and a line-by-line keep, update, add, remove, and verify scope.
4. Assign sources, reviewers, dependent technical changes, QA, and a versioned release plan.
5. Publish, inspect the live result, and monitor against a dated baseline and update trigger.

## Blank template

### Asset and baseline

- **Page title and URL:** [Enter]
- **Current version or last material update:** [Enter]
- **Owner:** [Name/team]
- **Primary reader task:** [Describe]
- **Current unique value:** [Evidence, tool, process, example, other]
- **Measurement period and comparison:** [Enter dates]
- **Search query/page evidence:** [Summarize]
- **User feedback or support evidence:** [Summarize]
- **Indexing, canonical, and technical status:** [Record]

### Refresh diagnosis

- **Obsolete or unverifiable claims:** [List exact passages]
- **Changed product or policy behavior:** [List]
- **Unanswered reader questions:** [List with evidence]
- **Intent or audience drift:** [Describe or None]
- **Internal overlap:** [URLs and task comparison]
- **Weak structure or examples:** [Describe]
- **Discovery or engagement concern:** [Describe without assuming cause]
- **Maintenance risk:** [Owner, source, or review gap]
- **Decision:** [Refresh / Merge / Redirect / Retire / Leave unchanged]

### Change map

Duplicate for each material section.

- **Section or element:** [Enter]
- **Action:** [Keep / Update / Add / Remove / Verify]
- **Reason:** [Reader, evidence, product, search, accessibility, other]
- **Required source:** [Owner and due date]
- **Proposed contribution:** [What useful change will result?]
- **Risk if changed incorrectly:** [Describe]
- **Reviewer:** [Name/role]
- **Acceptance condition:** [Observable result]

### Publication plan

- **Title, description, or heading changes:** [List]
- **URL decision:** [Keep / Migrate with plan]
- **Internal links and navigation:** [Updates]
- **Canonical, redirect, sitemap, and schema:** [Updates or None]
- **Localization impact:** [Locales and source-lock date]
- **Fact and expert review:** [Owners]
- **Accessibility and responsive QA:** [Owner]
- **Release date and final approver:** [Date, name]

### Measurement and maintenance

- **Baseline reference:** [Saved report or notes]
- **Expected reader outcome:** [Describe, not a ranking guarantee]
- **First and second review dates:** [Enter]
- **Search, engagement, or completion signals:** [List]
- **Confounding changes to annotate:** [Campaign, release, season, migration]
- **Next maintenance trigger:** [Product, source, policy, or scheduled date]
- **Responsible owner:** [Name/team]