Resources/Core concepts/Documents

Documents

Document: a file on a record. Every document keeps its version and its timestamp. Each document is either restricted or not.

Applies to everyone with a login
Updated 2026-09-08

A document is a file on a record: a bond form, a release letter, a certificate, a contract, a permit. Every document keeps its version and its timestamp. A drop cannot exceed 250 MB. Every document is either restricted or not. Documents is the screen that shows all of them across your portfolio, by project.

Every document belongs to a record

You do not upload to a folder. You upload to a bond, a certificate, a project, or a huddle, and the document shows on that record’s Documents tab. Documents, the page, is the view across all of them: grouped by project, filtered by category. Bond documents, contracts, compliance documents, insurance documents, other.

Every version stays

Uploading a newer version of a document does not replace the old one. Both stay, each with who uploaded it and when. When an auditor, a surety, or a claims adjuster asks what was on file on a given date, the answer is the version history, not someone’s memory of which attachment was current.

When you can use a file

When you upload a file, we mark it Clean right away. A file that arrives by email stays Pending until you or a teammate accept it, and then we mark it Clean. You can submit a file for review, or record it as executed, only once it is Clean.

A document is restricted or it is not

Two choices, not four. Not restricted means anyone who can see the record can see the document. Restricted means only people on a team that grants restricted access can open it. Financial statements are the usual case; see Financial vault. Files on a huddle use Public, Internal, or Restricted. That choice lives on the huddle; see Huddles.

We read a document when you upload it

Upload document opens one wizard with one file. As soon as the file lands, we register it and read it, the same way we read a forwarded email. Below the drop target you see a processed card with what we found: which project, which bond, what kind of document, what event it records. We check each item for you. Uncheck anything that is wrong. The second step asks only for what we could not read: tags, a description, restricted or not, and the project and bond if we did not recognize them. The third step is review, then save.

Our guesses on this screen are marked for review until the upload path earns its own precision bar. We do not carry the email surface’s confidence over to a different kind of input.

You work with documents on these screens

ScreenWhat it showsState today
DocumentsEvery document across your portfolio, grouped by project, filtered by category. Upload document in the header. Recent uploads in the sidebar when there are any.Live.
Record → Documents tabThe documents on one bond, certificate, project, or huddle, with versions.Live.
Home → Document processingDocuments that arrived by email, and what we propose to do with them.Live.
Upload document wizardOne file, read on arrival, then the fields we could not read, then review.Specified; in build. Today’s upload registers the file without the reading step.
Financial vaultYour company’s financial documents. A separate place with its own access rules, not the project document list.Live.

We use these terms

Version
One upload of a document. Older versions stay on the record.
Restricted
Visible only to people on a team that grants restricted access.
250 MB
The largest file a Documents drop will take.
Category
Bond document, contract, compliance document, insurance document, or other.
Pending, Clean
Pending: a file that arrived by email and that no one on your team has accepted yet. Clean: a file you uploaded or accepted. You can move a record forward only with a Clean file.
Timeline entry
The dated line we write on the record when a person uploads a document or changes a status.

Product pages that build on this concept: Keep every bond's history · Forward a bond email