TLTreatLog
Menu
FeaturesSee how it worksROIPricingBriefingsNewsStatesMCPSee how it worksStart free

Resources

California monthly pesticide use reporting for structural PCOs

Who this is for: the owner or office manager at a structural pest control company who already keeps an application record and has to turn the month into a county summary. Date: 2026-09-24. Re-read the agency pages below before you file. Portals and form revisions move.

Compliance disclaimer

This is an operator checklist, not legal advice, and not a filing. TreatLog is not a government filing agent and is not certified by the Department of Pesticide Regulation (DPR), the Structural Pest Control Board, any county agricultural commissioner, or the U.S. EPA. You remain responsible for the accuracy of your records and for what you submit. State packs are templates and best-effort field mappings. They can lag a form change. Verify the current form and your county’s portal rules before you file. Full notice: treatlog.com/legal/compliance.

Two different records

Structural shops in California are dealing with two obligations that software often mashes together.

The application record. A registered company compiles a report for each structural pest control application (other than fumigation) and keeps it at least three years. 16 CCR § 1970 says that report contains:

  1. Date and time of application.
  2. Name of the owner or their agent.
  3. Address of the property.
  4. Description of the area or areas treated.
  5. Target pest or pests.
  6. Pesticide product name, including the U.S. EPA or California registration number on the label, and the amount used.
  7. The applicator identities and license numbers the subsection specifies (certified commercial applicator where restricted materials are applied or supervised, and the noncertified commercial applicator where that applies). Read (b)(7) itself before you shorten it to “tech name.”

The same section says the term “fraudulent act” in Business and Professions Code § 8642 includes falsification of these records. That is a reason to correct a mistake with an amendment instead of quietly overwriting it. It is not a legal opinion about any shop’s past paperwork. Fumigation is a separate log (the Standard Structural Fumigation Log). TreatLog is not that log.

The monthly summary. People who have to keep pesticide use records under the pesticide-use rules report a summary of the month’s use to the commissioner of the county where the work was performed, by the 10th of the following month. If it is mailed, the postmark is the delivery date. The regulation is 3 CCR § 6627. The form DPR publishes for this is the Monthly Summary Pesticide Use Report, DPR-PML-060 (counties also call it DPR-ENF-060 / PR-ENF-060).

DPR’s form instructions say, in short:

  • File with the county agricultural commissioner for the county where the work was done. A separate report for each county.
  • Use code 10 for structural pest control: work within or on buildings and other structures. Landscape around a building is a different code (30). Do not assume every job on the route is code 10.
  • Identify the pesticide, including the EPA or state registration number on the label, and the amount used.
  • Report the number of applications of each pesticide. The form instructions say to count each separate site (a home, an apartment complex, a building) as one application, and to credit each pesticide in a tank mix with an application.
  • For a month with no pest control work, licensed pest control businesses submit a use report by the 10th to each county where they are registered, stating that no work was performed. That sentence is on the form instructions. Confirm it with the county you are registered in.

A 2012 DPR enforcement letter (ENF 12-18) told counties that structural businesses report the total number of applications for each registered pesticide on the monthly summary, restricted or not. Some counties also expect a structural stamp with the summary under Business and Professions Code § 8505.17, and county CalAgPermits tutorials say the stamp procedure is not the same in every county. Ask your commissioner before you assume a portal click finished the job.

TreatLog does not submit this form.

What to have in hand on the 8th

Use this as a prep list. It is not a substitute for the form.

  • Company name and address, and the county (and county number, which the commissioner publishes) for this report.
  • Month and year.
  • For each product used in that county: product name, EPA or CA registration number exactly as on the label, amount used in the unit the form wants, number of applications, site code 10 when the work was structural.
  • The underlying application records that add up to those totals, kept so an inspector can see date and time, address, areas, target pests, product and registration number, amount, and applicator identity.
  • A no-work report if you are registered in a county and did nothing there.
  • Your own copy. The form tells you to retain one.

What TreatLog exports today

The MVP state pack for CA is a stub, not a filled DPR-PML-060 and not a CalAgPermits upload.

What the log can hold, per application: when it was applied, the site (address, city, state, ZIP), areas, target pests, method, the applicator, license numbers, and each product’s EPA registration number, brand, undiluted amount and unit, dilution, and total volume.

What the downloaded CA file actually contains today: one row per application-product, as CSV (or JSON), with state, applied-at, application id, brand, EPA Reg. No., undiluted amount, unit, areas, and an incomplete flag. Dry-run is the default. Incomplete rows stay in the file and are flagged. They are not dropped to make the month look clean. Marking a report “filed” stores your office’s attestation and a confirmation reference you type. It does not contact DPR or the county.

What that file is not:

  • A rollup by product and county.
  • A count of applications the way column D on DPR-PML-060 describes a site.
  • A county field. The site record has no county yet, so the stub cannot fill “county where work was performed.”
  • Proof that “undiluted amount” is the number your county wants in “amount used.” Compare one month to the form before you rely on it.
  • An auto-filed report. You or your office still submit.

Other states in the product (TX, FL, WA, IL, OH, NC) are not this pack. Asking for them returns pack_unavailable until that pack ships.

Plans that include a state pack, month-to-month: Treat Starter is $49 (one pack), Treat Compliance is $99 (up to three), Treat Multi-State is $179 (the eight sampled packs). Field Free is $0 and includes one state profile, not this pack. Prices are public. None of them include filing.

A sane monthly rhythm

  1. Techs log the treat the day it happens, with the EPA number from the company library rather than a nickname.
  2. The office clears the completeness inbox before the 8th. A missing amount or EPA number is fixed on the application, with the correction visible, not pasted over.
  3. Download the CA stub as a dry-run. Read every incomplete=yes row.
  4. Build the county summary yourself (or in CalAgPermits) from those rows plus anything the stub does not total. Diff it against last month’s accepted file the first time you do this.
  5. Submit on the county’s terms by the 10th. Keep your copy with the application records.
  6. If a column you need is missing, name it. That is an ask, and the person who asked should hear when it ships.

If you want this walked through on your file

Bring last month’s summary. Ten minutes is enough to see the stub next to it: book a binder funeral, or start free if you are a solo logging one state. Questions about an export you already ran: support@treatlog.com. A shop, a plan, or a design-partner cycle: sales@treatlog.com.

Sources