Form Metadata & Organization

Name, describe, and bookmark forms so your team can find the right template without hunting through an unorganized list

Overview

Every form record in Instafill.ai carries a metadata layer stored alongside its field definitions and workspaceId. This metadata - name, description, and training status - is scoped to the workspace and is not shared with other workspaces, even when two workspaces hold the same form template identified by the same field-hash.

The field-hash that create_form() computes for deduplication is also part of the form record. This hash determines whether a newly uploaded PDF can be served from an existing entry in the catalog (avoiding re-extraction), and it determines which forms benefit from shared AI fine-tuning. Workspace-specific metadata is layered on top of the shared structural record, so each workspace can name and document forms according to its own workflows without affecting other workspaces.

Key Capabilities

• Form Name and Description: Set a human-readable name and a plain-language description explaining what the form is, who fills it, and when it is used
• Starred Forms: Star frequently-used forms to pin them to your workspace for quick access - visible under the "Starred" tab in your Forms library
• AI Training Status: The form record exposes the training_status object ({status, fields_total, fields_finetuned, version, first_page_only}) so workspace members can see at a glance whether the form has been fine-tuned, is being fine-tuned, or has never been fine-tuned

How It Works

1. Set Form Name: After upload, the file name is used as the default. Rename it to something meaningful - e.g., "CMS-1500 - Medical Claims (2024 Version)" rather than "CMS-1500_v3_final.pdf".

2. Write a Description: Enter a plain-language description explaining the form's purpose, the regulatory context, and which department or role uses it. Example: "IRS W-9 Request for Taxpayer Identification - collected from all new vendors before first payment is issued."

3. Star a Form: Click the star icon on any form to add it to your starred list. Starred forms appear under the "Starred" tab in the Forms library, so frequently used templates are always one click away.

4. Review Training Status: The form detail page reads the training_status object from the AI fine-tuning pipeline. The workspace can see whether fine-tuning is "In Progress", "Completed", or has never been run - and whether a free-tier run (first_page_only: true) was the only processing performed.

Prepopulated Static Fields

A closely related feature worth knowing about: prepopulated static fields let you save fixed values directly into a form template so the AI leaves those fields untouched on every future fill. This is different from metadata - prepopulated values appear in the actual filled PDF, not just in the library.

Common uses: company name, office address, EIN, attorney bar number, license number - anything that never changes across submissions.

Once you save a value in a field, the AI skips it entirely and focuses only on the remaining fields. Values can be updated or cleared at any time, and they are stored per form. See the full guide to prepopulating PDF form fields with static data for step-by-step instructions.

Use Cases

Naming and describing forms matters most when a workspace grows beyond a handful of templates.

An HR department managing W-4, I-9, and state-specific new-hire forms benefits from descriptive names like "I-9 - Employment Eligibility (2024 Rev)" rather than the default upload filename. Combined with starred forms for the three templates used in every new hire workflow, the team spends no time locating the right form at the start of each session.

A healthcare billing team can use the AI training status field to identify which CMS-1500 and UB-04 templates have been fine-tuned to completion vs. which are still running on the base model - then prioritize AI fine-tuning for the highest-volume forms first.

A legal team with dozens of jurisdiction-specific court filing forms can write a description on each template noting the court name, case type, and filing deadline rules - context that would otherwise live in a separate wiki or require asking a colleague.

For workspaces with large libraries, form metadata works alongside Folder Management. Folders handle where a form lives in the workspace hierarchy. Metadata handles the description and status information attached to it regardless of location.

Benefits

• Workspace-Specific Context on Shared Infrastructure: Names and descriptions are workspace-scoped even when the underlying form field-hash is shared across the catalog - each workspace documents the form according to its own workflows without affecting anyone else
• Training Status Visibility: Surfacing training_status.fields_finetuned and training_status.version gives workspace administrators a concrete measure of AI optimization progress without navigating to a separate admin panel
• Starred Forms for Fast Access: Frequently used templates are one click away without searching or browsing folders every time