Modernizing a reverse mortgage operation: cutover and adoption
Pilot an operating change with explicit rules for unfinished files, rehearsal and rollback checks, then measure eligible work and handoff quality.
In this article
Start with a demonstrated operating gap. In this fictional case, 4 of 12 sampled handoffs lacked a receiving reviewer acknowledgment. That is an observation, not proof of its cause. The proposed change adds an explicit acceptance step; it does not confer underwriting approval.
Stage the change
| Stage | Work | Go/no-go evidence |
|---|---|---|
| Current state | Trace request, sender, receiver and missing context | Agreed definition of a usable handoff and documented baseline sample |
| Pilot | Rehearse six synthetic cases, including absence and a returned file | All six produce a named owner and usable next action; essential failures stop pilot |
| Cutover | Apply procedure v2 using the transition rules below | Operations accepts exact version; dependencies and fallback reconciled |
| Adoption review | Review eligible tasks and receiving-team quality | Counts, exclusions, workarounds and unresolved causes recorded |
These are proposed gates for this example, not industry benchmarks. Separate technical release authority from operating-procedure approval.
Tell unfinished files which procedure applies
New work uses v2 after the approved trigger. A pending v1 handoff remains with its current owner until the receiver explicitly accepts transfer. Returned work records why it returned and whether the policy owner requires v2 re-review. Do not let a calendar date silently choose the answer.
Rehearse sender absent, receiver lacks access and document replaced mid-handoff. Keep the previous procedure available for authorized fallback. If v2 loses ownership or evidence, stop expansion, identify every in-flight v2 task and reconcile it before reverting. Reverting a document alone does not repair records created during the pilot. Update linked checklists, training and saved replies together.
Measure work, not logins
Synthetic review: 20 tasks were in scope; 2 were approved out-of-scope cases, leaving 18 eligible tasks. Of those, 14 used the intended workflow (14/18); 11 of the 14 reviewed records supported the next action (11/14). Report both fractions. Do not remove access failures from the eligible denominator to improve the rate.
Record each off-system reason: missing permission, unclear instruction, unavailable function or approved planning aid. A private reminder pointing at the official record differs from a competing status spreadsheet. Preserve the workaround's necessary function until an approved replacement exists. Coach a knowledge gap; fix access through the administrator; route a product gap for a product decision.
Review a proposed ten-business-day pilot with the operating owner, tracking waiting time, hands-on time and downstream returns separately. Easier files or lighter volume can explain improvement; the before/after comparison alone does not prove causation.
Continue with the relevant workflow
Reverse mortgage staff training. Resources.
Bring one handoff failure and the proposed eligible-work definition to a workflow-scoping session.