Worked example: removing a retired staff contact from every active path
A fictional business has a receptionist knowledge document saying that warranty enquiries go to Pat in operations. Pat leaves the role, and Taylor becomes the approved warranty contact. The office manager edits the visible FAQ and saves it. A test call asking who handles warranty now produces Taylor's name, which looks successful. But a transfer request still uses Pat's old direct number from a separate routing field.
The update was only partly complete. The source register should have identified the FAQ answer, transfer destination, after-hours fallback, staff notification recipient and any embedded examples that mention Pat. Each has a different operational effect. A correct name in the spoken answer does not prove that the actual handoff goes to the new owner. The maintenance task must cover the whole approved change.
Prepare a change record stating that Taylor now owns warranty enquiries, the effective time, the approved internal destination and the public wording. Specify that Pat's contact details are retired from active routing and caller-facing answers. Do not automatically publish Taylor's direct number merely because it is used internally. The information boundary remains a separate decision from the routing update.
Apply the change through each supported source and refresh mechanism. Then ask who handles warranty, request a warranty transfer and trigger the approved unavailable-person fallback with controlled test conditions. Inspect the receiving queue or message. Ask a leading question about Pat's old role to check whether historical examples still cause the receptionist to offer the retired contact.
Now test a neighbouring category, such as general accounts enquiries, which should continue using its existing owner. This catches an overly broad edit that replaced every occurrence of an operations destination rather than only the warranty rule. A maintenance change is accepted when the intended topic changes and unrelated behaviour remains consistent with its approved source.
Suppose the FAQ refreshes but the routing control cannot be updated immediately. The honest interim scope is to stop promising a direct warranty transfer and use an approved message path that reaches the current owner, if available. Do not announce the maintenance complete merely because the visible answer is correct. Record the remaining routing limitation and the person responsible for resolving it.
The completed evidence record contains the approved source change, active configuration references, caller-facing test results and destination checks. Historical notes about Pat remain in the appropriate archive, excluded from current receptionist answers. The next owner can understand what changed without guessing from file timestamps, and the business has a repeatable process for the next staff or policy change.
Use a small change worksheet whenever a business owner approves an update: topic, authoritative source, exact old statement, exact replacement, effective period, affected actions, removal targets, test questions and reviewer. The worksheet should make omissions visible without becoming an administrative project of its own. A temporary service pause needs an expiry check; a permanent staff change needs old references removed. Neither should be closed merely because a new paragraph was added. Store the evidence with the change record so the next maintainer can distinguish an approved decision from an informal suggestion that was never published.