TLTreatLog
Menu
FeaturesSee how it worksROIPricingBriefingsNewsStatesMCPSee how it worksStart free

Resources

The audit ZIP and the SDS binder

Who this is for: the office manager who still has a binder under the seat, and the commercial account manager who gets asked for “everything on Plant 4” the week an auditor shows up. Date: 2026-09-24. Standards linked below are the publishers’ documents. TreatLog is not accredited by NPMA, NSF, AIB, SQF, or EPA.

Compliance disclaimer

This is a description of an inspector-oriented pack and of how shops keep SDS and labels today. It is not legal advice, not a guarantee you will pass an audit, and not a claim about how many hours a binder costs you. We have not measured that. You remain responsible for the records, for whether an SDS is current, and for what you hand an inspector or an auditor. Full notice: treatlog.com/legal/compliance.

Why the binder is still in the truck

Operators say the quiet part in public. A vehicle-log thread on r/PestControlIndustry starts from a Google Sheet of what is on the truck, and a reply describes a thick binder of every SDS and label, printed. A later thread has a California tech rejecting a roughly $70-a-month SDS app and keeping the binder under the driver seat. Someone else in that thread keeps a personal binder because the route has no reception. Those are forum comments, not a census. The $70 figure is one comment, not a market price.

The binder fails in a specific way. The food-plant auditor does not want “a PDF of chemicals.” NPMA’s pest management standard for food processing says the file should hold safety data sheets and labels, and that service tickets should show the pesticide, the amount, and the EPA registration number. An NSF-style documentation checklist used by plants asks for the SDS and the specimen label, plus the application record: product, EPA (or PMRA) registration number, rate, location, method, amount, date and time, signature. Label and SDS are not the same document. A shop that filed one of them has done half the request.

California adds a customer-facing cousin, not an audit ZIP: 16 CCR § 1970.42 is the post-application notice rule operators cite when a customer asks what was applied. The customer PDF is that conversation. It is not the plant pack.

None of this makes a paper binder illegal. If the binder is current, on the truck, and you can produce it, Field Free at $0 does not beat it. The question is whether the EPA number, the SDS, and the label are findable for the account and the dates the inspector named.

What an inspector-ready pack is

For one customer, one site, or a date range, the pack people are actually asking for looks like this:

PieceWhy it is in the pack
Application listDate and time, address, areas, target pests, product, EPA Reg. No., amount, who applied
SDSOne per product used, current enough that you know when you last checked it
Specimen labelThe label, not a second copy of the SDS
Applicator licensesName, state, number, expiration, for the people on those jobs
A manifestSo the recipient can see what was included and what was left out

Trend graphs and device maps show up in food-plant standards. They are thin in this product. This pack does not promise them.

Amendment history matters for a reason that is not a slogan. 16 CCR § 1970(c) treats falsifying structural pesticide records as a fraudulent act under the Business and Professions Code section it cites. Silent overwrite is how a record becomes something you cannot explain. The pack should come from the applications as they were logged and amended, not from a cleaned spreadsheet.

What TreatLog’s ZIP contains today

On Treat Compliance and above, an audit export builds a ZIP for a customer, a site, or a period. Current contents:

  • applications.txt — each application in scope: id, date, areas, pests, completeness score, and each product with brand, EPA Reg. No., and undiluted amount. Text, not a designed PDF.
  • licenses.csv — name, state, license number, expiration, when license rows exist.
  • sds/ — a text stub per product that has an SDS document attached: brand, EPA Reg. No., the stored file location, and the last-verified time. The original PDF bytes are not embedded yet.
  • labels/ — the same kind of stub for the specimen label, when one is attached.
  • manifest.json — counts and the file list, including whether SDS, labels, and licenses were requested.

That is the honest MVP. It is enough to see whether the account is empty. It is not yet “email the auditor a ZIP of every original SDS.” Emailing the pack is also not wired; a notify address can be passed and is not a sent message. Offline cache for the canyon with no signal is not in this version. Presets in the library still beat writing “Tempo” on a napkin and backfilling next week, and completeness warnings are how the office sees what never got logged. Same-day, 72-hour, and two-working-day clocks in other states are reminders in the product, not filings.

Approved-product lists (warn when a tech picks something the account does not allow) sit on the Multi-State plan. If that warning is not on for your org, the ZIP will not enforce it.

How to use it without over-claiming

  1. Put EPA Reg. No., SDS, and specimen label on the product before the route. Both files. Note the day you verified them. You refresh them when the manufacturer does; the timestamp is yours to update.
  2. Log the treat with amount, areas, pests, and applicator. The ZIP cannot invent a row the tech skipped.
  3. Export the account or the date range the auditor named. Open the ZIP. Read applications.txt and the manifest before you send anything.
  4. If the SDS stub points at a file you trust, attach the real PDF yourself until the export embeds it. Say that plainly if a QA manager asks what the .txt is.
  5. Do not tell the plant you are NPMA-certified software, EPA-partner software, or that the pack “passes NSF.” You produced documents. They audit.

Field Free is $0 and does not include this ZIP. Treat Starter is $49 (the library and one state pack, not the ZIP). Treat Compliance is $99 and includes the audit ZIP. Treat Multi-State is $179. Month-to-month. The ZIP is a reason to be on Compliance if a commercial account is why you are here. It is not a reason to throw out Jobber.

See it on a fake food account, or send the real one

The demo builds a pack for a sample food account in the same ten minutes as the log and the state stub: book it. If you already have an export that does not match this page, write support@treatlog.com. If you want the pack on a live account this month, write sales@treatlog.com with the state list, the FSM you schedule in, and the audit date.

Sources