Project management

How to set up project folders for every job

Set up project folders by creating one numbered template folder structure, copying it for every new job with a consistent job number and name, setting simple file naming rules, and assigning who files each type of document.

Two construction professionals review paper plans beside a tablet at a jobsite workbench.
Plan reviews connect field conditions, drawings, and the next decisions on a job. AI-generated illustration.

The best way to set up construction project folders is to build one template and copy it for every job. Give each job a folder named with the job number and a short name, such as 2617 Lakeside Dental. Inside, use numbered top-level folders in the same order on every job: contract, estimate, budget and cost, schedule, drawings and specs, RFIs, submittals, changes, billing, subcontractors, field reports, safety, meetings, photos, and closeout. Add a short file naming rule and decide who files what. When every job looks the same, anyone in the office can find the signed change order on any job in seconds, and nothing gets lost when a PM leaves.

Why a standard folder structure matters

Without a standard, each PM invents a system. One files change orders under Contract, another under Billing, a third leaves them in email. That works until someone is out sick, an owner asks for every approved change in a hurry, or a dispute two years later needs the daily logs from one week in March. Standard folders are also the first step toward any software, because a company that cannot agree where a document goes will not agree how to set up an app either.

A project folder template you can copy

Sample project folder structure (adjust to your company)
FolderWhat goes in itWho files it
01 ContractSigned contract, proposal, insurance and bond docs, notice to proceedPM
02 EstimateFinal estimate, quotes, bid leveling, clarificationsEstimator
03 Budget and CostBudget, job cost reports, committed costs, POsPM and accounting
04 ScheduleBaseline, updates, look-aheadsPM or scheduler
05 Drawings and SpecsBid set, IFC set, current set, superseded (archived), drawing logProject engineer
06 RFIsRFI log, one subfolder or file per RFI with answerProject engineer
07 SubmittalsRegister, transmittals, approved submittals by spec sectionProject engineer
08 ChangesChange order log, requests, pricing backup, signed change ordersPM
09 BillingPay apps, schedule of values, lien waivers, retainageAccounting and PM
10 SubcontractorsOne subfolder per sub: subcontract, COI, scope, change orders, waiversPM and admin
11 Field ReportsDaily logs, inspection reports, test resultsSuperintendent
12 SafetySite safety plan, toolbox talk sign-ins, incident reportsSuperintendent
13 MeetingsAgendas and minutes, numbered by meetingPM
14 PhotosSubfolders by date, then by area if neededSuperintendent
15 CloseoutPunch lists, warranties, O&M manuals, as-builts, final waiversPM

How to set it up in 6 steps

  1. Agree on the structure once. Get the owner, PMs, supers, and the bookkeeper in a room for an hour. Start from the table above and change it to fit how you work. Keep the list short enough to remember.
  2. Create a blank template folder. Save it somewhere nobody files real documents. Copy it for each new job; never build folders by hand.
  3. Use a consistent job number. Pick a format, such as year plus sequence (2617 for the 17th job of 2026), and use it in the folder name, accounting system, and file names.
  4. Set file naming rules. Job number, document type, number or description, date in a sortable format. Example: 2617_CO-004_Added-data-outlets_2026-03-14.pdf.
  5. Assign who files what. The right-hand column of the table is the rule. If a document type has no owner, it ends up in someone's downloads folder.
  6. Audit monthly and at closeout. Ten minutes per job: is the latest pay app there, are change orders signed and filed, are subs' COIs current. Fix gaps while they are small.

File naming rules that hold up

  • Start with the job number. Files moved or emailed outside the folder still say which job they belong to.
  • Write dates as year-month-day. 2026-03-14 sorts correctly. 3-14-26 does not.
  • Use document numbers. RFI-031, CO-004, SUB-07A. The number ties the file to the log.
  • Avoid FINAL and NEW. Every file eventually becomes not final. Use revision numbers instead: R0, R1, R2.
  • Keep it readable. Short descriptions with hyphens beat long sentences with spaces and symbols.

Worked example: finding a change order in 30 seconds

Here is an example. A general contractor runs 12 jobs a year. Eighteen months after closing a $720,000 office remodel, the owner disputes a $6,400 invoice for added electrical work and says it was never approved.

With a standard structure, the office manager opens 2617 Lakeside Dental, then 08 Changes, finds CO-004 in the log, and opens 2617_CO-004_Added-data-outlets_2026-03-14.pdf with the owner's signature. She checks 13 Meetings for the minutes where the change was discussed and 11 Field Reports for the daily log showing the work. The packet goes to the owner the same morning.

Without one, the PM who ran the job has left the company. The office spends two days searching email, a shared drive, and a box of paper. They find an unsigned version. The $6,400 becomes a negotiation.

Subcontractor subfolders

The subcontractors folder deserves extra structure because it is where compliance problems hide. Give each sub its own subfolder named with a short code and company name, such as SUB-07 Ace Electric. Inside, keep the signed subcontract and scope, the current certificate of insurance with its expiration date in the file name, change orders, pay applications, and lien waivers matched to each payment. When an insurance certificate expires mid-job, the expired one stays in place and the new one is added beside it, so the record shows coverage was in force on every date. That one habit makes audits and claims far easier. For more on keeping COIs current, see how to track subcontractor insurance certificates.

Photos that stay findable

Photos are the fastest-growing folder on any job and the hardest to search. Sort them into dated subfolders (2026-03-14) and, on larger jobs, by area within each date. Ask the superintendent to rename key photos with a few words, such as the RFI or change number they support, so they can be found without scrolling through hundreds of thumbnails.

Mistakes to avoid

  • Too many folders. Fifty subfolders means people stop filing. Fifteen or so is usually enough at the top level.
  • Email as the filing system. Save signed documents and decisions to the job folder the day they arrive.
  • Mixing current and superseded drawings. Keep an archive subfolder for superseded sheets, as described in how to manage construction documents and drawings.
  • Changing the structure job to job. Improvements go into the template, not one job.
  • No retention rule. Decide how long closed job folders are kept. See construction document retention.

Templates, terms, and tools

Many of the documents that fill these folders have templates: the change order log template, RFI log template, submittal log template, and construction daily report template. Related terms: document control, audit trail, and drawing log.

Smart Business Automator creates a standard record for every job from the accepted estimate, so contracts, changes, RFIs, logs, and invoices land in the same place on every project. See construction workflow automation.

Frequently asked questions

What folders should a construction project have?

Common top-level folders are contract, estimate, budget and cost, schedule, drawings and specs, RFIs, submittals, changes, billing, subcontractors, field reports, safety, meetings, photos, and closeout. Adjust to how your company works, then use the same set on every job.

Should project folders be numbered?

Numbering the top-level folders (01, 02, 03) keeps them in the same order on every job and screen, which makes them faster to scan.

What is a good file naming convention for construction?

Job number, document type and number, a short description, and a year-month-day date, separated by underscores or hyphens. Use revision numbers instead of words like final.

Where should project folders be stored?

In a shared location everyone on the job can reach, with backups and access controls, such as a company cloud drive or your project management software. Avoid personal laptops and email as the primary store.

Written and edited by

Maurice Francois writes and edits construction operations guides for Smart Business Automator. More from Maurice on the Scaling Legends podcast.

Get a free assessment