Docs/Workflow Model

Workflow model

Every SealAudit workflow follows the same three-stage model: Trigger, Verification, and Action. Each stage contributes to a defensible evidence record.

1. Trigger stage

A workflow begins when someone scans a QR code or opens a direct URL. The trigger resolves to a specific published workflow version and starts a new scan session.

QR scan endpoint

A printed or displayed QR code resolves to a published workflow version.
Field workers scan with any phone camera or QR reader.
Each scan creates a new session and audit event, even when verification fails.

Direct URL entry

A secure link opens the workflow directly in a mobile browser.
Useful for scheduled inspections sent via operational messages.
Same session and audit tracking as QR-based triggers.

2. Verification stage

After a trigger is resolved, the workflow applies configured verification rules. Rules can be optional or required. Each rule records its outcome as pass, fail, bypass, or error.

Authentication verification

Requires the user to sign in before the workflow proceeds. Supports required or not-required modes depending on policy.

Geolocation verification

Compares the user location to a configured point and radius. Consent-based and recorded as an outcome in the audit trail.

3. Action stage

Once verification checks are complete, the workflow executes one or more ordered actions. Actions can be mandatory or optional depending on the workflow configuration.

Record check-in

Captures workflow completion evidence with timestamp proof.

Redirect

Sends the user to an internal or approved external resource such as policy or training content.

Show document

Displays a required document for the user to review inline.

Acknowledgement

Captures a user sign-off or acknowledgement record tied to the workflow version.

Form submission

Presents a structured form with user-submitted data stored as part of the evidence package.

Versioning

Workflow definitions are versioned. Publishing creates an immutable version so historical records remain interpretable even as workflows evolve over time.

Each published workflow version is immutable -- deployed triggers reference a specific version.
Document versions are tracked alongside workflow versions for complete audit context.
Version references preserve the exact rules and steps in force when a scan occurred.

Start building your first workflow

Create an account and configure a compliance workflow in minutes.