Mortgage Referral Partner Activity Workflow: A Review Guide for Loan Officers
Written by Yuri Polukeev, CEO, BNTouch
Last reviewed: August 2026
Partner activity is easy to turn into a pile of vague relationship tasks. A better workflow lets a loan officer open one record and answer four practical questions: What has happened with this partner? Who owns the relationship today? Why is the next step useful? What should happen if the context is missing or contradictory?
What the public tutorial demonstrates
A public BNTouch partner-tracker tutorial shows a partner-record sidebar with activity history and a MAIA chat entry point. View the source video at 01:27. The video was published in 2024, so it is visual record-context evidence only. It does not establish current behavior, access, account setup, fields, partner-facing functionality, or MAIA availability.
Use a five-record partner review
| Partner record | What to inspect | Decision to record |
|---|---|---|
| Active referral relationship | Recent activities, current relationship owner, visible next action, and the reason for the touch. | Whether the next action remains useful and who completes it. |
| New partner with limited history | How the relationship started, what information is known, and what should be verified before a planned follow-up. | Owner, first review step, and escalation path for missing context. |
| Partner with a handoff | What a new owner can understand from the activity trail and what remains unresolved. | Named handoff owner and a written next step. |
| Inactive relationship | Whether the last activity explains why a re-engagement task exists or why the record should pause. | Later review point or no-action decision. |
| Record with conflicting notes | Which facts require a person to verify before the relationship is contacted again. | Reviewer, source to check, and disposition of the exception. |
Build a reviewable activity trail
One relationship record should give the next loan officer enough context to continue the work responsibly. That means activity entries need an owner, date, reason, and follow-up decision. It does not mean that every interaction must become a long note. Brief, consistent entries are easier to use than broad status labels.
| Activity element | What it should answer | Exception path |
|---|---|---|
| Relationship source | How the loan officer and partner know each other or why the record exists. | Ask the relationship owner to confirm when the source is incomplete. |
| Current owner | Who is responsible for the next partner-facing action. | Route an unavailable owner to a named backup or manager. |
| Activity history | What was discussed, completed, or left unresolved. | Review conflicts against the original record context before a new touch. |
| Next action | Why another action is useful now and when it should be reviewed. | Pause when the record cannot explain the purpose or owner. |
| Relationship boundary | What the partner should and should not be expected to handle. | Escalate borrower-specific questions to the appropriate internal owner. |
Keep human review in the workflow
Relationship records can organize context, but a person still decides whether a message, meeting, or next step is appropriate. When records are missing history, the ownership changed, or notes conflict, give a reviewer a defined job: identify the source of truth, document the decision, and state what happens next. That makes a partner workflow more durable than a generic recurring reminder.
Method and source trail
This page is an operational review guide. It is not a product specification, a data-sharing policy, a communication approval, or a performance promise. Confirm current account behavior, permissions, and process ownership in the environment being evaluated.
