A first conversation about document control does not need a binder, a slide deck, or a complete history of the company. It needs a look at how the current job actually runs, and one problem that is already costing you time or risk. From that, we can tell whether a simple setup will hold, or whether you would be better off having someone else keep the file.

This is a short, practical call, not sales theater. You should leave knowing what I think the file needs, and what, if anything, I would do next. I will talk through the fee on that call, based on scope. It is usually carried as a fee in the job’s general conditions. If we talk about a live job, I will be straight with you about the kind of help that fits: setup, a retainer, closeout, or “you can run this yourself with a tighter folder.”

What to bring, if you have it

Bring what you can. Missing items are themselves useful information.

A look at where the drawings live now. A shared-screen walk through the folder, Drive, Dropbox, a desktop directory, or a stack of emails is enough. I want to see whether there is one current set, or several “latest” PDFs. You do not have to tidy it first. A messy folder is a better starting point than a cleaned-up sample.

One recent RFI thread, or a recent submittal that came back “approved as noted.” I want to see how a question or an approval actually moves: who was copied, where the answer landed, and whether the field can be shown to have received it. A single example tells me more than any description of “our process.”

One pain point. A pour that got ahead of an answer, a revision that did not reach a sub, a pay app held over missing waivers, a closeout that is already behind, a superintendent change. One is enough. We can go deeper if we need to.

Optional, if they are easy to hand over: the contact list for the job, the contract’s closeout requirements, or a punch or open-items list if you already keep one.

Do not send anything you are not allowed to share. Redact pricing or personal data if you need to. We can talk at the level of structure without putting a full drawing set into a new inbox. Please do not send personal information the job does not need. I am based in Arizona, and I work remotely with GCs and trades in any state, in Google Drive, Dropbox, and spreadsheets. Write to travis@builtonrecord.com.

What we will talk through

The call is a diagnosis, not a tour of my résumé. I will use my background only where it helps the file: I did document control at Mortenson Construction on a mission-critical data center project, from startup through Phase 1, and I helped onboard Procore there. I also completed my senior capstone project at Northern Arizona University on document control. I am not here to talk you into that software.

We will walk:

  1. Where the official current set is, and whether a superintendent can open it on a phone.
  2. How RFIs and submittals are tracked, and whether the logs (if they exist) are current.
  3. How a change gets to the people who will build from it, and whether you can prove it was sent.
  4. How closeout is (or is not) being collected.
  5. Whether DIY, a one-time setup, a retainer, or closeout help is the honest recommendation.

You should feel free to say “we already know the file is a mess.” That is a normal starting point. I will tell you what I see in your file, and what would make it trustworthy. I will not promise a dollar savings I cannot see.

After the call

If the right next step is that you run the file yourself, I will point you to the setup article, the templates, and the two or three habits that matter most. If the right next step is working together, I will say which service fits and what I would need to start. The files, if we proceed, stay in your account.

Write to travis@builtonrecord.com. A recent RFI thread and a look at where the drawings live are enough. The rest we can work out on the call.

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