Why 'real-time' is the wrong answer to how often sales data should be refreshed, the cadence each measure actually needs, weekly for coverage and pipeline, monthly for share of wallet and concentration, quarterly for norms and segments, annually for definitions, what a refresh more frequent than the measure's cadence does to the reader, and the export schedule that follows.
Asked how often sales data should be refreshed, most people say as often as possible. Each measure has its own cadence, set by how fast it moves and how often anyone can act, and refreshing faster than that makes the measure worse. This guide gives the cadence per measure and the export schedule that follows.
| Cadence | Measures | Why |
|---|---|---|
| Weekly | Coverage, untouched accounts, first-touch latency, pipeline coverage, slip count, hygiene checks, surge, quiet clients | They change weekly and are worked weekly; the list is the Monday |
| Monthly | Revenue against plan, share of wallet, gap at norm, dormancy, churn, concentration, margin, price realisation, movements | The ledger closes monthly; the measures move monthly; the pack is monthly |
| Quarterly | Norms, segments, tiers, cadence per tier, forecast bias, win rate by cell, health score weights, attainment shape | They describe the base; recomputed more often, they oscillate |
| Annually | Definitions, role matrices, rate cards, thresholds review | Changing them restates history; once a year, versioned |
| Measure refreshed | At | Effect |
|---|---|---|
| Share of wallet | Daily | Moves by rounding; the reader stops looking |
| Coverage | Hourly | Watched like a stock ticker; the list is never finished |
| Norms | Monthly | Customers cross segment boundaries and back; the gap list churns |
| Thresholds | Weekly | Tuned to last week's noise |
A measure refreshed faster than its cadence teaches the reader that movements do not mean anything.
| Export | Cadence | Period cut | Control total |
|---|---|---|---|
| CRM activities | Weekly | Week ending Sunday | Activity count |
| Pipeline snapshot | Weekly | As at Sunday | Open pipeline value |
| Ledger | Monthly | Calendar month | Revenue on the finance screen |
| Customer master, assignments | Monthly | Month end | Account count |
| Norms, segments, tiers | Quarterly, computed | Quarter end | |
| Definitions | Annually, versioned |
Two weekly drops, two monthly drops. The rest is computed.
| Day | What happens |
|---|---|
| Monday | Weekly exports dropped; validation read; the lists and the digest go out |
| First working day | Monthly ledger dropped; validation read; the pack computed; movements read |
| Quarter end plus a week | Norms and tiers recomputed; movements caused by recomputation listed as such |
One cadence for the tool. Everything daily, or everything monthly.
Real-time as a goal. Noise, watched.
Norms recomputed monthly. The gap list churns at the boundaries.
Definitions changed mid-year. History restated silently.
Covirage computes each measure on its cadence from exports dropped on the schedule, and states the cadence and the period on every table. The monthly refresh guide covers the monthly drop step by step, and the threshold guide covers why the weekly digest is not noise when the cadence is right.
Because share of wallet does not change between Tuesday and Wednesday, and a coverage figure that moves every hour is watched instead of worked. Real-time is the right cadence for an operations console. For a measure that produces a weekly list, the weekly refresh is the cadence, and anything faster is noise with a cost.
Then revenue-based measures are monthly by construction, and that is correct. Activity-based measures can still be weekly from the CRM export. The two cadences coexist, and the report says which measures are on which.
No. A weekly measure and a monthly measure use the same definitions. The cadence sets the period cut and the refresh; the definition sets what is computed. Both are stated on the report.