Short answer: Mortgage referral-source attribution is the practice of recording how a relationship entered the database, which partner or campaign is connected to it, when that connection was first verified, and who owns the next partner-facing action. It is not a compensation calculation or a legal conclusion; it is a disciplined relationship record that helps an MLO avoid guessing where business came from.
Referral relationships are easy to overstate in a dashboard. A borrower may have a partner introduction, a web inquiry, a previous relationship, and several communications before becoming active. A useful attribution model preserves that context rather than forcing every record into a single vague source label.
The referral-attribution record
| Field |
Purpose |
Review question |
| Relationship source |
Identifies the broad origin: partner, past client, website, event, or another defined channel. |
Is the source category controlled and understood by the team? |
| Referral source detail |
Captures the specific partner, campaign, or named relationship when known. |
Was the connection verified, or is it an assumption? |
| First verified date |
Records when the team confirmed the relationship context. |
Can a later report distinguish a first introduction from later activity? |
| Partner owner |
Names the person responsible for the partner relationship. |
Does one person own the next partner-facing action? |
| Borrower record owner |
Names the person responsible for the borrower workflow. |
Are partner communication and borrower follow-up clearly separated? |
| Attribution notes |
Captures uncertainty, context, or an agreed correction. |
Could another teammate understand why the field was set this way? |
Keep partner records separate from borrower records
A referral partner relationship and a borrower relationship are connected, but they are not the same record. The partner record helps a team manage relationship history, communication cadence, and ownership. The borrower record supports the borrower workflow. Connecting the records makes attribution reviewable without turning a partner note into borrower data or a borrower task into a partner report.
The Referral Partner CRM Workflow explains the broader operating model: relationship record, permissioned communication, milestones, attribution, and a review cadence. This article narrows the focus to the source fields that keep those reports honest.
Four attribution mistakes to avoid
- Combining channel and source detail: “Realtor website” does not explain whether the relationship came from a named partner, a co-branded asset, or an unknown web visit.
- Changing the original source to match the latest touch: Keep the origin and subsequent activity distinct.
- Assigning a partner without verification: An unknown value is more useful than a confident but wrong report.
- Using attribution as a shortcut for compliance or compensation decisions: Track the relationship; route policy questions to the appropriate review process.
A monthly partner-source review
Review records that have a partner source but no named partner, records with a named partner but no owner, and records whose source changed without an explanatory note. Then look for the workflow cause: unclear lead capture, an incomplete handoff, duplicate contacts, or a missing partner record. A good report leads to a fix in the process, not a debate over a chart.
For digital sources, use a consistent campaign naming convention. Google’s Campaign URL Builder is a useful reference for tagged links. Keep analytics campaign names and CRM source definitions aligned where that is practical, while leaving room for a human to document an offline referral.
Next step: Bring one referral source report that your team does not trust to a BNTouch product consultation. Start with the origin, partner detail, owner, correction path, and the next relationship action.
Sources and further reading
