Ownership maps that survive a vendor exit

Vendor exits leave applications with documentation that still lists contractor numbers. Operational readiness assessments spend more time on contact truth than on polished wiki prose.

One map, three roles

We ask for build owner, release owner, and pager owner as separate names. When the same person fills all three after a vendor leaves, that is not automatically wrong — but the register should say so, because holiday cover becomes fragile.

Alert routes are part of the map

A spreadsheet of names that does not match the live escalation policy is a decorative artefact. During readiness work we open the alert console and dial the night path (in a controlled test) or at least verify destinations against HR-active directories.

Handover packets need a retirement list

Incoming teams inherit three wikis and none marked authoritative. A useful readiness register names which pages to retire, not only which pages to keep.

If handover day is fixed, book an operational readiness assessment early enough that interview slots are not jammed against the exit date.