Flattening form fields before filing

Interactive form fields are convenient for data capture - and often harmful at filing. A field that looks completed on the firm desktop may appear empty, shifted or still editable in a court viewer. That is why flattening form fields belongs in many firm standards before upload.

What flattening does to forms

Flattening burns field values into fixed page content. Values can no longer be changed by tabbing, and the visible text matches what would print or rasterise. Without that step, some portals store only the field definition without the value - or a recipient overwrites fields accidentally on open.

Flattening is not the same as “save as image only”. Done well, text often remains searchable; done poorly, you get huge image PDFs with no text layer. The aim should be: fix values visually, keep file size reasonable, preserve searchability where possible.

When fields may deliberately remain

Internally fillable checklists, client questionnaires still in progress and templates for recurring pleadings may keep fields - clearly marked as working copies. Once the file is meant to reach court, opponent or the matter file as a final version, that exception ends. Mixed packs with partly flattened and partly open fields are especially error-prone.

A sequence that holds under deadlines

1. Complete and save the form
2. Visual check of every page with fields
3. Flatten on a copy
4. Verify: no blank former field positions, tab no longer jumps
5. Only then merge with exhibits

Teams that merge first and flatten later often inherit field conflicts from different form sources. Order is quality work here.

Spot checks after flatten and before merge

After flattening, a glance at page one is not enough. Jump deliberately to pages with mandatory fields, date fields, checkboxes and signature blocks. Typical failure pictures: a value missing visually though it was set before flatten; a checkbox looking “half”; text spilling from the former field box. Those spots generate questions from court or client.

Keep a short list of forms the firm uses often - with known trap fields. New joiners need that list more than a generic “please flatten” instruction. Merge only after a successful spot check; anyone who must still correct individual fields afterwards risks reintroducing an interactive layer.

If a portal still treats a flattened file as a form, inspect leftover empty field definitions without values. Sometimes a second flatten with another tool or a print-to-PDF pass on the problem pages helps. Document the chosen method per form family so every matter does not reinvent the experiment.

LexLogik supports these preparation steps in the browser. Responsibility for correct field values stays with the fee-earner - flattening does not correct wrong answers; it only fixes them in place.

Check field values against source

Before flatten, support samples fields against the source template (amount, date, matter number). On mismatch, the run stops and the matter lead decides. Flatten without field checks cements typos into the filed copy.

Flatten form fields only when content and release are right. The filed copy then stays stable - and nobody must explain why an editable field was still changeable in the court system.