It is 9:40 the night before the board meeting. The deck goes out at 8. You are in the CRM, filtering closed-won deals by partner, hoping the result looks close to last quarter.
That is the whole process. It runs four times a year, and the number it produces is the one you will defend to the CEO, the CFO, and the board.
The quiet problem: a number that is only true four times a year
Most partner programs do not have a partner-sourced number. They have a partner-sourced event. Once a quarter, someone pulls a report, adjusts it by hand, and sends a figure up the chain. Between those dates, nobody looks.
The result is a number with no history. You cannot say what it was in week six. You cannot say which month it moved. You cannot say whether the change came from new partner activity or from a filter someone changed in the report.
A number that cannot be reproduced on a random Tuesday is not a metric. It is an estimate with a deadline.
The short version
Partner-sourced cadence is the schedule on which a channel team calculates, freezes, and reviews its partner-sourced number. A defensible cadence answers four questions: how often the number is refreshed, who owns the refresh, what gets frozen at each close, and how changes are explained between board meetings. Cadence is one of the four attribution decisions, alongside definition, credit rules, and data source.
The reframe: this is not carelessness
The quarterly scramble is not a sign that the VP of Channel is sloppy. It is what happens when the program grows faster than the process. The first year, one person can eyeball the number. By year three, the program has dozens of partners, three deal types, and a board that asks follow-up questions.
The number was never wrong on purpose. It was just never put on a schedule.
1. How often is the number refreshed?
Picture a board member asking, "What was partner-sourced pipeline in the first half of the quarter?" If the answer is "I would have to pull that," the cadence is too slow.
Defensible looks like a monthly refresh at minimum, and a weekly one for pipeline. The point is not more reporting. The point is that the number exists on dates other than board dates, so the board number is a rollup of numbers you have already seen.
2. Who owns the refresh?
When the answer is "whoever is available," the answer is the VP of Channel at 9:40 p.m. Ownership has to be a named role with a standing slot on the calendar, not a favor.
Defensible looks like one owner, one backup, and a written checklist. If the owner goes on vacation in the last week of the quarter, the number still closes on time, using the same steps.
3. What gets frozen at each close?
CRM data moves. Deals get reassigned, partner fields get edited, and closed dates shift. If you recalculate from live data each quarter, last quarter's number quietly changes, and nobody can say why.
Defensible looks like a dated snapshot at every close. The sourced number, the deal list behind it, and the rules applied are saved as they stood that day. When the CFO asks why Q2 is different from what you reported in July, you have both versions and the reason.
4. How are changes explained between meetings?
A flat number hides a lot. Two large deals can drop out while three small ones come in, and the total looks the same. A rising number can come from a new partner or from a definition change.
Defensible looks like a short variance note with every refresh: what moved, which partners drove it, and whether any rule changed. Three lines is enough. It turns the board conversation from "is this right?" into "what do we do about it?"
Why this matters now
Budget season rewards the leader who can say the number has been tracked monthly, snapshotted at every close, and explained at every change. It punishes the one who recalculates under pressure and gets a different answer than last time.
There is a scaling cost too. You cannot decide which partners to invest in, which to reactivate, and which to retire from a number you only see four times a year. Slow cadence means slow decisions, and the channel stays at the size it was when the process was last good enough.
If you want to see where your cadence stands against the other three decisions, the Partner-Sourced Pipeline Scorecard scores all four in about ten minutes.
You cannot defend what you cannot see
A number you look at four times a year is a number you do not see. Put it on a schedule, give it an owner, freeze it at every close, and explain every move.
Prove your channel first. Then scale it.
Want a second set of eyes on your cadence? Take the scorecard, or book a working session.
Frequently asked questions
How often should a partner-sourced number be calculated?
Monthly at minimum, with pipeline reviewed weekly. The board still sees it quarterly, but that figure should be the rollup of numbers you have already tracked, not a first-time calculation done the night before.
Why does the partner-sourced number change after the quarter closes?
Live CRM data keeps moving. Deals are reassigned, partner fields are edited, and close dates shift. Without a dated snapshot at each close, a recalculation produces a different answer and nobody can explain the gap.
Who should own partner-sourced reporting?
One named owner with a named backup and a written checklist. In companies without channel ops headcount, this often defaults to the VP of Channel, which is fine if the refresh is scheduled and documented.
What is a snapshot in channel attribution?
A dated copy of the partner-sourced number, the deals behind it, and the rules applied at the time of close. It lets you reproduce any past quarter exactly and explain differences later.
Is a monthly cadence too much work for a small channel team?
Not if the data source and credit rules are set. A monthly refresh on a defined process takes far less time than a quarterly rebuild from scratch, and it removes the deadline scramble.