Form data isn't where the work ends. It's where the workflow starts.

Why it matters

In most creative approval softwares, forms are input fields. The user fills them out, the data goes to a database, and the workflow runs on its own logic. Form data is reference material at best, fully decoupled at worst.

Aproove treats forms as the front-end of the workflow itself. The data captured in a form is the data that drives routing decisions, stakeholder assignments, automated actions, and downstream behavior. A "project kickoff" form does not just record who requested the project; it tells the workflow which account manager to assign, which brand template to apply, which compliance pathway to follow, and which deadline to honor. The form is the steering wheel.

This matters operationally for two reasons.

One, project managers stop being data-entry middlemen. The requester enters the project context once at intake. The workflow inherits all of it. Manual setup that used to take a project manager twenty minutes per project (assigning stakeholders, setting deadlines, configuring routing) collapses into the form submission itself.

Two, the data captured at intake stays usable for the life of the project and beyond. The same email address the requester typed into the project kickoff form is the email address the workflow uses six steps later when it sends the approved file back to them. The same brand code becomes the dashboard filter. The same project category becomes the reporting dimension. Capture once, use everywhere.

How it works

Form design. Administrators build forms in the admin tool by adding fields to a layout grid. Each field has a type (text, dropdown, date, etc.), validation rules (required, format constraints), and optional metadata mapping. The form's appearance and permissions are configured per audience.

Form Collections. When a single form is not enough, multiple forms can be grouped into a Collection. The administrator sets the order of forms, and for each form within the collection, can write a PHP eval formula that determines whether the form is shown based on values entered in prior forms. A common pattern: ticking "Other" in a checkbox on form one displays an "Other" text field on form two; not ticking it skips that form entirely.

Metadata storage. Field values are stored as metadata at the project level (or task level, depending on the form). The metadata is available to every Aproove subsystem: workflow routing, Trigger and Actions automation, dashboard column display, search filters, and report generation.

Workflow integration. Forms can be wired into workflow steps so they fire at the right moment. A form attached to a "Project Accepted" decision button presents the account manager with a "work instruction" form to complete before the project advances. Form data can drive which workflow branch is taken next, including triggering a different workflow entirely based on the captured values.

Task access. Form Collections can be exposed inside tasks (read-only by default) through the Proof Information popup. This gives external guests and users without Project Details permissions the ability to see the project context relevant to their task, without granting them broader access.

Ad-hoc tasks. Forms can be used outside of structured workflows for one-off task creation. A user fills out a basic "ad-hoc task" form (recipient, deadline, instructions) and the system creates a task in the recipient's To-Do List. When complete, the requester is notified.

Benefits

• Form data drives the workflow. Captured values are not just stored; they actively route, assign, and configure the work that follows.
• Capture once, use everywhere. The email address entered at intake is the email address used at approval. The brand code becomes the dashboard filter. The same data point serves all downstream uses.
• Complex intake handled cleanly with Form Collections. Multi-step intake processes are broken into sequenced forms with conditional logic, instead of one overwhelming form.
• Required fields enforce data completeness. Projects cannot start without the data the workflow needs to run. Cleanup work at later steps becomes unnecessary.
• Forms travel with the work. Form Collections can be made accessible inside tasks for guests and users without full project access, so external stakeholders see the context they need without broader permission grants.
• The same workflow serves many configurations. Form data determines routing, so one workflow template can serve dozens of project variants depending on what the form captures.‍
• No middleman data entry. Project managers stop spending time re-entering data that requesters already provided. The form submission is the configuration.

Who it's for

• Aproove administrators designing intake processes for their organization.
• Marketing and creative operations leaders running high-volume project intake where consistent data capture determines downstream throughput.
• Compliance and regulatory managers requiring structured data capture for audit and traceability.
• Customer-facing teams (account managers, project coordinators, customer service) handling intake from clients or internal requesters.
• Operations leaders evaluating whether a platform forces project managers into data-entry middlemen roles or lets requesters drive their own intake.

Under the hood

Custom Forms are configurable input layouts whose field values are stored as metadata at the project or task level. Field types include free text, dropdown, lookup, date, boolean, file upload, and others. Forms can be triggered at project creation, within workflow steps, on decision button activation, or as standalone ad-hoc task creation. Form Collections (released in 2025 R2) sequence multiple forms with PHP eval-based visibility formulas determining which forms in the collection display based on values entered in prior forms. Required fields gate the "Next" button between forms. Form Collections can be exposed inside tasks via the Proof Information popup as read-only, giving licensed users without Project Details access and external guests the ability to view forms relevant to their tasks. Form-captured metadata is available to Trigger and Actions for runtime variable substitution (the requester's email address typed at intake becomes the recipient address on a downstream automated notification, with no manual configuration). Dashboards can display form metadata as configurable columns. Reports can use form metadata as filtering and grouping dimensions. The same workflow can serve many distinct project variants by routing on form-captured metadata values (see Smart Routing at Scale).