Imagine a service page with preparation information beneath its main introduction. A colleague has shared an address ending in a section fragment so a prospective customer can reach that information directly. During a redesign, the content is reorganised and the original heading is removed. The page still opens, but the intended arrival is no longer clear. This is a hypothetical migration case, not a Kolkata client result.
The team identifies the useful old entry and agrees its relevant destination in the new structure. It may preserve an appropriate section target or choose another reviewed treatment supported by the implementation. A server route map alone should not be assumed to settle what happens to a fragment within the browser.
Acceptance follows the old shared address as well as the new navigation on the agreed layouts. The reviewer checks that the preparation information remains understandable and reachable in its new context. The aim is an intentional redesign with a useful transition, rather than reproducing the old screen or retaining every historic section without a reason.