Signing & Fields
Configure signing fields on a PDF
Place signer fields accurately and map each field to the right role.
9 min read · beginner
Fields are the contract between your document and signer actions. If fields are clear and correctly assigned, recipients complete quickly. If fields are vague or misassigned, envelopes stall and support workload grows. This guide helps you configure fields on PDFs with precision so sends are reliable at scale.
You can apply these practices in both Create Envelope and template editing flows. For end-to-end sending context, pair this guide with Create and send envelope.
Field setup principles before placement
Before placing your first field, lock three decisions: recipient role model, signing order expectations, and required data points for completion. Field configuration should reflect documented process requirements, not guesswork during last-minute sending.
Maintain a short field map for high-volume templates. This map lists each required field type, owning role, and page location. Template maintainers can use it for quality reviews whenever packet files are updated.
Step 1: Open Fields and select role first
In the wizard, navigate to Fields and select the target document tab. Then choose the role that should complete the next field. Always set role first. Placing fields before role selection is the fastest way to misassign work.
Step 2: Place required actions before optional inputs
Start by placing all mandatory signer actions, such as signatures, initials, required dates, and mandatory checkboxes. Only after required coverage is complete should you add optional or convenience fields. This sequencing prevents accidental release with missing core actions.
Use visual alignment and spacing standards so recipients can read documents naturally. Fields that overlap source text or sit far from relevant clauses increase error rates.
Step 3: Validate field settings for each role
After placement, inspect each role independently. Confirm required toggles, expected input formats, and field visibility. Then switch roles and repeat. This role-by-role audit catches hidden mismatches that are easy to miss when scanning one page globally.
If your team uses sequential routing, ensure later roles are not blocked by missing required actions from earlier roles. Pair this with Sequential signing order standards.
Field types reference table
| Field type label | Typical use | Configuration note |
|---|---|---|
| Signature Image | Primary legal signature action | Set required for binding execution steps |
| Initials | Clause acknowledgment on specific pages | Use consistently on every required page |
| Text | Open text entries like title or reference | Set required only when process-critical |
| Checkbox | Consent confirmations and option picks | Label clearly in nearby document text |
| Date / Signer Date | Date of signing or acknowledgment | Prefer signer date for signer-completed events |
| Number | Amounts, counts, or numeric identifiers | Use for structured numeric entry validation |
| Signer contact confirmation in document body | Avoid if email already captured elsewhere | |
| Phone | Contact number capture | Use only when operationally required |
| Signer Name / Signer Email | Auto-filled recipient metadata fields | Useful for readable completed records |
| Attachment | Recipient uploads supporting documents | Use sparingly and explain expected file type |
Step 4: Test field clarity from signer perspective
A technically valid field layout can still confuse signers. Review your PDF as if you were the recipient. Is each action obvious? Is sequence intuitive? Are required tasks near relevant text? Improving signer clarity reduces abandonment and reminder overhead.
For recipient-side behavior details, review /help-center/what-signers-see.
Step 5: Revalidate after document replacements
Replacing PDFs can shift page geometry and break precise placement. Any time a source file is updated, revisit field coordinates and role assignments. Never assume prior alignment remains valid after legal or branding changes.
Template owners should maintain a mandatory retest rule: no updated template can be used in production until one internal test send passes without corrections.
Field quality checklist before Review
- Every role has required fields for mandatory actions.
- No field belongs to the wrong role.
- Fields are aligned with relevant document context.
- Required flags reflect true process requirements.
- Optional fields are intentional, not leftover drafts.
- Updated documents were fully revalidated after replacement.
Frequent field configuration mistakes
- Assigning all fields to first role accidentally.
- Placing fields before confirming final PDF versions.
- Overusing optional fields that create visual clutter.
- Missing required signer action on one packet page.
- Using inconsistent field spacing across related pages.
Correct these with structured review and ownership accountability. In high volume teams, one field quality reviewer can prevent significant downstream support effort.
Troubleshooting and escalation
For editor-level troubleshooting, start at /help-center/configure-signing-fields. For sending-stage failures after field setup, check /help-center/send-your-first-envelope and then verify envelope status progression with /help-center/track-signers-and-reminders.
Next workflow optimization
Once field quality is stable, focus on execution speed and follow-up discipline with Send from template: Quick Send vs Customize and Track signers and send reminders.
FAQ
Frequently asked questions
Short answers to the questions teams ask most often about this topic.
Why are fields assigned to roles instead of documents only?
Role assignment controls who can complete each field. The same document can contain tasks for different recipients, so role ownership is required.
How do I reduce missed signer actions?
Use required fields for all mandatory actions, place fields near clear instructions, and validate each role coverage in Review before Send Envelope.
Should optional fields be avoided?
Use optional fields only when they support a real process need. Too many optional fields create visual noise and can confuse recipients.
Where can I troubleshoot field editor behavior?
Use /help-center/configure-signing-fields for editor troubleshooting and role-assignment checks.
Related guides
Follow along in the app
Open WoltSign and complete these steps in your workspace.