The End Process step marks the final outcome of a workflow or a branch within a workflow. Every workflow must end with an End Process step. Every branch created by a Decision Point must also end with its own End Process step.
WHEN TO ADD IT
Add an End Process step wherever a workflow or branch reaches its natural conclusion. If you have a Decision Point with two branches, both branches need their own End Process step.
FIELDS
Outcome / Deliverable
Describe what has been achieved or produced by the time the workflow reaches this point. Name it as an outcome, not as an action.
Good examples:
- "Client Fully Onboarded"
- "Invoice Paid and Reconciled"
- "Campaign Published to All Channels"
- "Lead Marked as Closed"
- "Design Approved and Sent to Client"
Avoid naming it after an action ("Send Final Email" belongs as a Manual Task before the End Process, not as the End Process title itself).
WHY IT MATTERS
The End Process step defines what "done" looks like. This is surprisingly useful for clients who have never explicitly articulated what the end state of a process is. Naming it clearly on the map creates shared understanding of what the process is trying to achieve, which is the foundation for measuring whether it is working.
In FixFlow reports, the End Process outcome is used as context for the executive summary. Naming it well leads to better, more accurate report language.
A COMPLETE WORKFLOW
A workflow is complete when every path through the map ends at an End Process step with no open branches. The Validation panel in the sidebar will flag any branches that are missing an End Process.