Hardware first, tools later: where acceptance history drops out
A refresh usually swaps hardware first and the supporting systems later. The second step is where test archives, maintenance logs and old inventory snapshots quietly drop out, because by then the project team is focused on the new estate and the old tools look like clutter.
Those tools hold the reasoning behind every acceptance decision. NIST SP 800-128 describes change control as changes being formally identified, proposed, reviewed, analyzed for security impact, tested and approved before implementation, with a configuration control board whose size and formality the organization sets, and a post-implementation review that catches unintended effects. SP 800-53A has assessors check that changes are analyzed for security and, separately, privacy impacts before implementation, and SP 800-171 Rev. 3 asks organizations to verify that security requirements are still met after a change. Operators that follow a process like this leave a dated artifact at every step.
The artifact that is easiest to lose is often the most revealing. A test plan built from the inventory can only check what the inventory knew about, so when a change passes every test and still breaks a customer dependency, the pre-change configuration backup is usually where the missing dependency was recorded. Retire the backup store and that explanation goes with it.
The records pass for refresh discovery
A network consultant scoping the refresh can add a short records pass to the discovery work. For each class, note the system, the years covered, the administering team and the retirement date in the plan.
- Change records. Requests, risk and impact assessments, approval board minutes and emergency-change justifications, with the change number as the key.
- Test evidence. Test plans, the scripts or templates they came from, and the pass or fail results with timestamps, wherever the test system stores them.
- Maintenance notes. The engineer's working log for each window: commands run, deviations from the plan, rollbacks considered.
- Acceptance approvals. Who signed off, at what time, against which test results.
- Configuration history. Pre- and post-change configuration backups, which often record dependencies the inventory never captured.
- Customer follow-up. Tickets linked to a change number, and post-implementation reviews.
A refresh inventory, filled in (Illustrative)
A fictional regional fiber operator with 420 employees might record the following. Every entry is metadata.
| Record class | Tool that holds it | Years covered | Administered by | Retirement in refresh plan |
|---|---|---|---|---|
| Change requests and approvals | IT service management platform | 2015 to now | Change manager | Stays; platform not in scope |
| Test plans and results | Legacy test automation server | 2017 to now | Network test lead | Phase 3, date not set |
| Maintenance notes | Shared engineering log | 2016 to now | Network operations | Phase 3, with the test server |
| Inventory snapshots | Legacy inventory system | 2014 to now | Network planning | Phase 2, after data load |
| Configuration backups | Backup appliance | Rolling, per device | Network operations | Phase 2, with old devices |
| Linked customer tickets | Customer care system | 2015 to now | Customer care lead | Stays |
Two rows deserve attention: "date not set", which is a question to raise, and "rolling, per device", which means older backups may already be gone. Where a date is not set, write that down rather than guessing.
Handle outage reports and contractor notes with care
Some records near this trail carry their own restrictions. Under 47 CFR Part 4, covered providers report outages of at least 30 minutes that potentially affect at least 900,000 user-minutes, among other criteria, with final reports due within 30 days of discovery, and those reports are presumed confidential. The operator's own incident and change records usually describe the same events better. Maintenance notes written by a refresh contractor or MSP may belong to the operator or the contractor depending on the services agreement; MSP ticket data covers that question from the provider side.
Do not recommend keeping records the company has no authority or reason to keep, and do not export anything for a licensing discussion. The inventory only tells a decision-maker what exists.
Does the operator qualify?
The introduced company needs 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license the records, and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 90% of the data is in English.
Ask the network operations head about coverage and rights: which tools, which years, who administers each, and who would decide whether to discuss licensing. What stays unknown until SourceX reviews it: buyer interest (see how AI labs buy data), the rights review result (see why data rights matter), and whether an offer follows. Partners sign the Channel Partner Agreement before submitting introductions, and attribution goes to the first valid introduction within the 90-day window, credited when the company submits a verified application. What happens if the law changes during a license answers a common counsel question, and more record types by sector are on the industries hub and the telecommunications page.
Go deeper on network change acceptance
- Network change acceptance referral brief template: a metadata-only brief for operator size, tools, years and owners, with one completed Illustrative example.
- Network change acceptance exception examples: a change that passed its tests and still failed a customer, worked through decision by decision.
- Network change records across systems: a system map of the change, test, inventory and ticket systems, and the change number that joins them.
- Who can license network change acceptance records: a decision tree for operator, contractor and customer records, and who can authorize a licensing discussion.
Next step
Refer a company. Earn up to $100,000. Default reward: 25% of Actual Supplier Payout, capped at $100,000 cumulatively per referred company. Eligibility and payment conditions apply, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.
If the refresh plan retires tools that hold years of tested, approved and reviewed changes, register as a partner, check the operator against who qualifies, and read the program terms and reward rules before you send the network operations head your note.