One Folder Per Job: A Document Filing System for Small Builders
Create a practical job-folder system with stable IDs, accepted document versions, field evidence, access controls, backups, and deliberate closeout.

Imagine preparing a final invoice when the signed contract is in email, the approved window selection is on a phone, and the superintendent's photographs are on another device. Everyone remembers the change, but nobody can assemble its full record.
A one-folder-per-job system gives each project a stable identity, an index, and a consistent place for issued documents, approvals, photographs, and closeout records. Create records such as the construction contract and daily report in Documentorium, then retain them in your chosen project filing system. Preserve authoritative versions and limit access to the people who need it.
Give the job an identity that stays put
Assign a stable ID, such as JB-02418, and use it on the intake, construction estimate, agreement, field records, purchases, and invoices.
Create a short index showing the customer, site, responsible staff, controlling contract, current drawing set, open decisions, and links to authoritative systems. The index should point to the signed agreement rather than become a second, conflicting contract summary.
Choose a manageable folder structure:
JB-02418/
01-estimate-contract/
02-plans-selections-permits/
03-purchases-deliveries/
04-field-logs-photos/
05-changes-decisions/
06-invoices-payments/
07-tests-closeout-warranties/
Sensitive finance, personnel, claims, and legal records may belong in separate restricted systems. Their relationship to the job can remain in the index without exposing their contents to the crew.
Preserve the version people actually used
Keep the complete accepted package: agreement, scope, drawings, terms, notices, attachments, and approval evidence. Do not preserve only the signature page.
Use filenames that identify document, revision, and status—for example, JB-02418_CO-003_rev-1_approved.pdf. A revision tells you which content; a status tells you whether it may be used. “Final2” tells you neither reliably. For estimates sent through several versions, use the estimate-revision guide to record the changes and connect acceptance to the right packet.
Keep issued and accepted copies intact. Later corrections should be dated amendments or new revisions with links to the earlier record. Withdraw superseded field copies from active use while preserving the history.
A change order should link request, evidence, price and time effect, approval, and released field work. The change-order guide explains why a price request and approved work need different statuses.
Capture decisions before they vanish
Set a daily capture habit for material texts, emails, field notes, photographs, inspection results, and delivery records. Preserve enough context to identify the sender, job, decision, and attachments. Convert the decision into whatever controlled approval the contract requires.
Use the daily report to record actual work and exceptions; the daily-report guide explains useful evidence. Label photographs by location and event rather than relying on camera-roll order.
Connect purchasing to received material and the vendor invoice. Connect customer billing to the contract or approved change and milestone evidence. IRS Publication 583 explains supporting business records; a payment entry alone may not explain the purchase or establish its tax treatment.
Control access and prove recovery
The FTC's personal-information guide recommends identifying sensitive information, limiting what is kept, protecting it, and disposing of it securely when appropriate.
Use individual accounts, access based on role, and prompt removal of access when a worker or subcontractor leaves. Keep bank details, identification numbers, medical information, passwords, and access codes out of the general project folder. Create a customer handoff copy instead of sharing the internal root folder.
NIST's small-business cybersecurity guide is voluntary guidance addressing protection and recovery, including backups and restoration tests. Check that recovery copies survive unwanted deletion or corruption in the working folder. Test restoration of an actual closed-job package, including readable PDFs, photographs, and necessary exports from linked systems.
Close and retain the record deliberately
At handoff, reconcile approved scope, open changes, inspections, tests, punch items, payments, manuals, and warranties. Use a completion signoff that states remaining exceptions. The cleanup and closeout guide helps document the final field condition.
Set retention by record class and applicable obligations. IRS retention guidance expressly distinguishes record types and warns that non-tax needs may last longer. A single tax period is not a deletion rule for every contract, warranty, claim, or safety record.
Preserve records subject to a claim or legal hold through the authorized process. Dispose of sensitive material only when all applicable obligations permit it. Add later warranty work as a linked record without rewriting the historical job.
Sources
The linked IRS, FTC, and NIST sources were reviewed October 30, 2026.
Common questions
Does every file need to be physically in one folder?
No. The job index can link to authoritative systems. Preserve necessary exports and recovery access when those links may later disappear.
Can the whole crew share one account?
Use individual, role-appropriate access so permissions and activity remain accountable.
How long should a closed job be kept?
Use a record-specific retention policy covering applicable legal, contractual, tax, warranty, insurance, and hold requirements. There is no universal period for the whole folder.