Variance Commentary

A variance without commentary is a data point. A variance with commentary is intelligence. The difference between "revenue missed plan by 8%" and "revenue missed plan by 8% due to a 15-day increase in enterprise sales cycles driven by buyer procurement delays, which we expect to normalize in Q2 based on pipeline aging data" is the difference between triggering anxiety and enabling a decision. Commentary transforms numbers into narrative.

1. The Four-Part Variance Framework Every variance commentary should answer four questions in this order: (1) What is the variance? (Net new ARR missed plan by $340K, or 8.2%.) (2) Why did it happen? (Enterprise cycle times extended 15 days; 3 deals slipped from March to April.) (3) Is it temporary or structural? (Pipeline aging suggests normalization in Q2; slipped deals are in final contracting.) (4) What is the impact on the full-year forecast? (No change to annual plan; Q1 shortfall recovers in Q2 based on committed pipeline.)
2. Materiality Thresholds Not every variance needs commentary. Define thresholds: any metric more than 5% off plan gets a one-line note, more than 10% gets the full four-part framework, more than 20% gets a separate deep-dive slide. These thresholds focus attention on what matters and prevent boards from spending 15 minutes on a $12,000 variance in a $25M business.
3. Forward Impact Language Always connect the backward-looking variance to a forward-looking implication. "Q1 missed by 8%" is history. "Q1 missed by 8%, and based on current pipeline, we project Q2 recovery of $280K of the $340K shortfall, leaving a net annual gap of $60K" is actionable intelligence. The board does not care about last quarter. They care about what last quarter means for next quarter.