Field Bulletin Tracking

Managing On-Site Design Directives and Revision Logic

Field bulletins are essential tools in the architect's arsenal for managing the inevitable shifts that happen once a project moves from the drafting table to the job site. Unlike a full revision of a drawing set, a bulletin often targets specific details or systems, providing a surgical update to the contract documents. Without a robust system for field bulletin tracking, teams risk building from outdated information, leading to costly rework and schedule delays.

The Structural Logic of a Bulletin

A field bulletin typically originates from a clarified design intent, often triggered by an RFI (Request for Information) or a coordination clash discovered in the field. The bulletin package includes a narrative description of the change, a list of affected drawings, and supplemental sketches (SKs) that provide the visual detail needed for implementation.

Managing these documents requires more than just filing them in a folder. You need a tracking system that links the bulletin number to the specific sheets it modifies. This ensures that when a sub-contractor opens a floor plan, they are immediately aware that a specific bulletin has modified the partition types or structural supports in their area.

Best Practices for Tracking and Implementation

The most successful project managers treat the bulletin log as a living document. It shouldn't just record the date of issuance; it should track the status of the change across the entire team. We recommend a few core protocols:

• Centralized Bulletin Log: Maintain a single source of truth that lists the bulletin number, issuance date, description, and the status of the subsequent Change Order.
• Sheet Annotations: Immediately update the 'Revision' block on affected sheets. Even if the full sheet isn't reissued, a reference note to the bulletin should be added to the master set.
• Distribution Confirmation: Use digital document management tools to verify that all relevant trades have received and opened the bulletin package.
• Integration with As-Builts: Ensure that the changes outlined in the bulletin are captured in the final as-built drawings to provide the owner with an accurate record of the facility.

FAQ: Common Bulletin Questions

What is the difference between a Bulletin and an ASI?
An ASI (Architect's Supplemental Instruction) is typically used for minor clarifications that do not involve a change in contract sum or time. A Bulletin is a broader term often used when the change is expected to result in a Change Order or a cost adjustment.

How often should the Bulletin Log be reviewed?
Ideally, the log is reviewed during every weekly coordination meeting. This keeps the team aligned on pending changes and prevents 'bulletin fatigue' where too many changes are issued without being processed into the contract set.