> ## Content Index
> Fetch the complete content index at: https://blog.jestor.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# How to Design an Approval Request Form That Actually Works
- URL: https://blog.jestor.com/approval-request-form-design/
- Published: 2026-09-17T22:27:23.000Z
- Updated: 2026-09-17T22:27:23.000Z
- Author: Bruno Bannach

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

1. Build the request form in **Jestor** with the fields your **ERP** requires, marking the mandatory ones.
2. Add a connected table block showing the cost centre's details in place.
3. Add a PDF block fed by the attachment field, so the document is visible without downloading.
4. Split the card into panels: information, supporting detail, and an action panel with the buttons.
5. 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](https://jestor.com/?ref=blog.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](https://jestor.com/?ref=blog.jestor.com) and see how to take your company's operations to a new level of efficiency and control.