Pesticide & Chemical Tracking
EPA-compliant chemical records built into every job. Pest jobs, inspections, and work orders aggregate into a CA DPR monthly use report — one click to generate, one click to file.
Key capabilities
How Bug HQ builds the monthly ag commissioner report
The monthly pesticide use report is a legal requirement for California structural pest control operators — due to your county agricultural commissioner by the 10th of each month for the prior month's work. Most companies track this in a spreadsheet or write it by hand, pulling records from multiple sources and hoping nothing was missed.
Bug HQ eliminates that process. When you open the monthly report and select a month, the system runs three simultaneous queries. The first pulls from pest_jobs — every completed job in that period, each with its chemicals_used array containing product name, EPA number, active ingredient, quantity, unit, method, target pest, and area treated. The second pulls from inspections where chemicals were applied. The third pulls from the chemicals_used relational table, which captures work order chemical applications with the same fields.
All three datasets merge into a single application list sorted by date. Each row shows applicator name and license number pulled from the technician's user profile — never entered manually at report time. The summary shows unique product count, properties treated, and total applications for the month.
The compliance alert. After the 5th of each month, Bug HQ checks whether the prior month's report has been filed. If it hasn't — either unsaved or saved but not yet marked submitted — a warning banner appears at the top of the chemical reports screen. It shows the specific month that's overdue and links directly to that pre-selected report. The alert clears the moment you mark the report as submitted and enter the confirmation number.
The county selector covers all 58 California counties. If your operation crosses county lines, generate separate reports per county by changing the selector. Each report saves independently with its own draft or submitted status, filing date, and confirmation number.
How it works
Techs Log Chemicals During the Job
In the field app, after completing a pest job or work order, the tech selects chemicals from the product library — EPA reg number and active ingredient are already populated. They enter quantity, unit, application method, target pest, and area treated. If there's no signal, the entry queues offline and syncs when they're back on the road. The log is attached to that job permanently.
Office Generates the Monthly Report
On any day before the 10th, the office manager opens Chemical Reports, selects the month, year, and county. Bug HQ queries all completed pest jobs, inspections, and work orders for that period and assembles every chemical application — across all three job types — into a single sorted list. The applicator license number pulls from the technician's profile automatically. No copy-paste from separate logs.
Download, File, and Mark Submitted
Click Download PDF to generate the report in the format required by CA DPR. Submit it to your county agricultural commissioner using whatever filing method they accept — paper MSPUR form, electronic filing, or county portal. Return to Bug HQ, click Mark Submitted, enter the confirmation number if provided. The report moves from Draft to Submitted in your filing history. The compliance alert clears until next month.
Who uses this feature
The product library means techs never have to look up an EPA number in the field. They pick from the list, enter how much they used and where, and move on. If they lose signal mid-job, the entry queues automatically — nothing gets lost.
Your QAL or QAC license is on the line every month. Missed or incomplete chemical use reports are an enforcement risk. Bug HQ gives you a single screen where you can verify every application was logged before you sign off and file.
No more chasing techs for paper chemical logs at month-end. The report builds itself from the jobs already in the system. Generate the PDF, submit to the county, mark done. The whole process takes minutes instead of a morning.
What this looks like in your day
It's the 8th. You open Bug HQ and the amber compliance banner is at the top of the screen: last month's chemical use report hasn't been filed. You click the link in the banner. The report pre-loads last month's date range — 53 applications, pulled from 31 pest jobs and 4 work orders, sorted by date. Every row has the product name, EPA number, applicator name, license number, and site address already filled in. You verify the county is set correctly, click Download PDF, and the report generates. You submit it through your county's filing system, get a confirmation number, come back to Bug HQ, click Mark Submitted, paste in the number. Done. The banner clears. The whole thing took under five minutes, and you didn't touch a spreadsheet.
Frequently asked questions
All three: pest control jobs, WDO inspections with chemicals logged, and work orders. When you generate the monthly report, Bug HQ queries pest_jobs.chemicals_used, inspections.chemicals_used, and the chemicals_used relational table (used for work orders) and merges them into a single application list sorted by date. You don't need to track separately by job type — it all flows into one report automatically.
Date, site address, applicator name, applicator license number, product name, EPA registration number, active ingredient, amount used, unit, application method, target pest, and source job number. These fields match what California's monthly pesticide use report requires — applicator license number comes from the technician's user profile, not a manual entry field.
Yes. When a tech logs chemicals without a signal, the application is stored as a pending mutation of type chemicals_inspection in the device's local IndexedDB. When connectivity returns, Bug HQ syncs the mutation to the database automatically. By the time you generate the monthly report at the office, all offline-logged applications are present — there is no separate step to reconcile offline data.
Yes. The report defaults to your company's county from your settings, but you can change the county dropdown before generating or saving. All 58 California counties are supported. If you work across county lines, you can generate separate reports per county by changing the county selector for each run.
After the 5th of each month, Bug HQ checks whether last month's chemical use report has been saved and marked as submitted. If it hasn't, a warning banner appears at the top of the chemical reports screen reminding you the report is due to the county ag commissioner by the 10th. The banner includes a direct link that pre-selects last month's date range so you can generate it immediately.
Related features
Stop rebuilding your chemical log every month
Free 14-day trial. Credit card required — cancel free anytime before trial ends. Setup in under an hour.
Get Started →