Every file lands
where the work is
Plans, specs, receipts and contracts filed against the record they belong to — the estimate, the invoice, the task, the project. Upload from a record and it lands in the project library too, so there's no version of this where the file is only in one person's downloads folder.
Trusted by the studios doing the work
The folder structure builds itself
You don't invent a naming convention and then police it. A document uploaded against an estimate lives with estimates; one attached to a task lives with tasks. The library organizes around the work rather than around whoever happened to save the file.
Add your own folders on top with a name and a description — the automatic structure is a floor, not a cage.
The checkbox that stops the second copy
Attach a document while you're looking at an estimate, tick one box, and it also lands in that project's document section. One upload, filed in both places, with no duplicate to go stale.
- Upload from the estimate, invoice, or task you're already looking at
- Name it something a human will recognize later, not scan_004.pdf
- Tick the box and the project library gets it too
- Documents shared into a channel can be pushed through the same way
Six months later is the real test
Look at everything, or narrow to one job's documents in a single step.
The PDF from around March, bigger than a scan — that's usually enough to find it.
See what's gone out, and put finished work away without deleting it.
Thumbnails when you're looking for a drawing; a list when you're looking for a name.
The drawing you need is the one you can find
A document is never just a file
Sits on the estimate
The revision the client signed stays attached to the estimate it belongs to, so nobody has to work out which version went out.
Proves the bill
A contractor's own invoice stays on the bill, so whoever approves the payment is reading the document rather than someone's retyping of it.
Travels with the task
Drawings and site photos attached to the task the trade is actually doing, rather than in a folder they'd have to be told about.
Collects from conversations
Anything shared in a channel gathers in that channel's files, and can be pushed through into the project library.
Shares with a link you can revoke
Send a document out and the link is listed with everything else you've shared — reachable, and closeable.
Reaches the client portal
What the client should see appears in their portal, and what they shouldn't simply doesn't.
Nobody has ever found a file called scan_002.pdf
Every studio has a shared drive full of final_v3, IMG_4471 and scan_002. The naming convention exists — it is written down somewhere — and it survives exactly as long as the week is calm.
Set the template once per upload context and Workroom renames files as they attach. Tokens it can resolve from the document fill themselves; tokens it cannot, like an order number, prompt the person uploading. The convention stops depending on anybody remembering it.
- A template per context — invoice, estimate, PO, general upload
- Tokens resolved from the document, or prompted for
- Live preview of the filename before you save
- Turn it off and original filenames are kept
Preview: 2026-08-03_Smith_INV-0042.ext
Purchase order attachmentsPreview: 2026-08-03_AcmeCo_PO-0042.ext
Documents, specifically answered
Does this replace Dropbox or Google Drive?
For project documents, that's the intention — the point is that the file sits on the record it belongs to rather than in a parallel folder tree someone has to maintain. Large archives of unrelated material are still better off where they are.
What happens if I upload the same file twice?
Ticking "add to project documents" files one upload in two places rather than creating a duplicate, which is the usual cause of two versions drifting apart.
Can I make my own folders?
Yes, with a name and an optional description. The automatic structure by record type is a starting point you can build on.
How much storage do we get?
25GB on Pro, 5GB on LITE, with usage shown against the limit so it isn't a surprise.
Can clients see our documents?
Only what you share. Documents reach the client portal when you put them there, and shared links are listed in link management where they can be revoked.
Run the project. See the real margin.
We'll show you a specification uploaded once and turning up everywhere it should — the estimate, the project, and the trade's task.