How to Set Up a Contractor Job Folder System That Survives a 6-Month Build
On a 6-month residential build you'll accumulate 80 to 150 documents per job. Permits, change orders, subcontractor certificates of insurance, daily logs, inspection signoffs, customer selections, progress photos, invoices, closeout docs. When the customer calls asking about that window upgrade they approved three months ago, you need to find the change order in under 60 seconds. Here's the contractor job folder system I've used on every build since 2019.
Why Your Job Folder System Matters More Than You Think
I've seen contractors lose change order money because they couldn't prove the scope in writing. I've watched permit inspections get delayed because the engineer's letter was buried in email. I've had a customer dispute an invoice because I couldn't produce the signed selections sheet.
Construction job documentation isn't about being organized for the sake of being organized. It's about protecting your money and your schedule. Every document you can't find in 60 seconds costs you time. Every missing signature costs you use when scope creep starts.
The system below works whether you're running folders on your phone, in Google Drive, or in a tool like Workhand. The structure matters more than the software.
The 9-Folder Taxonomy That Covers Every Residential Job
Every job gets the same nine top-level folders. No exceptions. This is the skeleton:
- <strong>Contracts</strong>: signed customer agreement, scope docs, payment schedules
- <strong>Permits</strong>: application, approval, engineer letters, site plans, any addenda the building department asks for
- <strong>Insurance</strong>: your COI, every sub's COI, any umbrella or bond docs the contract requires
- <strong>Change Orders</strong>: every approved scope change with customer signature and revised price
- <strong>Selections</strong>: tile choice, fixture models, paint colors, anything the customer picks
- <strong>Daily Logs</strong>: weather notes, crew on site, work completed, issues flagged
- <strong>Photos</strong>: progress shots, before/after, anything you'll need for warranty or dispute defense
- <strong>Invoices</strong>: what you billed, what you paid subs, material receipts
- <strong>Closeout</strong>: final inspection signoff, warranty docs, as-builts, lien waivers, customer handoff checklist
On a typical 6-month pool build I'll have 12 to 18 files in Permits, 20 to 30 in Change Orders, 40 to 60 in Photos, and 15 to 25 in Invoices. The folder structure stays the same whether it's a 3-month patio or a 9-month custom home addition.
Why YYYY-MM-DD File Naming Is the Only System That Scales
Name every file with the date first. Format: YYYY-MM-DD-description.pdf. Example: 2025-03-14-change-order-tile-upgrade.pdf or 2025-04-02-plumbing-rough-inspection-pass.pdf.
When you sort by name, files automatically sort by date. You can see the timeline of the job at a glance. When the customer calls asking about that inspection in early April, you don't have to remember what you named the file. You just look at April's cluster.
I used to name files things like CO tile.pdf or inspection plumbing.pdf. Then I'd have three files called CO tile.pdf and no idea which one was the final signed version. Date-first naming fixed that.
If you're tracking subcontractor insurance certificates, the naming convention looks like 2025-02-10-ABC-Plumbing-COI.pdf. One file per sub per renewal. When their coverage expires and they send you the new cert, you add a new file with the new date.
The 60-Second Retrieval Test
Here's the test: customer calls and says "Hey, what tile did we pick for the spa spillway?" You should be able to pull that selections sheet in under 60 seconds without asking them to hold while you dig through email.
If your system passes that test, it works. If it doesn't, your folder taxonomy is either too flat (everything in one folder) or too deep (folders nested four levels down with creative names you can't remember).
Nine folders is the sweet spot. Enough structure that you're not scrolling through 150 files in one list. Not so much structure that you're guessing whether the engineer's letter lives in Permits or Insurance or some folder you named Engineering Documents.
I built a tool called Workhand that bundles job documentation per job for exactly this reason. Every document, every photo, every change order lives under that job's record. When you're on a customer call you tap the job, tap the folder, done. Same taxonomy, zero hunting.
What Goes in Insurance vs. What Goes in Permits
This trips people up. The building department permit application goes in Permits. Your general liability COI that you gave the customer goes in Insurance. The structural engineer's sealed letter that the permit office required goes in Permits, even though it mentions liability.
Rule of thumb: if the building department asked for it, it's a permit doc. If an insurance carrier issued it or if it's proof of coverage, it's an insurance doc. If you're tracking COI expiration dates for subs, those all live in Insurance.
The one exception: if your contract requires the customer to carry builder's risk insurance and they send you the dec page, I file that in Contracts. It's a contract deliverable, not a permit requirement.
Digital vs. Paper and What Actually Needs to Live in the Truck
I keep digital copies of everything. Photos live on my phone, PDFs live in the app or in Google Drive, and I back up to an external drive every Sunday night.
The only paper I keep in the truck: current permit card, current signed contract, and a printout of any active change orders that aren't closed yet. Everything else is digital. If an inspector asks for the engineer's letter, I pull it up on my phone.
Paper gets wet, gets left on a tailgate, gets coffee spilled on it. Digital gets backed up. I've had one truck break-in in five years and the only thing I lost was a tape measure and a drill. All the job docs were safe.
Keep Every Job Document in One Place
Workhand organizes contracts, photos, change orders, and invoices per job so you can find anything in under 60 seconds.
See PricingFrequently asked questions
How do I organize photos when I'm taking 200 per job?
Create subfolders by phase or by date range. I do Photos/Demo, Photos/Rough, Photos/Finish. If you're taking daily progress shots, name them <code>YYYY-MM-DD-phase-description.jpg</code> so they sort chronologically.
Do I need to keep every material receipt or just invoices?
Keep both. Receipts prove you bought it, invoices prove what you charged. If you're ever audited or if a customer disputes a material charge, you want the paper trail.
What if a document fits two categories, like a change order that includes new permit drawings?
Pick the primary category and put it there. The change order is the legal doc, so it goes in Change Orders. If you need the drawing again later, you know where the change order lives and the drawing is attached.
Should I organize by job name or by customer name?
Job name. Customers sometimes refer to jobs by address or by project type, and you'll remember "the Smith pool" faster than "Smith, John."
How long do I need to keep job folders after closeout?
At least as long as your warranty period plus your state's statute of limitations for contract disputes. In Florida that's typically 5 years for written contracts. I keep digital folders forever because storage is cheap.
Can I use this folder system in Dropbox or Google Drive?
Yes. The taxonomy works in any file system. Just create the nine folders per job and name files with the date-first convention.
What happens when a subcontractor sends me 10 different versions of their COI?
Only keep the current valid one in your Insurance folder. Archive the old ones in a subfolder called Insurance/Archive if you want the history, but the active folder should only have live coverage.
Do I need separate folders for customer emails or texts?
No. If an email contains a document, save the document in the right folder with the date-first name. If a text thread includes a photo or a decision, screenshot it or save the photo and file it appropriately.