Forms
Office-designed checklists that standardize what technicians record on a visit. A template is not a completed response. Completing a checklist is not Closeout.
Settings → Forms · /app/w/{workspace}/settings/forms · capability forms · forms.view / forms.manage
Settings and the work-order type speak of Forms and a Form template (Create form). On the job, Field labels the same thing a checklist (Complete checklist). One authority — two labels. This is not Custom fields (office records) and not GRC/CAPA.
Create a form
Section titled “Create a form”- Settings → Forms → Create form. Name the template. Status starts Active.
- Add items: Text, Long text, Number, Checkbox, Single select, Multi select, Radio, Date, Time, Date & time. Structure: Section, Instruction (not answered).
- Mark a question Required when Closeout should depend on it being filled. Required is checked when the technician taps Complete checklist, not on every keystroke.
- Deactivate when you no longer want it on new jobs. Historical instances stay.
You can edit an Active template. Copy: Update the checklist. Existing job answers remain unchanged. If technicians already have instances, Veldriq stores a new template version; old visits keep the version they started. There is no Draft/Published workflow. A completed form is immutable.
How a checklist reaches the job
Section titled “How a checklist reaches the job”- Settings → Work order types → the type → Forms.
- Attach one or more Active templates. Scope: One form for the whole visit (shared answers) or Each technician completes their own form.
- Optionally Require before completion so Closeout waits until that instance is Completed.
- When office Add appointment, Veldriq creates the instances on that visit. A template alone does nothing.
Office can attach an extra form to an existing appointment (manual). Portal customers do not fill these checklists.
Field: complete a checklist
Section titled “Field: complete a checklist”- Start work on the visit. States: Not started / In progress / Completed.
- Answer questions. Optionally bind Equipment. Progress shows
:answered / :total completed. - Complete checklist — disabled until every required, visible question has an answer. Completing answers can offer Record finding from a failed check.
Why can’t I complete this checklist? Required answers missing; still paused/not working; already Completed; pending offline enqueue failed.
Completion requirements (Closeout)
Section titled “Completion requirements (Closeout)”They apply to Complete appointment, not office Complete on the work order.
| Requirement | Configured where | Technician action | Blocks Closeout? |
|---|---|---|---|
| Form | Type → Forms + Require before completion | Complete checklist | Yes — :name is incomplete. |
| Signature | Type → Signatures + Require before completion | Collect signature | Yes — :name is required. |
| Evidence | Require before photo / Require after photo (min count) | Add photo | Yes — Add at least :min :category photo(s) |
| Finding | — | Record finding (optional) | No |
Open findings do not block Complete appointment. Completing the checklist is not Closeout.
What-if
Section titled “What-if”If the form is not on the job: correct work-order type? Template attached and Active? Appointment exists? Per-technician form needs an assignment? Capability forms?
If you edit a template expecting old completed visits to change: they will not.
Related: Findings, Evidence, Signatures.