Set a research source refresh calendar that survives staff turnover
A source refresh calendar that records what to check, when to check it, and who can pick up the work after a handoff.

List sources by decision dependency
Start with the decisions the research supports, then list the sources those decisions depend on. A market sizing decision may depend on a census release, an industry association report, and an internal sales export. A competitive claim may depend on a competitor product page and a product documentation page. Linking the source to the decision shows why the refresh matters and what breaks if it is late.
Rank the sources by how much a stale value would change a decision. A headline statistic used in a board deck deserves a tighter refresh than a background link used in one blog post. Keep the rank visible so the calendar does not treat every source as equally urgent. A short list of high-dependency sources is easier to maintain than a long list that no one can finish.
Assign a refresh interval from change rate
Choose an interval based on how often the source actually changes. A regulatory page may change on a known schedule, while a competitor homepage can change without notice. Use the source's own update cadence when it publishes one. Otherwise, check it twice at the start of the year to estimate how often it moves. Set the interval from that evidence rather than from a general rule.
Write the interval and the next check date beside each source. Use a small number of buckets such as monthly, quarterly, and annual to keep the calendar readable. A source that changes often but supports a low-stakes claim can still use a longer interval. The purpose is to catch a decision-relevant change, not to monitor every page on the internet.
Record the last verification date
Every source in the calendar needs the date it was last checked and the result. The result can be unchanged, updated, moved, or unavailable. A date without a result does not tell the next analyst what happened. Add a short note when the page moved or the publisher changed the format. Those details save the next person from repeating the search.
Keep the verification date in the same record as the source URL and the claim it supports. If the source is used in several articles, show each use so a refresh can trigger a content review. A central calendar that does not connect to the published work will miss the pages that need an update. The record should make that connection obvious without a separate search.
Store the check steps with the source
Write the steps needed to verify the source. Include the exact page, the table or section to read, and the value or statement the team records. If the source requires a login or an annual report download, say so. A successor should be able to repeat the check without reconstructing the original analyst's process. Steps that live only in memory disappear when the analyst leaves.
Add a note about what counts as a material change. A revised footnote may not matter, while a changed definition or base year probably does. Write the threshold before the next check so the decision is not made under time pressure. When the source changes materially, the note should say which published pages need review. That link turns a monitoring task into a content maintenance action.
Hand the calendar to a named backup
Name a backup owner for every high-dependency source. The backup should be able to run the check and record the result without asking the primary owner for context. Give the backup access to the calendar and the source list before the handoff is needed. A backup named only in a document is not a real backup if that person cannot open the tools.
Schedule a short handoff test each quarter. Ask the backup to verify one source and update the record while the primary owner watches. Fix any missing step or access problem before the primary owner is unavailable. This test is more useful than a written succession plan because it exercises the actual calendar and reveals where the process depends on one person.
Review missed refreshes monthly
At the end of each month, list the sources that passed their check date. Group the misses by cause: no owner, no access, unclear steps, or a source that takes too long. Fix one cause at a time and record the change. A calendar that quietly accumulates missed checks is worse than a shorter calendar that the team can keep current.
Report the completion rate and the material changes found, not just the number of checks performed. A month with no material changes can still be a successful refresh if the high-dependency sources were verified. Use the review to retire sources that no longer support a live decision. The calendar should shrink when the work changes, and the record should show why each removal happened.