Lawn care and pest control route service records, 14 firms
Summary
Route service records from 14 US lawn care and pest control companies: scheduled visits, treatment notes, callbacks, customer requests and office mail. Notes record target pests, treated areas, weather at application and follow-up, in the plain language techs type on a phone between stops, often switching between English and Spanish. Customer names, addresses and phone numbers are replaced with placeholders, and product names are reduced to active ingredient.
Collected to order. We collect it from US companies for your order. Scope, volume and timing are confirmed in writing before you sign.
Pricing on request
Request scope and pricingAt a glance
- Planned scope. Volume, sources and timing are confirmed in writing before you sign.
- Records
- 4.2Mservice visits, customer requests and emails
- Size
- 7.3 GB
- Tokens, estimated
- 680M
- Years
- 2019 to 2026
- Firms
- 14
- Owner profile
- 14 US lawn care and pest control companies, residential and commercial routes, 5 to 48 staff each, Southeast and Texas
- Industry
- Field services
- Data type
- Field operations
- Headcount
- 5 to 48 staff per firm
- Region
- United States (Southeast, Texas)
- Languages
- English, Spanish
- Formats
- JSONL, Parquet
- Updated
Sources
| System | Kind | Records |
|---|---|---|
| Jobber visits and technician notes | Field operations | 2.74M visits |
| Jobber requests | Support tickets | 318K customer requests |
| Google Workspace mail | 1.1M messages |
Good for
- training scheduling agents that rebuild routes around weather and callbacks
- classifying customer requests into new service, callback, billing and cancellation
- extracting treatment, target and area details from short technician notes
- evaluating bilingual models on notes that switch between English and Spanish
Fields
| Field | Type | Description |
|---|---|---|
| visit_id | string | Unique visit id within the pool |
| firm_code | string | Placeholder for the company |
| service_line | enum | lawn, pest, termite or mosquito |
| visit_type | enum | initial, scheduled, callback or reservice |
| scheduled_for | timestamp | Start of the booked window |
| completed_at | timestamp | When the tech closed the visit |
| tech_note | string | Technician note as written |
| targets | array<string> | Pests or turf problems treated |
| active_ingredients | array<string> | Active ingredient and formulation, brand names removed |
| weather | object | Temperature, wind and conditions at application |
| language | enum | en, es or mixed |
Example record
{
"visit_id": "LP14-VIS-1907733",
"firm_code": "[COMPANY_9]",
"service_line": "pest",
"visit_type": "callback",
"scheduled_for": "2025-05-06T08:00:00-05:00",
"completed_at": "2025-05-06T09:14:00-05:00",
"tech_note": "Cliente dice que siguen saliendo hormigas en la cocina. Found trailing from slab crack at back door to the dishwasher. Baited under sink and along crack, granular 3 ft out on perimeter, mulch beds done. Told [PERSON_402] no mopping baseboards for 2 days.",
"targets": [
"odorous house ants"
],
"active_ingredients": [
"indoxacarb gel bait",
"bifenthrin granular"
],
"weather": {
"temp_f": 74,
"wind_mph": 6,
"conditions": "partly cloudy"
},
"language": "mixed"
}Licenses available
Non-exclusive
Licensed to more than one buyer.
First look
One buyer gets 2 to 4 weeks to make an offer before anyone else sees the dataset.
What ships with it
- Datasheet: what it is, what it is good for, verified size, sources, years, format and limits.
- Provenance file: the owner shown by code, staff notice and consent status, exclusions, mapped to the EU AI Act Article 53 training-data summary and California AB 2013.
- Manifest with a hash for every file.
- QC report and de-identification report.
- Your own copy, with unique canary records.
How it is de-identified
Default exclusions removed, files flattened to text, identifiers found in three layers and replaced with consistent placeholders, and the result measured against a 99% bar for each identifier type in each source.