Good forms collect clean data the first time — no chasing, no retyping.
Almost every business still sends out documents that get printed, filled in by hand, scanned crookedly and emailed back as an unreadable image. Someone then retypes the contents into a spreadsheet, occasionally misreading a digit. A properly built fillable PDF removes that entire chain — and this guide covers how to build one that people actually complete.
What a fillable PDF actually is
A standard PDF is a fixed rendering of a page: visually perfect, functionally inert. A fillable PDF adds an interactive layer of named form fields on top of it. Because each field has a name and a data type, input can be validated, values can feed calculations, and responses can be exported to a spreadsheet.
The distinction matters commercially. A flat form transfers work to you. A fillable form keeps the work where the information originates — with the person who has the answers.
Choosing the right field types
Use dropdowns wherever an answer is finite
This single decision does more for data quality than anything else. Ask two hundred people to type their country and you'll receive "USA", "U.S.A.", "United States", "us" and at least one typo. A dropdown returns one consistent value every time, so your exported data sorts and filters without cleanup.
Radio buttons versus checkboxes
The rule is simple and frequently broken: radio buttons when exactly one answer is valid, checkboxes when any number can be. Using checkboxes for mutually exclusive options invites contradictory submissions that someone then has to resolve by phone.
Auto-calculation is the highest-value feature
If a form contains any arithmetic, calculated fields are what justify building it properly. On a typical order form, quantity multiplied by unit price produces a line total, line totals sum to a subtotal, tax applies as a percentage, shipping adds on, and a grand total updates the instant anything changes. Nobody calculates anything, so nobody calculates anything wrong.
Validation that prevents rather than corrects
Every field should reject invalid input at the moment it's typed. The alternatives — catching it during review, or not catching it at all — both cost more.
- Required fields so the form can't be submitted incomplete.
- Format masks forcing phone numbers, postcodes and reference numbers into a consistent shape.
- Numeric ranges rejecting impossible quantities or dates.
- Custom messages that explain what's wrong instead of simply refusing the entry.
That last point matters more than it sounds. An error reading "Invalid entry" creates a support email. One reading "Please enter the date as DD/MM/YYYY" does not.
Signatures and locking the document
An electronic signature is a drawn or typed mark — quick and widely accepted for routine commercial documents. A digital signature is cryptographic and tamper-evident: if anything changes after signing, the signature visibly invalidates. For internal approvals and standard agreements the former is usually sufficient; for high-value or regulated documents, the latter is worth the setup.
Either way, configure the signature field to lock the document on signing. A signed form whose figures can still be edited afterwards provides no protection at all.
Accessibility isn't optional
If your form will be used by the public, by government bodies or by any large organisation, accessibility compliance is frequently a procurement requirement and in many jurisdictions a legal one. An accessible form needs tooltips on every field (screen readers announce the tooltip, not the printed label), a logical tab order following the visual reading sequence, tagged structure, sufficient contrast, and a declared document language.
These take minutes during the build and are painful to retrofit. They also improve the form for everyone — a clean tab order means keyboard users can complete the whole document without touching a mouse.
Getting the data back
| Method | Best for | Limitation |
|---|---|---|
| Email submit button | Low volume, known recipients | Depends on the user's mail client |
| Save and attach manually | Universal compatibility | Relies on the user following instructions |
| Submit to a web endpoint | Higher volume, structured data | Needs a server to receive it |
| Export FDF / CSV | Bulk processing | Requires consistent field naming |
Whichever you choose, enable Reader Extensions so recipients using free Acrobat Reader can save their completed copy. Without it, users fill in the entire form, press save, and discover their data has vanished — the single most common complaint about poorly prepared PDF forms.
Mistakes that get forms abandoned
- Fields too small for real answers. A 20-character box for a company name guarantees truncation.
- No tab order set. Pressing Tab jumps randomly and users give up.
- Everything marked required. Forms that demand irrelevant information get closed rather than completed.
- Inconsistent field naming. Exported data becomes unusable when fields are called Text1, Text2, Text3.
- Never tested on mobile. A significant share of recipients will open your form on a phone.
Frequently asked questions
Need a form built properly — fields, calculations, signatures and all? Send me your document and I'll turn it into a fillable PDF, usually within 24 hours.