Electronic signing does not fix a bad PDF. The sender must first prove that the content is final, pages are readable, recipient roles are clear, fields belong to the right person, and the completed record can be retained.
Freeze the approved content before placing fields
Identify the person authorized to approve the text and record the source version. Resolve tracked changes, comments, blanks, pricing, dates, exhibits, references, and signature blocks before building the signing transaction. Editing after fields are placed can shift coordinates or create disagreement about which text was approved.
Source control
Document ID: ______ Version: ______
Content approver: ______ Approved at: ______
Source filename and hash: ______
Exhibits included: ______
Inspect every page
- Correct order, orientation, crop, and page size.
- No blank, duplicated, missing, or unintentionally hidden pages.
- Headers, footers, page numbers, exhibits, and cross-references agree.
- Scans are straight, legible, and complete at practical zoom levels.
- Redactions remove underlying content rather than drawing a visible box over it.
- Links and referenced attachments lead to the intended material.
Check text, fonts, and document structure
Confirm text can be selected and searched where expected. Review font embedding and substitution on another device. Scanned text may need optical character recognition, but OCR output must be checked against the image rather than assumed correct.
Accessible PDFs require more than readable pixels. Review headings, reading order, language, alternative text for meaningful images, table structure, labels, keyboard movement, contrast, and form-field names. The W3C publishes PDF techniques related to WCAG. Use an accessibility specialist where the document or audience requires it.
Map recipients before fields
| Recipient | Role | Required actions | Order | Authentication or delivery rule |
|---|---|---|---|---|
| Customer representative | Signer | Initial scope, choose option, sign acceptance | 1 | Approved verified address and required identity step |
| Internal manager | Approver | Approve pricing exception | Before or after customer, as policy requires | Authenticated internal account |
| Accounts team | Viewer or copied party | No signature field | After completion | Controlled delivery |
Do not give every recipient every field. Assign each required field to one role, define what happens if a recipient declines, and identify who can correct a contact address or restart the transaction.
Place only fields the workflow needs
Use clear labels and sufficient target size. Keep fields away from text, page edges, and one another. Mark required fields deliberately. Signature and initial fields should sit beside the language they acknowledge, but a field’s position does not repair ambiguous contract text.
Where a value already exists in the approved source, decide whether the signer may change it. A free-text field can create a new term or conflict if the document does not explain its effect.
Test conditional and calculated fields
If one answer reveals another section, test every branch, including no selection and contradictory selection. For calculated totals, reconcile displayed amounts, underlying inputs, rounding, currency, tax, deposits, and the final stored value. Preserve how the calculation worked at signing time.
Run a mobile and keyboard pass
- Open the actual signing preview on a narrow phone and a desktop.
- Read from the first page to the last without using field navigation.
- Then move through fields using keyboard controls where supported.
- Zoom and confirm labels remain associated with fields.
- Test a long name, long email address, and maximum expected text.
- Confirm the review and download path works before and after completion.
Verify the transaction summary
Before sending, compare the transaction to the recipient map: exact document version, parties, contact addresses, roles, order, fields, required states, authentication, reminders, expiration, decline behavior, message, and copied parties. Use a second-person review for high-impact agreements.
Name the completed record before it exists
Define the final filename, document ID, storage location, access group, retention category, and system record that will link to it. The electronic-signature evidence checklist explains what to retain beside the completed PDF.
Final send gate
- Approved content and exhibits match the transaction.
- Every recipient address and role was independently checked.
- Required fields are complete, assigned, legible, and accessible.
- Mobile, keyboard, conditional, and calculation behavior was tested.
- Consent, authentication, reminder, and expiration settings match policy.
- Closeout storage and audit exports have an owner.
If the document changes scope, price, or schedule after work begins, route it through the controlled change-order process rather than editing a completed file.