Give each source an owner
Record the exact page or document an answer may use. Include topics, owner, approved version and review date. A general website address does not establish which of two conflicting price lists is authoritative.
Update on events as well as dates
A change in pricing, service, hours or booking rules should trigger review of affected answers. Find copies in FAQs, campaign pages and old documents. Resolve contradictions before approving the source again.
Retest affected questions
Keep a routine question, an ambiguous wording and an unknown task for each important source. After a change, compare answers, handoffs and review effort. A correct answer to one question does not prove every answer is correct.
Remove obsolete sources from answer material
Mark superseded versions and record their replacements. Establish the product’s actual refresh process and confirm the change with a test. A new public page does not automatically mean an existing knowledge base has updated.
Use the monthly review
Review unanswered questions and corrections with the person who takes over. Prioritise sources with recurring errors. Record the owner, action and retest date in the log. The aim is fewer ambiguities, not merely more documents.
Use the worksheet
Version 15 October 2026. Fill in your own facts; illustrative values are not results or an agreed service.
SOURCE LOG — 15 October 2026 Source ID | URL or document | Owner | Current version/date | Scope | Approver | Change trigger | Test ID | Status Example: SERVICE-01 | Approved service page | Service owner | Enter actual date | Hours and area | Owner | Opening hours change | T01 | Awaiting test Monthly review: conflicting sources, unanswered questions, price changes, revoked access, obsolete documents. Record the change and retest. Do not use customer records in this sample.
Choose the next useful action
Compare the current scope before requesting setup. An educational guide does not activate a product or accept a paid engagement.