A content archive decision record for a Philippines editorial team

Start with the reader promise

Old content should not disappear because a spreadsheet labels it stale. An article may still answer a useful question, carry external links, or provide historical context. It may also contain guidance that no longer belongs in public. A content archive decision record helps a Philippines editorial team prepare evidence before an owner chooses to retain, revise, redirect, or remove a route.

Create one record per canonical article. Capture the title, route, family, original publication date, last substantive review, current owner, purpose, important sources, internal links, known inbound value, and observed concern. State why the review began. Age alone is a weak reason; a changed claim, duplicate answer, broken reader path, or obsolete service boundary is more actionable.

Compare disposition options

The publisher owns disposition and route behavior. Subject owners decide whether guidance remains accurate, technical owners approve redirects or removals, and service owners review commercial implications. An inventory assistant can prepare options but cannot erase publication history, merge articles, or assume that low measured traffic means no reader depends on the page.

A Philippines-based assistant can inspect the live route, compare current sources, map incoming and outgoing internal links, note duplicates, and assemble a before-and-after summary. They may correct inventory fields. They should not redate an article, replace its canonical, delete assets, or publish a rewritten version without explicit approval and a documented migration plan.

Protect route history

The record should show the observed problem and the evidence for each option. Retention may require no change or a scheduled review. Revision needs scoped claims and sources. Consolidation needs a target that genuinely answers the same reader question. Removal needs a plan for links and route response. Keep uncertainty visible, especially when analytics or backlink data are incomplete.

Bulk cleanup fails when it treats routes as files rather than reader promises. Redirecting every old article to a general Blog page creates a working response but a poor destination. Quietly rewriting and changing the date creates false publication history. Another failure is preserving risky guidance solely because it once attracted traffic. The record must hold both value and harm in view.

Check the surrounding path

Two articles may both discuss handoffs, yet one covers shift continuity and the other covers editorial approval. Similar vocabulary does not make them duplicates. The assistant compares questions, examples, links, and conclusions. The owner may keep both, narrow one, or consolidate only the overlapping section. The decision follows reader intent, not title similarity alone.

Track records reviewed, decisions by disposition, unresolved owner questions, broken paths found, redirects retested, and repeated reasons for review. Do not call removed page count an improvement. Pair counts with examples and post-change checks. A smaller corpus can be easier to maintain, but only if readers still reach the appropriate answer.

Verify the approved outcome

Present the current condition, options, risk of each option, recommended next check, required owners, and decision deadline. After approval, record exactly what changed and verify the public route, canonical behavior, index, sitemap, and important internal links. Preserve the decision record even when the article is removed, because future editors need to know why.

Schedule archive review from evidence signals rather than an arbitrary purge. High-risk and frequently changed guidance deserves closer attention; stable operating explanations may remain useful for years. A careful record slows the deletion decision just enough to protect history, then makes the approved change easier to execute and verify.

Carry out the chosen disposition safely

For a revision, create a bounded brief that names the claims and reader paths under review. Preserve the original publication date unless the site’s documented policy supports another treatment, and use a truthful modified date where appropriate. A refresh is not a newly created article merely because substantial editing occurred.

For consolidation, map every useful section and incoming internal link to the proposed destination. Confirm that the destination can satisfy the original reader question without a confusing jump. Record which material will be retained, rewritten with evidence, or omitted. The owner should approve the combined thesis before implementation begins.

For removal, decide the route response from reader intent and technical policy. A relevant replacement may justify a redirect. No replacement may justify a clear unavailable response and repaired internal links. Sending every removed route to the homepage hides the decision and can strand readers. Verify external behavior without promising control over third-party links.

After any disposition, sample search results, navigation, related links, and the sitemap after the normal update interval. Keep the article in the decision inventory until these checks pass. Closure means the intended public path works and the historical decision is recorded, not simply that a source file changed.