skip to content

Streamline Form Processing

Lessons in this Workflow

Upload and group your forms

Start by uploading and isolating the forms you want to process so you can run the same extraction workflow across a consistent set of documents.

  • Upload your intake or other form documents into your project.

  • Use searches, binders, or folders to group the forms you want to process together.

  • Keep similar form types together when possible so you can apply the same extraction and reprocessing decisions across the set.

[Optional] Reprocess scanned or handwritten forms

  • Description: If your forms are scanned or filled out by hand, reprocess them before running extractions so more of the form content is available for search and extraction. Note: This step is most helpful when important answers are written directly into the form rather than stored in metadata.

  • Open a results table with the forms that need better text recognition.

  • Click “Batch” and then “Reprocess.”

  • If the forms include English handwriting, choose the handwriting-optimized OCR option.

  • Reprocess these forms before you set up or run extractions on them

Create and test extraction fields for form data

Once your form set is ready, create custom extraction fields for the exact answers or values you want Everlaw to pull from those documents.

  • Identify the questions or values you want to capture, such as applicant name, date of birth, case type, income, language, urgency, or eligibility information.

  • Create extraction fields with clear names, field types, and detailed descriptions.

  • In each description, explain what information to include, what to ignore, and how the value is likely to appear on the form.

  • Test your fields on a small sample of documents and refine them before using them more broadly.

Run extractions, review the output, and export

After testing your extraction fields, run them across your form set and organize the output so your team can review, filter, and use the extracted values more easily.

  • Batch generate your extractions once you know your fields are working well.

  • Click “View” and then “Add or remove columns” and then add the extraction fields column to display the extracted values you want to review.

  • Use sorting and filtering to compare answers across forms and locate documents with missing or high-priority values.

  • If you need a structured list of form answers outside the platform, click “Export” and then “CSV.”

  • [Optional] If certain forms should feed into case-building work, add key forms to Storybuilder.

[Optional] Evaluate forms with Coding Suggestions

If you want to assess forms against criteria like eligibility, completeness, or urgency, use Coding Suggestions after your extraction workflow is in place. Note: Coding Suggestions is most useful when your team wants to evaluate forms against criteria, rather than simply pull values out of them.

  • Decide what question you want to answer across the form set, such as whether a form appears complete, whether it seems to meet eligibility requirements, whether any required information is missing or inconsistent, or whether it should be prioritized.

  • Create or confirm the codes you want to use for that decision.

  • Configure Coding Suggestions with a detailed case description and clear code criteria.

  • Test Coding Suggestions on a smaller sample before running them more broadly.

  • Refine the criteria if needed, then run Coding Suggestions more broadly.

product-illustration-review-ai-assistant-doc-summary