Use fields suited to the information
Combine short and long text, integers or decimals, checkboxes, single or multiple choices, and dates or date-times. Add labels, help text and required rules so requesters know what to provide.
Arrange data, visibility rules, tables and attachments so each request carries the information approvers need.
No payment required · Trial starts after onboardingTell us what your team needs.
Combine short and long text, integers or decimals, checkboxes, single or multiple choices, and dates or date-times. Add labels, help text and required rules so requesters know what to provide.
Set field visibility based on answers in other fields. Conditions distinguish request needs without making every requester work through questions that do not apply to their case.
Use dynamic tables with up to 10 columns for items or expenses, with configured row limits. Add attachment fields so approvers can review proposals and evidence alongside the form data.
Save form versions and use them in published workflow releases. Active requests retain the version they received; design changes for later submissions do not replace the structure of an ongoing process.
Tell us what your team needs.
Design around what requesters can provide and what approvers need to review.
Choose the information needed for your request category.
Add fields for each data type, repeated line items and attachments.
Configure required inputs, choices, value limits and visibility conditions.
Use the form version in a workflow ready to receive requests.
Illustrative scenarios you can adapt to your organization’s policies.
A requester needs to list several items, estimated costs and a vendor proposal.
Purchase details follow a consistent structure for review.
An IT team needs extra questions only for particular access types.
Requesters see relevant questions while reviewers receive the context they need.
Start with the team, forms and documents your work needs.