Addenda during bidding. Bulletins during construction. Supplemental instructions on fast-track projects. Change order documentation when scope adjustments happen.
Whatever you call them at your firm, they all represent the same thing: changes to the contract documents after they've been issued. And they're one of the most reliable sources of confusion, disputes, and coordination failures in the design and construction process.
The problem isn't that changes happen, changes are inevitable. The problem is tracking them in a way that everyone on the project can rely on.
Why Addenda and Bulletins Are Uniquely Difficult
When you issue a drawing set at SD or DD, you're distributing a complete package. Everyone gets the same thing. If something changes, you issue a new revision and the old one becomes superseded.
Addenda and bulletins are different. They're supplements to a base document set: they don't replace drawings, they modify them. Which means you can have a current drawing set and a series of addenda that together represent the "truth" of the project, but neither one alone is complete.
This creates a cognitive overhead problem: to know what's actually specified at any given detail, you have to know both the base drawing and every addendum or bulletin that has modified it.
When that information is scattered — some addenda in email, some on a file sharing platform, some printed and sitting in someone's truck — the probability that someone is working from incomplete information is high.
The Addendum Log
The foundation of addendum and bulletin management is a log. A single, maintained document that tracks everything that's been issued and what it affects.
At minimum, the log should capture:
| # | Type | Date Issued | Description | Sheets Affected | Distributed To | Notes |
|---|
The "sheets affected" column is the most important. When a contractor has a question about a specific detail, they should be able to check the log, see that Addendum 3 modified Sheet A-301, and know to look there for the current information.
The log doesn't replace the actual addenda. It's an index. But it makes the addenda findable.
Numbering and Naming
Consistency here prevents significant confusion. A simple system:
- Addenda (issued during bidding): Addendum 1, Addendum 2, etc. Numbered sequentially throughout the bidding period, regardless of scope.
- Bulletins (issued during construction): Bulletin 1, Bulletin 2, etc. Starting fresh from 1 for construction.
- Supplemental Instructions (when used): SI-01, SI-02, etc.
Keep the numbering sequential and never reuse a number. If Addendum 2 is issued and then a correction is needed before it's formally responded to, the correction is part of Addendum 2. Not a new addendum 2a. Parallel numbering systems (2, 2a, 2b) create audit trail confusion.
Distribution
This is where most firms lose control of addenda and bulletins: inconsistent distribution.
An addendum only controls the project if everyone who needs it actually receives it. If the mechanical sub-contractor didn't get Addendum 3 because their name wasn't on the distribution list, the information gap is as real as if the addendum hadn't been issued.
A clean distribution system for addenda:
- Maintain a master distribution list for each project. Everyone who receives contract documents
- Issue every addendum to the complete list, simultaneously
- Log the issuance: who received it, when, via what channel
- For critical addenda, require receipt confirmation from key parties
The receipt confirmation step is often skipped because it requires follow-up. It's worth doing for addenda that materially affect scope, cost, or schedule.
Incorporating Addenda into the Record Set
At the end of a project, the record set should tell the complete story of what was built. That means the addenda and bulletins need to be incorporated: either into a revised drawing set or clearly indexed so the record set + change document index = complete information.
How this is handled varies by firm. Some firms issue revised drawings for every addendum change and treat them as a new drawing revision. This is cleaner but more labor-intensive. Others maintain the addendum log as a permanent part of the project record, with the understanding that the record set and the addendum index together represent the final design.
Either approach works if it's consistent and if the record is complete. The worst outcome is an as-built drawing set that contradicts the field conditions because the addenda that changed it were never incorporated.
The Speed Problem
One practical reality: addenda on fast-track projects often need to get out quickly. Taking the time to properly log, number, and distribute an addendum when the contractor is waiting for an answer can feel like unnecessary overhead.
The discipline here is worth maintaining even under pressure. A poorly distributed, unlogged addendum creates more downstream work than the time saved in issuing it quickly. If the system is set up well — the log is maintained, the distribution list is current, the numbering is clear. Issuing an addendum shouldn't take more than a few minutes of administrative work on top of the actual technical content.
The overhead comes from maintaining a system under pressure. The alternative, winging it and cleaning up later: consistently takes longer.
