Automation Guide
Building & Using Forms
| Before you begin: Forms live in the left sidebar under Automation › Forms. You will need to create and publish a form template before you can attach it to a workflow, step, or batch. |
What are Forms?
Forms are a flexible way to capture any structured data you want recorded against a batch or step. They can act as worksheets, daily logs, observation records, or compliance check-ins — whatever your team needs to fill out as work happens. Common examples include:
- Production worksheets filled out per batch
- Environmental readings such as temperature, humidity, or pH
- Packaging counts and output totals
- IPM applications and treatment logs
- Any KPI or Metrc data you want to track over time
You build a form template once, then attach it to a workflow or step so it shows up at the right time, for the right person, on the right batch. Every submission is saved on the template and on the batch so you always have a clean paper trail.
Forms can also feed into custom dashboards — so the numbers your team enters in the field flow straight into the metrics and KPIs you use to make decisions.
Coming soon: Forms will tie into Issues. You will be able to attach a form to an existing issue, or have an issue automatically trigger a form for someone to fill out — so corrective action data lives right alongside the issue it relates to.
Creating a Form Template
Start by creating a blank template. You can save it as a draft, build it out over time, and publish when you are ready.
| Step 1 Open the Forms page |
Use the “Show all versions” checkbox in the top right if you want to see older versions of templates. |
| Step 2 Create a new template |
Note: Schedules are not set here — you will set them later when you attach the template to a workflow or step. |
| Tip: Use descriptive template names that match what your team will recognize (“BCA Application Log” rather than “Form 1”). The template name is what shows up in the operator fill panel. |
Adding Fields to Your Form
Inside the template editor you will see three tabs at the top — Fields, Assignments, and Records. Fields is where you build the form. The left side lists your fields, and the right side shows a live Preview that updates as you add and edit fields.
| Step 3 Add a field |
The preview on the right updates the moment you click Add, so you can see exactly what the operator will see. |
| Step 4 Pick the right field type | ||||||||||||||||||||||||
There are 11 field types to choose from. Most are simple, but four (Number, Dropdown, Table, Linked batch field) open extra options when you select them.
|
| Step 5 Configure a Number field |
After choosing Number as the Type, a NUMBER OPTIONS section appears.
Warnings are non-blocking — the operator will still be able to submit, but they will see “Above expected maximum” or “Below expected minimum” so out-of-range readings get flagged for review. |
| Step 6 Configure a Dropdown field |
After choosing Dropdown as the Type, a DROPDOWN OPTIONS section appears.
|
| Step 7 Configure a Table field |
After choosing Table as the Type, a TABLE OPTIONS section appears.
|
| Step 8 Configure a Linked batch field |
Linked batch fields pull existing batch data into the form automatically, so operators do not have to re-type it.
On the preview and the live form, this field will read “Auto-fills from batch.{attribute}” — operators do not need to fill it in. |
| Tip: Only check “This data aggregates” on numeric fields you actually want totaled or averaged in reports. Aggregating non-numeric data will not produce meaningful numbers. |
Publishing Your Form
While the template is in Draft state it can be edited freely, but it cannot be attached to a workflow or filled out. Publishing makes it available for assignment.
| Step 9 Publish your template |
Once published, you can also Clone or Retire the template using the buttons next to the state badge. |
| Tip: Use Clone if you want to make a small variation of an existing template instead of editing the original. This protects past submissions tied to the original template. |
Assigning a Form to a Workflow or Step
Assignments tell Hashio when and where a form should appear. A published template can be attached to a Workflow (so it fills at the batch level) or to a specific Step inside a workflow.
There are two ways to create the same assignment — pick whichever is easier for you:
- From the form template itself, using its Assignments tab (Steps 10–12 below).
- From the Workflow or Step you want the form on, using the Forms tab (Steps 13–14 below).
Either path creates the same kind of assignment, and any assignment you make shows up under both the template and the workflow.
| Step 10 Open the Assignments tab |
|
| Step 11 Attach the form at the Workflow level (batch-level) | ||||||||
Choose Workflow (batch-level) at the top of the New Assignment popup if you want the form filled out once per batch (or daily across the whole batch).
If you choose Daily while in phase, a Phase dropdown appears with: Propagation, Vegetative, Flowering, Harvest, Drying. Pick the phase the form should run during.
|
| Step 12 Attach the form at the Step level | ||||||
Choose Step at the top of the New Assignment popup if you want the form tied to a specific step inside a workflow.
When Required on every hash-out is checked, the operator must either submit the form or reject it with a note before they can hash out. If they reject it, the worklog is flagged for audit so a supervisor can follow up.
|
Prefer to work from the workflow side? The next two steps do the exact same thing, but you start from the Workflow or Step instead of the template.
| Step 13 Attach a form from the Workflow page (batch-level) |
Use this when you are already looking at a workflow and want to add a form that fills out once per batch.
|
| Step 14 Attach a form from the Step page (step-level) |
Use this when you want a form tied to one specific step.
|
| Tip: You can add more than one assignment to the same template. For example, one template could be attached to two different workflows with different schedules. |
Filling Out a Form from the Batch Screen
Forms attached through a workflow show up automatically on the batch. You can also add a one-off form to a single batch.
| Step 15 Open the Records tab on a batch | ||||||||
Tip: “Scope” tells you whether a form is filled once for the whole batch (batch-level) or each time a specific step is worked (step-level) — so you can tell at a glance where each form belongs. |
| Step 16 Fill out the form |
There are two ways to open a form to fill it out. The easiest is to click a card in the Due today section, so you know you’re filling out exactly what’s currently due.
You can also fill out any form by clicking Fill on its row in the Attached forms list below. This is handy for filling out a form ad-hoc before it’s due — but for day-to-day work, the Due today cards are the best place to start. Warnings are intentional — they flag readings worth a second look without blocking the operator from recording what they actually measured. |
| Step 17 Add a form to a batch (optional) |
Useful when a form was not on the workflow when the batch was created, or for a one-off log.
The new form will appear in the Attached forms list for this batch only — it will not affect other batches. |
Filling Out a Form from the Workstation Beta View
When operators are hashed into a batch, forms come to them right in the Workstation Beta View — no need to leave their work area. A required form appears in the active step bar, and a Forms button in the top right opens every form for the batch.
| Step 18 Fill out a form from the Workstation | ||||||||
When you are hashed into a batch, the active step bar at the top shows the step name, the batch, and your timer. Forms reach you in two places here:
If you are not hashed into a batch, On this batch will say “Not hashed in” and point you to either hash in or use Find a form. Hashing out: if a form is set to be required on hash-out, clicking Hash Out will prompt you to handle it first. You must either submit the form or reject it with a note — rejecting it flags the worklog for audit so a supervisor can follow up. |
Viewing Submissions
Every submission is stored in two places — on the template (across all batches) and on the batch (across all templates). Both views are useful in different situations.
| Step 19 View all submissions for a template |
This view is best when you want to see every submission of a single form across your whole facility. |
| Step 20 View submissions on a single batch |
This view is best when you are reviewing the full record of a single batch — every form, in one place. |
| Tip: Submissions never disappear, even if you Retire a template. Retired templates simply cannot be assigned to new workflows, but past records stay visible. |
You are now ready to build, assign, and capture data with Forms. Start with a simple template, attach it to one workflow, and have your team fill it out for a few days. From there, expand to more complex forms with Tables, Linked batch fields, and step-level triggers as your team gets comfortable.
Related guides:
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article