Designing a matrix plan that survives spillover
Spillover is the most misunderstood feature in matrix plans. It is sold as “your upline builds for you”, but in production it raises concrete questions that must be answered in the plan document.
Question 1: whose position fills first?
When a member sponsors someone and their own matrix is full, the new member spills into the first open position in their downline. Define the traversal order precisely — left to right, breadth first, or by join date. Different orders produce very different team shapes.
Question 2: do inactive positions block spillover?
If a position belongs to an inactive member, does the next joiner skip it? Most plans skip, but the rule must be explicit and visible in reports. Otherwise two admins will read the same tree differently.
Question 3: how is commission attributed?
The sponsor and the position owner are often different people. Decide who earns the direct bonus, who earns the level commission, and whether the position owner earns anything at all for a member they did not sponsor.
Question 4: what happens on refunds?
A refunded member leaves a hole. The engine should either keep the position empty or pull the next member up — never silently rewrite history. Choose one behaviour and document it.
Reporting requirements
- Open positions per member, visible to the member themselves.
- Spillover attribution: who sponsored vs who received the position.
- Level-wise commission with the position path recorded.
- Export of the full matrix with placement timestamps.
A practical test
Simulate 200 members with a 3×3 matrix and a realistic sponsor distribution. Check that no position is double-filled, that every member’s level commissions match a manual calculation, and that the tree remains readable in the admin panel. If the simulation is painful, production will be worse.
Disclaimer: plan design should be reviewed with your legal and financial advisors; this article covers software behaviour only.

