> ## 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 Reduce the Number of Fields on a Form
- URL: https://blog.jestor.com/reduce-number-of-fields-on-form/
- Published: 2026-09-17T22:34:14.000Z
- Updated: 2026-09-17T22:34:14.000Z
- Author: Bruno Bannach

To **reduce the number of fields on a form**, you rarely need to remove data. Most long forms are long because they ask for things the system could derive, connect, or hide.

## Where the length comes from

Forms grow one reasonable addition at a time.

- Fields asked of everyone that apply to few
- Data typed that exists on a related record
- Values that could be calculated from other answers
- Fields added for one edge case and never removed

## Four ways to shorten without losing data

| Technique            | What it removes                                        |
| -------------------- | ------------------------------------------------------ |
| **Conditionals**     | Questions that do not apply to this case               |
| **Connected fields** | Data that already exists on a related record           |
| **Formula fields**   | Values derivable from other answers                    |
| **OCR**              | Data readable from an attached document                |
| **Pagination**       | Perceived length, when every field is genuinely needed |

## How to apply them in Jestor

1. Add conditionals in **Jestor** so questions appear only when they apply.
2. Replace typed details with a connected field pointing at the client or supplier record.
3. Use formula fields for values derivable from what was already entered.
4. Let **OCR** read an attached invoice or receipt rather than asking for its values.
5. Use pagination where the remaining fields are all genuinely required.

## Why choose Jestor for efficient intake?

Because **Jestor** is relational, a connected field replaces several typed ones — selecting a supplier brings their details rather than asking for them again.

Formula fields and OCR remove more: a value calculated or extracted is a value nobody has to type, and one fewer opportunity for an error.

## Frequently Asked Questions

### Can I ask for less without losing data?

Yes — connect, calculate, or extract instead of asking. See [jestor.com](https://jestor.com/?ref=blog.jestor.com).

### What if every field is genuinely needed?

Use pagination to reduce perceived length.

### Can a document supply the values?

Yes, through OCR on an attachment.

## 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.