A Single Named Approver
One person is the approval step. They take leave, and the process stops for a fortnight with no signal that anything is wrong. Group approval exists precisely so a decision is not hostage to one calendar.
Formstack Workflow Automation
A Process That Stops in Somebody's Inbox Is Not Automated
Formstack workflow automation turns a sequence of forms, documents and signatures into a governed process with named owners, defined approvals and a visible audit trail. Twopir Consulting designs that process first — including what happens when it goes wrong — then builds it across Formstack Workflows and, where it belongs there instead, Salesforce Flow.
Process Orchestration Model Twopir · 2πr
Layer 01
Process Steps
Form Submission Approval Decision Document Generation Signature CRM Update
Layer 02 · 2πr
Twopir Orchestration Layer
Step & Routing Logic Approval & Ownership Exceptions & SLA
Layer 03
A Governed Process
Work Assigned Decisions Recorded Cycle Time Visible
Design Rule Every step needs an owner and a timeout
What Is Formstack Workflow Automation?
Formstack workflow automation is the sequencing of form, document, signature and approval steps into a single governed process. Formstack Workflows provides a visual builder for this: you drag steps onto a canvas, add step logic to control which path a submission takes, and add approval steps that can be assigned to an individual or to a group, with the assigned work surfaced in a shared workspace.
The consulting work is not the canvas. It is deciding what the process actually is: who is accountable at each step, what condition has to be true before the next one starts, what happens when nobody responds, whether a decision needs to be recorded against a CRM record, and — critically — which steps should not be in Formstack at all.
Visual builder Drag-and-drop canvas that recognises the Formstack apps on your account, so form, document, sign and approval steps can be assembled without code.
Step logic Conditional routing so different submission types follow different paths — including entirely different approval chains rather than one chain with skipped steps.
Approvals Customisable approval steps with individual or group assignment, so a decision is not blocked by one person's calendar.
Workspace A shared view of assigned work, which is what turns a notification into an actual queue somebody is accountable for.
Formstack Workflows or Salesforce Flow?
Teams that own both usually end up with process logic duplicated across them, which is worse than having it in either one. The question is not which tool is better — it is which system the process genuinely belongs to.
| The step | Put it in Formstack Workflows when | Put it in Salesforce Flow when |
|---|---|---|
| Collecting the information | The submitter is external, unlicensed, or occasional — a customer, applicant, supplier or member. | The submitter is a licensed Salesforce user already working inside the record. |
| Approving a request | The approver does not live in Salesforce, or the approval spans people without licences. | The approver works in Salesforce daily and the decision has to be visible on the record's own history. |
| Producing a document | The document draws on data from several systems, not only Salesforce. | Salesforce holds the data and the file should be attached to the record natively. |
| Updating the system of record | Rarely — this is normally the CRM's own job. | Almost always. Record-level automation, validation and rollups belong where the record lives. |
| Escalating a delay | The work is sitting with someone outside Salesforce and the reminder is to them. | The work is represented by a Salesforce record and escalation should create a task or update a status field. |
| Reporting on cycle time | Only the process steps matter, and Formstack holds them. | Cycle time needs to sit alongside pipeline, case or revenue reporting — which means the timestamps must land on Salesforce records. |
The rule we apply. Capture and approval by people outside the CRM belong in Formstack. Anything that changes the meaning of a record, or that has to be reported alongside other record data, belongs in Salesforce. Where a process crosses that line, the hand-off gets a written contract — which system owns the status, which fields are authoritative, and what happens if the two disagree — because an undefined hand-off is where duplicated logic starts.
Where Automated Processes Quietly Stall
No Timeout on Any Step
A step with no time limit has no failure mode — it just waits forever. Without a timer and an escalation path, the difference between "in progress" and "abandoned" is invisible to everyone including the person waiting.
One Chain Forced to Serve Every Case
A high-value and a routine request follow the same three approvals because the chain was built for the worst case. The routine work is slowed permanently, and people start routing around the process rather than through it.
Rejection With Nowhere to Go
The approval path is fully designed. The rejection path is a notification. The requester does not know what to fix, there is no route back in, and the work restarts from a blank form with the original context lost.
Decisions That Never Reach the Record
The approval happened in the workflow tool and the CRM record still says "pending". Two systems now disagree about the state of the same thing, and whichever one a given team looks at becomes their version of the truth.
No Measurement of the Process Itself
Nobody can say how long an average request takes, which step it waits at, or how many are rejected. Without that, process improvement is opinion — and the loudest opinion wins rather than the most accurate one.
What a Workflow Engagement Delivers
Process Design
The future-state process on paper, with every step owned and every branch accounted for, before anything is configured.
- Step-by-step map with accountable owner per step
- Entry conditions and completion criteria
- Branching by request type, value or risk
- Parallel versus sequential step decisions
- The steps that should be removed entirely
Approval Architecture
Approval that reflects your delegation of authority rather than whoever was available when it was built.
- Approval matrix mapped to authority limits
- Group approvals so no step has a single point of failure
- Delegation and out-of-office handling
- Rejection paths with a route back in
- Decision records written to the system of record
SLA & Exception Handling
What happens when the process does not behave — designed up front rather than discovered in production.
- Time limits per step with escalation routes
- Reminder cadence that does not become noise
- Recall, reassignment and cancellation paths
- Handling for submissions matching no rule
- Operational alerting for stuck work
Cross-System Orchestration
The hand-offs between Formstack and the systems that own the record.
- Boundary definition between Workflows and Salesforce Flow
- Status ownership contract between systems
- Document generation and signature steps in sequence
- CRM write-back at each state change
- Reconciliation so the two sides cannot silently diverge
Process Measurement
The instrumentation that turns process improvement from opinion into evidence.
- Cycle time captured per step
- Queue depth and ageing visibility
- Rejection and rework rates
- Reporting surfaced where leadership already looks
- A review cadence with a named owner
Audit & Control
The evidence a regulator, auditor or customer will eventually ask for.
- Complete decision trail per case
- Segregation of duties in the approval design
- Retention rules for process records
- Access control on workflow administration
- Change control for the process definition itself
Processes We Are Usually Asked to Fix First
Employee Onboarding
New-hire data captured once, offer and policy documents generated from it, signatures collected, and the record landing in the HR and CRM systems without anyone retyping a name.
Contract & Quote Approval
Commercial terms routed by value and risk, approved by the right authority level, generated into the agreed template and sent for signature — with the decision written back to the opportunity.
Applications & Enrolment
Multi-stage applications with document upload, eligibility checks, committee review and a decision letter — where the applicant can see where they are without emailing to ask.
Expense & Purchase Requests
Requests routed by amount against a delegation matrix, with group approval so the chain does not stall, and an audit trail that survives a finance review.
Supplier & Partner Onboarding
Due diligence capture, document collection, internal review across several teams in parallel, countersignature, and the supplier record created only once everything has cleared.
Regulated Change Requests
Processes where segregation of duties matters — the requester cannot approve, the approver cannot implement, and the whole trail has to be reconstructable long afterwards.
Answers Before the First Call
Put the approval where the approver already works. If the approver is a licensed Salesforce user who lives in the record, Salesforce approvals keep the decision on the record's own history where reporting can reach it. If the approver is outside Salesforce — a department head without a licence, an external party, an occasional reviewer — Formstack approvals reach them without buying licences for people who approve four things a year. What does not work is building the same approval in both, which is how two systems end up disagreeing about the same decision.
Whatever you designed — and if you did not design it, the answer is that the request waits indefinitely. We specify a time limit for every approval step, a reminder cadence, and an escalation route to a named alternative. Group approvals help considerably here, because the step is satisfied by any member of the group rather than by one individual's availability. Automatic approval on timeout is possible but we recommend against it for anything with financial or legal consequence: silence is not consent, and an auditor will say so.
Yes, and step logic is designed for exactly that: conditional routing lets different submission types follow completely different approval chains rather than sharing one chain with steps skipped. The judgement call is how much variation one workflow should absorb before it becomes hard to reason about. Our rule is that if a reader cannot trace any given path through the workflow in one pass, it needs splitting — maintainability matters more than having one canvas.
By capturing a baseline before you change anything, which is the step almost everyone skips. The four measures worth having are end-to-end cycle time, waiting time per step, rejection and rework rate, and queue ageing. Instrument those from the first release so improvement is evidenced rather than asserted. We also recommend surfacing them where leadership already looks — a process dashboard nobody opens has the same value as no dashboard.
Sometimes, and sometimes it is the wrong tool for the job. Formstack Workflows is strong where the process is driven by human steps — someone submits, someone reviews, someone signs. It is not an integration platform. If the bulk of your process is system-to-system data movement with a few human checkpoints, the orchestration usually belongs in your CRM or your integration platform, with Formstack handling the human-facing steps. We will tell you when that is the case, because we do not resell Formstack and have no reason to recommend more of it than the process needs.
Where This Connects
Parent Formstack Consulting Services The full practice and every other engagement type across the Formstack Suite. Adjacent Formstack Document Automation When the process exists to produce a document, the document lifecycle is the better framing. Boundary Formstack Salesforce Integration Where process state has to be written back to the record, and how that hand-off is contracted. Delivery Formstack Implementation Services The phased model for building a process end to end, with the exception paths designed before the build starts. Systems Formstack Integration Services When a process spans several systems, the integration design matters more than the workflow canvas.
Next Step
Name the Process That Waits in an Inbox. We Will Map It With You.
Bring the process everyone complains about. In one working session we will map the steps, find the ones with no owner and no timeout, and tell you which parts belong in Formstack and which belong in your CRM.
Process design from a team that will tell you when a step belongs in Salesforce instead — we do not resell Formstack licences.
