A referral tree grows quietly. Without structure it becomes impossible to explain.
Show the tree
A visual or list of who referred whom, with member counts. Propto provides Teams and Referrals in tree and list views.
Tie it to commissions
Levels determine payouts. Keep the tree accurate before processing statements.
Prune inactive branches
Archive inactive partners to keep reports clean.
What a referral tree is
In some partner programmes, partners can bring other partners into the network. The person who referred a new partner may earn a share of that partner’s commissions, sometimes across several levels. The structure of who referred whom forms a referral tree.
Managing it well matters because commissions depend on it. Errors in the tree lead to wrong payments and disputes.
Showing the tree
Display the tree clearly, with each partner, their referrer and the partners they referred. Both tree and list views help: the tree shows structure, while the list makes searching and filtering easier.
Show counts of members at each level, so partners and managers can understand the size of each branch.
Tying the tree to commissions
Commission rules for referral levels should read directly from the tree. When a booking is made, the system identifies the closing partner and their upline according to the rules, calculates each share and shows it on statements.
Keep the number of paid levels small and documented, so calculations stay understandable.
Recording referrals correctly
Record the referrer when a partner joins, with a timestamp. Changing referrers later should require approval and a reason, because changes affect commissions.
Avoid relying on verbal claims about who referred whom.
Pruning inactive branches
Over time, some partners become inactive. Decide how inactive partners affect the tree: whether their downline moves up, stays in place or remains linked for historical commissions. Document the rule.
Review inactive partners periodically.
Transparency for partners
Partners should see their own downline and the commissions they earn from it, but not private details of unrelated partners. Transparency builds trust; over-exposure risks privacy.
Show the rules for referral commissions alongside the tree.
Preventing abuse
Multi-level structures can attract attempts to game the system, such as fake partners created to capture commissions. Require KYC for every partner and monitor unusual patterns, such as many new partners with no activity.
Pay referral commissions only on genuine bookings with payments received.
Why it matters for the business
A well-managed referral tree can expand reach, but a poorly managed one creates disputes, overpayments and reputational risk. Clear structure, accurate records and transparent rules protect both the business and honest partners.
Simplicity is a strength; complexity invites confusion.
Getting the team involved
Partner managers maintain referral records, finance applies commission rules, legal documents the programme and management approves changes. Configure rules in your system so calculations are consistent.
Train partner managers to explain the tree with examples.
Building the habit
Review the tree monthly for new partners, inactive branches and unusual patterns. Reconcile referral commissions with statements before payouts.
Communicate changes to partners in advance.
A worked example
Partner A refers Partner B, who later refers Partner C. When C closes a booking and the payment trigger is met, the system calculates C’s commission, B’s level-one share and A’s level-two share according to the rules. Each partner sees their share on their statement with the booking reference.
When B becomes inactive, the documented rule determines how future referral commissions flow.
Common mistakes
Common mistakes include unrecorded referrers, too many paid levels, referrer changes without approval and no KYC for new partners.
Another mistake is paying referral commissions before booking payments are received.
Questions teams often ask
How many levels should be paid? Usually no more than two or three.
Can a partner change their referrer? Only with approval and a recorded reason.
A referral tree checklist
Tree and list views. Referrers recorded with timestamps. Commission rules read from the tree. Limited, documented levels.
Inactive partner rules. Partner views restricted to own downline. KYC for all partners. Monthly reviews.
In practice
Map your current referral relationships, record them in the system with dates and configure commission rules. Share tree views with partners and explain the rules with examples.
Review the first quarter’s commissions carefully.
A final word
Referral programmes reward partners for growing your network, but only if the records behind them are trusted. Accurate, transparent trees protect honest partners and the business alike.
If the structure ever becomes hard to explain in a short conversation, simplify it before it grows further.
In short
Record referrals accurately, show the tree clearly, calculate commissions from it with few levels, handle inactive partners by rule, protect privacy, require KYC and review monthly.
A final word
Referral trees reward partners for growing your network, not for bringing buyers directly. Keep that distinction clear in how you explain the programme, so partners understand why two different kinds of effort both deserve recognition, and so the structure never feels like it competes with direct selling.
Review the structure every year as the network grows.
In one line
Clear structure, honest records and limited levels keep referral programmes rewarding rather than confusing.
Keep it simple.
Review yearly.
Transparent, simple rules keep the whole network confident in how they are rewarded.
Is there a tree view?
Yes, Teams and Referrals offers a tree and list with member counts.