Software companies
Field service software vendors: licensing work order data from your platform
By SourceX Editorial · Reviewed by Noah Loul ·
Short answer
A field service software vendor can license work order data only through one of two rights paths: its own vendor records, such as support and engineering history, or a customer opt-in program in which contractors agree in writing. Homeowner names, addresses, interior photos and payment details are excluded on either path.
Key takeaways
- Work orders, technician notes and job photos created by contractors are their records, even though they live on your servers.
- Support conversations, product engineering history and job templates your team wrote form the vendor-owned path.
- An opt-in program needs a separate agreement with each contractor, not a quiet change to the subscription terms; data read through another platform's API needs that platform's agreement too.
- Homeowner identity, location, access codes, interior photos and payment details stay out of any licensed package.
What work order data does a field service platform actually hold?#
A field service platform holds two different kinds of work order data: records contractors create to run their businesses, and records your company creates to build and support the software. Mixing the two is the fastest way to stall a licensing project.
Contractor records include service requests, estimates, dispatch assignments, technician notes, parts used, equipment model and serial numbers, before-and-after photos, invoices, warranty claims and callbacks. Together they trace a job from the first call to the repeat visit, which is why AI developers working on diagnostics, scheduling and service agents find them interesting.
Vendor records include Intercom or Zendesk conversations with dispatchers and office managers, Jira issues about scheduling bugs, GitHub history for the technician mobile app, release notes, and the job templates and checklists your team authored. They show how service businesses use software rather than how a specific furnace was repaired.
Which rights path fits your records?#
The rights path that fits depends on who created the record and what your customer agreement says about it. Most vendors find that vendor-owned records can move first, while contractor work orders need a deliberate opt-in program.
The two paths can run side by side, but they should be scoped, documented and approved as separate packages. A buyer reviewing provenance needs to see which records rest on your ownership and which rest on a contractor's signed consent.
A third source of records sits outside both paths. If your product is an add-on that reads jobs through another field service platform's API, that data also comes under the platform's API terms. ServiceTitan's API Terms, for example, grant a license to use its APIs only to develop, test, use and maintain an interconnection between your application and the platform. Treat integration-sourced records as out of scope unless the platform and the contractor both agree in writing.
| Question | Vendor-owned records path | Customer opt-in program path |
|---|---|---|
| What is in scope | Support conversations, engineering history, release notes, authored templates | Selected contractors' work orders, technician notes, parts and equipment records |
| Who approves | Your company's authorized signer | Each participating contractor, then your signer |
| Contract basis | Your ownership of internal records | A separate data contribution agreement per contractor |
| Main preparation task | Remove contractor and homeowner details quoted in tickets | Remove all homeowner identity, location and payment data |
| Main risk | Customer details left inside ticket text or attachments | Contractors feeling their data was used without real choice |
| Relative pace | Faster, with fewer parties | Slower, with one agreement per contractor |
Why homeowner data stays out of every package#
Homeowner data stays out because it identifies private individuals at their homes, and neither your contractor customers nor your company collected it for AI training. A single work order can carry a name, phone number, service address, gate or lockbox code, notes about pets or occupants, and sometimes a card on file.
Technician photos are the hardest part. A photo of a water heater may also show family pictures on the wall, a street number or the inside of a bedroom. Presidio, an open-source PII detection SDK, includes a module for redacting PII in images, but its own documentation warns that automated detection gives no guarantee of finding all sensitive information. Most packages therefore exclude interior photos unless a specific buyer request justifies image-by-image review.
US state privacy laws may apply to homeowner information, and the analysis depends on the contractor's notices, the vendor's role and the buyer's intended use. That assessment is made deal by deal with counsel.
| Work order field | Treatment in a licensed package |
|---|---|
| Homeowner name, phone and email | Remove |
| Service address and GPS coordinates | Remove or generalize to a broad region |
| Gate codes, alarm codes and access notes | Remove |
| Payment and card details | Exclude entirely |
| Equipment make, model and age | Keep; core technical value |
| Fault description, diagnosis and parts used | Keep after free-text review |
| Interior photos | Exclude unless reviewed image by image |
| Technician names | Pseudonymize consistently |
How to design a contractor opt-in program#
A contractor opt-in program works when participation is a real choice, the scope is narrow and the benefit is clear. Burying consent in a renewal or a terms update undermines all three, and contractors talk to each other.
Franchise networks deserve their own review. A franchisee may run the platform account while the franchise agreement gives the franchisor rights in customer and job records, so both may need to sign before any records move.
- Offer a separate data contribution agreement rather than adding a clause to the subscription terms.
- Let contractors choose which job types, date ranges and service areas to include.
- Show exactly which fields leave the platform and which are removed.
- State the permitted AI uses and whether a buyer may use records to build competing field service software.
- Explain compensation or credit, and how withdrawal works for future deliveries.
- Check franchise systems separately, because franchisor and franchisee may each claim the records.
Illustrative: an appliance repair platform picks its first package#
Illustrative: a fictional vendor sells scheduling, dispatch and invoicing software to independent appliance repair and plumbing shops. It has years of Intercom conversations with dispatchers, Jira issues on its route optimizer and offline mobile app, and GitHub history for both.
Leadership first considered a license built from platform work orders, because the fault codes and parts records looked distinctive. Counsel pointed out that the customer agreement limits customer data to running the service and that every work order carries homeowner details. The team chose the vendor-owned path instead.
The first package links dispatcher support conversations to the Jira issues and pull requests that fixed them, with shop names and homeowner details removed. A small opt-in pilot is planned with a few long-time shops, limited to equipment, fault and parts fields.
Mistakes field service vendors make with platform data#
The mistakes field service vendors make with platform data usually come from treating the production database as a single asset. Each one below is avoidable at the scoping stage.
None of these mistakes is exotic. They tend to happen when a promising buyer conversation moves faster than the internal rights review, which is why scope should be written down before any samples are discussed.
| Mistake | Why it causes trouble | Better approach |
|---|---|---|
| Treating anonymized work orders as automatically licensable | Removing names does not change who controls the record | Use the opt-in path for any contractor records |
| Leaving technician notes unreviewed | Notes can name occupants or describe their health and routines | Review free text with tools plus human checks |
| Ignoring photos attached to support tickets | Dispatchers attach job photos when reporting bugs | Exclude ticket attachments from the vendor package |
| Assuming franchise records belong to the franchisee alone | Franchise agreements may give the franchisor rights | Confirm both parties' positions in writing |
| Licensing job data pulled through another platform's API | Platform API terms may limit use to running the integration | Exclude integration-sourced records unless the platform agrees in writing |
| Announcing a program before scoping it | Contractors react to rumors, not terms | Scope first, then brief key accounts |
How SourceX handles field service platform records#
SourceX handles field service platform records by treating the vendor-owned package and any opt-in program as separate transactions under the SourceX five-step transaction: Supply, Rights, Preparation, Approval and Delivery. The first conversation uses metadata only, such as systems, years of history and record families.
Rights review records which contract governs each record family, preparation removes homeowner and contractor details, and the supplier approves every step before anything is delivered. The SourceX Evidence Packet documents provenance, licensing rights, permitted use, the privacy record and release authorization for each package.
Frequently asked questions
Can we license equipment failure data if we strip out homeowner details?
Possibly, but removing details does not settle who controls the records. Equipment, fault and parts fields usually come from contractor work orders, so they belong on the opt-in path. Counsel should check whether your customer agreement allows any use beyond running the service before such fields are included.
Do technician photos and videos have value to AI developers?
They can, especially when linked to the diagnosis, parts used and outcome of the job. They are also the hardest records to prepare, because they show homes, people and addresses. Most vendors leave them for a later, carefully reviewed phase rather than a first package.
What if a contractor asks us to license its data on its behalf?
That can work under a written agreement that makes the contractor the supplier and your company the operator of the export. The contractor approves scope and preparation, the homeowner exclusions still apply, and your role should be documented so responsibilities are clear on both sides.
Should contractors share in the revenue?
If their work orders are licensed, they usually should receive something, whether a revenue share, a service credit or another benefit set out in the agreement. Purely vendor-owned records, such as your support and engineering history, do not require sharing, although some vendors explain the program to customers anyway.
Do we need a minimum number of participating contractors?
No fixed minimum applies. Buyer interest depends on the record type, depth of history and how well jobs link from request to outcome. A narrow pilot with a few contractors who have long, clean histories can be more useful than a broad program with thin records.
Sources
- Presidio is an open-source, MIT-licensed SDK for PII identification and anonymization in text and images, and its documentation warns that because it uses automated detection there is no guarantee it will find all sensitive information. Source
- ServiceTitan's API Terms grant a limited, non-exclusive, nonsublicenseable, nontransferable, royalty-free license to use the APIs only to develop, test, use and maintain an interconnection between your application and the platform. Source
Related resources
- QuestionCan SaaS data be licensed?
- InsightConstruction software companies: what project data you can and cannot license
- InsightAI features in acquired products vs licensing records out: a holdco rule
- IndustryFintech software data
- QuestionWho owns enterprise data?
- InsightData licensing rules for call centers and BPOs
See if your company qualifies
A short company assessment. No data uploads are needed.