Measure seniority, not headcount
Eight attendees from the operations team is a worse result than one director who runs the budget. Score the highest-ranking attendee on each review and track the trend.
| Highest attendee | Reading |
|---|---|
| Economic buyer or executive sponsor | Relationship intact at the level that renews |
| Program owner or manager | Operational relationship, budget exposure unknown |
| Day-to-day user only | The purchase has lost its internal advocate |
| Nobody, meeting canceled twice | Treat as at risk regardless of usage data |
Absence is the signal
A skipped review produces nothing to react to, which is why it gets rescheduled instead of escalated. ORM applies the same reading on the sales side, where the earliest signal of a deal going wrong is the lack of a signal, meaning no activity, no data changing, and no notes. Retention behaves identically, and a customer who stops attending has told you something clearer than any survey response.
Support data confirms or contradicts the read. ORM's view across its customer base is that an account with no support cases at all is at risk of churn, as is one filing seven or more in a year, while accounts filing three to five routine cases are less likely to churn. An account that skips its review and files nothing is disengaged on both channels at once.
Turning it into a play
Attendance belongs in the account score with weight, not as a note in a CRM field. Weight the decline rather than the level, since an account that has always run lean on attendance behaves differently from one whose sponsor stopped appearing two quarters ago.
Then route by cause. A sponsor who left requires a new relationship built from scratch, usually with executive air cover from your side. A sponsor still present but no longer attending requires a different agenda, because the review stopped being worth the hour. Neither problem is solved by a better slide template.
Accounts flagged this way should carry a haircut in the renewal number rather than being modeled at full value, which keeps net revenue retention planning honest and gives the team a quarter of warning instead of a week. The same discipline that improves forecast accuracy on new business applies here. Score the signal, weight it from outcomes, and act on it before the renewal quarter starts.
Frequently Asked Questions
How do you calculate QBR attendance rate?
Divide the number of reviews attended by the number scheduled over the trailing four quarters, then multiply by 100. Track it per account rather than as a team average. A team-level number of 80 percent hides the specific accounts where nobody has attended since last year, and those are the only accounts the metric was meant to find.
Should a delegate count as attendance?
Count it separately. An economic buyer sending a coordinator is a downgrade in engagement even though the meeting happened, and rolling both into one number erases the signal. Score attendance by seniority of the highest-ranking attendee, not by headcount.
Is a canceled QBR a churn signal?
A single cancellation is scheduling noise. Two consecutive cancellations, or a pattern of the meeting being pushed and then quietly dropped, is a signal worth acting on. The pattern matters more than any one instance, and the direction of travel matters most.
What should happen when attendance drops?
Stop rescheduling the same meeting and find out whether the sponsor changed. Attendance declines often trace to a personnel change on the customer side that nobody logged. Re-earning access to a new stakeholder is a different play from sending a fourth calendar invite to someone who has stopped replying.
Put these metrics to work
ORM builds custom revenue forecast models that turn concepts like qbr attendance rate into prescriptive action for your team.
Schedule a Demo