Regulated Materials

Most field trades put something regulated on or into a customer's property: a pesticide around a foundation, a herbicide on a lawn, chlorine in a pool, refrigerant in an air conditioner. The material is regulated before it ever reaches the truck, and its use is regulated again at the property: who may apply it, how much, where, when, what has to be written down, and who has to be told. For a pest control or lawn company the application record is the most heavily regulated document in the business, more so than the contract or the invoice, because it's what an inspector asks for after a complaint.

This chapter is about building those rules into the system so that a technician can't create a record that a regulator would reject, and so that the record still says what was true years later. Pesticides are the deepest example and most of the chapter; the same shape fits the other trades, covered at the end.

The Label Is the Law#

In the US, pesticides are regulated under the Federal Insecticide, Fungicide, and Rodenticide Act (FIFRA). A pesticide can't be sold until EPA registers it, and registration approves a specific label: the products it may be used on, the pests, the sites, the rates, the protective equipment, the restrictions. EPA puts the consequence plainly: the label is the law. Every label carries the statement that it is a violation of federal law to use the product in a manner inconsistent with its labeling, and FIFRA makes that use unlawful (7 U.S.C. 136j(a)(2)(G)).

That shapes the data model more than anything else in this chapter. The label isn't documentation the technician might read; it's the source of the constraints the system enforces:

• Sites and targets. Which sites (indoor, outdoor perimeter, turf, crack and crevice, wall voids) and which pests the product is labeled for.
• Rates and dilution. The amount per area or per volume of mix, often as a range, sometimes different by pest or site.
• Frequency and limits. The minimum interval between applications and the maximum number per season or year.
• Restrictions. Buffer distances from water or wells, weather conditions (wind, rain, temperature), re-entry intervals, sites it must never be used on.
• Protective equipment the applicator must wear.

Each product is identified by its EPA registration number, written EPA Reg. No. followed by a company number, a hyphen and a product number. A third segment (for example 1234-12-567) marks a supplemental distributor product: the same registered formulation sold under another company's name. EPA's Pesticide Product Label System (PPLS) can be searched by registration number for the approved label versions, which is the right source to check a catalog against.

Labels also carry a signal word that reflects acute toxicity: DANGER (category I, the most toxic, sometimes DANGER-POISON), WARNING (category II) and CAUTION (category III, optional for category IV). Some states key rules to it, and it belongs on a service slip.

A Catalog That Knows the Label#

Build the product catalog as a model of labels, not a list of names:

Record	Holds
Product	Brand name, EPA registration number, registrant, formulation (liquid concentrate, granule, bait, dust, aerosol), signal word, restricted-use flag, links to the label and safety data sheet
Active ingredients	Each ingredient's common name and percentage
Label rules	Allowed sites and targets, rate ranges per unit of area or mix, mix ratios, maximum applications per period, buffer zones, timing and weather restrictions, required protective equipment
Variants	Package sizes and concentrations of the same registration, so inventory and rates stay correct
Jurisdiction rules	Where the product is allowed, restricted or banned, and any extra fields a jurisdiction requires

Two details are easy to get wrong:

• Labels change. A registrant amends a label, EPA approves a new version, and the rates or sites change. Version the label rules with effective dates, and have every application reference the version that was in force on the day.
• Units are part of the rule. A rate of "0.5 fl oz per gallon" and "1 gallon of mix per 1,000 sq ft" are two separate rules with two separate units. Store quantity, unit and basis (per gallon of mix, per 1,000 square feet, per bait placement, per linear foot of trench) as data, and do arithmetic only between compatible units. A technician who records "2" with no unit has recorded nothing.

Bait stations, traps and similar products also need a place. EPA regulates some of these as devices, which carry an establishment number rather than a registration number, and some states require device use to be recorded alongside pesticides.

Restricted Use and Who May Apply#

EPA classifies some products as restricted use pesticides (RUPs). They aren't available to the general public; they may be used only by a certified applicator or someone under a certified applicator's direct supervision. Certification is federal in structure and state-run in practice. 40 CFR Part 171 sets the standards, and states certify applicators under plans EPA approves. Commercial applicators are certified by category; the one that covers most home-services pest control is industrial, institutional, and structural pest control, alongside categories like ornamental and turf (lawn care), right-of-way and public health. Certifications expire at most five years after issuance unless the applicator recertifies, and a state may set a shorter period.

Supervising a noncertified applicator isn't a signature on a form. Under 40 CFR 171.201, the supervisor must make sure the person:

• is at least 18 (with narrow exceptions for family farms),
• has been trained within the last 12 months on a specified list of topics, from toxicity and first aid to label reading and spill cleanup, by a qualified trainer,
• has been instructed within the last 12 months on the equipment they'll use,
• has the label accessible at all times during the application,
• has a means to communicate immediately with the supervising applicator.

A commercial applicator must keep the training records (name and signature, date, trainer, course) at its principal place of business for two years.

Federal certification only applies to restricted-use products. State licensing goes much further, typically covering commercial pest control businesses and the people who apply pesticides for hire whether the product is restricted or not; Texas, for example, licenses every structural pest control business location and every technician. That licensing is the subject of Licenses & Permits. For this chapter, the consequence is that the record of an application has to name the people involved and their license numbers, and the system has to check, before the record is saved, that those licenses covered this product, this category and this place.

The Application Record#

Every state that regulates commercial pest control requires a record of each application, and the fields overlap heavily. Two examples:

• Texas requires structural pest control use records kept for two years at the business location: the customer's billing name and address, the service address, each pesticide's name and EPA registration number, the amount applied (or the mix rate and total mix applied), the devices used, the target pest, the date, and the name and license number of everyone who applied, supervised or was trained on the job, plus the business's license number. Termite treatments add the square footage treated and, for some preconstruction work, tank counts and start and stop times.
• New York requires commercial applicators to keep, for each application, the EPA registration number, product name, quantity, date, and address with five-digit ZIP, plus the dosage rate, method and target, retained for at least three years. They also file an annual report of those applications by February 1 for the prior year. State guidance says the location must let someone return and find the exact place applied, which can mean the apartment or room, not only the street address.

Across states, plan for these fields, and let jurisdiction rules mark which are required where:

Field	Notes
Product and registration number	From the catalog, snapshotted (see below)
Amount and unit	Of the product as applied, or the mix rate and total mix
Concentration or dilution	Derived from the mix ratio where possible, not typed
Application method	Spray, bait, dust, granular, injection, fumigation
Site and area treated	Interior or exterior, specific locations, and area (square feet, linear feet) where required
Target pests	From the label's targets
Date and times	Start and stop where a state or treatment requires them
Location	Service address, plus the specific unit or structure
People and licenses	Applicator, supervisor, trainees, each with license number; the business license
Conditions	Weather (temperature, wind speed and direction) where required

Some states require weather conditions for outdoor applications, or the area treated for every application, or every technician present listed on the record, not only the lead. Those differences are why the required-field set is data keyed by jurisdiction rather than code: you add a state's rule, you don't redeploy the app. Check each state's current regulation when you add it; these rules change, and the version you enforce should have an effective date.

Capture conditions automatically where you can. Weather can be pulled from a weather API for the property's coordinates at the time of application; area can come from the property record, with the technician confirming it; the people come from who is checked in on the appointment. What the technician types should be what only they know: what they applied, how much, and where.

Check Before You Save#

The point of modeling the label is to stop a bad record at the moment it's created, while the technician is still at the property and can fix it. The checks, in order:

1. Allowed here. The product isn't banned or restricted in this state, county or city, and isn't excluded by the business's own policy for this branch.
2. Applicator qualified. Every person on the record holds a license that covers this category in this jurisdiction, unexpired on this date, and a restricted-use product has a certified applicator on it.
3. Within the label. The rate is inside the label's range for this site and pest; the interval since the last application of this product at this property respects the label's minimum; the count for the period is under the maximum.
4. State fields present. Everything the jurisdiction requires is filled in.

Treat 1, 2 and the hard label limits as blocking: the record can't be saved, and the visit can't be completed as serviced, until it's fixed or the product is removed. Treat softer issues (an unusual but legal rate, a weather reading near a label limit) as warnings the technician acknowledges, and keep the acknowledgment. Field apps work offline (The Technician App), so the checks have to run on the device against a cached copy of the catalog and rules, and run again on the server when the record syncs. A record that passes on a stale device and fails on the server is a compliance exception for a supervisor to review, not a silent rejection.

A visit that applied nothing is a legitimate outcome (an inspection, a no-activity monitoring check), but it has to be an explicit choice, not a missing record. Where the service being sold is a pesticide treatment, my default is that completing the visit requires either at least one application record or a stated reason none was made (Proof of Service covers the rest of completion).

Snapshots, Not References#

An application record must say what was true on the day it was made, forever. If the record points at the product row and the product's name, label or registration number later changes, a report run next year describes an application that never happened.

So at the moment of saving, copy into the record everything a regulator might ask about:

• product name, EPA registration number, formulation and signal word,
• each active ingredient and its percentage,
• the label version and the rate range it allowed,
• the applicator's and supervisor's names and license numbers as they were.

Keep the foreign keys too, for joins and analytics, but the snapshot is the record of fact. After the visit is completed, corrections are new versions with a reason and an author, never edits in place, and the original stays readable. This is the same discipline as an audit-safe ledger: history is appended, not rewritten. A retention policy should hold these for the longest period any jurisdiction you operate in requires (two years in Texas, three in New York, longer for some records elsewhere), and longer if your own risk counsel says so (Data Retention).

The same applies to legacy data you migrate in (Migrating Off a Legacy System). Old systems often have hundreds of near-duplicate product rows; you can map them onto a clean catalog for the future, but the historical records keep their original product data in the snapshot.

Rates, Mixes and Arithmetic#

Technicians mix concentrate with water in a tank and apply the mix. Regulators may want the amount of product, the amount of mix, the dilution, or the amount of active ingredient. Those are all derivable from three numbers, so record those and derive the rest:

• Mix ratio from the label (for example, product per gallon of water),
• Total mix applied,
• Product concentration (the active ingredient percentage, from the snapshot).

Product applied is the ratio times the mix; active ingredient applied is product times concentration. Compute these server-side with exact decimal arithmetic in stored units, and display them in the units each report expects. Don't let a technician type a computed number; a typed number disagrees with the inputs eventually, and then the record contradicts itself.

The same numbers drive inventory. Product applied, summed by technician and vehicle, should reconcile against what was loaded onto the truck (Fleet, Inventory & Safety). A gap is either a recording problem or a product problem, and either is worth knowing.

Buffers, Timing and Neighbors#

Some rules depend on what's around the property, not just the product:

• Buffer zones. Labels and state rules can forbid application within some distance of water, wells, schools or sensitive sites. If you know the property's coordinates and have the geography, the system can warn before the visit rather than after.
• Timing restrictions. No application before forecast rain, above a wind speed, or during certain hours or seasons. These belong in the rules model with the product, and the app can check them against current conditions.
• Sensitivity registries. Some states keep registries of people with a physician-verified sensitivity to pesticides, and require commercial applicators to notify them before nearby applications.

Pennsylvania is a well-specified example. The Department of Agriculture keeps a Pesticide Hypersensitivity Registry, distributed to licensed commercial and public application businesses with effective dates of March 1 and July 15 each year. Before certain applications, a business must notify each registered person whose residence or listed location is within 500 feet of the application site, between 12 and 72 hours ahead, with a start-to-finish window of no more than 24 hours. The notice includes the date, location and time window, each product's brand name, EPA number and active ingredient, and the business's name, phone and license number. Every attempt is recorded, and the record is kept for at least three years. Other states run similar registries with different distances, timing and categories of work.

To support a registry:

• Import the list as data, per state and per effective date, and geocode each entry. The lists arrive as files, often with messy addresses; geocode in batches, keep entries that fail geocoding in a queue for a person to resolve, and never drop them silently.
• Match by distance from the service address (property line where the rule says so, which is harder than a point distance) when a visit is scheduled, and attach the notification requirement to the appointment.
• Make notification a task with a deadline, tied to the scheduled window, with each attempt and its method recorded. A rescheduled visit needs a new notice.
• Block or warn if the visit is about to start without a completed notice.

Registries also interact with Recurring Schedules: a notification window of 12 to 72 hours means the visit's date has to be stable by then, which argues for locking routes that touch registry neighbors earlier than others.

Safety Data Sheets#

The label governs use; the safety data sheet (SDS) governs workplace hazards. OSHA's Hazard Communication standard requires employers to keep an SDS for each hazardous chemical in the workplace, readily accessible to employees during each shift. Electronic access is allowed if it creates no barrier to immediate access. Where employees travel between workplaces during a shift, which describes every technician, the SDSs may be kept at the primary facility as long as employees can get the information immediately in an emergency.

For a field platform that means:

• SDS and label links on every product, reachable from the technician app.
• Available offline. "Immediately in an emergency" doesn't wait for signal; cache the documents for every product on the technician's truck.
• Current versions, with the date each was last updated, and the old versions retained.

Other Trades, Same Shape#

Pesticides are the deepest example, but the pattern of a regulated material, qualified handlers, use records and reporting recurs:

• HVAC refrigerants. Under Section 608 of the Clean Air Act, only certified technicians may purchase refrigerants intended for stationary refrigeration and air-conditioning equipment, and wholesalers must keep invoices showing who bought what. Certification comes in types by equipment class, so a technician's certification type limits which systems they may service. The records a contractor keeps (refrigerant added and recovered per system, leak repairs) follow the same pattern as application records: material, quantity, place, person, date, snapshotted.
• Lawn and turf. The same FIFRA framework, under the ornamental and turf category, plus state and local rules on fertilizer timing, phosphorus, posting signs after application and notifying neighbors.
• Pools and water treatment. Pool chemicals carry SDSs and storage rules; some are registered pesticides (algaecides, sanitizers) and follow the label.
• Cleaning and disinfection. EPA treats disinfectants as pesticides and registers antimicrobial products, which surprises cleaning companies the first time an inspector asks for a label.

The model generalizes: a catalog of regulated materials with rules and versions, a qualification check on the person, a structured record of use with a snapshot, and reports derived from records rather than typed separately.

What This Means for the System You Build#

• A catalog modeled on labels, with registration numbers, ingredients, versioned rate and site rules, and SDS and label links.
• Required fields as data per jurisdiction, with effective dates, not code per state.
• Blocking checks at entry, on the device and again on the server: allowed here, applicator licensed and certified where required, rate and frequency within the label.
• Immutable snapshots of product and license data on every application record, with corrections as new versions.
• Derived quantities, computed from mix ratio, mix applied and concentration, never typed.
• Captured conditions: weather, area and personnel filled in automatically where possible.
• Registry imports and notification tasks with distance matching, deadlines and recorded attempts.
• Offline access to labels and SDSs on every truck.
• Retention for the longest period any jurisdiction requires, and reports generated from the records.

References#

Specifications

• 7 U.S.C. 136j: Unlawful acts, using a pesticide inconsistently with its labeling, and refusing or falsifying required records
• 40 CFR 171.101: Commercial applicator categories, including industrial, institutional, and structural pest control
• 40 CFR 171.107: Recertification, certifications expiring five years after issuance unless renewed
• 40 CFR 171.201: Direct supervision of noncertified applicators, age, 12-month training and equipment instruction, label access, communication, and two-year training records
• 4 Tex. Admin. Code 7.144: Pest control use records, Texas record fields, termite additions and two-year retention
• 7 Pa. Code 128.111: Registry, Pennsylvania's hypersensitivity registry and its March 1 and July 15 effective dates
• 7 Pa. Code 128.112: Notification, 500 feet, 12 to 72 hours, notice contents and three-year records
• 29 CFR 1910.1200: Hazard communication, safety data sheets readily accessible each shift, and employees who travel between workplaces

Reference

• EPA: Introduction to Pesticide Labels, "the label is the law" and the federal-law statement on every label
• EPA: Label Review Training, Parts of the Label, the format of the EPA registration number
• EPA: Pesticide Product Label System, more information, searching labels by registration number, and distributor product numbers
• EPA: Restricted Use Products Report, RUPs limited to certified applicators or those under their direct supervision
• NPIC: Signal Words, DANGER, WARNING and CAUTION and the toxicity categories
• NYSDEC: OGC 3, Pesticide recordkeeping and reporting of commercial applicators, New York record contents, February 1 annual reports, three-year retention and exact location
• EPA: Refrigerant Sales Restriction, only Section 608 certified technicians may buy refrigerant for stationary equipment

In practice

• EPA: Questions and answers for Section 608 certified technicians, certification by type of appliance, and Universal certification
• EPA: Selected EPA-registered disinfectants, disinfectants as pesticides that EPA regulates and registers
• TDA: Structural Pest Control Business, a business license per location in Texas