Conditional fields are document fields that dynamically change based on the signer's input. Instead of showing every possible field to every signer, conditional logic lets you create documents that adapt -- showing only what is relevant.
For example, a standard service agreement might include optional clauses for rush delivery. Rather than cluttering the document with fields that most signers will leave blank, you can set a condition: "If rush delivery is checked, show the rush surcharge acknowledgement."
This makes documents cleaner, reduces signer confusion, and ensures that required information is only collected when it is actually needed.
Documents with conditional fields see 35% fewer completion errors and 20% faster signing times. Signers only see what is relevant to them, reducing cognitive load and the chance of missing a required field.
SignAndGo supports three operators for conditional field rules. These cover the vast majority of real-world document workflows.
The target field appears when the source field value matches exactly.
Example
If "State" equals "NSW", show "NSW-specific disclosure" field.
The target field appears when the source field contains any value.
Example
If "Phone Number" is not empty, show "Preferred contact time" field.
The target field appears when a checkbox or radio option is selected.
Example
If "Acting on behalf of a company" is checked, show ABN and company name fields.
Upload a PDF or choose from SignAndGo templates. The document opens in the field editor where you can place signature, text, checkbox, and dropdown fields.
Add the field that will control the condition. This could be a checkbox ("Is this a company?"), a dropdown ("Select your state"), or a text field ("Enter your ABN").
Add the field that should appear or become required when the condition is met. For example, a "Company Name" text field that only appears for business entities.
Select the target field and open the conditional logic panel. Choose the source field, select the operator (Equals, Not Empty, or Checked), and set the trigger value if applicable.
Decide what happens when the condition is met: show the field, hide the field, or make it required. You can also chain multiple conditions for complex logic.
Use the preview mode to test your conditional logic. Click through the document as a signer would, verifying that fields appear and hide correctly. Then send to your recipients.
Show different clauses based on employment type. Full-time employees see superannuation fields; contractors see ABN and invoice terms.
Reveal pet bond fields when "Pets" is checked. Show company guarantor fields when tenant is a business entity.
Display optional add-on pricing when specific services are selected. Show payment schedule fields for projects over a threshold.
Reveal vehicle details when "Motor Vehicle" is selected as asset type. Show dependant information when "Dependants" checkbox is ticked.
Start with single conditions before chaining. Most workflows only need one condition per field. Complex chains increase the chance of logic errors.
When the condition is yes/no, use a checkbox with the "Checked" operator. It is the most intuitive for signers and the simplest to configure.
Before sending a document with conditional fields, walk through the signing experience using preview mode. Verify that every combination works as expected.
Do not create conditions where Field A depends on Field B and Field B depends on Field A. This creates a loop that prevents signers from completing the document.
Conditional fields are form fields that appear, hide, or become required based on the signer's input in other fields. For example, checking a 'Company' checkbox can reveal ABN and company name fields that are otherwise hidden.
SignAndGo supports three operators: 'Equals' (field value matches a specific value), 'Not Empty' (field has any value entered), and 'Checked' (checkbox or radio button is selected). These cover the vast majority of conditional logic needs.
Yes. You can set multiple conditions on a single field, requiring all conditions to be met (AND logic) before the field appears. This enables complex workflows like showing payment fields only when both a service type is selected and a specific region is chosen.