Bid day is not the end of the document set. It is the moment the set has to be pinned down to what actually governs the work: the bid documents, plus every addendum, plus the accepted alternates, plus whatever the signed contract says is included. If those pieces live in separate emails, and the field is still looking at the first set issued for bid, the job gets built to the wrong documents.

This is a filing habit, not a lesson in contract law. Your signed agreement, and a construction attorney when the language is in dispute, tell you what governs. The practical rule is simpler: after bid day, put the governing set in one place, and get the superseded bid set out of the truck.

What belongs together after the bid

Create a clear home in the job file for the documents that govern, typically:

  • The signed contract, and any exhibits or general conditions that came with it
  • The specifications, including all addenda that changed them
  • The drawings that were issued for bid, updated by addenda, and then issued for construction
  • Addenda, complete, in order, not just the cover pages
  • Accepted alternates, and a short note on rejected ones so nobody later "remembers" an alternate that was not taken
  • Bid clarifications or pre-bid questions and answers if they were made part of the contract
  • The issued-for-construction set, when it arrives, as the current drawings, with earlier bid sets moved to a clearly marked place

Addenda belong with the specs and drawings, not loose in email. An addendum can change a spec section, a sheet, a bid item, or all three. If the field never sees it, the bid set in their hands is incomplete.

When the issued-for-construction set comes out, treat it as the start of current-set control: one current folder, one date, and superseded bid drawings out of the truck. I walk through that rule in "Current-Set Control: One Place, One Date, One Rule." The bid set is still worth keeping, clearly marked, because you may need to see what changed. It is not what you build from unless it is still the official current set.

Write a one-page README that says what the governing set is as of a date: contract date, addenda included, accepted alternates, and the current drawing date.

The miss this prevents

The pattern is familiar.

An addendum, issued before bid, changes a product, a detail, or a count. The estimator sees it. The bid reflects it, or is supposed to. After award, the superintendent is handed a printed set that never got the addendum, or a sub is still working off the first invitation-to-bid drawings. Work is installed to the old requirement. Then someone compares the contract set, and you have a rip-out, a purchase that does not match, or an argument about what was "in the bid."

Bid day went fine. What failed was getting the governing documents into one place and into the hands of the people building the work.

How to run it in the job file

In the Google Drive or Dropbox job folder, keep specs and addenda together, and keep the current drawings separate from superseded bid sets. Name addenda with the date and the number so they sort in order: 2026-03-04_245_ADD_02.pdf. If an addendum includes replacement sheets, those sheets should end up in the current set when they are official, and the older sheets should move to Superseded.

Distribute the governing set on purpose after award, and again when IFC drawings are issued. A short transmittal that lists the addenda and the current drawing date is worth more than a verbal "you've got the set." File that transmittal.

If the job already started on a messy set

Stop and line up the paper before any more work gets built to a guess. Collect the signed contract, every addendum, the accepted alternates, and the latest official drawings. Put them in the job file, mark what is current, and tell the field.

When the habit will not hold on its own, I can set up that job file, run document control on a retainer, or prepare closeout. If you want help, bring the bid set you still have and whatever addenda you can find. I will tell you straight whether a single governing folder 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