Your process. A form that fits.
Build reusable operational forms, publish controlled templates and keep submissions and reviews in one workspace.
Forms,
with the context you need.
The Forms workspace connects template authoring, controlled publishing and submission handling. Use permission-aware equipment or facility lookups where relevant, then give reviewers the context and evidence they need.
Reusable templates
Build and edit operational forms in a no-code authoring workspace.
Versioned publication
Publish a fixed template version while retaining earlier submission history.
Audience access
Control which departments and audiences can find and fill a form.
Reviewable submissions
Handle drafts, submissions, revisions, attachments and PDF export.
How the work connects.
- 01
Define the purpose
Choose the decision or record the form needs to support.
- 02
Build the template
Add the required fields and relevant authorized data lookups.
- 03
Review and publish
Check the intended audience and publish the reviewed version.
- 04
Collect and review
Keep responses, revisions and supporting evidence in the submission workspace.
Before you
get started.
Do users need to write code to build a form?
No. Template authors use the form builder. Publishing and access are controlled through the configured permissions.
Can a form use equipment and facility lists?
Supported data-source fields can use registered equipment, facility and other operational lookups. Each source still applies its own access permissions.
What happens when a template changes?
Published templates use fixed version snapshots. New edits are managed through the template lifecycle so earlier submissions keep their original context.
See forms in context.
Bring a representative workflow. We’ll walk through the records, responsibilities and configuration together.