Lab · Technology
Digital service records
What is digital service records?
Software that records each service visit electronically: products and amounts applied, device checks, pest sightings and site maps, which the office and the client can then pull up. It can make regulatory and audit records complete and searchable. It does not set what a record must contain. Your state and the client's audit scheme do that.
Reviewed by LTK editorial team
Where it fits
- Restricted-use applications, where required fields can be made mandatory. Federal rules require state plans to make certified commercial applicators keep restricted-use records for at least two years. The required fields include customer, location, area treated, site, time and date, product, EPA registration number, amount per location, and the applicator's certification number.
- Food-plant accounts that have to show trends. The SQF Food Manufacturing code requires the pest programme to record sightings and trend pest activity to target applications, and to measure effectiveness and identify trends. That is hard to do from a stack of paper tickets.
- Keeping the device map current. SQF requires the site map to show the identification, location, number and type of every pest control and monitoring device. When devices are recorded at each check, the map changes with the account.
- Long retention periods and fast retrieval. Minnesota requires structural application records to be kept for five years. SQF requires records to be readily accessible, retrievable and securely stored against loss or unauthorised access.
Where it does not
This is the part the brochure leaves out, so it is the part worth reading.
- As proof of compliance on its own. The federal restricted-use list is a minimum that states must meet or exceed. Minnesota's structural record adds the target pest, and temperature and exposure time for fumigations. It must be completed within five days of application. A national template that does not match your state's fields produces a tidy record that is still missing required fields.
- Records the technician did not actually confirm. SQF requires records to be confirmed by the person doing the monitoring. Federal rules require states to be able to suspend or revoke certification for falsified records. Pre-filled "no activity" entries and copy-forward visit notes are exactly what an auditor or an inspector will test.
- Replacing what has to happen at the site. In a rented apartment, Minnesota requires the applicator to post a list of the label's post-application precautions in a conspicuous place inside the unit. SQF requires contractors to report to a responsible authorised person on arrival and after the work. A PDF emailed to the office covers neither.
- Platforms where the records cannot leave with the account. SQF retention follows customer, legal and regulatory requirements, with the product's shelf life as the minimum. State retention can run to five years. If you cannot export the full history in a usable format when you change software, or when the client changes contractor, the records are not "readily accessible" when an audit asks for them.
Sources
- 40 CFR 171.303 — Requirements for State certification plans (restricted-use pesticide recordkeeping) — eCFR
- Minnesota Statutes §18B.37 — Pesticide application records — Minnesota Office of the Revisor of Statutes
- SQF Food Safety Code: Food Manufacturing, Edition 9 (2.2.3 Records; 11.2.4 Pest Prevention) — SQFI (check for a newer edition before an audit)
