Workflow Template
Chemical application and product record Workflow
Captures every pesticide application record from field technicians, routes it through supervisor QA review (with a technician correction loop when needed), marks it Recorded, and emails the client a summary of the application.
Organisations managing pesticide application services need a consistent, auditable way to capture field data and confirm it before it reaches the client, particularly where product, dosage and site details carry compliance implications. This workflow takes a technician's submitted application record through supervisor QA review, routes it back to the technician for correction when details are incomplete or incorrect, and only marks the record Recorded once the supervisor confirms it is accurate. Field technicians, supervisors, and clients (via an emailed summary) are each involved at a defined point in the process, with every status change and review outcome kept on the record's timeline.
Business Outcomes
- Helps standardise how pesticide application details are captured across technicians and sites
- Supports consistent supervisor QA checks before records are finalised
- Reduces back-and-forth by giving technicians a structured correction task with the supervisor's notes attached
- Improves visibility into application status across submitted, correcting and recorded records
- Makes it easier to keep clients informed with a consistent application summary
Workflow Steps
Steps
- 1Create Application Recordcreate record
Registers the submitted pesticide application as a chemical_application record.
- 2Set Status to Submittedupdate record
Sets the record status to Submitted upon creation.
- 3Supervisor Reviews Application Recordcreate task
Assigns the supervisor a task due in 3 days to check the record for completeness and correctness.
- 4Save Supervisor Review Resultupdate record
Persists the supervisor's review result and notes to the record.
- 5Route on Supervisor Review Result
Branches to correction or finalisation depending on the supervisor's review result.
review_result: "Complete and correct"→Set Status to Recordedreview_result: "Needs correction"→Set Status to CorrectingDefault→End - 6Set Status to Correctingupdate record
Sets the record status to Correcting when the supervisor flags issues.
- 7Technician Corrects Application Recordcreate task
Assigns the technician a task due in 2 days, showing the supervisor's notes, to update product details, quantity applied and dilution rate.
- 8Save Technician Correctionsupdate record
Writes the technician's corrected product name, quantity applied and dilution rate to the record.
- 9Return to Supervisor for Re-Checkrestart from step
Closes this iteration and restarts the supervisor check with the corrected record.
- 10Set Status to Recordedupdate record
Sets the record status to Recorded once the supervisor confirms the record is complete and correct.
- 11Email Client the Application Recordsend email
Sends the client a summary of the pesticide application including product, active ingredient, areas treated, quantity applied and re-entry interval.
Fields
- Technician Name*
- Technician Licence Number*
- Client Name*
- Client Email*
- Site Address*
- Application Date and Time*
- +20 more fields
Forms
Pesticide Application Record
20 fields
Data Views
Pesticide Application Records
application_datetime, site_address, product_name, active_ingredient +2 more
Dashboard Widgets
Recommended integrations
Setup the following integrations to extend workflow capability.
Send email in the workflow
AWS SES
Similar Workflows
Similar Categories
FAQs
What does this workflow record at each stage?
The record captures the technician's original submission, the supervisor's review result and notes, and, where corrections are needed, the technician's corrected product name, quantity applied and dilution rate. Status changes (Submitted, Correcting, Recorded) and each step's outcome are kept in the record's timeline. This gives a running history of who entered what and when, which each business should review against its own regulatory record-keeping obligations.
Who is involved in this workflow?
A field technician submits the initial application details through the request form. A supervisor is assigned a review task to check completeness and correctness, and if issues are found, the same or another technician is assigned a correction task showing the supervisor's notes. The client receives an emailed summary of the completed application at the end of the process.
What happens when the supervisor flags a correction?
When the supervisor's review result is 'Needs correction', the record status changes to Correcting and a technician task is created showing the supervisor's notes. The technician updates the product name, quantity applied and dilution rate, and once saved, the record is returned to the supervisor for a fresh review. This loop can repeat until the supervisor confirms the record is complete and correct.
How do we change what the request form or tasks ask for?
Any step in this workflow, including the fields on the request form, the supervisor's review task, or the technician's correction task, can be adjusted by describing the change in plain English or editing the step directly in the workflow editor. Earlier versions of the workflow are kept, so changes can be made with a record of what the process looked like before.
How is the client kept informed of the application?
Once the supervisor confirms the record is complete and correct and the status is set to Recorded, the workflow emails the client a summary covering the product, active ingredient, areas treated, quantity applied and re-entry interval. This email is sent automatically as part of the workflow using the platform's built-in email capability.
What does the supervisor see when reviewing an application record?
The supervisor is assigned a task, due in 3 days, showing the full submitted record including technician details, product information, dilution rate, quantity applied, and site and safety information. The supervisor enters a Review Result and Notes, which are saved to the record and used to determine whether the record proceeds to Recorded or returns to the technician for correction.
Can the workflow show which applications are still awaiting review or correction?
Yes, each application is a record with a status such as Submitted, Correcting or Recorded, and table views and dashboards display records grouped by status. This makes it straightforward to see, at a glance, which applications are waiting on supervisor review, which are back with a technician for correction, and which have been finalised.
Who submits the original application details?
The field technician submits the original application details through the public request form, entering information such as technician licence number, product details, batch number, dilution rate, application method, weather conditions and any sensitive areas nearby. This submission creates the chemical_application record and sets its initial status to Submitted.
Ready to use this workflow?
Create a free account and customise this workflow for your business.
