01
Trigger
A field user starts a workflow from a QR code or secure direct URL.
Both paths resolve to a published workflow version, create a scan session, and carry the deployment context needed for audit review.
02
Verification
SealAudit evaluates the configured identity and location rules before action execution.
Authentication and consent-based geolocation checks produce explicit outcomes that operators and auditors can interpret later.
03
Action
The user completes the required step in a mobile browser, with no native app required.
Actions can redirect, show a document, collect acknowledgement, capture form responses, or record a check-in event.
Trigger options
Two entry paths, one runtime model
QR codes and direct URLs are deployment choices. After resolution, both paths create a scan session and point to the same published workflow version so evidence stays consistent.
Field users complete the flow in a phone browser. MVP field execution does not require a native mobile app or a separate installed tool.
QR scan
A printed or displayed QR code opens the assigned endpoint for a site, asset, handover point, or inspection location.
Direct URL
A secure link in an operational message or internal system opens the same runtime path without requiring a printed code.
Verification outcomes
Checks are explicit, even when they do not pass
Workflows can require authentication, consent-based geolocation, or both. SealAudit records the outcome in plain operational terms so exceptions are visible instead of hidden in generic logs.
Pass
The configured check completed successfully, such as a signed-in user or an approved location match.
Fail
The check ran and did not meet policy, such as a missing login or location outside the configured radius.
Bypass
Policy allowed continuation without the check blocking the user, while still recording that the check was bypassed.
Error
The check could not complete cleanly, for example because a browser permission or network condition prevented collection.
Action execution
The workflow guides the required field action
Actions are the work the user actually completes after trigger resolution and verification. Each action can record started, completed, failed, or abandoned state for later review.
- Redirect to an approved destination, such as a policy page or training resource.
- Show the exact document version assigned to the workflow step.
- Capture acknowledgement against a document version or required message.
- Collect structured form responses with workflow-specific fields.
- Record a check-in with timestamp and workflow context.
Exception handling
Failures stay visible
Compliance teams need to understand what happened when a workflow does not complete normally. SealAudit treats blocked, failed, and abandoned runs as reviewable operational facts.
- A paused, revoked, or expired trigger can stop the workflow before field action begins.
- Failed or errored verification checks can block continuation or continue with an exception flag, depending on policy.
- Abandoned or failed actions remain visible instead of disappearing from the operational trail.
Stored evidence
Every run leaves a reviewable trail
SealAudit is designed to explain runtime behavior after the fact. The evidence record connects trigger, verification, and action data to the workflow and document versions that were active when work happened.
Session timeline
The record shows when the workflow started, which endpoint was used, and how the session finished.
Verification results
Pass, fail, bypass, and error outcomes stay attached to the session for operational review.
Version references
Workflow and document version references preserve what rules and content were in force at the time.
Action output
Completion state, acknowledgement records, form responses, and check-in evidence remain linked to the run.