# What Pest Control Treatment Records Should Capture > A practical overview of customer, property, product, application, technician, and evidence fields used in pest service records. **Published:** 2026-08-30 **Last reviewed:** 2026-08-30 **Canonical source:** https://wildpipe.com/resources/pest-control-treatment-records-compliance ## Short answer A treatment record should connect the customer and service property to the technician, date and time, target pest, application areas, products and EPA registration numbers, quantities and concentrations, weather where relevant, findings, customer instructions, signatures, and supporting evidence required by the applicable jurisdiction. ## Requirements vary Federal labels, state rules, local requirements, contract terms, and company procedures can differ. Software should make required fields configurable and preserve the completed record; it does not replace legal or label-specific compliance review. ## Operationally useful fields Beyond the minimum required record, capture station history, pest activity, conducive conditions, recommendations, photos, material usage, lot or inventory context when needed, and the customer-facing summary. ## Keep evidence connected The strongest record links the application to the exact appointment, technician, customer, property, route, product inventory, invoice, and any follow-up work. That makes audits and customer questions easier than searching separate PDFs and spreadsheets. ## What to test Create a treatment template with a conditional required question, complete it on a phone, use a tank mix, attach evidence, correct an answer through an approved workflow, and produce a customer report. Confirm that the historical record remains attributable. ## Related authoritative sources - [Pest control module](https://wildpipe.com/features/pest-control) - [Field service app](https://wildpipe.com/features/field-app) - [Training and certifications](https://wildpipe.com/features/training)