Seller field guide · 3 min read
How do you evaluate ServiceTitan data for an AI license?
Assess company-owned internal methods and coordination, such as dispatch decisions or internal troubleshooting procedures. Client or customer files and anything produced for customers stay excluded, including customer-facing diagnostic reports. A revenue report can inventory activity; it does not establish a reusable collection of internal reasoning.
Check whether a report is aggregated or detailed
ServiceTitan documents report exports to PDF or XLSX and an option to export only aggregated data. Report filters also affect which results appear.
Inspect the chosen report with your administrator. Totals by business unit or date can help inventory operations, but they do not prove that diagnosis notes or dispatch reasoning are included. Confirm the actual available fields on a small allowed job sample before describing a larger archive.
Source notes: ServiceTitan: run, filter and export reports
Define one useful unit of field-service work
An internal operations note may explain scheduling constraints, a diagnostic method or how the team handled a follow-up. Keep the assessment limited to that company-owned reasoning. A customer service report or repair recommendation is a deliverable for the customer and remains outside the scope.
Separate the team’s internal operating methods from household records, customer photos and work produced for customers. Removing an address does not turn an excluded customer file into an eligible internal record. If the permitted method or coordination note cannot be understood without excluded material, omit the example.
Choose a defensible evaluation scope
This is our suggested scoping framework, not a statement that a buyer accepts every record below. Review contractual rights and the intended use before preparing a sample. Technical access to a record does not establish permission to license it.
| Record or context | What to evaluate | Boundary to keep |
|---|---|---|
| Job or dispatch summary | Work category and operational sequence | Remove customer identifiers and precise locations |
| Internal method or coordination note | Company-owned reasoning and handoff logic | Exclude customer-facing diagnosis reports and all customer files |
| Report aggregates | Inventory and coverage across time | Do not present totals as detailed case histories |
Check callbacks and ambiguous outcomes
Include permitted examples where a job required another visit or the final result is uncertain. Explain whether related jobs can be connected after redaction. Otherwise a callback may look like an unrelated new request and the sample can overstate first-visit success.
Keep customer call recordings, photographs, customer files and customer-facing deliverables outside this assessment. Ask the buyer whether the company-owned internal methods and coordination are sufficient for its purpose. Avoid treating a trade-specific headline about data deals as a price benchmark for that narrower collection.
Illustrative scenario · fictional company
ServiceTitan: a fictional scoping example
A fictional field-service contractor reviews internal dispatch exceptions and company-owned method notes, excluding all customer files and work produced for customers. The team verifies that its XLSX report contains job-level rows rather than only totals. It excludes addresses, door codes, customer photos and payment information. A callback is linked with a replacement identifier where permitted, and an unresolved repair is labelled accurately. The evaluation package describes the actual notes available without promising a payout or complete customer history.
When to pause or narrow the scope
Client work and customer files are excluded from this starting scope. Assess company-owned internal records separately from personnel, health, privileged or NDA-restricted material.
- The candidate material is customer files or work produced for customers, including diagnostic deliverables.
- The available material contains only invoices or aggregated performance totals.
- Customer access details and sensitive attachments cannot be separated.
- The company cannot establish rights for the proposed use of job records.
Your preparation checklist
- Choose the field-service workflow and relevant report.
- Verify detailed rows, active filters and note availability.
- Keep customer files and customer-facing diagnostics excluded.
- Label callbacks, follow-up visits and uncertain outcomes.
- Describe remaining context and agree on sample use.
Start with a description of the records. The quote form does not ask you to upload a dataset.
Discuss your dataSources and further reading
- ServiceTitan: run, filter and export reports · Checked October 26, 2026
This is general information, not legal advice or confirmation that a buyer will accept your records. Published buyer ranges describe their programs, not an offer for your dataset. Buyers may pay QuoteMyData when a deal closes; see how we are paid.
