A naming convention is not about being tidy. It is about a tired person trusting that the newest file sorts to a place they can find, and that Final_v3_USE_THIS.pdf never becomes the unofficial current set.

The rule below is a practical starting point, not “the industry standard.” Paste it into a one-page README in the root of every new job folder, next to the current-set rule and the list of who may replace drawings. If the team will not follow a more complicated scheme, use this one and stay with it.

The pattern

Use this pattern for files you control:

YYYY-MM-DD_Job_DocType_Number_ShortDescription_Rev

  • Date first, in year-month-day order, so files sort in order on a phone, a laptop, and a shared drive. 2026-06-14 comes after 2026-06-12. A date like 6-14-26 or 14 June will not sort reliably.
  • Job is a short job number or code you already use, such as 245. Keep it consistent for the whole project.
  • DocType is a short, repeatable label: DWG, RFI, SUB, ASI, CCD, CO, PHOTO, TRN, PAY, DLY, MTG, SPEC. Pick a list, put it in the README, and do not invent a new abbreviation every week.
  • Number is the official number when there is one: sheet A201, RFI 017, submittal 048.
  • ShortDescription is a few words a superintendent can read in the sun: SlabSleeves, FloorPlan, FloorDrains. No novels. No all-caps shouting.
  • Rev is the revision, status, or version when it matters: Rev4, Response, AAN (approved as noted), R&R (revise and resubmit).

Examples you can paste under the rule:

  • 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-06-18_245_ASI_004_DoorHardware.pdf
  • 2026-07-02_245_PHOTO_GridB3_SleevesBeforePour.jpg
  • 2026-07-08_245_TRN_ArchitecturalSet_Rev4.pdf
  • 2026-07-31_245_PAY_App03_July.pdf

If a file has no official number, skip that part rather than inventing one. 2026-07-02_245_PHOTO_GridB3_SleevesBeforePour.jpg is fine.

What to do with the names other people send you

Designers, subs, and vendors will not follow your scheme, and you should not spend the job policing their inboxes. The habit is simple: when you file the official copy into the job folder, you rename it.

If the architect sends A201_Floor_Plan_Rev 4 FINAL (1).pdf, it becomes 2026-06-14_245_DWG_A201_FloorPlan_Rev4.pdf in 02_Drawings_Current. If you need to prove what arrived, keep the original name in the transmittal note, or keep the original email in 15_Correspondence. Do not keep both FINAL and Rev4 in the current folder and hope people guess.

The same goes for photos from a phone (IMG_4588.jpg), submittals named shop drawings latest.pdf, and pay-app packets called scan.pdf. Rename on the way in. Dates first.

Do not rename a file in a way that overwrites the official current PDF with a markup. A field markup is a new file, with a description like Markup or FieldNote, stored in the right folder, not a silent save over Rev4.

Make the rule short enough to survive a busy week

A convention dies when it gets too precious. If someone forgets the job number or shortens a description, that is fixable. What is not fixable is a folder full of final, final2, use this, and copy of copy.

A few standing rules are enough:

  1. Dates first, year-month-day.
  2. Rename when you file, not six weeks later.
  3. One current file for a given sheet or document in 02_Drawings_Current. The rest go to Superseded, named as they were when they were current.
  4. No Misc folder as a way around the rule.
  5. The README in the root is the official version of this convention. New people should be able to join the job and name a file without a meeting.

Put this same one-pager in every new job so you are not inventing a system in week three. The job folder template (Job Folder Template for Google Drive or Dropbox) includes a README you can copy.

If you want the next project to start with the folders, the naming rule, and the logs already in place, I can set that file up, run it on a retainer, or prepare closeout when the time comes. 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