Choose pesticide recordkeeping software by the completed record and the workflow it supports. FarmQA documents manual and recommendation-linked spray records, field selection, applicator identities, editing, and PDF or Excel exports. USDA and state sources define the information and access tasks against which an exported record should be compared. Start with those required outputs, then test the software with representative application documents. [1][2][4]
Define the output before comparing interfaces
Write down whether you need the private-applicator RUP data set, WPS application/hazard information, a state-specific submission, a customer copy, or a certification record. For each purpose, identify its fields, attachments, units, timing, and recipient. Preserve the source of the requirement in a small specification rather than comparing tools only by their screenshots.
USDA's federal private RUP guidance lists product identity and EPA number, total product quantity, application date, location, crop/site, treatment size, and applicator name and certification number. It requires no standard federal form, allowing integration with the applicator's existing system. That flexibility concerns the layout, while the data elements remain the comparison point. [2]
Washington provides a useful additional format test: WSDA permits complete records in any format but requires an official WSDA form if it requests submission. Keep the ability to map your data to the destination form among the software acceptance tasks. [4]
FarmQA: two documented creation routes
FarmQA's support page says spray records are created automatically when a recommendation is completed. It identifies the resulting link back to the recommendation and access through the recommendations area and Field Journal. Preserve the distinction between the recommendation and the actual application information when reviewing this route. [1]
The support page also describes manual creation in the web application. Its steps include selecting a field, started and completed timing, products or a mix, water volume in gallons per acre, application method, and notes. For a software trial, compare the completed record with the actual application source note rather than assuming every recommendation value describes the work performed. [1]
| Trial question | Documented FarmQA feature to examine | Evidence to compare |
|---|---|---|
| Can the actual place and extent be identified? | Field selection and whole/partial acreage | Application note and location key |
| Can timing be reviewed? | Started and completed fields | Actual work dates and times |
| Can product identity be traced? | Products or selected mix and product details | Actual labeled product |
| Can people be assigned? | Applicator directory and selection | Responsible/actual-person information |
| Can an independent copy be read? | PDF or Excel export | Destination record specification |
The middle column summarizes the support documentation. The final column defines editorial acceptance tasks for your own records; it does not state that the product's default output satisfies every jurisdiction. [1]
Applicator setup and staff permissions
FarmQA documents creation of an applicator in the web application under the enterprise-admin role. The entry includes name, license number, licensing authority, an optional connection to an existing account, and organization permissions. Preserve which person and credential a directory entry represents before assigning it to application records. [1]
The support page describes different role permissions for manual creation, editing, and exports. In a trial, have the staff member responsible for each task demonstrate access using the intended role. Keep that review focused on whether the assigned person can complete the record or retrieve a copy when needed. [1]
Build a handover checklist for a staffing change: identify who maintains applicator identities, who reviews completed treatments, and who can export the archive. Ask a backup office contact to retrieve an older record. Document a failed task specifically rather than concluding that a familiar interface guarantees operational access.
Partial fields and repeated information
FarmQA's multi-field workflow provides whole-field or partial-field acreage and an apply-to-all control for information shared among selected fields. Treat that as a preparation convenience, then compare the copied information with each actual field treatment. Preserve field-specific extent, people, and timing where the work differs. [1]
For an acceptance exercise, use two source application notes with a shared product but different treated extents or dates. Review whether a copied value remains appropriate in each resulting record. Keep the test notes labeled as an organizational exercise and avoid inventing a product rate or treatment recommendation to populate the software.
FarmQA also documents adding product lot numbers. Decide how that optional traceability information relates to your operation's purchase or certification evidence. Keep the lot reference separate from the EPA registration number and the applicator license so the identifiers do not become interchangeable in an import. [1]
Review editing and interval information
The documented edit workflow includes whole/partial-field selection, start/completion dates and times, products and product rates, water volume, method, wind speed, preharvest interval, rainfast time, reentry interval, and notes. Verify which values were entered or carried forward and preserve the source of a correction to an application record. [1]
FarmQA describes displaying field REI and PHI information based on completed spray records and product information. Compare the displayed information with the actual product and treatment data used in the record. Keep the underlying label and timing evidence available rather than allowing a displayed date to become the only surviving explanation. [1]
For covered WPS information, preserve the SDS, active ingredients, treated-area description, start/end dates and times, and label REI. The rule's record requirement is broader than a visible interval indicator. Review where those attachments and fields are stored and how they are made accessible. [3]
Export the record and inspect the result
FarmQA documents PDF and Excel export from its Spray records tab. Its support page lists exported information including applicator name and certification number, application date, product name and EPA identifier, treated area, rate and total product amount, field name, and crop. Open the resulting file as an independent document during your evaluation. [1]
Check a product amount against its unit, an area against its meaning, and an applicator number against the named person. Confirm the location description remains useful after the record is detached from the map interface. Review start/end details and attachments required by your own record specification rather than relying solely on the support page's short export list.
Keep a saved specimen of the export with the software-review date and the requirements compared. If a state form uses different column names, create a mapping that explains the correspondence and any additional information needed. Preserve the source of a limitation or unresolved field in the internal evaluation rather than hiding it behind a broad compliant label.
Review archive access as well as data entry
WPS application/hazard information is retained on the establishment for two years after the applicable REI expires and is subject to specified worker and medical access provisions. A software evaluation should therefore include retrieval of the information and its attachments, alongside daily entry. [3]
USDA's federal RUP guidance also identifies immediate record availability in a medical emergency. Assign a backup person and test a retrieval path that does not depend on the usual field adviser being present. Keep the location directory, product documents, and archive index connected to the exported records. [2]
Decide from a documented trial
Prepare an acceptance note listing the record purposes, source documents used, staff roles tested, exported specimens, and any field mapping or attachment arrangement. Distinguish an interface preference from a failed requirement. Revisit an unresolved quantity, timing, or retrieval task with the people who prepare and use the records.
Use that trial to choose the workflow that your operation can maintain consistently. The comparison above concerns documented FarmQA behavior and official record requirements; it does not assign an unsourced price, free plan, agency approval, or automatic legal-compliance status to a product. Keep the concrete evidence from your own trial with the decision.
Keep the software trial reproducible
Prepare a small acceptance matrix naming the staff role, representative record, expected output, and observed result. Include a partial-field application, a treatment with several products, an amended applicator identity, and a request for an older archived copy. Use your own documented examples or clearly labeled blank-field exercises without inventing rates.
Save the exported specimen and describe any manual step needed to connect it with a safety data sheet, state form, or location legend. Ask a second staff member to repeat the retrieval using the recorded instructions. Treat a missing permission, truncated heading, detached attachment, and unexplained conversion as separate findings. Preserve the resolution alongside the specimen so a later software update can be compared with the same practical requirements.
Calculation notes and a working record
Use the tank mix calculator to prepare quantity calculations and the spray record sheet guide to choose a printable worksheet or official form resource. Keep the preparation note attached to the treatment it describes.