Reverse mortgage LOS user access review: a worksheet
Review existing access with a reusable decision register, a fictional role change, and checks that separate approval from verified completion.
In this article
A reverse mortgage loan origination system (LOS) user access review compares current work with existing permissions. The useful output of a reverse mortgage LOS user access review is a documented retain, change, or remove decision, followed by evidence that an approved change took effect.
This explainer provides a reusable review register and a fictional processing-to-training role change. It covers existing access; use the team onboarding article for new-account setup.
Scope a reverse mortgage LOS user access review
Start with a defined population and a dated access snapshot. A job title alone does not explain which loan files, document actions, reporting functions, or administrative tasks someone needs. Record the work being performed and the access boundary being reviewed.
The National Institute of Standards and Technology (NIST) Cybersecurity Framework (CSF) 2.0 describes access management and review in PR.AA-05. It includes least privilege and separation of duties. The NIST CSF 2.0 publication offers general outcomes, not a mortgage-specific review timetable or a product certification.
- Identify the system, business unit, reviewer, and snapshot date.
- Compare the active-user list with an authorized source for current responsibilities.
- Distinguish ordinary users, administrators, and separately owned service identities.
- Note any access source you cannot inspect rather than declaring the inventory complete.
Ask the system owner how access is actually granted: direct assignments, group membership, loan assignments, or another mechanism. These are questions to verify with your provider, not claims about a particular platform. A review that covers only one route may leave the effective access question unanswered.
Build a reusable access-decision register
Give each access boundary its own row. One person can legitimately retain one permission while losing another. Keep the business decision, the implementation action, and the verification result separate so a requested change is not mistaken for a completed change.
| Register field | What to capture | Who supplies it |
|---|---|---|
| Account and current work | Account reference; team; current task; business reason | Business owner |
| Observed access | Action; file scope; source of grant; snapshot date | System owner |
| Decision | Retain, change, remove, or unresolved; reason; approver | Authorized reviewer |
| Execution | Approved change reference; implementer; completion time | Administrator |
| Verification | Expected versus observed access; evidence; checker; date | Assigned verifier |
| Open exception | Unanswered question; decision owner; next action; revisit date | Review owner |
Copy those fields into your approved tracking system and leave unknown values visibly unresolved. Use account references and controlled evidence links; the register does not need borrower documents, passwords, or copied customer details. Follow your organization's information-handling rules for the underlying records.
Worked example: processing coverage becomes training
Consider a fictional employee, Morgan, who has finished temporary processing coverage and now prepares training material. The business owner confirms that Morgan needs the training environment, but no longer needs to edit production processing files. A separate question remains about access to production reports.
The reviewer breaks the request into three decisions. All roles, permissions, and environments below are illustrative; they do not describe a ReversePilot configuration or a real customer.
- Retain: access to approved synthetic training files, supported by the current training assignment.
- Remove: the temporary production processing grant, after the authorized owner confirms the coverage handoff.
- Unresolved: production reporting access, because the training task description does not establish a need for it.
The reporting row stays open with the business owner assigned to clarify the task and the system owner assigned to identify the grant source. An unresolved row is not authorization to expand or preserve access indefinitely. The responsible owner decides its treatment under the organization's existing policy.
Before the administrator implements the approved processing change, the operations owner confirms who now owns unfinished files. The capacity planning and coverage article helps separate task ownership from permission decisions. Keeping a file moving and retaining a former worker's access are different decisions.
Verify the changed boundary, then close the row
A saved settings change is evidence of an action, but it does not by itself demonstrate the resulting access. Agree on a safe verification method with the system owner. Use authorized test identities and synthetic records in an approved test environment when demonstrating behavior.
- State the expected allowed action, such as opening an approved training record.
- State the expected denied action, such as editing a file outside the approved scope.
- Check the effective result and investigate any other grant that could explain a mismatch.
- Record the evidence, checker, date, and remaining limitations before closing the row.
Do not treat a hidden menu as sufficient evidence of an access boundary. Ask the authorized technical owner what verification is appropriate for the system. Keep testing within approved scope; this worksheet is not permission to probe production records or borrow another person's credentials.
The software testing article provides broader context for recording expected and observed results. For Morgan, closure means the approved training access remains, the approved processing removal is verified, and the reporting question has its own accountable disposition.
Key takeaways
- Review current work and effective access, not job titles alone.
- Separate the decision, implementation, and verification in the register.
- Keep unresolved access questions assigned and visible until an authorized owner resolves them.
For a software evaluation, bring one synthetic role-change scenario to the discussion alongside the reverse mortgage LOS buyer guide.