QEHSQEHS

Workflows

Workflow engine that runs your program, not just your forms.

Visual state machine with guards, effects, approvals, SLAs, and escalations. Simulate changes in a sandbox before they touch production.

Every QEHS program is a set of transitions — Draft → In review → Approved → Closed; Reported → Investigated → Action plan → Verified. The Workflow engine lets you design, version, and run those transitions without a line of imperative code.

Parallel approval branches and nested guards

1h

Critical SLA on Enterprise, escalations included

0

Downtime to roll a workflow version forward or back

States and transitions

Declare the states a record can be in and the transitions between them — with role, location, and module-scoped permissions.

  • Per-module state machine, versioned with the template
  • Role + location scoping on every transition
  • Parallel approval branches with join conditions
  • Per-tenant override of parent template transitions

Guards — keep dirty data out

Predicate expressions that block a transition until conditions are met.

  • Require a signature, approver, or linked record
  • Require a field value, range, or computed expression
  • Require a capability (feature gate) — e.g. SSO on Enterprise-only transitions
  • Human-readable error messages, localised per tenant

Effects — automate the side effects

Every transition can fire one or more effects, processed by the BullMQ queue.

  • Email, in-app notification, push, SMS
  • HMAC-signed webhook to an external system
  • Create or update another record (cross-module)
  • Assign a task to a user, role, or location group
  • Log to audit trail + SIEM feed

SLAs, escalations, and scheduled work

Time-based rules that run against records on a schedule, not just on user action.

  • Per-transition SLA with tier-gated response windows (24h / 8h / 1h)
  • Escalation paths — reminder, manager, fallback role
  • Scheduled tasks — recurring inspections, training renewals, permit expiries
  • Per-tenant calendar (working days, holidays) applied to SLAs

Sandbox simulation + audit

See what a workflow change will do before you publish it.

  • Sandbox tenant replays production records through a proposed workflow
  • Diff of transitions, effects, and SLA impact per record type
  • Immutable audit log — every event, actor, before/after, effect outcome
  • Rollback to a previous workflow version without data loss
Approvals, escalations, SLAs, and scheduled work all share one engine — not three SaaS subscriptions. Every action is auditable and replayable.

Ready to see Workflows?

Pick a slot with our team.

30-minute demo tailored to your QEHS programs and your stack. No slide decks, just a working tenant.