Connects to the tools you use
Set up connections through ERP.AI and Proto workflows, with every change logged.
- Form Builder Platform
- Source systems
- External action providers
Form Builder Platform manages a form from field policy through a versioned definition, publication, submission review and follow-up. Organizations own field policies and forms.
Form definitions in one list
Independent Reviewer decides whether the source revision is approved, returned or rejected.
Every feature works on the same records. Pick one to see the screen your team works in.
Keep a form revision ready for publication.
Form definitions
| Number | Name | Revision | Status | Owner | |
|---|---|---|---|---|---|
| FD-93618 | Vendor onboarding questionnaire | 810 | Draft | Iris Chen | |
| FD-60866 | Facility inspection checklist | 750 | Validated | Mira Desai | |
| FD-19393 | Employee equipment request | 250 | Published | Evan Brooks | |
| FD-81318 | Customer feedback form | 100 | Retired | Amir Okafor | |
| FD-17004 | Incident report intake | 100 | Archived | Theo Nguyen |
Define the questions and their rules.
Field definitions
| Name | Code | Organization | Effective from | Effective to | Active | |
|---|---|---|---|---|---|---|
| Primary contact email | CONTACT_EMAIL | Cedarline Operations | 23 Oct | 30 Oct | Yes | |
| Tax registration number | TAX_REG_NO | Riverbend Program Office | 04 Nov | 10 Nov | Yes | |
| Inspection date | INSPECT_DATE | Riverbend Program Office | 27 Oct | 03 Nov | Yes | |
| Equipment serial number | ASSET_SERIAL | Harborfield Services | 13 Oct | 16 Oct | Yes | |
| Incident location | INCIDENT_SITE | Juniper Hill Services | 02 Nov | 04 Nov | Yes |
Keep each submitted line tied to its form.
Form submissions
| Parent | Sequence | Description | Outcome | Source reference | |
|---|---|---|---|---|---|
| Incident report intake | 40 | New vendor submitted tax and contact details | Pending | WEB-2026-1701 | |
| Quarterly compliance attestation | 90 | Inspector reported blocked side exit | Pending | KIOSK-2026-1702 | |
| Quarterly compliance attestation | 40 | Employee requested a replacement laptop | Pending | EMAIL-2026-1703 | |
| Grant application review | 50 | Customer reported a late delivery | Pending | WEB-2026-1704 | |
| Customer feedback form | 60 | Witness described a minor loading injury | Pending | MOBILE-2026-1705 |
Make the review decision inspectable.
Approval conditions
| Source | Source revision | Decision | Reviewer | Evidence reference | |
|---|---|---|---|---|---|
| Employee equipment request | 880 | Pending | Evan Brooks | DOC-2026-4101 | |
| Vendor onboarding questionnaire | 360 | Pending | Salma Nasser | PHOTO-2026-117 | |
| Facility inspection checklist | 940 | Pending | Lucia Ferreira | QUOTE-2026-084 | |
| Quarterly compliance attestation | 710 | Pending | Salma Nasser | RECEIPT-2026-291 | |
| Employee equipment request | 680 | Pending | Jun Park | WITNESS-2026-035 |
Assign the work that a review creates.
Follow-up actions
| Title | Source | Due date | Status | Assigned to | |
|---|---|---|---|---|---|
| Verify vendor tax document | Grant application review | 26 Oct | Open | Amir Okafor | |
| Review failed fire exit check | Event registration form | 13 Oct | In progress | Evan Brooks | |
| Approve replacement laptop | Customer feedback form | 24 Oct | Completed | Lucia Ferreira | |
| Call customer about delivery issue | Facility inspection checklist | 12 Oct | Open | Amir Okafor | |
| Collect incident witness statement | Customer feedback form | 15 Oct | In progress | Evan Brooks |
Trace what happened to an approved action.
Operation runs
Definition to reviewed submission ships ready to use. One step needs a named approval before the work moves on: Review revision (Independent Reviewer).
Record field policy and conditional rules for the organization.
Check the exact schema version before review.
An Independent Reviewer decides against the source revision.
An Operator publishes the validated revision with an action trace.
An Independent Reviewer checks the line and its evidence.
The assignee records the resolution of due work.
Open any form definition to see its evidence documents, the roles that work on it, its process stages and its approvals on one page.
Revision, Schema version and Owner.
Each line is linked to this form definition.
Admin, Form Owner and Operator, each with their own permissions.
Every status change, in order.
Review revision, with who decides.
1.0 · Draft
| Title | Source | Document date |
|---|---|---|
| Vendor tax form, October 2026 | Customer feedback form | 14 Oct |
| Fire exit inspection photo | Customer feedback form | 28 Oct |
| Laptop replacement quote | Quarterly compliance attestation | 04 Nov |
The reviewer records a decision against a source revision; the operator handles the subsequent action.
Signed in as Independent Reviewer
| Decision | Approver | |
|---|---|---|
| Review revisionAn Independent Reviewer decides against the source revision. | Independent Reviewer | |
| Approve form definitions | Independent Reviewer |
Everyone opens Form Builder Platform to the work that is theirs. Pick a role to see what it starts with.
Maintains organizational access and the people who own form work.
Owns the definition, field policy and publication handoff for a form revision.
This is the first screen this role sees.
Form definitions · Form Owner
Works on submissions and records the result of a validated action.
This is the first screen this role sees.
Execution attempts · Operator
Decides whether a source revision and its submitted lines can proceed.
This is the first screen this role sees.
Form definitions · Independent Reviewer
Checks supporting documents and records who verified them.
This is the first screen this role sees.
Evidence documents · Evidence Verifier
| Title | Source | Document date | Verified | Verified by | |
|---|---|---|---|---|---|
| Vendor tax form, October 2026 | Customer feedback form | 14 Oct | No | Iris Chen | |
| Fire exit inspection photo | Customer feedback form | 28 Oct | No | Salma Nasser | |
| Laptop replacement quote | Quarterly compliance attestation | 04 Nov | No | Nadia Rossi | |
| Customer delivery receipt | Facility inspection checklist | 23 Oct | No | Jun Park | |
| Incident witness statement | Customer feedback form | 29 Oct | No | Nadia Rossi |
Owns outstanding actions raised during review.
This is the first screen this role sees.
Follow-up actions · Follow-up Assignee
Read form outcomes, review queues and operation results from linked records.
This quarter
How far records got this quarter
| Stage | Reached | Step | |
|---|---|---|---|
| Draft | 39 | ||
| Validated | 19 | 49% | |
| Published | 9 | 47% | |
| Retired | 5 | 56% |
Sample totals per stage
Group submission lines by parent form and outcome.
Count form revisions by status and owner.
Show review decisions marked pending by reviewer and source revision.
Group evidence documents by verification value and source form.
Show open and in-progress actions by assignee and due date.
Follow failed operation runs into numbered steps and their failure details.
Compare a form revision with its linked submission lines and outcomes.
Show field definitions with their source and target mappings.
See how Form Builder Platform fits your kind of team.
Each stage of definition to reviewed submission names the role that acts and the status it records, so a change is never anonymous.
Each stage, the role that acts and the status it records
Ask Proto to prepare form configuration and trace a review case.
Set up connections through ERP.AI and Proto workflows, with every change logged.
Every record lives in a table you can see, extend and export. Add fields or whole tables in Proto.
Browse all 14 tablesStart with one team and one process, then add the rest once the basics are running.
Select an organization, owner and recurring form whose decisions can be reviewed with a real case.
Record the field policy, mapping, required setting, condition expression and validation rule.
Identify the Form Owner, Independent Reviewer, Operator, Evidence Verifier and Follow-up Assignee.
Validate a definition, record the revision decision and test complete and incomplete submitted lines.
Open the operation run, numbered steps, state history and any due follow-up action before expanding use.
$0per user
The base account and everyday work in the ERP.AI app are free, for every user.
| Usage | Per $1 |
|---|---|
| Record reads (list, filter, get) | 20,000 |
| Search or aggregate queries | 4,000 |
| Record writes | 4,000 |
| Imported or synced records | 200,000 |
| Workflow runs | 2,000 |
| AI agent runs | 2,000 |
| Scheduled jobs or webhooks | 20,000 |
| File uploads (MB) | 2,000 |
| CSV or PDF exports | 100 |
Click Get started, then use Proto to configure Form Builder Platform for your business. Begin with one organization, one form owner and a form with a conditional required answer. Rehearse its review and publication before adding more forms.
A Form Definition belongs to an organization and has an owner from People. Choose a named Form Owner for each working revision.
The form definition carries a required setting, condition expression and validation rule. Test both sides of the condition against the version being published.
Form Submissions are linked to their parent Form Definition. Each line has an outcome such as Pending, Accepted or Rejected.
An Independent Reviewer records a decision against the exact source revision. The decision can be Pending, Approved, Returned or Rejected.
Evidence Documents hold an attachment, source form and verification value. The Evidence Verifier records the check, and the reviewer considers the result with the decision.
Keep the rejected line visible and assign a Follow Up Action with an assignee and due date. Record the resolution when the work is complete.
Operation Runs and their numbered Operation Steps retain the source revision and action trace. Execution Attempts can carry a failure reason and provider reference.
Create a successor Draft revision and review it before publication. Keep the prior revision and its operation evidence for earlier submissions.
Start free, then use Proto to change fields, steps and approvals before your team goes live.