Written by Yuri Polukeev, CEO, BNTouch
Published September 7, 2026
A referral partner quarterly review should answer three questions: are introductions reaching the right person, are communication expectations being met, and what should change before the next meeting? Referral counts alone do not explain the quality of the working relationship.
The agenda below is a suggested service-review format for mortgage professionals. It is not a referral compensation program or a promise of more business.
In this guide
- A practical 30-minute agenda
- What to review before the meeting
- A completed meeting note
- Three measures more useful than a contact count
- Prepare a review packet the partner can use
- Read a small sample without inventing a performance story
- Choose the agenda that fits the relationship
- Discuss service problems with evidence
- Leave with a short decision record
- Use the next meeting to check the prior decision
- Record the meeting in the partner history
- Keep referral arrangements out of informal promises
- See a partner review in the CRM
A practical 30-minute agenda
| Time | Discussion | Leave with |
|---|---|---|
| First 5 minutes | Check the previous meeting’s commitments. | Completed, still open, or deliberately changed for each item. |
| Next 10 minutes | Review a small sample of introductions and communication handoffs. | A specific point where the process worked or broke down. |
| Next 10 minutes | Agree on one process improvement or useful educational question. | A defined action and person responsible. |
| Final 5 minutes | Confirm the next review and the record of the meeting. | A short written summary, not a new list of vague promises. |
What to review before the meeting
- Previous commitments and whether they were completed.
- Introduction records with enough context to identify the source accurately.
- Examples of unanswered process questions or unclear receiving contacts.
- The partner’s current contact and communication preferences.
- A short list of items your team can actually resolve.
Use aggregated or appropriately de-identified examples where possible. Do not disclose private borrower information simply to make a relationship review more detailed.
A completed meeting note
Illustrative meeting: The partner could not tell whether an introduction had reached the team’s shared inbox.
Finding: The introduction was present, but neither side had a clear acknowledgment step.
Decision: The branch’s designated intake person will confirm receipt through the approved process and identify the receiving loan officer.
Follow-up: Relationship owner reviews the next sample of introductions with the partner at the next agreed meeting.
Not a commitment: A loan approval, a promised closing, guaranteed referral volume, or compensation for introductions.
Three measures more useful than a contact count
| Measure | Definition for your team |
|---|---|
| Clear receipt | Introductions with a documented receiving person divided by the introductions reviewed. |
| Kept commitments | Due process commitments completed as agreed divided by the commitments due in the period. |
| Repeat friction | Count of the same unresolved handoff issue appearing again after a correction was agreed. |
These are proposed operating measures, not industry benchmarks or BNTouch customer results. Keep the sample size and period visible. A small sample helps spot a problem; it does not establish a reliable conversion forecast.
Prepare a review packet the partner can use
Build the packet around the work both sides can recognize. Start with the last meeting’s action list, a defined review period, and a small set of process observations. Avoid opening with an unexplained production total. A partner cannot help resolve an acknowledgment problem if the discussion stays at the level of applications and closings.
For each observation, record the period, the source, and any missing information. If the source of an introduction is uncertain, mark it unresolved. Do not assign credit to a partner because that person appears somewhere in the relationship history. Resolve the source through the team’s approved process before using it in a comparison.
- Previous actions: What was promised, who owned it, and what happened.
- Process sample: Which introductions or handoffs were reviewed and why that sample was chosen.
- Known issue: A specific step that caused confusion, with private borrower details removed.
- Proposed next action: A change the responsible people can approve and test.
- Unresolved question: An item that needs a separate operations or compliance discussion.
Read a small sample without inventing a performance story
Suppose a fictional team reviews ten introductions. Six have a clear receiving contact, two lack acknowledgment records, and two have an uncertain source. The review should not report a 60% contact rate. It has established that six records show a receiving contact, not that the other four people received no response.
Separate missing evidence from confirmed service failures. Ask the record owner to resolve the four uncertain cases. If the evidence remains incomplete, report it that way and improve the recording step. This produces a better next meeting than turning incomplete data into a claim about the partner’s quality or the loan officer’s performance.
Use comparable periods when looking for changes, and disclose differences that matter. A partner who changed offices or paused introductions creates a different operating context. Small samples can identify a broken handoff; they cannot support a confident forecast of future business.
Choose the agenda that fits the relationship
| Situation | Focus of the review | Useful next action |
|---|---|---|
| A new working relationship | Who receives introductions, how receipt is acknowledged, and where process questions go. | Confirm the introduction process and test it with a fictional example. |
| An established partner with recurring confusion | Where the last agreed process failed and what evidence is missing. | Assign one repair, a responsible person, and a review point. |
| A quiet period with few introductions | Whether business contacts, roles, or the partner’s needs have changed. | Update the relationship record and agree on useful future contact without pressuring for referrals. |
| A staffing change on either side | Whether existing contact paths and outstanding commitments still reach the correct person. | Introduce the new contact and transfer unfinished actions. |
Discuss service problems with evidence
If the partner reports that “nobody follows up,” ask which process step they could not see: receipt, assignment, a permitted update, or resolution of a question. The answer determines whether the team needs to fix service delivery or clarify what information the partner can expect to receive.
Acknowledge a confirmed missed commitment and assign the correction. When the evidence is incomplete, commit to checking the record rather than defending the team or assigning blame. Keep borrower-specific disputes in the proper restricted process; an ordinary business review should not become an informal channel for sharing a private loan history.
Leave with a short decision record
Record the agreed action in terms a colleague can verify. “Improve communication” is too broad. “Confirm which intake contact acknowledges an introduction, test the approved contact path, and review the next sample” identifies work. Name the relationship owner who will check completion and a backup if that person is absent.
If the partner asks for a new service or arrangement that has not been approved, record it as a request. Separate it from commitments already accepted by the team. The next review should make that distinction visible so an unresolved request does not become an assumed promise.
Use the next meeting to check the prior decision
Begin by reopening the previous action list. Was the contact path corrected? Did the next sample contain acknowledgments? Did the same question recur? If the process still failed, look at the exact step and decide whether the proposed correction addressed it.
A useful review can end with no new campaign or collateral. It may establish that the current process works and that the team should keep it. Record that conclusion and the evidence behind it. Adding activity for its own sake makes the next quarterly review harder to interpret.
Record the meeting in the partner history
BNTouch’s Partner Tracker tutorial around 4:00 demonstrates adding an event to a partner record; the later section around 7:00 covers tracker reporting. Review those features when deciding how the meeting and subsequent activity will be recorded.
The agenda and formulas in this article are examples created for the review. They are not represented as prebuilt BNTouch reports.
Keep referral arrangements out of informal promises
RESPA Section 8 can prohibit things of value exchanged under an agreement or understanding for covered settlement-service referrals. A meeting label does not make an arrangement permissible. Have compensation, co-marketing, gifts, and other arrangements reviewed against the rules that apply to the business. See the CFPB’s RESPA FAQs.
Use the referral partner CRM workflow for the relationship record, and the CRM note examples for writing the next-action summary.

See a partner review in the CRM
Bring an anonymized meeting agenda to a product demonstration. Ask to see the partner record, activity event, and follow-up work.



