The goal isn't a perfect archive — it's a findable one
Document organization fails one of two ways: either nothing is organized and finding anything takes twenty minutes of searching, or the system is so elaborate that maintaining it becomes its own job nobody has time for. The right system for a small contractor sits in between — simple enough to actually maintain, structured enough that anyone on the team can find what they need without asking.
The test for whether a system works: can someone who wasn't part of the original conversation find the current contract, the latest drawing, and the change order log for a specific project in under two minutes? If not, the system needs simplifying or better naming, not necessarily more categories.
The five document types that need a home
Almost every residential or light-commercial project generates the same core document types, and each needs a clear, consistent place to live: the signed contract or proposal, drawings and site plans, change orders, field records (daily notes, photos, pre-dig reports), and closeout documents (final invoice, warranty information).
- Signed contract or proposal — the scope baseline for the whole project
- Drawings and site plans — see [how to organize construction drawings](/blog/how-to-organize-construction-drawings) for version-control specifics
- Change orders — see [how to track change orders](/blog/how-to-track-change-orders) for the full process
- Field records — daily notes, photos, and reports like a [crew-ready pre-dig report](/blog/how-to-create-a-crew-ready-pre-dig-report)
- Closeout documents — final invoice, warranty terms, as-built notes
A simple structure that scales from one job to many
- 1
One folder per project
Named consistently — client name and address, not a job number only office staff can decode.
- 2
Five subfolders inside
Contract, Drawings, Change Orders, Field Records, Closeout — the same five every time.
- 3
One current version per document
Superseded versions moved to an archive subfolder, not deleted and not left sitting alongside the current one.
- 4
One owner per project
A single person responsible for keeping the folder current, even on a two-person crew.
Where SiteBuildHub fits into this system
SiteBuildHub's project drafts and Reports feature are built to keep drawings, notes, and field records connected to one project record rather than scattered across a folder structure that depends on someone remembering to file things correctly. For contractors who want the document structure above without building and maintaining it manually in a generic cloud folder, that's the specific gap it fills — the contract and closeout paperwork can still live in a standard folder, while drawings and field notes stay connected to the same project record they were created from.
Common mistakes
- Inventing a new folder structure for every project instead of reusing one consistent template
- Leaving superseded drawings or contracts in the same folder as the current version
- Not assigning a single owner, so document upkeep quietly becomes no one's job
- Storing field photos separately from the project record they document, disconnected from context
A worked example
A two-person renovation crew keeps one project folder per client, named "LastName-Address," with the same five subfolders on every job. When a change order comes up mid-project, it goes straight into the Change Orders subfolder with a sequential number, referencing the original contract. When the job closes out, the final invoice and warranty letter go into Closeout, and the whole folder gets archived as a unit rather than scattered across whoever happened to generate each document.
Six months later, when the client calls with a warranty question, finding the original contract, the drawing that was approved, and the closeout warranty terms takes under two minutes — because the structure was the same on this job as on every other one, not reinvented each time.