A naming convention is not about being tidy for its own sake. It is about being able to find the right PDF at 4 p.m. on a Friday, or at 4 a.m. before a pour, without opening six files named Final_v3_USE_THIS.pdf.

You already know how this goes wrong. A designer sends a revision with a generic name. Someone saves it next to the last one. A sub forwards a copy with "new" in the filename. By the next week, the job folder is a pile of near-identical names, and the current set is whichever one somebody guessed.

The pattern

Use this pattern, and paste it into a one-page README at the root of every job folder:

YYYY-MM-DD_Job_DocType_Number_ShortDescription_Rev

Examples:

  • 2026-06-12_245_RFI_017_SlabSleeves_Response.pdf
  • 2026-06-14_245_DWG_A201_FloorPlan_Rev4.pdf
  • 2026-06-18_245_SUB_Plumbing_FloorDrains_AAN.pdf
  • 2026-07-02_245_PHOTO_GridB3_SleevesBeforePour.jpg
  • 2026-07-15_245_CO_003_AddedSleeves_Executed.pdf

Dates first, in year-month-day order, so the newest file sorts to a place a tired person can trust. The short job number keeps two projects from mixing when someone downloads a file to a phone. The document type and number tell you what you are looking at before you open it. The short description is for humans. The revision or status (Rev4, Response, AAN for approved as noted) keeps two versions from looking like twins.

Keep descriptions short. Do not try to retell the whole document in the filename. If a designer sends Final_v3_USE_THIS.pdf, rename it when you file it. Leave the original name in a transmittal note if you need to prove what arrived.

A few habits make the pattern survive a busy week:

  • Name the file the day it arrives, not in a Friday cleanup that never happens.
  • Use the same abbreviations every time: RFI, SUB, DWG, ASI, CCD, CO, PHOTO, TRN, PAY. A README with that list is enough.
  • Do not put spaces or special characters that break on a phone. Underscores are enough.
  • If you get a revised sheet, the new date and the new revision go in the new name, and the old file moves to Superseded instead of being overwritten.

The miss this prevents

The pattern is familiar.

Two versions of the same floor plan sit in the drawings folder. One is named A201_floor_plan.pdf. The other is A201_floor_plan_updated.pdf. A superintendent, working off a phone in the sun, opens the one that looks familiar. A crew lays out to that sheet. The "updated" file was the official revision. The layout is wrong, and you find out when someone compares stamps, or when an inspector does.

The trouble was a pair of names that did not sort, carried no date, and did not tell you which one was current.

How to run it in the job file

The convention only works if it lives in the same folder structure as the current set. Put the README in the root of the Google Drive or Dropbox job folder, next to folders like 02_Drawings_Current, 05_RFIs, and 06_Submittals. New people should be able to join the job and name a file without a meeting.

You do not need a special program to rename a PDF. You need agreement, and one person willing to rename a bad file instead of leaving it. Most of the team can add photos and dailies. Only a short list should be able to replace drawings in the current-set folder, named or not.

Used carefully, an AI tool can suggest a filename or help you search a messy folder. A person still checks that the date, the number, and the revision match the source PDF. Do not let a chatbot rename the current set in bulk without a review.

I put this same pattern, with a full folder tree, in "A Procore-Level Job File With Google Drive (or Dropbox) and a Spreadsheet."

If the old names are already a mess

You do not have to rename every historic file on a job that is already moving. Start the convention on the next official drawing, the next RFI, and the next photo that matters. If a current sheet has a dangerous name, rename that one now and move the older copy to Superseded.

If you want help, I can set up the job file and the naming rule, run document control on a retainer, or prepare closeout. I can also look at a current folder and tell you which names are putting the field at risk.

The files stay yours.

If you want help, not just a checklist

Some jobs run fine on a clean file and a superintendent who gives the log fifteen minutes twice a week. Others do not: revisions are moving fast, closeout is already behind, or the field simply has no hours left for paperwork.

That is where I come in. I set up the job file, run the logs on a retainer, or prepare closeout before the scramble starts. Your files stay yours, and there is no software contract to sign.

Email travis@builtonrecord.com Get the free Job File Kit