Practise updating an external source reference with the next editor

An organisation may use the same institutional source in several publication cards. A handover that says “update the links when they change” leaves important questions unanswered: which reference is intended, what evidence establishes its replacement and where the change will appear.

This fictional exercise gives a successor one bounded change in an existing outgoing-link registry. The registry capability is assumed to have been inspected in the chosen CMS; a real platform needs its own supported procedure.

Define the reference before touching its uses

Reference S-22 identifies an external institution's public guidance page. Three cards use that registry record: a programme page, a publication note and a reading list. The institution has moved that guidance from https://old-source.example/guidance/ to https://new-source.example/guidance/.

The successor, Arta, receives the institution's published move notice and the new page. The content owner confirms that the notice concerns S-22 and that the new destination is the intended source. A second reference, S-23, has a similar page title but belongs to a different institution and must remain unchanged.

The example uses fictional domains so the exercise can be rehearsed without editing or requesting changes from an actual institution.

Inspect the supported editing path

Arta's ordinary editor role can open the outgoing-link registry, view a reference's uses and submit an approved target change. It cannot change unrelated account settings. The handover identifies the exact record and the reason for the update, rather than asking Arta to search and replace every occurrence of a title.

The registry stores the source identity and destination separately from the text on each card. This matters because the three cards describe different uses of the guidance. Updating the common destination should not replace those descriptions with one generic paragraph.

Before saving, Arta checks that the usage list shows the expected three cards and no unexpected references. If it showed a fourth use with a different meaning, that discrepancy would require review before proceeding.

Make the approved change and inspect the result

Arta changes S-22's destination to the confirmed new URL through the supported registry action. The source identity remains S-22. The change record identifies the approving owner and the institution's move notice.

The preview then produces this result:

Arta follows each link in the controlled review and confirms the intended destination identity. A successful response alone would not establish that the page belongs to the right institution. The checked title, source and move evidence matter together.

The website continues to link to the external material. It does not create a local mirror or imply that the organisation now maintains the institution's guidance.

Finish with a repeatable instruction

The receiving editor can now explain the procedure: identify the registry record, inspect its uses, obtain the source owner's approval, change the supported target and verify the resulting public routes. The instruction also names the escalation point for uncertain replacements.

That is a more useful handover result than a note saying the original developer knows where links are stored. The successor has performed the task with the intended account and can distinguish the source record from its several public presentations.

The organisation retains the old destination in its change evidence where appropriate. It does not assume control over the external site's redirects or availability. If the new source later becomes unavailable, the editor follows the agreed review process rather than substituting a similarly titled page.

Use the same approach for your handover

Choose an ordinary task that crosses more than one page but has a clear boundary. Provide the source evidence, the authorised action and a control that must remain unchanged. Ask the successor to perform the task and explain what would make them stop.

Access failures, unclear instructions and unexpected uses become concrete handover work. They should be resolved while the people who understand the setup are still available.

Read support responsibilities to define continuing ownership, or discuss website care when the existing site needs an inventory before an editor can safely take over.