Your forms. Governed properly.
Build the inspections, hazard assessments, equipment checks, toolbox talks and checklists your company actually uses — inside schemas that keep them meaning something.
Build → Publish → Complete → Preserve
A form template belongs to a kind, and the kind fixes what is not negotiable — that a hazard assessment has a hazard section, that a signature is the signer’s own attested name, which audit elements the form feeds.
A published definition is frozen into a version, and every submission binds to the version it was completed against. Reword an item in March and every February record still reads as February’s form. Editing a live form does not disturb the crews filling it in either — the change sits as a draft until you publish it.
| You decide | The kind decides |
|---|---|
| Which items appear, their wording, their order | That a hazard assessment has a hazard section |
| Your own company-specific checks and fields | The audit elements the form feeds |
| Where the form applies | That a signature is the signer’s own attested name |
| Retiring it, and versioning it | Which field types exist at all |
What you can build
Workplace inspections
Formal and informal, scoped to the sites and frequencies you set.
Hazard assessments
FLHA and JHA, with the hazard and control structure preserved.
Equipment inspections
Pre-use and periodic checks tied to the asset they belong to.
Toolbox talks
Delivered on site, with attendance recorded attributably.
Work checklists
Operational checks that belong to the job rather than the program.
Service reports
What was found, what was done, what the customer needs to know.
Customer sign-off
An acknowledgement that means exactly what its wording says.
Commissioning forms
Structured records for handover and start-up work.
Governed, not an open canvas
There is a deliberate boundary here, and it is worth being plain about: Orientra is a form authoring tool, not an application builder.
Twelve field types, all of which render, print and audit. No scripting, no formulas, no conditional visibility, no external lookups, and deliberately no “other” field — because that absence is exactly where a form builder turns into a second, ungoverned system nobody can audit.
If a form your company genuinely needs cannot be expressed, that is a reason for us to extend a schema deliberately. It is not a reason to open a canvas.
Incidents are not authorable, on purpose. An incident is a first-class record with its own investigation and reporting duties. Its form belongs to that record, not to a template somebody can restructure.
A submitted form is evidence. Signed, locked, bound to its version, and carrying what the signer’s competencies were at the time. That is what makes it worth producing to an auditor.
See the form builder with one of your own forms.
Start a 45-day free trial with your own company — no card required — or book a demonstration focused on the workflows that matter to you.