Stale content often remains visually polished. A useful inventory makes volatile facts, evidence, ownership, and consequences visible before deciding whether to update, combine, redirect, or retire a page.

Finish with

Outcome

A small content inventory ranked by change frequency, consequence of error, and uncertainty, with an explicit action and review trigger for each page.

What you need

  • A list of public URLs from navigation, a sitemap, search, analytics, or manual browsing.
  • People or records that can verify important facts and clarify page ownership.
  • A worksheet that can preserve source locations and dates.
  • Permission to recommend changes, while recognizing that deletion or redirection may require separate authority.

The observable problem

An old date is easy to notice. A former staff name, changed eligibility rule, obsolete form, or outdated emergency instruction may look current. Search terms can discover candidates, but each fact still needs comparison with an authoritative record.

This guide uses a transparent house method, not a research-backed risk score. Rate change frequency, consequence of error, and uncertainty as low, medium, or high. The ratings help order review work; they do not calculate legal risk or prove that one page matters more than another.

Invented for instruction

Fictional worked example

Fictional worked example: East Mere Workshop is an invented community space. Its inventory includes an event page, emergency closure instructions, a staff listing, and a history page. The records and outcomes are illustrative, not measured findings.

The completed rows are: event page, high change, medium consequence, high uncertainty, event has ended, archive now; emergency page, medium change, high consequence, medium uncertainty, verify contact chain today; staff page, medium change, medium consequence, high uncertainty, confirm names; history page, low change, low immediate consequence, low uncertainty, keep with a trigger tied to new archival evidence.

The emergency page has low traffic, but it remains high priority because a rare visit can occur when accurate instructions matter most. The event page receives an archive action because its purpose has ended. The staff page stays public only after current names and ownership are confirmed.

Procedure

  1. Build a bounded URL sample

    Start with primary navigation, top task pages, recent announcements, policy pages, and pages containing dates or contact details. State what the inventory omits. A bounded sample completed today is more useful than an imaginary complete inventory that never reaches review.

  2. Mark volatile facts and evidence

    For each page, identify names, prices, dates, hours, providers, forms, addresses, policies, schedules, and words such as current. Record where each important fact can be verified and when that source was checked. Unknown evidence is a finding, not permission to rely on memory.

  3. Assign ownership and transparent ratings

    Name a person or role able to confirm accuracy. Rate change frequency, consequence of error, and present uncertainty as low, medium, or high, with a short reason. Do not multiply the ratings into a false precision score.

  4. Choose update, combine, redirect, or retire

    Update a useful page whose facts or presentation need repair. Combine genuinely duplicative pages when one destination can serve both tasks. Redirect only to an equivalent replacement. Retire a page when its purpose has ended and preserve records when policy or law requires it.

  5. Attach event-based review triggers

    Use a staff change, price change, provider change, event completion, form replacement, or policy revision as a trigger. A calendar date may supplement the trigger for important pages, but a universal annual date should not replace observation of real changes.

Reusable worksheet

Stale-page inventory. The ratings are transparent editorial prompts, not a validated risk model.
URL and purposeOwnerVolatile factsLast verified and evidenceChange, consequence, uncertaintyDependenciesAction and trigger
/events/autumn-repair/, promote one eventEvents roleDate, booking stateUnknown; event calendarHigh, medium, highHomepage cardArchive; event completion
/emergency/, closure instructionsOperations rolePhone, processLast month; signed procedureMedium, high, mediumPrinted noticesVerify; provider or policy change
/people/, identify contactsAdministration roleNames, roles, emailUnknown; staff recordMedium, medium, highContact pageUpdate; staff change
/history/, organizational backgroundArchive roleDates, namesThis year; catalog recordLow, low, lowAbout pageKeep; new archival evidence

Decision rules

  • If a page remains useful but contains a wrong or uncertain fact, update it and retain the evidence record.
  • If two pages serve the same task and can share one complete destination, combine them and repair inbound links.
  • If a genuinely equivalent replacement exists, use an intentional redirect after checking the full reader task.
  • If purpose has ended and no retention duty applies, retire the page with an honest missing or removed response.
  • If traffic is low but the consequence of wrong information is high, keep traffic from becoming the retirement rule.

Limitations and escalation

  • This worksheet cannot establish legal retention duties, records-management requirements, contractual obligations, or organizational authority to delete content.
  • A URL sample can miss orphaned pages, alternate hosts, files, localized versions, application states, or content excluded from search.
  • Ratings depend on current knowledge. Record uncertainty and seek a responsible owner rather than treating the table as objective measurement.

Review list

Check the work

  • The inventory states its boundaries and includes high-value and time-sensitive pages.
  • Volatile facts have an evidence location and verification date or are marked unknown.
  • Every important page has an owner or an explicit ownership gap.
  • Ratings include reasons and are not presented as research or a compliance score.
  • Each action accounts for inbound dependencies and a real review trigger.

Review again when

  • A staff or provider change
  • An event ends
  • A price, policy, form, or schedule changes
  • A new sitemap or orphan-page report appears
  • A retirement or redirect is proposed