Pesticide use records: what an assistant checks after every stop.

Georgia's rule is unusually concrete. A legible record is required every time a pesticide is applied or a termite control system is installed or modified; the technician completes it at the time of service; the property owner, resident or custodian receives it when the service is complete; and the company keeps it for at least two years (as checked on 15 October 2026). An empty field is a gap in a regulatory document that has already been handed over.

An AI assistant can compare each record with that list after the stop and draft a note to the technician naming what is missing. Completing, correcting and signing the record stay with the technician who applied the pesticide. Rules differ from state to state: Georgia is the worked example here, not a rule for anywhere else.

The Structural Pest Control Section of the Georgia Department of Agriculture publishes a compliance fact sheet, SPCS notice 14-02, on pesticide use record keeping under the Rules of the Georgia Structural Pest Control Act, which were amended in April 2014. Read on 15 October 2026, its points are these.

• WHEN

  Every time a pesticide is applied, and every time a termite control system is installed or modified.

• WHO

  The technician who applied the pesticide is responsible for completing the record.

• AT SERVICE

  The record is completed at the time of service.

• TO WHOM

  It is provided to the property owner, resident or custodian of the property on completion of the service.

• WHICH FORM

  Any form that carries the required information; a state pest control association can supply model forms.

• SEVERAL PRODUCTS

  One record per job is acceptable but, in the fact sheet's words, it should include the required information for each product, linked to its own target pest, area treated and method.

• RETENTION

  The company keeps every pesticide use record for at least two years.

• ELECTRONIC RECORDS

  A record may be made electronically at the time of application and kept electronically, and must be provided or made available electronically when the application is complete.

• ACKNOWLEDGMENT

  For electronic delivery, the owner, resident or custodian completes an electronic communication acknowledgment statement, which is kept either for as long as the contract remains in effect or for two years past its expiration.

• ITS OWN LIMITS

  The sheet does not include every requirement and points to the full Rules, which the owner reads before writing the field list. The assistant never decides what the rule requires.

The middle column below paraphrases the Georgia fact sheet as checked on 15 October 2026. The right-hand column is Aevrion's design for the check.

The right-hand column is narrow on purpose. A check can see a blank field, an EPA Reg. No. that disagrees with the owner's product list, or a school stop with no times. Whether the concentration was right or the method suited the site are applicator judgments, made at the stop.

Nor does the check suggest what a blank should contain. 'Target pest missing on the second product' is a useful note. 'Target pest missing, probably German cockroach' is the assistant writing the record.

The checker is a Bot that the owner sets up in Grok Bot, following Aevrion's design: a named assistant working on a persistent cloud computer, whose job is a routine. In Grok Bot a routine assigns a workflow to a single Bot and says when it runs, at set times or, where supported, when something happens, and the documentation names six points to settle when one is created. Here is how Aevrion would settle them for this check.

• THE OWNING BOT

  Records Check, and no other Bot owns the same job.

• SCHEDULE AND TIME ZONE

  Every thirty minutes through route hours, in the company's time zone. A schedule cannot fire more often than once every five minutes, and this one is far slower, so 'after every stop' means within the half hour, not the moment the tablet syncs.

• INPUT SOURCE

  Records synced since the previous run, read through a custom integration with the field-service software or an export it already produces, plus the owner's field list.

• EXPECTED RESULT

  One gap list per run, giving the record, the field and what is missing, with a drafted note to the technician.

• APPROVAL BOUNDARY

  Read only: no edits and nothing sent. When a routine asks for approval and nobody is there, the request goes stale in roughly ten minutes (Cursor's help pages say thirty) and the step never happens, so this one is built to ask for nothing.

• MISSING SOURCE

  If the records cannot be read, the run says so and stops, rather than checking an older copy.

Based on the Grok Bot documentation at docs.x.ai as checked on 15 October 2026. Its statements on Bot rules, Bot-to-Bot messaging, routine triggers, connected apps, approval expiry and payments were rechecked against docs.x.ai and Cursor's help pages on 26 October 2026. The trade examples are Aevrion's illustrations, not documented Grok Bot use cases. Aevrion Ops is an independent consultancy. It is not affiliated with, endorsed by or a partner of xAI, SpaceXSI or Cursor. Grok Bot is named here only to describe it.

The field list is kept in the company's own system; Grok Bot's documentation tells users not to treat what a Bot remembers as the record of truth.

1. 01

   Completed at service

   Owner

   The technician who applied

   Advances when

   Every field is filled in on the tablet before the technician leaves

2. 02

   Provided at completion

   Owner

   The technician

   Advances when

   The customer receives a copy, on paper or electronically where an acknowledgment is on file

3. 03

   Synced

   Owner

   The field-service software

   Advances when

   The record reaches the company's system

4. 04

   Checked

   Owner

   Records Check Bot

   Advances when

   The next run compares it with the owner's field list

   Ends when

   A record with no gaps goes straight to retention

5. 05

   Gap noted

   Owner

   The owner

   Advances when

   The owner reads the gap list and sends the drafted note, or corrects their own record

6. 06

   Corrected

   Owner

   The technician

   Advances when

   The record is corrected, marked and dated as a correction, under a procedure the owner has confirmed with the Structural Pest Control Section; how a corrected copy reaches the customer is part of that procedure, as the fact sheet does not address it

7. 07

   Retained

   Owner

   The owner

   Advances when

   Kept for the periods set out in section 01

   Ends when

   Removed only by a person, after the retention period the owner has confirmed

The same Bot can compare the accounts marked for electronic delivery with the acknowledgments on file, list any account without one and draft a request for the owner to send. It never signs the statement or marks it received.

Each is a lasting rule the Bot is told to remember. A remembered rule instructs the Bot without enforcing anything, so approval rules for editing, sending and deleting stand behind it.

• NO WRITING

  It does not complete or correct any field, including the obvious ones.

• NO ATTESTING

  It does not sign, initial or mark a record as complete or compliant.

• NO VERDICTS

  Whether a gap is a breach of the rule is for the owner, and the state agency if needed.

• NO PRODUCTS

  It never suggests a product, a rate or a method.

• NO DELETIONS

  It never removes a record, before or after the retention period.

The Bot's conversation details list the routine's recent runs, each marked as worked or failed, beside controls to pause, test or edit it. The documentation mentions no automatic second attempt and no warning when a run fails, so a failure leaves records unchecked until a person looks. The owner looks weekly and, as a house rule, runs the routine's test again whenever the field-service software or its export changes.

Applicator certification follows federal standards but, according to EPA's certification-standards page on 15 October 2026, is administered by certifying authorities (states, territories, tribes and some federal agencies) under plans EPA approves; Georgia's record rule is a state rule. Fields, timing, delivery and retention can differ elsewhere, so an owner outside Georgia builds the list from their own state's rule.

Aevrion Ops can work through a state's rule with an owner until it is a field list, set up the check and its routine, and connect it to the company's field-service product if that vendor's API and terms permit, testing the connection before anyone relies on it. The article on reliable AI workflows goes deeper into how routines like this one should be designed; the readiness assessment is the natural first step.

1. Georgia requires a record at every application: the applying technician completes it during the visit, the customer gets it when the visit ends, and the company holds it two years or more.
2. Electronic records in Georgia need a signed acknowledgment, kept, in the fact sheet's words, for as long as the contract remains in effect or for two years past its expiration; the owner confirms the retention period with the Department.
3. An after-stop check can report blank, mismatched or missing fields; it never fills, corrects, signs or judges a record.
4. Rules vary by state: build the field list from your own state's rule, not from Georgia's.