Keep a record that holds up
Numbered, versioned, and acknowledged. When the job gets contentious, Formis is the record that says who had what, and when.
The dispute never starts with the drawings. It starts with the record
Six months in, someone says they never got the revision. The transmittal log is a spreadsheet three people edited. The "latest" set has two candidates. Now you're reconstructing history from your inbox, and the clock is running.
Source: PlanGrid / FMI, Construction Disconnected
One controlled register
Every controlled document gets a number and a revision lineage you can follow back. Revisions supersede cleanly, and a controlled number is never quietly reused.
Proof of receipt
Send a package, track exactly who opened and acknowledged it, and close it out when your policy is met. The acknowledgment trail is the record you reach for when a claim lands.
Fewer rejections
Formis AI Pre-Submission Insight checks a submittal for completeness against the project's own documents before it goes out, so it comes back approved instead of returned.
Number it, classify it, control it, your way
Document control is not one-size-fits-all. Formis lets you define how the register works, then does the sorting for you.
Define your own numbering
Set the document numbering schema your organization actually uses. Document categories, document types, and custom fields are all yours to define, so the register matches your standard instead of forcing a new one on you.
Auto-classification does the sorting
Formis AI reads incoming documents and classifies them by type, discipline, and number, filing them to the register automatically. It front-loads the heavy tagging at kickoff and keeps the record clean as the job runs. A first pass you can always adjust.