When a homeowner dies or a property interest changes, the first person contacting a mortgage servicer may not yet appear as a borrower in the servicing system. Support still needs to recognize the notice, explain the confirmation path, collect documents securely, and keep the case from disappearing between general service, estate, legal, and loss-mitigation queues. This study protocol evaluates that intake work.
The protocol is not legal advice and does not decide whether a person owns a property, owes a debt, or qualifies for a mortgage option. It studies whether records show a consistent response to a potential successor in interest under the organization's applicable policies and current regulatory interpretation.
Define the intake episode
One episode begins when the servicer first receives information indicating a possible transfer of ownership or interest tied to a mortgage loan. Sources can include a phone call, letter, uploaded document, loss-mitigation application, returned mail, or notice from an authorized representative. The episode ends with confirmation, a documented determination that the person is not a successor, a request for specified additional documents, withdrawal, or the study cutoff.
Link repeat contacts and submissions to the same episode. Preserve the first-received timestamp even if a later team creates a formal case. A common measurement error is to start the clock at specialist assignment and erase time spent in general service.
Use distinct states: notice received, potential successor identified, document description sent, documents partly received, review underway, additional documents specified, confirmed successor, not confirmed with reason, and unresolved. Do not use "borrower" or "authorized party" as an imprecise substitute for these states.
Identify the regulatory evidence question
CFPB's official Regulation X text says servicing policies and procedures must be reasonably designed to retain notice of potential successors, promptly facilitate communication, promptly identify documents reasonably required, and promptly notify the person of the result or additional needs where the provisions apply (12 CFR 1024.38). The official commentary notes that notice can arrive in multiple ways, including information about death, divorce, separation, or another transfer.
The study should therefore ask whether the record preserved notice, produced a usable document path, and reached a traceable state. It should not convert those questions into a universal checklist for every jurisdiction or transfer type. The regulation's commentary recognizes that relevant property law and circumstances vary.
CFPB's mortgage servicing resource center links the operative rules, interpretations, and compliance resources (Mortgage Servicing Rules). Capture the policy and source versions used in the study so later rule changes do not silently alter historical coding.
Reconstruct the first contact
Review what the person said, what the agent recorded, which loan identifiers were available, what authentication or privacy boundary applied, and what next step was given. Code whether the agent recognized a potential-successor signal without demanding that the caller already be listed as a borrower.
Separate basic intake from disclosure of protected account information. An agent may be able to record notice and explain a document process while remaining unable to disclose balances or account activity. The study should reward accurate boundary-setting and a viable next step, not either indiscriminate disclosure or reflexive refusal to help.
Capture language access, disability accommodation, and channel constraints. A process available only through an inaccessible upload portal or an unexplained postal address may not produce a usable path even if the script is technically recited.
Audit the document-description process
Record each requested document, the reason category, the policy or jurisdictional rule supporting it, when the request was sent, and how submission instructions were delivered. Version the list. If reviewers later request something new, preserve the earlier list and the explanation for the change.
The official interpretation of section 1024.38 states that documents required to confirm identity and ownership interest must be reasonable in light of applicable law, the specific situation, and records already held by the servicer. It gives illustrative examples such as a death certificate, executed will, or court order, while emphasizing that situations vary (12 CFR 1024.38).
Test for vague or circular requests. "Send legal documents" is not a specific description. Requiring proof already in the servicer's possession without documenting why can create avoidable rework. Conversely, the study should not infer that an unreviewed document was sufficient merely because it had a familiar title.
Test written-request handling
Regulation X section 1024.36 includes a response provision for certain written requests indicating that a person may be a successor in interest and containing information that enables the servicer to identify the account. The response includes a written description of documents reasonably required and contact information for further assistance (12 CFR 1024.36).
Build a cohort of qualifying and near-qualifying written requests. Determine whether mail, secure messages, uploads, and representative submissions entered the same tracking system. Record receipt, account matching, acknowledgment, response content, outbound evidence, and returned-mail or delivery status.
Do not mark a response complete simply because a letter was generated. Check whether the address or channel was usable and whether the description matched the current case state. If the account could not be identified, record what search and follow-up occurred rather than assuming the request lacked merit.
Follow documents through review
For each upload or mailed item, preserve receipt time, document class, indexing result, reviewer assignment, decision, and linkage to the episode. Avoid copying sensitive document contents into broad-access notes. Analytical extracts should use study keys and categorical results.
Measure duplicate requests, misindexed documents, unreadable-file follow-ups, and items received but not associated with the active case. A document can exist in the repository while remaining operationally invisible to the reviewer. The study should count that as a continuity failure, not customer nonresponse.
Record reviewer authority. Frontline agents may explain status but should not invent a determination. Specialist notes should show which documents were accepted, which additional documents were needed, or why confirmation was not made.
Separate confirmation from loan obligation
CFPB's official interpretation explains that a confirmed successor in interest is treated as a borrower for specified Regulation X servicing provisions regardless of whether the person assumes the mortgage obligation under state law (Official Interpretation of 12 CFR 1024.30). The interpretation also distinguishes regulatory treatment from contractual liability.
This distinction should be tested in support copy. Flag statements that equate confirmation automatically with personal liability or require assumption merely to begin the applicable confirmation process. Also flag promises that confirmation itself changes title, ownership, or every loan term.
After confirmation, verify that the state propagated to systems needed for communications, statements, and applicable servicing workflows. A correct specialist decision that never reaches frontline systems can still produce repeat denials and unsafe disclosure patterns.
Measure continuity, accuracy, and burden
Report time from first notice to document description, first document receipt, review start, request for additional material, and final state. Count contacts, transfers, duplicate submissions, and contradictory instructions. Stratify by notice source, transfer category, channel, and whether an authorized representative participated.
Review customer-facing messages for accurate state language. "We received your documents" differs from "you are confirmed." "Additional evidence is required" should name the missing category and a route for assistance. Code whether the person received a reference that worked across channels.
Two reviewers should independently code a sample containing confirmed, not-confirmed, additional-document, representative, and unresolved episodes. Measure agreement on notice date, state, request specificity, evidence receipt, decision basis, and communication accuracy. Adjudicate disagreements before computing results.
Missing data must remain visible. Returned mail, inaccessible recordings, and legacy document repositories can limit conclusions. The study can show where intake evidence or continuity fails. It cannot adjudicate property rights, determine liability, or decide a specific servicing dispute.
For financial-services teams, the operational implication is a staffed chain of custody: first-contact recognition, secure document intake, specialist review, and status communication must share one case identity. Organizations evaluating that capability can relate the method to financial services support, order and account support, and email and ticket support.