When you move to a new numbering scheme, operators will keep searching by the old number for years, since that is what is printed in the binders, written on equipment and stuck in everyone’s memory. If the old number stops working in search, people go back to the paper copy, which defeats the point of digitizing and leaves the site with two sources of truth again.
Old numbers also live in places that are hard to update, such as work orders, permits, training records, risk assessments, contractor documents and references inside other procedures. Even with a careful migration plan, some of those references will survive for a long time, and every one of them is a moment where someone types an old number into search and expects to find the right document.
The simple fix is to keep the legacy number on each procedure as an alias, so a search for either the old or the new number finds the same document, and to show both numbers on the procedure for a transition period. The alias should be a proper field on the procedure rather than a note buried in the text, so it stays consistent, searchable and preserved through future revisions.
Some legacy numbers will not map cleanly, since one old procedure may have been split into several new ones or several old ones merged into a single new standard. In those cases the old number should lead to all the relevant new procedures with a short explanation, rather than pointing to just one and leaving the operator to wonder where the rest of the content went. A mapping table kept by document control helps here, and it is worth checking it against the most frequently searched old numbers early in the rollout.
Once people have had time to get used to the new scheme, the old number can stay in the background for search without cluttering the procedure. There is rarely a good reason to remove it entirely, since an old reference can surface in a historical record or an investigation years later and still needs to lead somewhere sensible.
