How to Design an Approval Request Form That Actually Works

A good approval request form captures everything the approver needs to decide, and nothing else. That means conditional fields, connected data shown in place, the supporting document visible, and the action buttons separated from the inputs.

Why most approval forms get sent back

Approvals stall for one reason more than any other: the approver does not have enough information and has to ask.

Requests missing the detail needed to judge them
Supporting documents attached but not viewable in place
Cost centre and supplier data living one screen away
Approval buttons buried at the bottom of a long form

What belongs on the form

Core request fields — description, value, dates, supplier
The routing field, usually the cost center, which determines the approver
Connected data, such as the cost centre's owner and description
The document, displayed inline as a PDF rather than downloaded
Conditional fields, like a rejection reason that appears only on refusal

How to configure it in Jestor

Build the request form in Jestor with the fields your ERP requires, marking the mandatory ones.
Add a connected table block showing the cost centre's details in place.
Add a PDF block fed by the attachment field, so the document is visible without downloading.
Split the card into panels: information, supporting detail, and an action panel with the buttons.
Add conditionals so a rejection reason appears only when a request is refused.

Why choose Jestor for approval processes?

Jestor puts the decision and the evidence for it on the same screen — connected records, documents, and history — which is what removes the back-and-forth that delays approvals.

Once approved, the entry can post straight into the ERP through a native integration, so nothing is retyped.

Frequently Asked Questions

Can approvers see the invoice without downloading it?

Yes, PDFs display inside the card. See jestor.com.

Can the rejection reason be hidden until needed?

Yes, using a conditional rule.

Can buttons sit in their own panel?

Yes, using multiple forms on the open card.

Video Tutorial: Step by Step

Check out other practical tutorials on the Jestor YouTube channel.

Get to know Jestor

With Jestor, you can automate workflows, connect teams, and build internal systems your way — all without code and powered by AI. Discover Jestor at jestor.com and see how to take your company's operations to a new level of efficiency and control.

How do you choose an AI tool for professional services operations teams in SMBs?

To choose an AI tool for professional services operations teams in SMBs, look for a platform that combines no-code tables for clients, engagements, and documents with AI features that answer messages, read documents, and summarize data, while keeping professionals in control of advice. In Jestor, these pieces work together,

How do you build a business continuity plan for a services firm?

To build a business continuity plan for a services firm, list critical processes and deadlines, identify risks such as system outages or key person absence, define backup options, assign roles, and test the plan. In Jestor, processes, risks, and actions are connected, so the firm keeps serving clients during disruptions.

What is the best way to run IT security awareness training for staff in a services firm?

A practical way to run IT security awareness training for staff in a services firm is to define short training modules, assign them to all staff, track completion, run simulated phishing tests, and schedule refreshers. In Jestor, staff, modules, and results are connected, so security habits become part of the

How do you route website lead forms to the right team in a services firm?

To route website lead forms to the right team in a services firm, ask for the service and company size in the form, route leads automatically to the right team, set response time targets, record follow-ups, and track conversion by source. In Jestor, forms, leads, and teams are connected,