> ## Documentation Index
> Fetch the complete documentation index at: https://docs.encoreos.io/llms.txt
> Use this file to discover all available pages before exploring further.
# Forms & Workflow Overview
> Overview of the Forms & Workflow core in Encore OS — purpose, scope, and key responsibilities.
The Forms & Workflow core (FW) provides cross-cutting form management and business process automation for Encore OS — form builders, workflow definitions, durable execution, event-driven automation, workflow versioning, and form analytics.
**Architecture:** FW is a cross-cutting capability used by multiple cores through the Platform Integration Layer. Other cores consume FW via integration contracts and events — never direct imports.
## How automation flows
Authors build forms and compose them into versioned workflow definitions. Triggers — cross-core events, scheduled cron, or webhooks — start a durable, resumable execution whose step history and completion feed analytics.
```mermaid theme={null}
flowchart LR
Form["Form builder
(schema + logic)"] --> Workflow["Workflow definition
(branching · retries ·
human-in-the-loop)"]
Workflow --> Version["Versioning"]
Trigger["Triggers
(events · cron · webhooks)"] --> Exec["Durable execution"]
Version --> Exec
Exec --> Analytics["Analytics
(completion · drop-off ·
time-to-complete)"]
Cores["Other cores
(via events)"] -.-> Trigger
```
## What FW covers
Schema definitions, conditional logic, validation, and multi-step forms.
Durable processes with branching, retries, and human-in-the-loop steps.
Long-running, resumable executions with full step history.
Triggers from cross-core events, scheduled cron, and webhooks.
Schema versioning and migration of in-flight instances.
Completion rates, drop-off, and time-to-complete metrics.
## Get oriented in FW
Define a schema with conditional logic and validation in the form builder.
Compose durable steps with branching, retries, and approvals.
Wire [cross-core triggers](/architecture/integrations/event-based-workflow-triggers-integration) so workflows run when other cores publish events.
## By role
Design and deploy workflows; manage versions and migrations.
Build intake, assessment, and audit forms.
Monitor durable executions and debug failed steps.
Audit completed forms and workflow evidence.
## Scope at a glance
* **Form builders** — schema definitions, conditional logic, validation rules, multi-step forms.
* **Workflow definitions** — durable processes, branching, retries, human-in-the-loop steps.
* **Event-driven automation** — triggers from cross-core events, scheduled cron, webhook entry.
* **Versioning** — form and workflow schema versioning, migration of in-flight instances.
* **Analytics** — completion rates, drop-off, time-to-complete metrics.
## Related
How FW listens to events from other cores.
Workforce forms and workflow automation.
Clinical event hand-off into workflows.
Practice-management-triggered automation.