When large general contractors buy enterprise platforms, they are not paying for a logo on a login screen. They are paying for a short list of habits: questions get tracked until they are closed, there is one current set of drawings, there is a trail of who got what and when, and closeout is collected along the way. The software facilitates those habits. It does not replace them. Procore facilitates a process. There are many tools to accomplish the same goals.

I learned that from the document control seat, not from a sales deck. I did this work at Mortenson Construction on a mission-critical data center project, from startup through Phase 1, and I helped onboard Procore there. Switching platforms did not create the need for a current set or an RFI log. That need was there all along.

Most contractors running several jobs at once, with a superintendent or PM doing the paperwork on top of the work, have no Procore budget and no one whose only job is the logs. That is not a failing. The smart move is to borrow the habits and run them in tools you already understand.

The habits, stripped of the dashboard

Strip away the dashboards and you are left with four jobs, the same ones I describe in "What the Big GCs Know About Paperwork That Saves Them Money": track RFIs and submittals until the field has seen the answer; keep one current drawing set, with a date, and move everything it replaces into a superseded folder; leave an audit trail of transmittals, distribution, and dates; and treat closeout as a habit, not a last-month panic.

None of those jobs requires a particular platform. Each of them can live in a shared Google Drive or Dropbox folder, a spreadsheet for the logs, a phone for dated photos, and a short weekly cadence someone will actually keep. The current set still has to be a human rule. If everyone can overwrite today's drawings, you do not have a current set. You have a shared pile.

What this looks like in tools you already have

A shared folder for each job, with a current-drawings folder, a superseded folder, and places for RFIs, submittals, transmittals, daily reports, photos, pay applications, and closeout, is enough structure. A one-page note in the root should state the current-set rule and who is allowed to replace drawings.

The RFI and submittal logs can be a Google Sheet or an Excel file in that same job folder. Review open items the afternoon before a pour, a cover-up, or an inspection. In an Arizona summer, heat pushes work into the early hours, and a 4 a.m. pour is a bad time to discover an open question.

Used carefully, an AI tool can help at the edges: summarize a long RFI, draft a transmittal, or search a folder when you are in a hurry. It cannot tell you which drawing is current, and it should not "approve" a submittal. I walk through a concrete folder tree and log columns in "A Procore-Level Job File With Google Drive (or Dropbox) and a Spreadsheet." The value is the rule and the cadence, not the logo.

If you want the habits set up for you

Some teams will copy a folder structure and run it themselves. Others are already buried mid-inbox, mid-revision, or being asked to work in a platform they do not use every day.

If that sounds like your job, I can set up the job file, run the logs on a retainer, or prepare closeout. If you want a second set of eyes, show me where your drawings live now and bring one recent RFI thread. The files stay yours. You do not need enterprise software to borrow enterprise habits.

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