Pesticide Application Recordkeeping: What Pest Control Operators Must Keep

A missing record costs more than a bad treatment

The fear most operators carry is doing the treatment wrong. That is rarely what suspends a license. What suspends a license is a state inspector asking for the record of a treatment from eight months ago and the operator either not having it or producing one with holes in it. A treatment that went fine but was never documented is, as far as a regulator or a court is concerned, a treatment that may as well not have happened.

The record does three things at once. A state inspector treats it as the compliance document for the visit. If a customer later claims the application harmed a pet, a garden, or someone's health, it is the evidence that you applied an approved product at a legal rate. And the next technician on the account reads it to see what went down last time, which matters for product rotation and for resistance management. Lose the record and you lose all three of those at the same time.

Most operators do the treatment correctly. The gap is the paperwork: a log filled in from memory at the end of the week, a product name with no registration number next to it, a concentration nobody wrote down. Each small omission is the one an inspector or an attorney eventually asks about.

What a complete pesticide application record contains

States write their own lists and the wording differs, but the core set of fields is consistent across nearly every state structural pest control regulation.² A record for a single application should capture all of the following:

1. The product's brand or trade name. The name as it appears on the label, not the shorthand the crew uses for it.
2. The EPA registration number. Every registered pesticide carries one, printed on the label. It is the single field operators skip most often, and it is the one that ties the application to a specific approved product.
3. The amount of product used and its concentration or dilution rate. "Two gallons of finished solution at 0.05 percent" is a record. "Treated the perimeter" is not.
4. The target pest. What you were treating for.
5. The date of the application, with month, day, and year.
6. The address and a description of the specific site treated. The unit, the rooms, the perimeter, the crawlspace. "123 Main St" is weaker than "123 Main St, exterior perimeter and garage interior."
7. The applicator's name and license or certification number. The person who did the work, not the supervisor who signed off later.
8. Your company name and address.

Fumigation adds fields. A structural fumigation record generally also has to include the temperature and the exposure time, because those determine whether the fumigant worked and whether re-entry is safe.³

The test for whether a record is complete is simple. Could a different qualified person, reading only the record, reproduce what you did and confirm it was legal? If a field is missing that they would need, the record is missing it too.

Here is what that looks like filled in. The example below is a routine quarterly exterior treatment, written the way a state inspector would want to see it. Bracketed fields are the ones that come straight off the product label or the technician's license:

• Product: [brand name exactly as printed on the label]
• EPA registration number: [the number on that label, formatted like 1234-567]
• Amount and concentration: 3 gallons finished solution, 0.06 percent dilution
• Target pest: ants, perimeter prevention
• Date: [month, day, year of the visit]
• Site: 1400 Oak Ridge Dr, exterior foundation perimeter, garage interior, two crawlspace access points
• Applicator: [technician name], license number [number]
• Company: [company name and address]

Notice that two of the most important fields, the product name and its registration number, are facts that exist only on the label in the technician's hand at the time of the application. Recorded later from memory, they are a guess.

Federal rules vs state rules: which one governs your business

There are two layers here, and operators often worry about the wrong one.

The federal layer is the Federal Pesticide Recordkeeping Program. It applies to certified applicators who use federally Restricted Use Pesticides, and it was built around agricultural use. It sets a two-year retention period for private applicators, lists the data elements that have to be recorded within fourteen days of an application, and requires a commercial applicator to furnish the customer a copy within thirty days.¹ The program is administered through the USDA and has been largely dormant since its dedicated funding lapsed, so federal enforcement of it is thin in practice.

The state layer is the one that governs a structural pest control company day to day. Every state runs a structural pest control program, usually inside its department of agriculture, and that program writes the recordkeeping rule you are inspected against. State rules are generally broader than the federal one. They typically require a record for every application, not only for restricted-use products, and they often require longer retention.²

One federal change is worth knowing even so. EPA's certification rules under 40 CFR Part 171 were revised, and the enhanced supervision and recordkeeping standards for certified applicators who oversee noncertified applicators using restricted-use pesticides took effect on January 1, 2026.⁴ If uncertified technicians apply RUPs under your certification, the supervision itself is now something you have to be able to document.

The practical takeaway: read your own state's structural pest control regulations and treat them as the floor. The federal list is a useful baseline, but your state almost certainly asks for more.

How long do I need to keep pesticide application records?

Retention is set by each state, and it varies more than people expect. The federal baseline for restricted-use pesticide records is two years under the USDA Federal Pesticide Recordkeeping Program.¹ Many states match that two-year floor for general structural pest control. Some extend it, and a handful go significantly longer. Minnesota requires structural pest control records to be kept for five years after the treatment, with additional fields required on fumigation logs.³

The safe operating rule for a growing or multi-state operation is to keep records for the longest period any state you work in requires, and apply that period everywhere. Storage is cheap. A reconstructed record is not a record, and a destroyed one cannot be reconstructed at all.

Retention is not only about the regulator either. Pesticide-related complaints and liability claims can surface long after the visit. A record you discarded at the two-year mark because your state allowed it is a record you no longer have when a claim arrives in year three.

How to find your state's exact retention rule

Every US state publishes its rule, but the path to it varies. To find yours in under a minute:

1. Open your state department of agriculture website.
2. Look for "structural pest control program" or "pesticide regulation division" in the navigation. Most state ag departments organize the program under one of those two headings.
3. Search the agency page for "recordkeeping" or "records retention." The retention rule is usually given either as a statute citation (Minnesota's, for instance, is at Minn. Stat. 18B.37) or as a numbered chapter of the state administrative code.
4. If the agency page doesn't surface the rule, the state administrative code is the authoritative source. Most are searchable through the state legislature's website or a public law library.

Two states with publicly published retention rules that operators commonly cite as reference points: North Carolina (commercial applicator records governed by the NCDA Structural Pest Control and Pesticide Division)² and Minnesota (five years under Minn. Stat. 18B.37).³ Confirm the current rule in your own state before relying on either as a model; state rules change.

What's the penalty for an incomplete or missing pesticide record?

Consequences for a recordkeeping failure run on three layers in parallel, and most operators only think about the first one.

State administrative action. Every state structural pest control program has authority to issue civil penalties for recordkeeping violations, and most do. The exact penalty schedule is published in your state's pesticide regulations, usually as a per-violation dollar amount that scales with severity and history. Stop-work orders that suspend the company's ability to perform applications, license suspensions, and full license revocation are on the table for repeat offenders. Each missing record can be counted as a separate violation, which means a single inspection that turns up a quarter's worth of incomplete records produces a multiple of the base penalty, not a single citation. The state's public disciplinary action list, where most agencies post the result, is a record a litigant or a competitor can find later.

Federal civil penalty under FIFRA. EPA can bring civil action under the Federal Insecticide, Fungicide, and Rodenticide Act for violations including recordkeeping. The maximum per-violation amount is set in 7 U.S.C. § 136l and adjusted annually for inflation under the Federal Civil Penalties Inflation Adjustment Act; EPA publishes the current ceiling in the Federal Register and at 40 CFR Part 19.⁵ The ceiling for commercial applicator violations sits well into five figures per violation. Federal enforcement against a single missing record on an otherwise compliant operator is uncommon. Federal enforcement against a company with a pattern of missing records and a customer-complaint trigger is not.

Civil liability. This is the layer that hurts most, and the one operators talk about least until they've lived through it. If a customer alleges harm to a pet, a garden, a child, or themselves and you can't produce a complete record of the application (product, registration number, concentration, site, date, applicator), you've lost most of the defense before suit is filed. The record is the document that establishes you applied an approved product at a legal rate at a known site on a known date. Without it, the plaintiff's narrative becomes the only one in the room.

The math of those three layers is why operators with established compliance habits tend to say the record is what saves you. Not the treatment. The treatment is fine. The record is what proves it.

The customer's copy is part of the requirement

The record is not only for your filing cabinet and the inspector. Most state structural pest control rules require that a copy go to the customer, and they are specific about timing.² Some require the technician to leave the record at the site immediately after the application. Others require it to be delivered to the person who ordered the work, or to the property owner, within a set number of days. The federal program gives a commercial applicator thirty days to furnish the required data.¹

This is easy to let slide on a busy route and easy for an inspector to catch, because the inspector can simply ask the customer whether they received it. Build the customer copy into the close-out of every job rather than treating it as a separate task for later.

The same close-out habit applies to billing. If recurring contracts are a large part of your book, our guide on when to send invoice reminders covers getting those invoices paid without chasing them.

Why the record has to be made at the door, not on Friday

This is where most operators lose, and it is the part of recordkeeping we wrote EosLog around. The treatment is fine. The record is the problem, and the problem is timing. A log filled in at the end of the week from memory and a stack of stop notes is exactly where the concentration gets approximated, the EPA registration number gets left blank, and the site description shrinks to a street address.

A record made at the point of application, by the technician who did the work, while standing at the property, is accurate because there is nothing to reconstruct. The product is in their hand. The label and its registration number are right there. The site is in front of them. Every field a state inspector will later ask about is, at that moment, a fact rather than a memory.

That is the real reason to move recordkeeping off the Friday paper log and into something the technician completes on the job. It is not about going digital for its own sake. A structured form the technician fills in before leaving the property forces every required field to be answered while the answer is still in front of them, and it timestamps the record so there is never a question about when it was created. The same record then becomes the customer's copy and your retained copy without anyone re-typing it.

Get that timing right and recordkeeping stops being the part of the job that fails an inspection. It becomes a thirty-second step at the door that you never have to think about again.

---

Sources and further reading

1. USDA Agricultural Marketing Service, "Understanding Federal Pesticide Recordkeeping" (required data elements, the 14-day and 30-day timelines, and the 2-year retention period for restricted-use pesticide records).
2. North Carolina Department of Agriculture and Consumer Services, Pesticide Recordkeeping Requirements; University of Florida IFAS Extension, "The Importance of Keeping Pesticide Records" (PI246); Pesticide Environmental Stewardship, "Requirements for Non-Private Applicators".
3. Minnesota Statutes, Section 18B.37 (structural pest control recordkeeping, the five-year retention period, and fumigation log fields).
4. U.S. Environmental Protection Agency, "Federal Certification Standards for Pesticide Applicators"; eCFR, 40 CFR Part 171, Certification of Pesticide Applicators.
5. Federal Insecticide, Fungicide, and Rodenticide Act, 7 U.S.C. § 136l (civil penalties); U.S. Environmental Protection Agency, "Civil Monetary Penalty Inflation Adjustment Rule" (current per-violation ceilings published annually in the Federal Register and 40 CFR Part 19).

This guide describes general structural pest control recordkeeping practice and U.S. regulations as of 2026. Required record fields, retention periods, customer-copy rules, and fumigation requirements are set by each state and change over time. This is not legal advice. Verify the specific rules for every state you operate in against that state's structural pest control regulatory agency before relying on anything here.