In this article
When a product changes its navigation, update the affected instruction and its source. Do not rewrite every production procedure, and do not assume a new label changes the underlying responsibility.
A concrete example from Cast & Crew
The July 9, 2026 New Experience release describes moving offer creation into Manage Offers, with a Create Offer button rather than a standalone navigation page. It also documents a profile check before the start packet. These are dated product changes, not a guarantee that every project or role sees an identical interface today.
A team note that still says “open the Create Offer navigation page” may waste time even if its larger process remains sound. The appropriate response is a targeted update: identify the changed instruction, cite the current source and retain the rest only if it is still accurate.
Keep a small instruction register
For each local job aid, record its purpose, intended role, linked official source, last actual review and the person responsible for maintaining it. Avoid a false precision such as “always current.” A date explains when someone reviewed a source; it does not prevent the product from changing tomorrow.
Prefer a short task description linked to official steps over a copied gallery of product screenshots. Screenshots can become stale, reveal private information or make an independent page look like an official account interface. Original process diagrams should describe the handoff rather than imitate the service’s screen.
Review by impact
- Navigation-only: the destination or label changed, but the decision owner did not.
- Workflow-related: an additional review or confirmation step changes the handoff.
- Permission-related: the instruction needs an availability or role caveat.
- Unclear: a difference requires official clarification before updating the local aid.
These are editorial planning categories, not the vendor’s release classifications. They help a coordinator avoid both extremes: ignoring meaningful changes and treating every visual refresh as an entirely new operating model.
Fictional update notice
A production’s internal checklist points to an old navigation label. The coordinator verifies the current official guide, changes that one reference and asks the intended role to confirm the instruction in its authorized environment. The notice identifies the changed task and source, without claiming that the entire system has been tested or that all roles have access.
Retire the duplicate
After an updated job aid is approved through the production’s normal process, make clear which version should be used. Preserve required history according to the organization’s rules, but do not leave two equally prominent conflicting instructions. The goal is a clear current route, not a growing archive of almost-identical PDFs.
When a change affects the pre-send decision, revisit the offer review. When it affects responsibility, update the operating map rather than changing a menu label alone.
Evidence & scope
Public documentation checked October 25, 2026. Product facts are attributed below; planning methods and fictional examples are independent editorial analysis, not an official procedure or a private-account test. Availability depends on role and project. This is not legal, employment or payroll advice.