Map fields onto the document the farm already uses, assign a fresh form to an eligible worker, collect the worker portion without requiring clock-in, route farm-only follow-up fields, and retain one completed farm-owned PDF under the correct worker.
Inside the app
Actual Farmroute screens from the farm and employee demo accounts.
The source document stays recognizable. Farmroute adds a reusable field layer instead of replacing the farm’s layout with a generic survey.
A template is the reusable definition. Each assignment creates a separate fill request, so sending the same form again does not overwrite an earlier submission.
The employee can work directly on the bounded PDF canvas, turn pages with clear controls, or open a structured field list when faster keyboard entry is more practical.
When a template contains recursive fields, the worker cannot edit them. Their submission becomes Needs Work for the farm, which reviews the employee portion and completes only the remaining farm fields.
After the last required stage, Farmroute renders the answers and signatures into the PDF and stores the finished record under the submitting worker—not in the employee’s personal storage and not inside technical UUID folders.
How it works in practice
The template defines reusable pages and fields. An assignment is one request sent to one worker. The submission is that request’s completed output. Keeping those records separate allows the same template to be assigned repeatedly without replacing prior work.
Normal fields belong to the worker stage. Recursive fields belong to the farm stage and stay unavailable to the employee. Farmroute advances the assignment only after the responsible party confirms submission.
Workers can answer directly where the field appears on the PDF, then use the Fields panel for a simpler list when typing several answers. Both interfaces write to the same form state and preserve the original page geometry.
Farmroute retains the signature method, signer name, consent version, client timestamp, and drawn image when applicable. The final PDF preserves the signature’s aspect ratio rather than stretching it to fill the mapped box.
An assignment can notify the worker, and a returned recursive form can notify the farm with a Needs Work destination. The assignment and completed document remain in the database and storage even if a real-time or push notification is missed.
Completed output is stored under the submitting worker in Template Submissions and named with the FRW worker number plus the template name. Internal assignment-source objects are not shown as user folders.
Roles and responsibility
The farm maps the source, sends an independent assignment to an eligible worker, handles recursive follow-up, and receives the final farm-owned PDF in the correct worker record.
The employee opens the named farm request in Tasks, fills the actual paged document or its field list, signs, confirms, and submits without needing to clock into a shift first.
Complete workflow
Place the farm’s PDF in Templates and verify every page that should be part of the reusable form.
Position text, date, checkbox, signature, initials, and other supported fields on the correct page.
Reserve fields that should be completed by a farm administrator after the worker returns their portion.
Choose a worker with a current relationship to that farm. The assignment receives its own identity and does not mutate earlier submissions.
The request appears under Forms with the sending farm’s name and stays accessible even when normal operational tasks require clock-in.
Use the document pages or Fields panel, add the electronic signature, and confirm the destination before submission.
If there are no recursive fields, the document can finalize. Otherwise, the farm receives a Needs Work state linked to the remaining fields.
Review the employee answers, enter only the farm-owned follow-up, and confirm final completion.
Embed all answers and signatures, preserve signature geometry and metadata, then store one farm-owned file in the submitting worker’s Template Submissions folder.
Questions and answers
A template form is a reusable field map placed over a farm’s existing PDF. The farm can assign a fresh copy to a worker, collect the response, and retain a completed PDF without rebuilding the document as a generic web survey.
Yes. Every assignment is a separate request with its own identity, answers, status, and completed output, so later requests do not replace earlier submissions.
No. Assigned forms appear in the Forms section of Tasks and remain available off the clock. Other operational tasks can still require an active clock session.
Recursive fields are follow-up fields reserved for the farm. The employee completes and submits their portion first, then the farm receives a Needs Work stage and completes only the remaining recursive fields.
Yes. The employee can fill fields directly on the document or open the Fields panel for a structured list. Both views update the same assignment answers.
Farmroute retains the signature method, signer name, consent version, timestamp, and drawn image when applicable, and embeds the visible signature in the completed PDF while preserving its aspect ratio.
After all required stages are complete, the final farm-owned PDF is stored under that worker’s Template Submissions folder and named with the worker’s FRW number and the template name.
The notification is only a delivery cue. The assignment remains in the database, appears in Tasks after synchronization, and reconnecting devices use incremental sync to recover missed changes.
Get started
We pride ourselves on transparency. No need to call for a quote.