Your business process, drawn not coded

Why it matters

Most workflow tools ship with pre-built workflows. The customer picks the closest match and bends their process to fit the approval workflow software. This works on day one and breaks on day thirty when business reality diverges from the platform's assumption.

The alternative most platforms offer is "professional services." The customer hires the vendor's consultants to build a custom workflow. The build takes weeks. The workflow that comes out matches the business at the moment of build, but every change going forward requires another engagement. Workflows freeze, because changing them is too expensive.

Aproove's approach: give administrators the designer. Administrators are the people closest to the business, with the best understanding of what should change and when. A no-code visual designer puts workflow design in the hands of the people who know the work, with no engineering ticket and no consulting engagement required.

The result is workflows that match the actual business, and evolve with it.

How it works

The administrator opens the Business Process Workflow Builder and starts drawing.

Project creation criteria. Every workflow needs a trigger. The administrator defines what kicks off the workflow: a file upload, a submitted brief, an API call from another system, a form submission, or a trigger fired from another workflow. The workflow starts when its trigger condition is met.

The workflow diagram. The administrator adds steps by clicking and naming them, then connects them with arrows that represent decisions. Steps can branch into multiple paths and loop back on themselves. Steps can be color-coded and labeled to make the diagram readable at a glance.

Step behavior. Each step has its own configuration: how long it should take, whether a Conflict Manager is assigned, what release rules apply, what decision buttons appear in the reviewer interface, and whether the work is handled per-file or per-proof. Decision buttons are fully custom; administrators define as many as the process requires (Approved, Rejected, Send to Legal, Hold for Print, Escalate to Director, and so on).

Step Groups. Each step has at least one Step Group, which defines who does the work. The administrator assigns users, teams, or contact groups, and sets the rules for how the step resolves: unanimous agreement, majority answer, single decision advances, or team task anyone can pick up. Override permissions can be granted to designated users.

Triggers and Actions between steps. Between any two steps, the administrator can configure automated Actions that fire on specific decisions. These can move files, archive projects, post to chat, invoke Concoord middleware flows, or call external systems directly via the Callback URL Action. The Concoord vs direct API distinction is configurable per Action. Visual indicators show where Actions are wired in the diagram.

Step security. Steps that require regulatory compliance can be configured with e-signature requirements (FDA 21 CFR Part 11) and two-factor authentication, both on a per-step basis. The same workflow can mix lightweight steps and high-security steps without forcing the highest security ceremony across the board.

Reference documents and download paths. Workflows can be configured to link proofs to master files or templates through naming-convention matching (using regular expressions for complex naming structures). Download paths for any step can be routed via regex to specific filesystem locations, supporting integration with production systems that expect files in defined places.

Timesheet input. When a step's decision should prompt time tracking entry, the administrator configures which decisions trigger the timesheet popup. Time and Materials data flows into the project record and downstream reporting.

Built for business operators

The designer in our approval workflow software is intentionally not for developers. A few choices reinforce that:

• Visual-first. The workflow is drawn, not written. The diagram is the source of truth, not a config file.
• Plain-language configuration. Steps, decisions, rules, and assignees are configured through forms and dropdowns. No expression syntax beyond the optional regex for naming-convention matching.
• Live diagram updates. As Actions and assignments are added, visual indicators appear on the workflow diagram so administrators see what they have built.
• Iterative. Workflows can be edited without service interruption. Adding a step, changing a decision rule, or wiring a new Action does not require a release cycle.

This means a marketing operations lead can adjust a campaign approval workflow when a new market launches, a compliance manager can add a regulatory step when a new framework applies, and a production manager can re-route prepress handoffs when a vendor changes, without filing a ticket or scheduling a consulting engagement.

Benefits

• Workflows match your actual business. Every workflow in the approval workflow software is configured to the customer's process, not selected from a fixed menu.
• Administrators self-serve. No engineering ticket, no consulting engagement, no waiting on the vendor. Business operators design and deploy workflows themselves.
• Workflows evolve with the business. As the business changes, the workflow changes. The platform does not lock the process into the version it had on day one.
• Composable. The designer wires Aproove's primitives (decisions, parallel flows, conflict management, triggers, e-signature, time tracking) into the customer's specific process. The depth is in the primitives; the designer composes them.
• Multiple workflows run side by side. Different business units, brand families, product categories, or regulatory regimes can each have their own workflow without conflict.
• Security is per-step, not platform-wide. E-signature and 2FA apply where the workflow needs them, without imposing high-security ceremony on every step.‍
• The visual diagram doubles as documentation. The workflow diagram itself shows the business process. Audit, training, and onboarding can refer to the diagram directly.

Who it's for

• Aproove administrators designing workflows for their organization.
• Marketing and creative operations leaders mapping campaign approval chains.
• Compliance and regulatory managers encoding review requirements into workflows.
• Production and prepress managers modeling handoffs between creative, prepress, and press.
• IT and platform owners evaluating whether the platform supports administrator self-service or requires vendor consulting for every workflow change.

Under the hood

The Business Process Workflow Builder is a configuration layer over Aproove's workflow engine (BPM). Workflows are stored as configuration, not code, with the visual diagram and the runtime model staying in sync. Steps are defined with Step Groups (assignees), Decision Buttons (custom decision options), routing rules (which decision goes to which next step), duration and escalation policy, security requirements (e-signature per FDA 21 CFR Part 11, 2FA per step), and Actions (workflow-triggered automation). Triggers between steps can invoke Concoord middleware flows or call external systems directly via the Callback URL Action; the distinction is configurable per Action. Workflows can include branching, parallel paths, loops, conditional logic, and metadata-driven routing. The same workflow can serve many projects, with different metadata values resolving to different assignees at runtime (see Smart Routing at Scale). Workflow changes are deployable without service interruption; in-flight projects continue under the workflow definition active at their creation, while new projects pick up the latest version.