Permanent form numbers
A form number stays unique within the company and remains stable when the form changes.
FORM LIBRARY & VERSIONS
Manage the business form separately from the PDF-and-metadata package released into each environment.
A new upload should not make the current Production version ambiguous.
A form number stays unique within the company and remains stable when the form changes.
Versions use edition year, month, and sequence—for example 202610A. The system assigns the identifier.
Each revision binds its PDF, metadata, audiences, jurisdiction coverage, and dates. Released packages are not edited in place.
An untouched QA candidate can be corrected under the permitted workflow. Reviewed or downstream content requires a new version.
Current QA, UAT, and Production may hold different revisions. Creating a QA candidate does not silently replace Production.
Preserve history while controlling future use. Retirement is governed; ordinary maintenance is not a hard-delete shortcut.
Core product fields remain distinct from company-defined metadata.
Audiences remain separate and may be combined when appropriate. Custom categories do not automatically grant permission.
Maintain explicit state and District of Columbia coverage, with a defined all-supported-jurisdictions selection.
Effective and retirement dates describe applicability; the release timestamp records when a package is published.
The V2 local demo exercises validation and remediation. Production scanner, renderer, and storage qualification is still pending.
Intake tracks file identity, structure, size, and checks before accepting a file for a form revision.
Blocking findings, warnings, ownership, and supported retry or replacement paths explain what needs attention.
Automated accessibility diagnostics highlight potential issues. They are not accessibility certification or a replacement for expert review.