# Understanding Process implementation

> In Maestro, **implementation** is the step where a modeled process (your BPMN diagram) becomes an **executable, agentic workflow**. On the UiPath<sup>®</sup> Studio Web canvas you add runtime instructions (properties, variables/expressions, events, tasks, and gateways), bind them to automations, AI agents, and human steps, then test and publish to the process engine. This is distinct from [Process modeling](https://docs.uipath.com/maestro/automation-cloud/latest/user-guide/process-modeling-title) (designing the diagram) and from [Process operations](https://docs.uipath.com/maestro/automation-cloud/latest/user-guide/process-operations-title) (monitoring/running instances).

In Maestro, **implementation** is the step where a modeled process (your BPMN diagram) becomes an **executable, agentic workflow**. On the UiPath<sup>®</sup> Studio Web canvas you add runtime instructions (properties, variables/expressions, events, tasks, and gateways), bind them to automations, AI agents, and human steps, then test and publish to the process engine. This is distinct from [Process modeling](https://docs.uipath.com/maestro/automation-cloud/latest/user-guide/process-modeling-title) (designing the diagram) and from [Process operations](https://docs.uipath.com/maestro/automation-cloud/latest/user-guide/process-operations-title) (monitoring/running instances).

**Why it matters**: Maestro’s implementation stage is where the orchestration across robots, AI agents, and people is defined so the process can actually run end‑to‑end.

## A simple implementation example

**Use case**: Purchase request approval

![Purchase request approval process diagram](https://dev-assets.cms.uipath.com/assets/images/maestro/maestro-implementation-scenario-purchase-request-approval-617495-a0f5e349.webp)

The example process contains the following elements:

- **Variables** — `Amount:number` and `RequesterEmail:string` (Expression editor) drive routing and outbound notifications.
- **User task** — `Manager review`, assigned to the Manager role, captures the approval decision.
- **Exclusive gateway** — evaluates `Amount > 5000` and routes to `CFO approval` if true, or directly to fulfillment otherwise.
- **Service task** — calls an external system or automation to create a purchase order.
- **Send task** — emails `Request approved / rejected` to `RequesterEmail`.
- **Timer event** — on `Manager review`, escalates after 24 hours via an alternate path.
- **Test & publish** — the solution is validated with Simulate/Debug, then published to make the process available.

This example provides you clear routing by amount, auditable approvals, automatic PO creation, and notifications—implemented once, reused safely.

Start importing a BPMN model, or drawing new one, or using [Autopilot for Maestro](https://docs.uipath.com/maestro/automation-cloud/latest/user-guide/autopilot-for-maestro) to help you along. See [Process modeling](https://docs.uipath.com/maestro/automation-cloud/latest/user-guide/process-modeling-title) for canvas features details.