You do not need Procore to have a controlled job file. You need one place for the current drawings, a pair of logs that actually get updated, a naming rule people can follow when they are tired, and a habit of sending changes to the people who will build from them.

Under the dashboards, that is all the enterprise platforms are doing. I saw it from the document control seat at Mortenson Construction, on a mission-critical data center project, including the Procore onboarding when that job moved off Oracle Unifier. The software facilitated a process. It was never a substitute for one. Procore's Drawings, RFI, and Submittals tools exist so there is a current set, a place for open questions, and a record of approvals, and many tools can reach the same goals. On an Arizona job without a document control hire or an enterprise budget, Google Drive or Dropbox plus a spreadsheet can carry the same process, as long as you set them up on purpose.

Below is a concrete setup you can copy. It is a practical starting point, not "the industry standard," and it does not replace your contract.

The rule that makes the rest work

One current set. One date. One folder.

If a sheet is not in the current-drawings folder, do not build from it. When a new revision arrives, the new PDF goes into Current, and the old one moves into Superseded. Nobody "cleans up later." Later is how last week's set stays in the truck.

That one rule prevents the most common miss on jobs of every size: two people with two "latest" sets, and a crew installing the wrong one.

A folder structure you can duplicate

Create a shared Drive or Dropbox folder for each job, named with a short job number and name, and build this tree inside it:

00_Admin_and_Contract
01_Contacts
02_Drawings_Current
03_Drawings_Superseded
04_Specs_and_Addenda
05_RFIs
06_Submittals
07_ASIs_and_CCDs
08_Change_Orders
09_Daily_Reports
10_Photos
11_Meetings
12_Transmittals
13_Pay_Apps_and_Lien_Waivers
14_Closeout
15_Correspondence

Numbered folders stay in order on every phone and laptop. "Misc" is not on the list, because within a week it becomes a junk drawer.

A few placement rules keep the tree honest:

  • The issued-for-construction set, and every later official revision, lives in 02_Drawings_Current as a complete current set, or as clearly named current sheets. Everything those replace goes to 03_Drawings_Superseded. Do not leave both versions in Current.
  • RFIs that change the work also get a copy, or a combined "binding RFIs" packet, next to the current set, so the field is not hunting through 05_RFIs in the sun.
  • Addenda belong with the specs, not loose in email. After bid day, what governs is the contract set plus the addenda, and those should sit together.
  • Closeout starts empty on day one. Warranties, O&Ms, as-builts, extra-stock records, and test reports go in when they appear, not in the last month.
  • Pay applications, lien waivers, and backup go in 13 as a dated packet each month. This is a filing habit, not legal advice. In Arizona, preliminary notices and prompt-pay clocks have their own rules; keep the documents and the dates where you can find them, and talk to a construction attorney when the dollars matter. If your job is outside Arizona, your state’s rules differ, so check them.

Put a one-page "README" text file in the root that states the current-set rule, the naming convention below, and who is allowed to replace drawings. Someone new should be able to join the job and understand the file without a meeting.

A naming convention that sorts itself

Use this pattern, and paste it into the README:

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

Dates first, in year-month-day order, so the newest file sorts to a place a tired person can trust. Keep descriptions short. 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.

The two logs that replace a software module

In the job folder, keep two Google Sheets (or Excel files, if that is what the team will actually open): an RFI log and a submittal log. Share them with the same people who have the job file.

RFI log columns: Number; date sent; subject; drawing or spec reference; who has the ball; due date; date closed; one-line answer; does this change the work (yes/no); filed in current set (yes/no); field received, by whom, and date; link or path to the PDF.

Submittal log columns: Number; spec section; description; type (shop drawing, product data, sample); date submitted; date returned; status (approved, approved as noted, revise and resubmit, rejected); notes that must reach the field; field received, by whom, and date; link or path to the PDF.

Color or filter the open rows so they jump out. A log that is only a list of PDFs is not doing the job. From that sheet, on a phone, a superintendent should be able to answer three questions: what is still open, who owes us a response, and did the field see the answer?

Review open RFIs the afternoon before a pour, a cover-up, or an inspection, not at 4 a.m. when the trucks are already on the way. Arizona heat makes that timing real.

Permissions, phones, and photos

Most of the team should be able to view and download the current set. Only a short list of people (you, a PM if you have one, or the person running the file) should be able to move or replace files in 02_Drawings_Current. In Google Drive, that means a shared drive with viewer or commenter access for most people, and editor access for a few. In Dropbox, it means careful folder permissions, not a single wide-open link. If everyone can overwrite today's drawings, you do not have a current set. You have a shared pile.

The current folder has to work on a phone. Pin it, or put a shortcut on the home screen. If the superintendent cannot open today's sheets in the sun, the "official" set still lives in the truck, and the phone will collect a private stash of PDFs.

Photos belong in 10_Photos, in folders by date or area, named so you can tell what they show six months later. A camera roll is not a record. Before a pour, a cover-up, or a change-of-condition argument, take the picture, name it, and drop it in the job file the same day if you can.

Where AI helps, and where it should not

Used as a clerk, an AI tool can save you a busy afternoon. Good uses:

  • Summarize a long RFI response into a short "what changed" note for the subs, then check it against the source PDF.
  • Draft a transmittal: what you are sending, to whom, and why. You still send it, and you still file it.
  • Search a messy folder or a long email thread for "sleeves" or a sheet number when you are in a hurry.

It cannot tell you which drawing is current. It should not "approve" a submittal. It should not be the last word on contract language, notice language, or anything you would have to defend later. If you let it rewrite a drawing list or a log, a person has to verify the result before anyone builds from it.

A weekly cadence a superintendent can keep

Fifteen minutes, twice a week, is enough for a lot of jobs:

  1. Move any new official drawings into Current, and move what they replaced into Superseded.
  2. Update the RFI and submittal logs. Close what is closed. Flag what is late.
  3. Send a short notice for anything that changed the work.
  4. Drop new photos and dailies into their folders.
  5. Before the next pour or cover-up, read the open RFI list for that area.

If that cadence slips for more than a week, the file starts lying to you. That is the moment to simplify the habit or get help, not to invent a new folder tree.

I walk through why these habits exist, and what a missed RFI can cost, in two companion articles: "What the Big GCs Know About Paperwork That Saves Them Money" and "The Missed RFI: How One Unanswered Question Turns Into a Rip-Out." The missed-RFI piece walks through a typical case.

If you want the file set up for you

Some teams will copy this structure and run it themselves. Others are already mid-job, or buried mid-inbox.

I can set up the job file, run the logs on a retainer, or prepare closeout before the scramble. If you want a second set of eyes, bring a look at where your drawings live now and one recent RFI thread. I will tell you straight whether this setup is enough, or whether you would be better off having someone else keep it.

The files stay yours. The point is a current set you can trust, not a new piece of software to feed.

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