A pest control company needs about six forms: an estimate, a service agreement, a service report, a chemical application record, an invoice, and a record of your applicators' licenses. Only one of those, the chemical application record, is a legal record your state can inspect, and it is the one most likely to have gaps on paper. Going paperless works when each form is filled in once, at the job, with the required fields enforced, and stored where you can find it years later. Scanning paper forms into a folder is not the same thing.
Below is each form, what it is for, what has to be on it, and where it should live once you stop printing.
What forms does a pest control business need?
| Form | Who it is for | When it is filled in | Legal record? |
|---|---|---|---|
| Estimate | Customer | Before the work | No, but a signed one protects you |
| Service agreement | Customer and you | When a recurring plan starts | A contract |
| Service report | Customer | At the end of each visit | Overlaps with the chemical record |
| Chemical application record | Your state regulator | At each application | Yes, in most states |
| Invoice | Customer and your accountant | When the job is done | Tax record |
| Applicator license log | You and your regulator | When licenses are issued or renewed | Proof of certification |
Some companies add inspection forms for termite or wood-destroying organism work, consent forms for interior treatments, and pre-treatment prep sheets for bed bug jobs. Those depend on your services and your state, so check what your regulator expects before you design them.
Each of the core forms has its own post with a template:
- Pest control estimate template
- Pest control service agreement
- Pest control service report template
- Chemical application record template
- Pest control invoice template
Which paperwork is a legal requirement?
The chemical application record. Everything else is good business practice or a contract between you and the customer, but the application record is what your state's pesticide agency can ask to see.
The fields and the retention period depend on the state. From our state guides:
- Florida keeps general pest control records for 2 years, and some termite or wood-destroying organism records for 3 years (Fla. Admin. Code R. 5E-14.142). Required fields include the customer name and address, application site, date, product name and EPA registration number, target pest, and the applicator's name and license number.
- North Carolina keeps records for 2 years generally, and wood-destroying organism agreements or waivers for 2 years beyond the agreement's expiration date (02 NCAC 34 .0328; 02 NCAC 34 .0604).
- New York keeps records for 3 years and requires commercial applicators to file an annual report with the state Department of Environmental Conservation on or before February 1 for the prior calendar year (N.Y. ECL §33-1205(1)).
- The federal floor for restricted-use pesticide records is 2 years under 40 CFR Part 171.
These are summaries, not legal advice. Rules change; confirm the current rule with your state's pesticide regulatory agency. Our state compliance guides cover 49 states with a link to each official source, and the guide to record requirements explains the fields in more detail.
What goes wrong with paper forms?
Paper is legal in most places. The trouble is not the paper; it is what happens to it between the truck and the filing cabinet.
- Blank fields. Nothing stops a technician from skipping the EPA registration number or the amount applied. You find out at inspection.
- Handwriting. A wet clipboard and a rushed signature produce records nobody can read a year later.
- Lost copies. The customer copy stays at the house, the office copy stays in the truck, and the third copy is wherever it fell.
- Retyping. The service report gets rewritten into a spreadsheet, the invoice gets rewritten into an invoicing tool, and every retype is a chance for a mistake.
Most of these failures are invisible until an audit. The pest control record audit checklist lists what inspectors usually look for, and it is worth running against your own files once a year.
