Blog · Coverage and territory · Education
How an education publisher, edtech or training provider measures programme fit per institution and builds a renewal watch from the CRM and order history: programmes held against eligible, renewals due with no contact, territory coverage per manager, and the reconciliation to invoiced revenue, with no student data involved.
Education is sold on the academic calendar, and a renewal missed in spring is a year lost. Providers know which institutions they invoiced last year. They rarely have a single view of which programmes each institution holds against what similar institutions hold, and which renewals are due with nobody having called. Both are in the CRM and the order history. This guide sets them out.
Per institution:
Programme fit = programmes held ÷ programmes in the norm for the institution's type and size Renewal at risk = renewal due in the window and no logged contact this term
Per regional manager:
Coverage = institutions with a logged contact this term ÷ institutions assigned Renewal watch = the list of at-risk renewals, ranked by value
Institution identifiers only.
Band institutions by type and size: primary, secondary, further, higher, by enrolment band. For each band, the share of institutions holding each programme in the trailing two years. The fit set is every programme held by more than half the band.
invoiced revenue = Σ regions = Σ managers = Σ institutions = Σ programmes
The by-programme equality catches a programme re-badged at the start of a year. The by-manager equality catches a district split between two managers without a date.
Secondary band, norm of four programmes. One institution, renewal due in twelve weeks.
| Programme | Held | Revenue | In norm | Gap at list |
|---|---|---|---|---|
| Core maths | Yes | £18,000 | Yes | |
| Core English | Yes | £16,500 | Yes | |
| Assessment | No | Yes | £9,000 | |
| Intervention | No | Yes | £6,000 |
Fit: two of four. Renewal on the two held programmes is due in twelve weeks, and the last logged contact was in the previous academic year. The manager's list for this week opens here: a £34,500 renewal with no contact this term and £15,000 of fit gap to raise in the same conversation.
Institutions under several identifiers. A multi-academy trust, its academies and a legacy school code all appear as separate institutions with partial programme sets. Roll up to the entity that signs the contract, and keep the sites as attributes.
Renewal dates missing. Orders without a renewal date fall out of the watch. Derive from the subscription term where the order has one, and count the orders that have neither.
Contact logged to the wrong level. A call with a trust's procurement lead logged against one academy leaves the other nine silent. Log at the contracting entity, or roll contacts up to it.
Fit against the whole catalogue. A small primary school shown missing a sixth-form programme discredits the list. Fit per band.
Mapped once, the order history and the CRM export produce the renewal watch and the fit list per manager at any point in the term, reconciled to invoiced revenue. Covirage builds this from the exports as they are, institution identifiers only. The education page describes the setup, and you can upload a sample order export and see the roll-up on your own rows.
No. The measures use institution identifiers, programmes, revenue and contact dates. Student records never enter it, which is usually the first question a school or university's data office asks.
The academic calendar sets it. A renewal due at the start of the autumn term with no contact by the end of the spring term is at risk, because the decision is made before the summer. Set the window per region's calendar.
Yes. Employers replace institutions, courses replace programmes, and the renewal follows the contract date rather than the term. The roll-up is the same.