Bid Communication Log: What to Record and How to Run One

A bid communication log is a single running record of every question, answer, call, email and addendum that touches a bid, with a date, a name and a status on each line. It does two jobs. On the owner’s side it proves that no bidder got an advantage. On the bidder’s side it proves what you knew, when you knew it, and what you priced from. If you bid commercial, institutional or public work, keep one for every pursuit.

This guide covers what goes in the log, how to separate informal answers from binding ones, a column layout you can build in Excel today, and the mistakes that cost bids.

TL;DR

• Log every bid-phase contact in one place: questions, answers, calls, site-walk comments, addenda and vendor quotes, each with date, source and status.
• Only a written addendum changes the bid documents. Verbal pre-bid statements and informal answers are not binding, so price from the addenda.
• A communication log is not a submittal log. One tracks bid-phase information, the other tracks technical submissions after award.
• Add a “priced?” column. It is the field that stops an addendum from being read, filed and never carried into the estimate.
• Close the log at submission, then reuse it in your debrief.

Table of Contents

• What a bid communication log actually is
• Informal answers versus binding addenda
• The fields every bid communication log needs
• A workflow that fits a 60 to 90 day bid cycle
• Communication log, RFI log or submittal log?
• Our perspective: the log is where bids are won quietly
• Common mistakes that cost bids
• Build it in Excel in ten minutes
• Where software takes over
• FAQ
• Sources

What a bid communication log actually is

Think of it as the paper trail of the bid period. Every exchange between your team and the owner, architect, construction manager or your own vendors gets a line. The log is not the same as your RFI log from the construction phase, although it borrows the format. During bidding, the questions are usually pre-award clarifications, and the answers may or may not become part of the contract.

The Construction Specifications Institute publishes a standard Communication Log form (Form 7.0B) among 44 CSI forms, alongside RFI, change order and submittal logs. That is a useful reference if your company wants an industry-recognized layout. Most estimating teams end up with a leaner version in a spreadsheet, because the bid period is short and the log has to be quick to update.

Why owners keep one

Public owners treat the log as risk management. The Caltrans construction manual says that no bidder should be given a real or perceived advantage over any other bidder, and that rule shapes how information is shared. If an answer goes to one bidder, it goes to all of them. Skip that and you invite bid protests, rejected bids or disputes over unbalanced pricing.

Why bidders should keep one too

You do not control the owner’s process, but you control your own record. Estimators change jobs mid-pursuit. Project managers inherit a bid they did not price. When an owner later claims a scope item was clear, your log shows what was asked, what came back and which addendum it appeared in. It also feeds the next bid: patterns in the questions you had to ask tell you which owners and architects issue thin documents.

Informal answers versus binding addenda

This is the line your log has to make visible on every row.

Caltrans is explicit that bidder inquiries should be handled by designated personnel only, with receipt acknowledged within two business days while the question is investigated. It also says a response to an inquiry does not modify the contract unless the change is formally incorporated into an addendum. Oklahoma’s construction instructions to bidders take the same position for pre-bid meetings: verbal statements are not binding, and changes must be issued as written addenda. Requirements vary by owner and jurisdiction, so read the instructions to bidders on each project instead of assuming these rules apply everywhere.

The practical consequences for your team:

1. Treat an emailed answer as information, not as scope. Log it, but do not rely on it for pricing until it shows up in an addendum.
2. Treat pre-bid meeting comments the same way. Write down what was said, who said it, and then watch for the addendum that confirms or contradicts it.
3. Expect cautious wording. Owners sometimes reply that you should bid per the current contract documents. Caltrans guidance describes that phrase as a common but sometimes risky way to avoid creating a non-binding interpretation. Log it as “no answer given, bid as documented” and price the conservative reading, with a clarification in your proposal if the owner allows one.
4. Record the answer’s status. “Informal,” “Addendum 2,” and “Pending” should be three distinct values in a dropdown, not free text.

If you have not yet planned the meeting where many of these comments arise, our pre-bid agenda and job walk checklist covers what to ask and capture on site.

The fields every bid communication log needs

Keep it short enough that people actually fill it in. These columns cover almost every case.

The “Priced?” column is the one most teams lack. Reading an addendum is not the same as carrying it into the numbers. A line that says “Addendum 3 revises Section 07 54 19 roofing membrane” should not close until the roofing sub’s quote and your estimate both reflect it.

What belongs in the log beyond owner questions

Owner and architect exchanges are the core, but the bid period also produces contacts that change your price:

• Vendor and subcontractor clarifications. A supplier who says the lead time slipped or a sub who excludes a scope item affects your number as much as an owner answer does.
• Site walk observations. Existing conditions noted at the job walk, with photos linked.
• Bid/no-bid decisions. The date, the people involved and the reason.
• Internal decisions. Alternates priced, allowances carried, and who approved them.

For the vendor side, a log works best alongside a leveled comparison of quotes. See our guide to the bid tabulation process for how to check unit prices once the responses are in.

A workflow that fits a 60 to 90 day bid cycle

A log only works if entries go in as events happen. Here is a workable routine.

1. Open the log on day one. Create the file when the invitation arrives, and log the invitation itself, the issue date of the documents and the stated deadline for questions.
2. Funnel contact through one channel. Designate one person per pursuit who sends questions to the owner. This mirrors the owner’s rule that only designated personnel handle inquiries, and it keeps your questions consistent. Shared inboxes help; if bid invitations land in a general mailbox, see how we handle bid email management so nothing is missed.
3. Batch questions from document review. Read the full set, including front-end clauses and divisions 00 and 01, before asking anything. Conflicts between sections and sheets are the best questions, and our spec conflicts guide lists the five fields worth logging for each one.
4. Submit before the question deadline. Many owners cut off questions several days before bid opening. Log the cutoff and treat it as a hard stop for clarifications.
5. Reconcile when addenda arrive. For each addendum, add a row, list the affected sections and trades, and mark which earlier informal answers it confirms or overrides.
6. Run a pre-submission audit. Filter for Open, Pending and unpriced rows. Nothing should remain unresolved without a deliberate decision to carry an assumption or exclusion.
7. Archive at submission. Lock the file, attach it to the bid record and carry it into the debrief.

The broader sequence this sits inside is laid out in our 60 to 90 day bid management workflow.

Communication log, RFI log or submittal log?

These three get confused, and the confusion has a cost.

A practitioner point worth repeating: a communication log records general inquiries and responses, while a submittal log tracks technical data, shop drawings and samples. A subcontractor procedures manual from Swinerton, for example, requires subs to provide a complete list of everything they must submit within one week of award notification. That is a post-award obligation, and it is a different document from your bid log.

The connection is that what you learn while bidding should flow into the submittal plan. If a bid-phase answer reveals a long-lead item, that belongs on the procurement schedule from day one. A delayed response to a critical RFI can ripple into fabrication and delivery delays, and those delays can land on the contractor if the submission schedule was not followed. Teams that want a tool for managing that later stage can look at submittal log management and schedule tracking as a starting point.

Our perspective: the log is where bids are won quietly

Most bid losses we hear about are not pricing losses. They are information losses. A clause in the front end that nobody read. A conflict between a spec section and a drawing that someone noticed but never logged. An addendum that changed a scope item after the sub’s quote came in.

We built ArosBid around the idea that the whole document set, including front-end clauses, has to be read and checked before anyone submits, and that automation should support human authority over the submission, not replace it. A communication log is the manual version of that belief. It forces a person to write down what was said and decide what it means for the number.

Three opinions we hold firmly:

• The log should live where the estimate lives. If your estimate is in Excel and your correspondence is in Outlook, the log should connect to both. A log in a separate system that nobody opens during pricing is a log nobody trusts.
• “Priced?” matters more than “Received.” Receipt is easy. Reflecting the change in the estimate and in every vendor quote is the hard part.
• The log is a learning asset. After the bid, the questions you asked and the answers you got show where documents were weak. Feed that into your lessons learned routine so the next pursuit starts smarter.

— arosbid team

Common mistakes that cost bids

Relying on a verbal answer. The pre-bid meeting sounded definitive, nobody wrote it down, and no addendum followed. Result: you priced something the contract never required, or skipped something it did.

Logging after the fact. Entries made three days later lose detail and sequence. Assign logging to the person who receives the message, and keep it to a two-minute task.

Mixing public and private rules. Public owners often prohibit contact outside the designated person and require that all answers go to all bidders. Private owners may allow direct conversations with the architect but still issue clarifications selectively. Our public versus private bidding checklist explains where the rules differ.

Pasting whole email threads into cells. The log becomes unreadable. Write a short summary and link to the original message or portal entry.

Forgetting that sub and supplier changes count. A qualified quote that arrives two hours before the deadline belongs in the log, with the decision you made about it.

Never closing the loop. Open items at submission should be a deliberate choice, with an assumption stated in the proposal, not an accident.

Build it in Excel in ten minutes

You do not need special software to start.

1. Create a sheet with the twelve columns above.
2. Add data validation dropdowns for Direction, Channel, Status and Priced?
3. Freeze the header row and add a filter.
4. Add conditional formatting: red when Response due is past and Response received is blank; amber when Status is “answered informally” and the bid is within five days.
5. Add a second tab listing addenda by number, issue date, sections affected and trades notified.
6. Save a copy of the template per project, named with the bid number.

Public owners also publish their own bid-phase forms. Connecticut’s Department of Administrative Services, for instance, posts a bid phase forms series that includes communications request forms. Check the owner’s library before you build, so your log can reference their form numbers.

Where software takes over

A spreadsheet breaks down when you run many bids at once, when several estimators touch the same pursuit, or when you need to prove that every addendum reached every trade. That is where we built ArosBid: it reads the full bid document set, flags missed clauses and conflicting specifications, and tracks bid approvals, vendor quotes and document compliance in one command center. It works with Excel and Outlook, so your team does not have to abandon the tools it already uses.

If you want to see how it handles addenda and vendor clarifications on a real pursuit, book a live demo. Plan details are on our pricing page, and the broader feature set is described on our estimating and bidding software page. For a look at how the document review itself works, see AI tender review, and for document handling around the log, our bid document management guide.

FAQ

What is a bid communication log?

It is a dated record of every question, answer, call, email and addendum during the bidding period. Owners use it to show that all bidders received the same information. Bidders use it to document what they knew and priced.

Are answers to bidder questions binding?

Not by themselves. Both Caltrans guidance and Oklahoma’s instructions to bidders say that clarifications become binding only when issued as a written addendum. Always check the instructions to bidders for the specific project.

How is a bid communication log different from a submittal log?

The communication log covers bid-phase questions and clarifications before award. A submittal log tracks shop drawings, product data and samples after award, and it works best as a schedule built around delivery dates.

Is there a standard template?

CSI offers a Communication Log as Form 7.0B within its set of 44 standard forms. Many teams adapt it or build a spreadsheet version with the columns described above, then check the owner’s own bid-phase forms.

Sources

• Caltrans Construction Manual, Section 3-2: Bidding
• Oklahoma Capital Assets Management, Instructions to Bidders
• CSI Forms, Construction Specifications Institute
• Swinerton Project Procedures Manual for subcontractors
• Connecticut DAS, 6000 Series Bid Phase Forms
• CivroBuild construction management software

Recommended

• Bid Tabulation for Estimators: 7 Steps, Unit Price Checks, Automation
• Construction Bid Lessons Learned: 48 Hours, One Action per Lesson
• Trade Estimators: One Page Bid Audit Trail for 5 Minute Clarifications
• Bid Document Management: A Practical Guide for Contractors