Forms

Build forms with 18 specialized field types designed for maritime operations. Input fields include TextBox, Number, TextArea, DatePicker, TimePicker, and Rating/Slider for numeric scales. Selection fields cover CheckBox, Select, MultiSelect, CheckboxGroup, and RadioGroup for structured choices.

The Question field type captures Yes/No/NA responses — the bread and butter of maritime checklists. Table fields handle structured data entry with rows and columns. Layout fields — Paragraph, Header, and Space — let you add instructions, section dividers, and visual structure to your forms. Rich Text Editor fields capture formatted text with inline styling.

Every form assignment can use one of four approval flow variants — Full (Ship + Office), Ship-only, Office-only, or No Approval. The approval flow is configured per assignment, not globally, so the same form template can require different approval levels depending on the vessel, rank, or operational context.

Each flow supports three execution methods — All of (every approver must approve), Any of (one approval suffices), and Not Required (auto-approved). Approvers are configured at the assignment level with specific ship ranks and office users, giving you granular control over who reviews every form submission.

Crew members fill forms on the vessel, while office staff review, approve, and manage form submissions from shore. The system handles the complete handoff between ship and office — submissions flow from vessel to shore for review, and approvals or rejections flow back to the crew.

Both ship and office users see the same form with the same fields, but their roles in the workflow differ. Ship crews create drafts and submit for approval. Office reviewers see pending submissions across the fleet and can approve, reject, or request changes. The dual-context architecture ensures forms work identically online and offline.

Assign forms to specific vessels and crew ranks with granular control. Each FormAssignment specifies which ships receive the form and which OnBoardRanks (29 available ranks) are responsible for filling it. Per-assignment approver configuration determines who reviews submissions for each vessel.

Assignments support both one-time and recurring distribution. A single form definition can have multiple assignments with different ships, ranks, and approval configurations — so the same safety checklist can require captain approval on one vessel type and chief officer approval on another.

Forms can be attached directly to PMS maintenance tasks and Risk Assessments through the AttachedObjectType system. When a maintenance job requires a structured form — inspection checklist, test record, safety assessment — the form links directly to the PMS work order.

Risk Assessment integration lets you attach forms to risk evaluations, capturing structured data as part of the assessment process. The IsPmsTreeItem interface ensures forms appear in the PMS equipment tree context. Linked forms inherit the parent task's vessel and scheduling context.

Add comments at every stage of the form lifecycle — during definition development, review, and request processing. Comments support add, edit, and delete operations with full user attribution and timestamps. Notes capture additional context that does not belong in form fields.

File attachments support evidence uploads on both form definitions and requests. Attach reference documents, images, supporting materials, and verification evidence directly to the form record. Every attachment is tracked in the event log with upload date, user, and file metadata.

Monitor your form program with three dedicated dashboard widgets: Awaiting My Approval (grouped by vessel), Completed Forms, and My Drafts. Each widget provides at-a-glance visibility into the most critical form management activities.

The Awaiting My Approval widget shows pending submissions grouped by vessel, so approvers can prioritize by ship. Completed Forms tracks submission history. My Drafts ensures in-progress forms are not forgotten. Drill down from any widget to the underlying form data.