If you have purchased Adobe Acrobat Pro from Licensgo, you already have everything you need to create reliable fillable PDF forms, validate entries and collect digital signatures. This guide is designed for office workflows—valid for both Adobe Acrobat Pro 2020 perpetual and the subscription edition. You can purchase or renew your licence here: Adobe Acrobat Pro.

1Step 1 — Prepare the PDF form

Open the source document (Word, InDesign or a scanned PDF). In Acrobat Pro go to ‘Tools’ > ‘Prepare Form’. Acrobat automatically detects fields (text, checkboxes, radio buttons, drop-down menus, dates, signature) and places them. Tidy up labels, align fields and set the ‘Tab Order’ for logical keyboard navigation.

Add or edit field types from the toolbar: text, multi-line, date, checkbox, radio button, drop-down, list, button and digital signature. Use consistent Field Names (e.g. applicant_firstname) and ‘Tooltips’ to help users. In drop-downs set export values consistent with reporting.

  • prefer clear labels above fields;
  • keep one question per line;
  • group related fields and set a logical tab order.
Quick alignment

Select multiple fields, then right-click > ‘Align’, ‘Distribute’, ‘Centre’ for neat grids in a few clicks.

2Step 2 — Validations and calculations

With a field selected open ‘Properties’. In ‘Format’ choose types such as Number, Percentage, Date, Time, Zip Code, Phone Number. In ‘Validate’ apply ranges or regex patterns; tick ‘Required’ for fields that must be completed. In ‘Calculate’ set Sum, Average, Min/Max or custom scripts only if strictly necessary.

Define meaningful export values for checkboxes/radio buttons (e.g. yes/no or 1/0). Keep calculations robust by referencing the exact field names. Test with sample entries and export a CSV to check headers and encoding before distribution.

  • mark critical entries as ‘Required’;
  • prefer built-in formats over custom scripts;
  • keep numbers as numbers (avoid currency symbols in the field data).
Data formats

Standardise date/number format everywhere to avoid inconsistencies in the CSV.

3Step 3 — Digital signatures (smart card/USB)

Distinguish between simple e-sign (typed/drawn) and digital signatures with a certificate. For compliant workflows add a ‘Digital Signature’ field. Recipients sign in Acrobat Reader or Acrobat desktop using a certificate on a smart card/USB token, with the vendor’s drivers installed. You can also ‘Certify’ the document to lock content after signing (‘File’ > ‘Protect’ > ‘Certify’).

For multiple signers, define signature fields in sequence and set permissions (who can fill in/what is allowed to change after each signature). Consider time-stamping via your organisation’s TSA if required. Mobile apps allow basic fill/sign but often don’t support certificate tokens.

Smart card tip

Install up-to-date drivers and middleware before testing signatures on target PCs.

4Step 4 — Send and collect responses

In ‘Prepare Form’ click ‘Distribute’. Choose email or a shared folder/SharePoint. Acrobat can track responses and create a collection file. To analyse results, export the data (‘More’ > ‘Export Data’) to CSV and open in Excel. If you need desktop Excel, consider Microsoft Office 2024 Professional Plus.

Before company-wide sending, run a pilot with 3–5 recipients on different systems (Windows/macOS, desktop/mobile) and ensure they use Acrobat Reader instead of browser viewers.

  • prefer shared folders with stable permissions;
  • export to CSV for integration with systems;
  • version the form (v1.0, v1.1) to track changes over time.
Track responses

Use ‘Distribute’ > ‘Track’ to monitor submissions and consolidate data in one place.

5Protections and compatibility

Set security from ‘File’ > ‘Protect’: restrict editing, printing or add an open password. For public forms prefer permissions that still allow filling and saving. Avoid flattening until archiving. For smaller files, see tips to optimise PDFs with Adobe Acrobat.

Browser PDF viewers have limitations (no calculations, signatures unsupported or partial JavaScript). Tell recipients to use the desktop Acrobat Reader or the Acrobat mobile app for critical workflows. Protect response collections at rest with appropriate policies; if needed, complement with good encryption practices: disk encryption vs per-file encryption.

Back up the collected data and signed PDFs according to your organisation’s retention rules. For a simple plan, see the guide to practical backups.

Browser warning

Do not complete or sign critical forms inside Chrome/Edge PDF viewers.

6Best practice — zero surprises

Use this checklist to cut support tickets and ensure smooth submissions across devices and departments.

  • embed fonts or use standard fonts for reliable rendering;
  • set ‘Required’ only on fields that truly need it;
  • keep field names stable; avoid renaming after distribution;
  • define export values for checkboxes/radio buttons;
  • test in Acrobat Reader (Windows/macOS) and on mobile before go-live;
  • avoid heavy JavaScript; prefer built-in functions;
  • keep the file light with optimised images;
  • document versions and the change log in the file properties.
Quick QA

Run a pilot with 3–5 users and export a trial CSV before broad distribution.

7Quick troubleshooting

Common issues and quick fixes to try before involving IT.

  • Fields not fillable: the recipient opened it in the browser viewer — ask them to use Acrobat Reader;
  • Calculations not working: check exact field names and numeric formats;
  • Cannot save the completed form: check permissions that allow fill+save;
  • Digital signature blocked: use a ‘Digital Signature’ field; check drivers/middleware;
  • Garbled characters in CSV: export in UTF-8 and open from ‘Data’ > ‘From Text/CSV’ in Excel;
  • Large file: optimise images; see our PDF optimisation guide;
  • Radio/checkboxes missing in export: set explicit export values.