What a utility contractor platform can license
A utility contractor's own field records can support an AI data license: storm deployment logs, tailboard and job briefing forms, crew productivity reports, fleet maintenance histories and incident investigations. Material that belongs to the utility customer, such as construction standards, system maps, circuit and protection data and anything the utility treats as critical infrastructure information, stays out.
For an operating partner, the question is not whether the platform does valuable work. It is whether the records describing that work belong to the contractor, and whether there are enough of them across enough years.
Why sponsors are looking at these records now
Sponsors have assembled platforms in distribution and transmission line work, substation construction and vegetation management, adding regional contractors one at a time. Each add-on arrives with its own field apps, timesheets and storm files.
The pressure to find value inside those platforms is real. McKinsey's Global Private Markets Report 2026 says multiple expansion and cheap leverage, which accounted for 59 percent of private equity returns between 2010 and 2022, have faded, leaving operational value creation as the likely primary source of returns. A one-time license payment for records the contractor already keeps is an operational lever that needs no new crews, trucks or capital.
AI developers want this material because it records high-stakes physical work with decisions and outcomes attached: a hazard named at a tailboard, a crew reassigned when a line stayed energized, a restoration estimate revised as damage assessments came in. That kind of context is thin on the public web.
What records utility contractors keep
| System | Records | Why AI labs and data users value them |
|---|---|---|
| Storm deployment files | Mobilization orders, crew rosters, staging and travel logs, daily assignments, restoration times, release dates | Time-stamped decisions under pressure, with clear outcomes |
| Job briefing and tailboard forms | Hazards identified, controls chosen, work method, sign-offs | Structured risk reasoning attached to each job |
| Crew productivity reports | Units completed per day, footage, poles set, spans trimmed, delays and causes | Planned-versus-actual records at crew level |
| Vegetation management plans | Trim cycles by circuit, hazard tree assessments, work completed, property owner refusals | Assessment-to-action chains over several years |
| Fleet and equipment systems | Bucket truck and digger derrick maintenance, telematics, breakdowns, repairs | Failure and repair histories tied to assets |
| Safety and incident records | Near misses, incidents, investigations, corrective actions | Root-cause analysis with follow-through |
| Estimating and bids | Unit-price bids, crew mixes, won and lost results | Pricing decisions with outcomes |
| Timekeeping and job costing | Hours by job and crew, cost codes, change orders | Links effort and cost to the work performed |
The energy and utilities industry brief covers the utilities themselves; this page is about the contractors that serve them.
Contractor-owned or utility-owned: where to draw the line
The master service agreement settles most of this. Read the data, confidentiality and work-product clauses before anyone describes the records to an outside party.
| Record | Typical position | How to treat it |
|---|---|---|
| Utility construction standards, specifications and design manuals | Belongs to the utility | Out of scope |
| System maps, GIS layers, circuit and protection settings, substation drawings | Belongs to the utility, often handled as critical infrastructure information | Out of scope |
| Work orders issued through the utility's portal | The utility's system; the contractor may hold copies | Check MSA confidentiality and data terms |
| The contractor's own job briefings and safety forms | Contractor | Candidate, with names and locations handled under agreed redaction rules |
| Storm logs kept by the contractor | Contractor, though they reference utility circuits and outages | Candidate once utility-specific details are removed or approved |
| Hazard tree assessments prepared for the utility | Depends on the MSA's work-product clause | Confirm ownership before including |
| Crew productivity and job-cost records | Contractor | Candidate |
If an MSA says every record generated under the contract belongs to the utility, the related records are out unless that utility agrees. Platforms that also serve data centers face a similar operator-versus-customer split, described in the guide on colocation company acquisitions.
Which platforms fit
- Size: 50+ full-time employees at peak (contractors excluded). Storm surges often lean on subcontracted crews, so count only the platform's own full-time staff.
- History: several years of documented operations, ideally covering multiple storm seasons and the archived systems of acquired companies.
- System depth: field apps, a fleet system, timekeeping, an ERP, safety software, email and chat, with records that connect across them.
- Rights: MSAs that leave the contractor owning its own operating records.
- A sponsor: the platform CEO, CFO or another authorized representative who can approve a license.
Vegetation management contractors, distribution line builders and substation construction firms tend to hold the most structured records. Crews that work only inside the utility's own systems tend to hold the least.
The grid-records screen for operating partners
Run these seven checks with the platform CFO before an introduction.
- ☐The platform reached 50+ full-time employees at peak (contractors excluded).
- ☐MSAs with the largest utility customers leave operating records with the contractor, or the utility would consider consent.
- ☐The records stay useful with all utility-designated critical infrastructure information removed.
- ☐Field app and fleet data can still be exported, including from systems retired after add-ons.
- ☐Job briefings and incident files can be handled under agreed redaction rules for names and locations.
- ☐The records have not already been licensed for AI training.
- ☐An authorized sponsor will consider a one-time payment for an exclusive license.
For a quick first pass that commits no one, use the company fit checker; the who qualifies page spells out every baseline requirement.
When in the hold to raise it
| Moment | Why it works | Question for the platform CEO |
|---|---|---|
| Add-on integration | Acquired contractors move onto the platform's field apps | Are the add-on's old briefing and storm files being kept? |
| After storm season | Deployment files are fresh and performance reviews are under way | Who owns the storm logs, and are they complete? |
| Field software consolidation | Legacy apps are about to be switched off | Can we take a full export before the cutover? |
| Annual budget | Non-dilutive income is on the agenda | Would a one-time license payment matter this year? |
| Exit preparation | Buyers ask what assets the platform holds | License before the sale, or leave it to the next owner? |
The wider method sits in the guide on assessing portfolio company data opportunities.
How the introduction runs
- You register as a partner and send the platform CEO your referral link, or submit the company through the referral form.
- SourceX confirms size, history, data breadth and rights with the sponsor.
- The platform inventories its systems and years of history, and its counsel reviews MSAs for ownership and confidentiality limits.
- Price and terms are agreed with the platform before any buyer sees a description.
- SourceX completes its final review.
- The license is signed, records are prepared and delivered under the agreed redaction rules, and the platform is paid.
You never export or describe field records yourself; the platform's own team owns the inventory.
What to say to the platform CEO
Our crews have years of storm files, tailboards and productivity data. Some contractors license records like these to SourceX for a one-time payment, keep ownership, and leave out anything the utilities own. SourceX runs the rights review and the process. Worth a short screen before we consolidate the field apps?
How the sponsor's reward works
Partners earn 25% of the compensation SourceX actually pays the company you refer, capped at $100,000 per referred company. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details. Because the reward is paid by SourceX, the platform's proceeds are unchanged. Check your fund's policies on fees connected to portfolio companies.
Next step
Pick the platform with the most storm seasons on record and walk through the grid-records screen with its CFO. If it passes, register as a partner and make the introduction; the page for private equity operating partners explains how the partner role works across a portfolio.