Construction document control comes down to two decisions and one habit. Every file follows one naming convention. Every file lives in one place per job. One person checks both, every week. A builder running 5 to 40 jobs does not need a document controller or a document management system to get there. Most file chaos is not a software failure. It is a decision nobody made — and every tool bought since has been trying to make it for you.
The decision nobody made
Documents arrive on a typical job like this. The signed contract is a PDF in the owner's email. Revision C of the drawings came from the architect as a download link that expires in 14 days. The electrician's submittal is an attachment called scan0042.pdf. Three change orders were approved by text. The superintendent has 400 photos on his phone, named by the phone.
None of that is a storage problem. Every one of those files could be stored somewhere. The problem is that nobody decided what each file is called or where it goes, so each person files it wherever is closest — their inbox, their desktop, a shared drive folder called Misc. When the file is needed six months later, finding it depends on remembering who touched it.
Buying software at this point moves the mess somewhere more expensive. A platform with folders, permissions and version history still needs someone to have decided what the folders are and what goes in them. Without that, it becomes a nicer-looking Misc folder.
Rule one: a file name that sorts itself
A naming convention does one job. It lets anyone find a file by reading the list, without opening anything. It needs four parts, always in the same order, separated by underscores.
- Job number — first, so a file dragged out of its folder still says which job it belongs to. 2417, not 'Henderson kitchen'.
- Document type code — from a short, fixed list: CON for contract, DWG for drawings, SUB for submittals, RFI, CO for change orders, LOG for daily logs, INV for invoices, LW for lien waivers, WAR for warranties.
- Sequence or revision — the RFI number, the change order number or the drawing revision letter. RFI_014, CO_006, DWG_RevC.
- Date in year-month-day — 2025-03-12. It is the only date format that sorts correctly by name.
Put together: 2417_CO_006_2025-03-12_signed.pdf. Anyone in the office, on site or at the owner's lawyer's office can read that without asking a question.
Three words are banned from file names: final, new and latest. Every builder has a folder holding Contract_FINAL.pdf, Contract_FINAL_v2.pdf and Contract_FINAL_revised_USE THIS.pdf. Those words describe how someone felt when they saved the file. Revision letters and dates describe the file. A status suffix is allowed only from a fixed list — draft, sent, signed — and nothing else.
Keep the type list short. Nine codes cover most residential and light commercial work. A list of 40 codes means people guess, and a guessed code is as unfindable as no code at all.
Rule two: one place per job, and only one
Every job gets the same folder structure, copied from a template the day the contract is signed. Numbered prefixes keep the folders in the same order on every screen, so a file is in the same spot on job 2417 as on job 2502.
- 01 Contract — signed contract, scope, allowances, insurance certificates
- 02 Drawings and Specs — current set only, with a Superseded subfolder
- 03 Submittals — product data and approvals, grouped by trade
- 04 RFIs — question and answer filed together under one RFI number
- 05 Change Orders — signed copies with their pricing backup
- 06 Daily Logs and Photos
- 07 Invoices and Lien Waivers — each waiver filed beside the payment it covers
- 08 Closeout — warranties, O&M manuals, final punchlist, as-builts
Waivers sit beside payments because that pairing is what gets checked. The difference between a conditional and an unconditional waiver is covered in our post on construction lien waivers — and it only matters if the right one can be found when the payment is questioned.
The harder part of 'one place' is naming what is not the place. An inbox is not the place. A phone camera roll is not the place. A text thread is not the place. As far as the job record is concerned, a document that only exists in one of those has not been received. The rule that makes this stick: an approval by email or text is not approved until it is saved as a named file in the job folder. That sounds bureaucratic until a homeowner disputes a $4,800 change order and the only approval is a thumbs-up on a phone the superintendent has since replaced.
The drawing set is where the money goes
Most misfiled documents cost time. One kind costs money: a superseded drawing still in circulation. A framer who builds to Revision B after Revision C moved a wall produces a rework bill, and the argument about who pays it starts with which set was issued to whom, and when.
When a new revision arrives, three things happen the same day. The old set moves to the Superseded folder. The new set is renamed with its revision letter and date. Printed sets on site are pulled and replaced. If the field works from tablets, the old file is moved, not left beside the new one — two revisions sitting in the same folder is how the wrong one gets opened.
Keep a one-line record of each issue: revision, date received, date sent to each sub. That line is what answers whether the framer had Revision C. Rework and delay disputes turn on records made at the time, not records reconstructed afterwards from memory and email searches.
Enforcement is a person, not a feature
A naming convention that is written down and not enforced lasts until the first busy week. Somebody has to own it. Not a role called document controller — a named person who already handles contracts and RFIs, usually an office manager or project coordinator, with 20 minutes a week on the calendar for it. The check is short:
- Anything in the shared inbox older than two days that belongs in a job folder
- Files that break the convention — rename them, then tell whoever saved them
- Change orders shown as approved in the budget or schedule with no signed file in 05
- Exactly one current drawing set per job, with older revisions in Superseded
- Field photos uploaded and filed to the right job
Telling the person who saved the file is not about blame. Conventions survive when the correction is fast and boring. They die when nobody notices for a month and the fix becomes a weekend project.
If nobody in the office has 20 minutes a week, that is the real finding. It usually means the back office is already short, and document control is the first thing dropped because nothing breaks the day it is skipped. What that shortfall costs beyond salary is laid out in what a construction back office really costs.
What software does once the decision is made
Once names and places are decided, software earns its place. Before that, it mostly stores disorder with better search. Here is the split, stated plainly:
- Software does: keep files attached to the job record, not to a folder somebody has to remember to open.
- Software does: hold a change order, its approval and its audit trail in one record, so the signed version is not a separate hunt.
- Software does: show the client the documents meant for them through a portal, which ends most 'can you resend the contract' emails.
- Software does not: choose your type codes, your folder template or who runs the weekly check.
- Software does not: fix a habit. If people keep saving scan0042.pdf, a person still has to rename it or the convention erodes.
BuilderSolve's file management keeps documents with the job alongside daily logs, change orders and the client portal, so the job folder and the job record are the same thing. Invoices and payments stay in QuickBooks as the book of record; the job holds the signed paper behind them. None of it chooses your naming convention. That is still a decision, and it is still yours.
What to do this week
- Write the type code list — nine codes or fewer, on one page.
- Write the naming order: job number, type, sequence or revision, date. Pin one real example where everyone can see it.
- Build the folder template once and copy it for every new job.
- Bring the two active jobs with the most open change orders into the convention first — those are the files most likely to be argued over.
- Name the person who owns the weekly check and put the 20 minutes on their calendar.
- Leave closed jobs alone unless a warranty claim or dispute pulls one back.
Active jobs can be brought into line over a couple of weeks; old jobs rarely repay the effort. If nobody in the office has the hours, BuilderSolve's back-office services team handles contracts, RFIs and change order paperwork as part of operations and admin, and can own the filing rule along with the documents it covers.
Common questions
what is document control in construction
Document control in construction is the system that decides what every project file is called, where it is kept and who keeps it current. For a small builder that means a fixed naming convention, one folder structure per job and a named person who checks both weekly. It covers contracts, drawings, submittals, RFIs, change orders, daily logs, invoices, lien waivers and closeout documents.
do I need a document controller for a small construction company
No. A builder running 5 to 40 jobs needs the function, not the title. An office manager or project coordinator who already handles contracts and RFIs can own document control in about 20 minutes a week, provided the naming convention and folder template are written down first. Without those decisions, even a full-time controller would spend their days renaming files.
best file naming convention for construction documents
Use job number, document type code, sequence or revision, then date in year-month-day order, separated by underscores — for example 2417_RFI_014_2025-03-12. Job number first keeps a stray file traceable. Year-month-day is the only date format that sorts correctly by name. Avoid words like final, new and latest, which describe a mood rather than a version.
how to manage drawing revisions on a construction project
Keep exactly one current set per job and move every older revision into a Superseded folder the day a new one arrives. Rename the new set with its revision letter and date, pull printed sets from site and log when each sub received it. That log is what settles a rework dispute about which revision a trade built to.
can construction software handle document control for me
Software can hold files against the job, track change order approvals and share documents with clients, but it cannot decide your naming convention or folder structure. Those decisions come first. Without them, a platform becomes a better-looking version of the shared drive's Misc folder. Someone still has to rename badly named scans and check the folders every week.