RPAA workflow sample
RPAA incident notice
Run a synthetic case, inspect the tasks, forms, decisions and evidence, then download the generated workflow as a file your engineering team can review before anything goes live.
Try the sample case
Synthetic data only — editable in your browser. Nothing is uploaded or filed.
Manual pain today
- – Incident facts in multiple ops tools
- – Impact assessment in slides
- – Notice drafts outside the evidence trail
- – Recovery closure not linked to the incident
Current vs proposed
Current: Pager → slides → email notice → forgotten closure
Proposed: Incident case → impact → gated notice pack → updates → recovery evidence
1 · Sample inputs
Source systems
- Observability — Incident signal
- Customer support — User impact
- Policy register — Notice criteria
2 · Workflow execution
Incidents span systems and users, but material-impact assessment and notice packages are rebuilt ad hoc.
3 · Generated form / output
Incident notice package preview
Incident
- INC-2026-091
- Payment API + webhook · ~1,240 users
Impact
- Degraded initiation 47 minutes
Status
- Awaiting owner approval
Sample does not file to a regulator. Authorized officers remain the reporting entity.
4 · Verification and evidence
Traceable, versioned, auditable sample events — not blockchain or immutable claims.
- Incident opened · Telemetry summary attached
- Impact assessed · Draft material-impact recorded
- Awaiting owner · Human approval gate
What TrustField would connect in production
- Observability — Incident webhook
- Support — Impact counts
Agent Execution Assurance
Your engineers review the workflow before it goes live
The agent builds the workflow and hands you the specification as a file. Your engineering and compliance teams read it, mark it up, and sign it off. Nothing touches a production system, a customer record, or a regulator until they do.
Step 1
The agent generates it
Stages, field mappings, validation rules, decision gates, and evidence events are produced from your scenario.
Step 2
You take the file
Download the full specification as JSON. It is inert: reading it, storing it, and diffing it changes nothing.
Step 3
Your team approves it
Your named reviewer records a decision in the signoff block and returns the file. Only then does TrustField configure it.
Who is reviewing it?
Optional. The download works without any of this.
Fill this in and the file is made out to your organization, with your reviewer named in the signoff block, so it arrives ready to circulate internally.
Status in the file: inactive. It cannot activate itself.
What your reviewers should check
- – Every source system listed, and whether the stated role for each is correct
- – Field mappings against your own field names and formats
- – Validation rules against your internal policy, not just the regulatory minimum
- – Whether each human decision gate sits with the role that actually holds that authority
- – Whether the evidence events satisfy your retention and audit requirements
- – Whether the boundaries match what your compliance function expects of an automated system
The file states what the system does and what it will not do, including that it does not make the filing decision and does not submit to a regulator without an authorized officer of your organization.
Choose one launch path. You do not pay CAD 4,900 plus CAD 8,500. Workflow Confirmation is optional.
Optional — if scope is unclear
Confirm the scope
CAD 900
No production deployment.
Fully credited toward a qualifying Controlled Launch within 30 days.
Choose one launch path
TrustField performs the implementation. You confirm data, roles, decisions, and access.
Recommended
Controlled Launch
CAD 4,900 total
One working workflow using CSV, secure file, structured form, manual intake, or another simple data source.
60 days Launch Care included.
Connected Launch
Connect to your live systems
From CAD 8,500 total
The working workflow plus one live API, webhook, database, SFTP, or application integration, automated case creation, retry/recovery, and status synchronization.
After go-live
Both production launch paths include 60 days of Launch Care. Continued hosting, monitoring, and support are optional afterward under Managed Care from CAD 750/month.
Already launched with TrustField? Live integration is quoted as incremental scope. Reusable workflow work is reflected in the SOW.
Boundaries
TrustField may collect and map data, route tasks, draft forms, validate fields, prepare packages, and preserve evidence. It does not make the legal filing decision, determine regulatory applicability, provide legal advice, guarantee compliance, or auto-submit in this public sample.