SERVICE-DEPENDENCY WORKSHEET
Prepared October 3, 2026 | Yenra
Guide: https://yenra.com/realnames-closure/
Purpose: identify who controls each step between a customer's first action and
your destination, then test a workable fallback. This is a planning aid; record
actual contract provisions and consult the responsible owner for interpretation.
Keep account details private and exclude passwords or recovery codes.

Service / customer task / reviewer / review date:
Current route (entry point -> intermediary -> destination):

Repeat this block for EACH operator or dependency:
- Step and operator:
- What would stop working if this step disappeared?
- Account/contract owner:
- Renewal and termination/change-notice provisions, with source/date:
- Records or mappings we can export; usable format:
- Export test date and reconciliation result:
- Alternative route and who controls it:
- Fallback test steps and expected result:
- Observed result, evidence location and unresolved gap:
- Gap owner and due date:

Customer communication channel, permitted use and responsible owner:
Exit timetable based on actual notice provisions:
Who decides when to switch? What evidence triggers that decision?
Next review trigger (contract, integration, routing or ownership change):

Fictional example: a repair shop uses a directory's short name. Its fallback is
a business-controlled domain on receipts and customer correspondence. Staff
check domain-renewal ownership, open the booking page directly and submit a
test inquiry. Record whether the inquiry arrives; successful technical access
does not predict how many customers would use the alternative route.