Make a form-ready, fill-and-return PDF safe
Goal
Handle a fill-and-return PDF form safely: collect the answers into a spreadsheet, then freeze the filled form so the stored copy cannot be edited, and lock it if it is sensitive.
A clinic sends a registration form to 40 families. Forty filled PDFs come back. You need the answers in one table, and a final, uneditable copy of each form for the file.
What this recipe does and does not do
Be clear before you start: no Documentize app creates fillable fields or restricts what a recipient can edit. Flatten freezes fields, Protector sets one open password but leaves every permission allowed. So you design the blank form in your own authoring tool, and this recipe covers what happens after the forms come back.
Starting state
- Filled-in PDFs that are interactive forms (text boxes, checkboxes, radio buttons, drop-downs), all from the same template.
- Not password-protected (otherwise Unlock).
- If the returned forms are printed-and-scanned, there are no fields: use Searchable and Extract Text instead.
Chain
Extract Form Data → Flatten → (Protector)
answers to CSV freeze password to open
Step by step
1. Extract Form Data
Upload all returned forms and press Extract. There are no options. You get one CSV per form, form_data_summary.csv (status per file) and form_data_export.csv. Why first: flattening turns fields into static page content and the fields then come back empty. See Extract Form Data.
Open the summary and look for failed files before moving on.
2. Flatten
Upload the filled forms and press Flatten with both option fields empty to freeze every field. If one field must stay live (for example a signature or office-use box), put its exact name in Fields to Skip (keep editable). Use either option box, not both. Names are case-sensitive and a typo means nothing is frozen. See Flatten.
3. Protector (only for sensitive forms)
Type a strong password, leave Full Document Lock, press Protect. Why last: Protector will not re-encrypt an already-encrypted file and many other apps cannot read it. Store the password in a password manager; Documentize cannot recover it. See Protector.
Why this order
Extract before you freeze (the answers live in the fields), freeze before you lock (a locked file cannot be edited by the other apps), and lock last. Reversing the first two loses your data; reversing the last two forces an extra Unlock.
Expected result
A spreadsheet-ready set of CSVs, and one flat, final PDF per form (optionally password-protected).
Check it worked
- The CSV header lists the field names and each form has its values underneath.
form_data_summary.csvshows no failed files, and the field counts match across forms.- In the flattened PDF, click a former field: it no longer accepts typing, and the typed answer is visible text on the page.
- A protected file asks for the password in your viewer.
Variations
- Keep a signature field open: list it under Fields to Skip.
- Need XFDF for another PDF tool: use Parser, which writes
formdata.xfdfinside a ZIP. - Make the final copy tamper-evident: after Flatten, sign it with Sign and do not add Protector (see Contract round-trip).
- Combine the answers: open the CSVs in a spreadsheet; see Tables and forms to spreadsheet.
What can go wrong
- Empty CSV values: the form was not filled in, or was already flattened.
- Columns do not line up: the files came from different templates; process each template separately.
- Weird characters in Excel: the CSV is UTF-8; import with that encoding.
- Annotations or comments: the chapter says Flatten is built around form fields; test a copy if you also need comments baked in.
- Expecting Protector to block editing or printing: it does not; it only controls opening.