Blog · Forecast and pipeline · Telecoms and connectivity
The complete renewal calendar calculation on five contracts, small enough to check by hand: end date, notice period and monthly value from the register, the notice window start per contract, the activity log's renewal-type entries in the last ninety days, the untouched-in-notice list, value ending per month, the co-terminus customer whose services end months apart, the rolling contract with no end date, and the identity that the calendar's total equals the contracted base, so a reader can reproduce every figure and then run it on their own register.
A renewal calendar is a set of dates and a lookup, and on five contracts it can be checked by hand, including the one with no end date. This page works the notice windows, the activity check, the untouched list, value ending per month, the co-terminus case and the identity. Today is 17 September 2026.
| Contract | Customer | Service | Monthly value | End date | Notice period |
|---|---|---|---|---|---|
| 1 | A | Leased line | $6,000 | 31 Oct 2026 | 90 days |
| 2 | A | Broadband | $2,500 | 31 Mar 2027 | 30 days |
| 3 | B | SIP | $4,000 | 30 Nov 2026 | 60 days |
| 4 | C | Mobile | $8,000 | 31 Dec 2026 | 90 days |
| 5 | D | Leased line | $7,000 | Rolling | 30 days |
Contracted base: 6,000 + 2,500 + 4,000 + 8,000 + 7,000 = $27,500 a month.
Window start = end date − notice period; in notice if today ≥ window start
| Contract | Window start | In notice today? |
|---|---|---|
| 1 | 2 Aug 2026 | Yes |
| 2 | 1 Mar 2027 | No |
| 3 | 1 Oct 2026 | No, in two weeks |
| 4 | 2 Oct 2026 | No, in two weeks |
| 5 | Rolling | Listed separately |
| Customer | Renewal-type contacts since 19 June | Note |
|---|---|---|
| A | None | Two fault tickets; not renewal activity |
| B | Quote issued 4 Sep | |
| C | Renewal opportunity opened 10 Sep | |
| D | None |
| Contract | Customer | Monthly value | Days to end | Untouched? |
|---|---|---|---|---|
| 1 | A | $6,000 | 44 | Yes: in notice since 2 Aug, no renewal activity |
One line. A competitor can quote A's leased line this week.
| Month | Contracts | Value ending |
|---|---|---|
| Oct 2026 | 1 | $6,000 |
| Nov 2026 | 3 | $4,000 |
| Dec 2026 | 4 | $8,000 |
| Mar 2027 | 2 | $2,500 |
| Rolling | 5 | $7,000 |
| Total | $27,500 |
Customer A: leased line ending October, broadband ending March. Five months apart: two renewal events, two chances for a competitor. Aligning both to one date is the retention move.
Σ value ending across all months and rolling = $27,500 = contracted base
End date as the trigger. A is called on 31 October, after the decision.
Any activity as renewal activity. A's fault tickets count; the list is empty.
Rolling contract given an end date. Contract 5 appears in some month it does not end.
Calendar not tied to the base. A contract entered twice or missed, and the total is not $27,500.
The same window per contract, the same activity type check, the same monthly sum, per account manager. Covirage runs it on the contract register and the activity log every week. The renewal calendar guide covers the measure, and the pipeline coverage by industry hub covers the calendar as the desk's pipeline.
Because the customer can give notice from the window's start, and a competitor quoting in that window wins before the end date arrives. An account manager who calls in the month the contract ends is calling after the decision.
A logged contact of renewal type, a quote issued, or a renewal opportunity opened, in the ninety days before the end date. A fault ticket or a billing query is not renewal activity, and the type field is what separates them.
It is on its own list, not silently excluded and not given a fictional end date. It is a customer who could give notice at any time, and it is worth a review on its own cadence.