How to design an internal form people will complete
To design an internal form people finish, the discipline is subtraction. Every field is a cost paid by the person filling it in, and most forms collect data nobody ever uses. In Jestor, conditional fields and pagination let a short form still capture what different respondents need to provide.
Why forms grow and never shrink
Each field was added by someone who wanted the information. None is removed, because removing it requires someone to argue it is unnecessary.
Within a year the form takes four minutes, completion rates fall, and the data that does arrive is filled carelessly.
What discipline produces:
- Higher completion, particularly among busy people
- Better quality in the fields that matter
- Faster processing, since less is reviewed
- Fewer fields to maintain when the process changes
- A clearer process, because the form reflects the decision
The test for each field
| Question | If the answer is no |
|---|---|
| Does a decision depend on it? | Remove it |
| Could we look it up instead? | Use a connected field |
| Is it relevant to everyone? | Make it conditional |
| Would we chase it if missing? | If not, it is not required |
| Has anyone used it in six months? | Remove it |
Step by step to build one
- Start from the decision the form supports, not from what is nice to know.
- List only the fields that decision needs.
- Replace lookups with connected fields, so nobody types what exists.
- Make everything else conditional, shown only when relevant.
- Paginate if the form still has more than a handful of questions.
- Test with someone who has never seen it.
- Review after three months, removing fields nobody used.
Why connected fields shorten forms more than deleting questions
A field asking for a client's address is really asking the respondent to retype something you already hold. Replacing it with a reference to the client record removes the question and improves the data at the same time, which deleting alone cannot do.
Why choose Jestor
In Jestor, forms support conditional fields, pagination, embedded explanations and public links without login, while connected fields reference existing records so respondents select rather than type. Submissions become structured records that can start an approval or a workflow directly.
Frequently Asked Questions
How do I decide whether a field belongs?
Ask whether a decision depends on it. If not, remove it. See jestor.com.
How do I keep a form short when different people need different questions?
Conditional fields, so each respondent sees only what applies.
How often should a form be reviewed?
Every few months, removing fields nobody has used.
Video Tutorial: Step by Step
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.