Projects and partners

Record domain custody before the agency handoff

You can establish a usable contact route only by matching the domain to a genuine registrar account record, identifying its actual custodian and confirming which merchant representative is authorized to coordinate with that person. Record the renewal owner separately. If a name, authority or reachable contact is missing, leave the domain handoff open even when the website still works. This is an operational custody record, not a conclusion about legal ownership or permission to transfer the domain.

For: An authorized representative of a research-only merchant preparing for an agency departure while the store's domain remains in use.

Updated 2026-10-01

Start with the domain, not the website login

Write the exact domain the business needs to keep operating and locate the corresponding account record in files the business already holds or in an account an authorized person can open. Record the registrar or domain service named there and the date of the evidence. An agency's name on a website project document is a lead to investigate; it is not a substitute for identifying the actual domain account.

Keep domain custody separate from the WordPress administrator, hosting contact and payment account contact. Those roles may be held by the same person, but the handoff should establish that relationship for this domain instead of inferring it from a working store. Someone's ability to edit a page does not answer who can act on the registrar account.

Record custody, authority and renewal as separate roles

For this worksheet, the account custodian is the person or organization documented as managing the registrar account. The authorized merchant contact is the business representative who may coordinate the handoff. The renewal owner is the person or team that has accepted responsibility for the renewal task. Naming one role does not establish the other two.

Use existing account records, the agency agreement, renewal correspondence and written responsibility confirmations to fill those roles. Record where the supporting evidence is held internally. A past renewal receipt establishes a past event; it does not, by itself, show who agreed to handle the next one. A project contact who forwards a request is not necessarily the person with account authority.

Where records conflict, preserve the conflict. If the agreement names the merchant but the available account record names an agency contact, write both with their evidence dates. Do not resolve the discrepancy by changing the account, assigning ownership to the payer or declaring the agency's rights from this worksheet.

Confirm the handoff route before marking it complete

Ask the identified custodian to confirm the domain they manage, the authorized merchant contact they recognize and the agreed route for renewal questions after the agency relationship ends. Keep the response with the handoff record. A contact address in an old proposal establishes a listed route; an actual reply about this domain is stronger evidence that the intended person can be reached.

Classify the handoff by what you have established. If the roles are documented and the custodian has acknowledged the contact route, the custody record is usable. If the custodian is named but has not replied, reachability remains unconfirmed. If nobody can identify the actual account, the account-custody dependency remains unresolved. None of those statuses requires guessing who legally owns the domain.

Carry any real renewal date or agency departure date into the unresolved item, preserving its source. Assign a person to obtain the missing confirmation and a merchant-chosen follow-up date. That follow-up is a work assignment, not a promise about registrar processing times. This page supplies no registrar-specific transfer, recovery or access procedure.

Make the unresolved dependency part of project acceptance

Keep the domain row open in the agency handoff until the missing evidence is supplied or the merchant explicitly records how the dependency will be handled. A delivered website and a documented domain contact are different acceptance items. The practical outcome here is a named person to reach, a defined responsibility and a clear next action for anything still unknown.

Prism's preparation guidance asks merchants to distinguish available records from unanswered questions. A scoped checkout consultation can start with the public site and an explanation of how the unresolved domain dependency affects the planned work. Requested assistance, pages, responsibilities, fees and terms must be confirmed before work; the merchant chooses changes. The inquiry form is for the website, products and question, with follow-up by email. It does not book an appointment, buy a service or submit a processing application.

Domain custody handoff

Complete one record for each actual domain involved in the handoff. Enter a non-sensitive evidence reference and its date beside each role. Treat a missing custodian, unconfirmed authority or unanswered contact as an open dependency rather than evidence of legal ownership.

Worksheet entries are not submitted by Prism’s worksheet and are not saved by the site. Use record types, availability, anonymized observations, or match/mismatch results. Do not enter government identifiers, customer names or addresses, customer messages, receipt-access links, card or bank details, passwords, or keys. Send sensitive documents only through the provider’s verified secure channel.

Domain custody handoff. The last column is for temporary notes.
Custody factExisting evidence to useHow to interpret itYour record
DomainExact domain in the authorized account record or existing domain-service correspondence.Match the record to the domain the store needs; a general agency account name is insufficient.
Actual account custodianAccount record and written identification of the person or organization currently managing it.Record operational custody without turning it into a legal-title conclusion.
Authorized merchant contactBusiness authorization or agreed handoff correspondence identifying the merchant representative.A website editor or invoice recipient is not automatically the authorized contact.
Renewal ownerWritten acceptance of the renewal responsibility, with any genuine renewal notice or date.Separate future responsibility from who paid a previous invoice.
Reachable handoff routeKnown business contact channel and an actual acknowledgment covering this domain.Distinguish a listed address from a confirmed route to the custodian.
Unresolved access dependencyMissing or conflicting account information, its assigned follow-up owner and any documented deadline.Leave it open until evidence resolves it; do not invent access, transfer rights or completion.

These are temporary notes. Leaving or reloading this page may clear them. Worksheet entries are not sent automatically. If you copy notes into the consultation message and submit the form, Prism receives them as part of your request.

Limits

  • This original worksheet organizes merchant records. It gives no registrar-specific transfer or recovery instructions and determines no legal ownership rights.
  • Record only accounts and contacts the merchant is authorized to use; a custody note does not grant access.
  • Keep passwords, transfer codes, recovery codes, identity documents and payment details out of this worksheet and the public consultation form.

Sources

  • Prism: How it works — checked 2026-09-21. Consultation scope defines pages, questions and follow-up before work; the merchant decides which changes to make. This is not a registrar procedure.
  • Prism resources — checked 2026-09-21. Preparation guidance separates genuine available records from unanswered questions. It does not establish this merchant's domain access or authority.
  • Prism solutions — checked 2026-09-21. Public support includes storefront review, processing preparation and provider website questions; scope, fees and terms are discussed before work.
  • Prism contact — checked 2026-09-21. The public inquiry asks for the website, products and question without passwords, payment-card details or customer records. Email follow-up does not constitute a booking, purchase or processing application.

Discuss my store project

Planning, moving or taking over a store?