Maintaining answers when a product or policy changes

When a product or policy changes, trace the community guidance it affects. Give the change an owner, locate maintained resources and prominent older discussions, verify the new position, and make corrections visible where members may still meet outdated advice.

Start with the change

Record what changed, when it applies and who can confirm the new position. A renamed button may need only a wording update; a change to eligibility, permissions or process may invalidate an entire answer. A recent edit date does not prove someone reviewed the answer against this change.

Search for the old feature name, policy term and common member phrasing. Check maintained guides, pinned material, selected solutions, templates and moderator replies that people may still encounter.

Assign affected items to an editor. Prioritise material that could lead members to take the wrong action. If the replacement answer is not yet known, use a visible notice where possible and direct members to a current help route instead of guessing.

Correct the answer and its context

Ask the responsible product or policy owner to verify the new wording. Check prerequisites, exceptions and screenshots as well as the main step. State an effective date only if it is confirmed and relevant. If some members remain on an earlier version or arrangement, say which instructions apply to them.

Update the maintained resource, then address older prominent answers. Depending on the community's controls, an editor might add a correction to a thread, reply with the current position or edit a staff-authored post with a visible note. Preserve the original discussion's context. Do not rewrite a member's account as though they had said something else.

A selected solution may remain prominent after its advice expires. Make the change visible near it using the controls available on that platform. Check how the result appears to an ordinary member.

Close the review loop

Keep a short change record: affected resource, reviewer, decision, date and any items still unresolved. Search again using old and new terms to find conflicting guidance that remains visible.

Use review triggers that fit the material. Product releases and policy approvals can prompt a targeted check; scheduled reviews can catch missed changes. Some knowledge-base platforms also offer verification reminders.

In Zendesk Knowledge, configured rules can flag articles for review and email their assigned owners. A Knowledge admin sets the rules, and reminder recipients are tied to article ownership.

Invite members and moderators to report old answers. Check each report and correct the affected guidance. That lets readers identify the current answer, its limits and where to ask about an unresolved case.