August 25, 2026
A technology renewal plan that starts with a school-year cutover : eleven hundred analog lines, three hundred devices, "it has to be done before students return" : usually fails at the first unowned date and dependency, not at the first line count. A calendar window is a constraint. It is not the brief. If you do not write the renewal and notice dates, which services and locations are in scope, who approves life-safety and facilities questions, what evidence a later reviewer will accept, and when the decision must already be made, the next device demo still controls the outcome.
That is why the live 120/90/60-day technology renewal plan starts with discovery around one hundred twenty days and aims to finish validation by sixty, so the remaining time is a buffer rather than a scramble. This note does not replace that page. It is a supporting reminder that a copper-replacement case study is a screening input, not a renewal plan.
What the public briefing is actually about
An Inside the Win episode dated August 12, 2026 records a supplier conversation on plain-old-telephone-service replacement. Presenters describe copper retirement gathering speed: one incumbent spending billions a year to maintain aging plant, others making similar moves after acquisitions or voice-portfolio changes, and a buffered industry-calendar date around 2030 against a 2029 shutdown target. They cite an estimate that about fifteen million POTS lines remain. The published example is a large Georgia school district: roughly eleven hundred lines and three hundred demarcations, with a hard constraint that the migration finish before the next school year. The story names a purpose-built analog-replacement device, multipath transport so an active emergency call does not wait on failover, forty-eight-hour power continuity, remote visibility and alerting, and local fire-code limits on whether LAN or LTE is primary.
Use that example as a requirements calendar only: a distributed environment, a non-negotiable academic window, life-safety endpoints, and a bake-off that started after competitors already had test sites. It is not a Data Partner engagement, not a TDP win, and not a recommendation of the named supplier, device, tracker, or campaign kit. Do not import partner residuals, incentive talk, lead-scraping tools, or "land and expand" language onto a public buyer page. Treat the line counts and dates as theirs, not ours.
What to add to the 120/90/60 plan
Before anyone treats a cutover story as the decision, fill these rows on the live plan:
- Decision identity: renew, renegotiate, redesign, or evaluate another path : and why now. A carrier sunset notice is a trigger, not the outcome.
- Scope: locations, line types, elevators, alarms, emergency phones, fax or elevator rooms, and what is explicitly out of scope.
- Dates: renewal, notice, termination, the academic or seasonal blackout, and the target decision date that leaves room for install and test.
- Owners: business sponsor, facilities, IT, security, finance, legal, and whoever must sign a life-safety or fire-marshal question.
- Continuity and evidence: power duration, path diversity, alerting, who tests an emergency call, and what written validation looks like.
- Comparison criteria: the same management, install, code, and support fields for every option so a late demo is not compared to an incomplete brief.
The technology renewal readiness assessment is the companion when the next step is a control register across contracts, not a single project. If employee or customer calling is in the same window, keep that work on the UCaaS and CCaaS assessment so analog replacement is not treated as a full communications decision.
Questions that belong in the first meeting
Ask the incumbent or a challenger to show, not describe:
- The exact notice and renewal dates, and whether the school-year or seasonal window sits inside the remaining buffer.
- Which endpoints are life-safety versus convenience, and which owner named the test method for each.
- What failed in any earlier trial : visibility, battery, signal, code, or install : in writing, not as a brand contrast.
- How they keep the same criteria if a second supplier arrives late, so a rescue narrative is not the evaluation.
If those answers are a line count and a promised summer install, you do not have a 120/90/60 plan. You have a cutover.
What this post is not
This is not a supplier reprint, not a POTS-product comparison, and not a claim that The Data Partner already migrated anyone's schools after a podcast. Skip incentive talk, skip branded trackers as a substitute for owners, and skip any suggestion that a device demo replaces a dated decision brief. Use the live 120/90/60-day technology renewal plan, write the dates and the dependencies, then request the next conversation.