Triggers
Start on a schedule, an inbound event, a form submission, or an API call from another system.
e.g. a tasker arrives · a form is filed
Build the workflows only your agency runs.
Workflow iQ is Feith's BPM engine for your agency-specific processes: approvals, taskers, routing, reviews. Model them in a visual designer; every step then runs inside your security boundary and writes to one audit trail.
The gap A process you run That no product ships.
model
Workflow iQ Model the process Triggers, decisions, approvals, SLAs.
run
Your boundary Deployed where you are On-prem to air-gapped IL7 (TS/SCI).
The custom processes between your systems, modeled once and run inside your own boundary, under your identity and audit controls.
IL7 (TS/SCI) highest deployedAir-gapped and deployed today
4 ways to run, one definitionOn-prem to air-gapped IL7 (TS/SCI)
1 audit trailEvery step, decision, and approval in one tamper-evident log
A BPM engine for sensitive processes.
The processes that carry classification, clearance, and chain-of-custody requirements, and can't run on a shared, internet-facing platform.
Build any process
Model the agency-specific workflows no product ships (triggers, forms, decisions, approvals, SLAs, integrations) in the visual designer.
Learn moreGoverned by the platform
Runs under the platform's access controls, on one tamper-evident audit trail.
Learn moreDeployable wherever the work lives
Runs wherever the work lives, up to air-gapped IL7 (TS/SCI): single-tenant in every deployment, one definition everywhere.
Learn moreModel any process. Visually.
Workflow iQ is a visual designer and execution engine for government processes. Drag in triggers, forms, decisions, approvals, and integrations; set the routing and the deadlines; deploy. An agency can model a leadership data call end to end in Workflow iQ.
Trigger Data call arrives Leadership issues a tasker with a deadline.
Form step Capture the tasker A custom intake form records the scope, the owner, and the due date.
Decision Which offices own it? The workflow branches to the responsible offices.
Branch: assign by office
AssignPolicy
Assign to the policy office AssignField
Assign to the field office TrackSLA · 10 days
Track responses against the deadline Escalate any office that runs late. Then: close it out
ActionConsolidate the responses
ApprovalRoute for concurrence
ActionNotify offices & archive
The building blocks
Forms & queues
Capture structured input and route work to the right person or office.
e.g. an intake form · an office work queue
Decisions & branching
Route on any data the workflow holds: values, dates, roles, prior steps.
e.g. branch by office, amount, or priority
Approvals & SLAs
Multi-level sign-off, parallel concurrence, escalation, and deadline tracking.
e.g. supervisor → budget → final approval
Integrations
Read and write external agency systems and the Feith applications through governed APIs.
e.g. look up a record · open a case
AI steps (optional)
When a step needs to read, classify, or summarize content, it can call Prompt Runner: bring-your-own-model, inside your boundary.
e.g. summarize an inbound response
Example processes
Incident report intake Reporting & triage
1 When A staff member files an incident report.
2 Do this Triage it and route to the responsible office.
3 Then Track it to closure and log the resolution.
System access request Access & identity
1 When A staff member requests access to a system.
2 Do this Route to the manager, then security, for approval.
3 Then Trigger provisioning and notify the requester.
Travel & purchase approvals Internal approvals
1 When An employee submits a travel or purchase request.
2 Do this Route to the supervisor, then to budget.
3 Then Record the decision and notify everyone involved.
Every step, governed.
A workflow runs as part of the platform itself, so it carries the platform's controls instead of adding its own.
Authorized users only
A step is offered only to users authorized for that record, and records stay under the platform's RBAC and ABAC throughout the workflow.
ABAC on every AI call
AI steps are checked against the user's attributes on every call, so the AI sees only what that user can see.
One audit trail
Every step, decision, approval, and AI call writes to a tamper-evident log.
Governed integration
Reaches the Feith apps, the records vault, and external systems through governed APIs: federated identity, in-boundary, nothing crossing the perimeter.
In the designer
Visual canvas for the whole workflow
Drag-and-drop steps, decisions, approvals, and forms
Live preview as you model the flow
Version control and rollback
Test mode runs against real data
Deploy without recompiling or redeploying code
The engine runs where you do.
Workflow iQ deploys wherever your work already lives, up to air-gapped IL7 (TS/SCI), single-tenant in every case, and the same definition runs everywhere.
Deployment matrix
| Environment | Where it runs | AI models (optional) | Footprint |
|---|---|---|---|
| On-premises | Your datacenter, your hardware | Local or air-gapped models | Most common |
| Agency cloud | Your cloud subscription | Cloud models in the same boundary | Widely deployed |
| Feith FedRAMP cloud | Feith's FedRAMP Moderate cloud | Models inside the FedRAMP boundary | Authorized environment |
| Air-gapped / IL7 (TS/SCI) | Inside the enclave | Models inside the enclave | Classified deployments |
One custom workflow. Across your platform.
A custom workflow reaches the Feith applications, the records vault, and your agency's own systems through governed APIs, in one execution, inside one boundary. The applications stay productized; the workflow is your glue.
1Custom trigger
An agency intake form is submitted Trigger 2RMA iQ
Read the related record through the API Integration · read 3Case Manager
Open a review case through the API Integration · write 4Notify & log
Email the offices, write one audit entry Action Audit log
Workflow iQ runs inside the same accredited boundary as the agency's records, FOIA, and declassification applications, DoDM 8180.01-compliant records management included.
The Feith applications it integrates with
Common questions about Workflow iQ.
Does Workflow iQ count toward our FedRAMP boundary?
Yes, when the agency runs Feith in the FedRAMP cloud, the engine is part of the FedRAMP-authorized environment. On-premises or in an agency cloud, the boundary is whatever the agency defines. The engine inherits the boundary of the deployment, not the other way around.
How long to stand up a new workflow?
A standard workflow can be modeled and tested in days; advanced multi-step integrations or custom AI steps take longer. Training runs about a week for designers and two for advanced builders, and Feith engineering stays available for complex architecture.
When a workflow uses AI, whose models run it?
Your choice. The optional AI step calls Prompt Runner, which is bring-your-own-LLM: cloud-hosted models (Anthropic, OpenAI, Google), customer-hosted models in agency cloud, on-premises models, and air-gapped models inside classified enclaves all work. The platform requires no specific model and doesn't charge for the model layer.
Tell us about your process. We'll show you the designer.
Request received.
We'll reach out shortly to set up the call.