Running a wholesale reverse mortgage channel: an operating playbook
Operating patterns for lender-controlled wholesale reverse mortgage programs: broker onboarding, shared pipeline visibility, conditions ownership, and manager oversight.
Broker onboarding and approval
A wholesale channel's risk profile is set largely at onboarding, not afterward. A workable approval process typically verifies NMLS licensing status for the broker entity and individual originators, establishes what products and states the broker is approved to submit, and sets explicit permission boundaries — what a broker can see and do in your system versus what stays lender-controlled. Revisiting broker approval periodically, not just at initial signup, catches licensing lapses before they become a submitted-file problem.
Submission and pipeline visibility
Brokers generally need enough visibility to manage their own pipeline — file status, outstanding conditions, expected timelines — without exposing lender-internal information like underwriting notes, pricing margin, or other brokers' files. The operating pattern that tends to hold up under volume is a shared file record with role-based views, rather than a separate broker-facing system that has to be kept in sync with the lender's system of record.
Conditions and shared ownership
Conditions on a wholesale file often split between broker-owned (documents only the broker or borrower relationship can produce) and lender-owned (underwriting decisions, internal review). Ambiguity about which is which is one of the most common sources of wholesale cycle-time drag. Making ownership explicit on every condition — not just its status — is usually more valuable than any amount of general pipeline reporting.
Compensation and compliance guardrails
Broker compensation structures are subject to compliance requirements around consistency and disclosure, and visibility into compensation is typically governed by lender policy rather than exposed by default. If your platform supports compensation visibility for brokers, treat it as a configuration decision made deliberately with compliance — not a default toggle — and confirm your specific program's requirements before enabling it for a channel.
Manager oversight patterns
Wholesale managers generally need a different view than either brokers or individual underwriters: pipeline health across the whole broker book, aging and exception concentration by broker, and early signal on brokers whose file quality or documentation completeness is trending down. Building this as a reporting layer over the same shared file record — rather than a separate manual rollup — is what keeps it accurate as volume scales.
Was this article helpful?
Your feedback goes directly to the engineer who wrote it.