Show signers only the fields that apply to them.
Not every signer needs every field. Conditional fields let a document adapt to the person filling it in, so a field stays out of the way until an answer elsewhere makes it relevant. The result is a cleaner document, less confusion, and information collected only when you actually need it.
What a conditional field is
A conditional field is shown only when another field on the document has a particular value. Instead of showing every possible field to every signer, you set a rule and the field appears when the rule is met.
Take a service agreement with an optional rush delivery clause. Most signers will never choose it, so rather than leave a surcharge acknowledgement that most people skip, you set a rule: if the rush delivery box is ticked, show the rush surcharge acknowledgement. Everyone else never sees it.
The conditions you can use
- Checked or not checked. For a checkbox (the editor says checked; your signer ticks it). Example: if "Signing for a limited company" is ticked, show the company name field.
- Equal to, or not equal to, a value. The field appears when another field's answer matches, or does not match, the value you enter. Example: if "Employment type" equals "Contractor", show the invoicing terms field.
- Filled in. The field appears once another field has any value at all. Example: if "Phone number" is filled in, show "Preferred contact time".
The field that drives a rule can be a checkbox, a text field, or a name, email, company or date field. A checkbox is the most dependable source, because it has only two states and the signer cannot spell them differently from the way your rule expects.
Setting one up
- Upload your document and open it in the field editor, where you place signature, text and checkbox fields.
- Place the source field. This is the field whose answer controls the rule, such as a checkbox asking "Is this a company?".
- Place the target field. This is the field that should only appear when the rule is met, such as "Company name".
- Add the rule. Open the target field's properties, switch on conditional visibility, choose the source field and the condition, and enter a value if the condition needs one.
- Test it. Send a test envelope to yourself and fill it in as a signer would, checking that the field appears and stays hidden when it should. Then send it for real.
Where conditional fields help
Employment agreements
Show the fields that apply to the type of engagement. A contractor sees invoicing terms that an employee never needs.
Leases
Show a pet clause acknowledgement only when "Keeping a pet" is ticked, and show guarantor details only when "A guarantor is required" is ticked.
Service agreements
Display optional add-on fields only when a particular service is selected.
Insurance forms
Reveal vehicle details only when "Motor vehicle" is chosen as the asset type, and dependant details only when the "Dependants" box is ticked.
Keeping your rules reliable
- Keep each rule simple. Most fields need only one condition, and simple rules are easier to check.
- Use a checkbox for yes or no decisions. It is the clearest choice for signers and the easiest rule to set up.
- Always test before sending. Walk through every answer that changes what appears, not just the most likely one.
- Avoid loops. Do not make field A depend on field B while field B depends on field A, or neither can appear.
Two details that catch people out
"Equal to" means exactly equal
An "equal to" rule compares the answer with your value exactly, letter for letter. If your rule expects "Contractor" and the signer types "contractor" or "Contractor " with a trailing space, the field stays hidden. Where you can, turn the question into checkboxes, one for each answer, and base the rule on a box being ticked. If you must use a text field, tell the signer in its label exactly what to type.
A hidden field is never demanded
If a field is marked required but its rule keeps it hidden, the signer is not asked to complete it and can still finish. That is what you want, but it means a mistake in a rule can quietly skip a field you meant to collect. Test each answer that should reveal a required field and confirm it appears.
A few more questions
Which fields can control whether another field appears?
A checkbox, a text field, or a name, email, company or date field. A checkbox is the most dependable, because its answer can only be ticked or not ticked.
What happens to a required field that stays hidden?
The signer is not asked for it and can finish without it. Only fields that are showing count as required.
Frequently asked questions
- What are conditional fields?
- Fields that are shown only when another field on the document has a particular value, so each signer sees only what applies to them.
- Which conditions can I use?
- A checkbox being checked or not checked, a field being equal to or not equal to a value, or a field being filled in with any value.
- Where do I set a condition?
- In the field editor, open the properties of the field you want to show conditionally and switch on conditional visibility.
- How do I know my rules work?
- Send a test envelope to yourself and fill it in as a signer, trying each answer that should change what appears.
See SignAndGo for your team
Send your first envelope in a few minutes, and keep every signed copy with its audit trail.
See how it works