A retainer is ongoing document control during construction: the current set, the logs, the distribution, and the weekly open-items review, kept current while the field stays on the work. It is the right service when a one-time folder setup is not enough, because the job will not wait for a superintendent’s leftover Friday minutes.

This is not a full-time staff member in your trailer, and it is not a software license. It is a person who keeps your official job file, in your Google Drive or Dropbox, with spreadsheet logs your superintendent can open on a phone. The files stay yours.

What the retainer actually covers

Week to week, the work is the same short list of habits that keep a large job honest. I kept that kind of record at Mortenson Construction, on a mission-critical data center project, including the Procore onboarding when the job moved off Oracle Unifier. The scale was different. The habits are the same.

On a retainer, you can expect:

  • Official drawings and design changes filed into the current set the same day they can be, with superseded sheets moved out of the official folder.
  • RFI and submittal logs updated as items are sent, returned, and closed, with open and late items obvious, and a record of whether the field received answers that change the work.
  • A short distribution when the work changes, and a transmittal or send-record in the file so “I never got that” has an answer.
  • A weekly written snapshot: what was issued, what is still open, what is late, and what upcoming work (a pour, a cover-up, an inspection, a pay-app cutoff) could be affected.
  • An extra look at open items the afternoon before a known pour, cover-up, or inspection, when you flag those dates.
  • New photos and dailies filed when they reach the job folder, and closeout documents dropped into the closeout folder as they appear.

What it does not cover, unless we add it in writing: means-and-methods decisions, design answers, submittal approval, legal advice, or being the superintendent. I keep the record. You run the job.

How we work together in a normal week

You should not have to chase the file. I should not have to chase the job. A simple loop is enough:

  • You (or the designer, or the GC) send or point me to new official documents as they land, or I pick them up from the agreed inbox or folder in your Google Drive or Dropbox.
  • I file, log, and distribute per the rules we set at the start.
  • You get a short weekly note, and a same-day flag if something that changes the work arrives before a pour or a cover-up.
  • The superintendent still confirms that the field has seen the answer, or tells me who should be on the distribution. Closing the loop in the field is still a field job. The log records it.

If that loop is quiet for a week, the file will start to drift. The retainer only works if new documents have a path into the official folder. Setup, at the beginning, is where we make that path obvious.

When a retainer is the right tool

A retainer fits a job with a fast revision cycle, a stack of open RFIs, a mid-job staff change, or a stretch where the field simply has no more hours for the paperwork. If a clean file and fifteen minutes twice a week will hold, you may only need setup. If closeout is the only remaining risk, you may only need closeout support. “When DIY Is Enough, and When It Isn’t” is the longer version of that choice.

A retainer is quoted for the job in front of us, based on scope, and is usually carried as a fee in the job’s general conditions. If you want to talk about a live job, bring a recent RFI thread and one pain point, and be ready to show me where the drawings live. I will tell you straight whether a retainer is what you need, or whether a simpler setup will hold. 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