Post-Award Bulletins vs. ASIs: How GCs Keep Pricing and Change Logs Aligned

Key takeaways

• One controlled pricing record keeps bulletin and ASI pricing aligned from intake through change documentation.
• Routine field changes and bulletin-driven repricing should not be forced through the same workflow.
• Trade pricing requests should define backup requirements before numbers are returned.
• A change log is most useful when it tracks traceability, not just totals.
• Clean handoffs between estimating, project management, procurement, and project administration reduce rework later.

GCs keep post-award bulletin and ASI pricing aligned by using one controlled pricing record from intake through change documentation. The record should carry the revision reference, affected trades, due dates, required backup, and change-log status so the same information follows the item at every handoff.

Tribuild Consultancy is a construction estimating, preconstruction-support, and project-administration company.

Use one pricing record from intake

The right starting point is one pricing record created as soon as the bulletin or ASI is received. That record becomes the file for revised drawings, scope notes, trade pricing requests, clarifications, vendor quotes, and change-log updates.

A GC intake record should capture:

• Bulletin, ASI, or revision number
• Date received
• File location or document links
• Revised sheets, details, and specification sections
• Affected trades or bid packages
• Pricing due date
• Internal owner
• Current log status

When the revision starts as an email chain instead of a controlled record, backup gets fragmented early. Estimating, project management, procurement, and project administration end up working from different versions of the same issue.

Treat both bulletins and ASIs as revision triggers that need the same routing discipline. The label may differ by project team, but the workflow should stay consistent.

Separate routine field changes from formal revision pricing early

GCs should separate routine field changes from bulletin-driven repricing as soon as the revision is logged. That keeps simple job-level pricing from getting mixed with revisions that need takeoff, vendor input, and broader scope review.

A practical split looks like this:

• Routine field changes: small quantity shifts, minor coordination items, straightforward owner selections, or clarifications that can be priced from current job knowledge
• Bulletin-driven repricing: revised sheets, detail changes, specification changes, scope reallocation, added alternates, vendor requotes, or multi-trade impacts

The goal is not to force every project into rigid categories. The goal is to decide early who owns the pricing path and what level of backup is required.

A simple triage check helps:

• Does the revision affect more than one trade?
• Does it require revised takeoff?
• Does it change specified products or assemblies?
• Does it affect released procurement?
• Does it require vendor requotes?
• Does it need owner-facing backup beyond a lump sum?

If several answers are yes, route the item through a formal estimating path instead of treating it like a routine field change.

Require backup with the pricing request

Trade pricing should be requested with the required backup defined at the start. If backup is gathered after the number comes back, the team usually ends up chasing assumptions, quantities, and quote dates later.

A trade pricing request should ask for:

• Scope narrative tied to the revision
• Quantity breakdown or takeoff support where quantities changed
• Labor, material, equipment, and subcontract components as applicable
• Vendor or supplier quotations for major material impacts
• Assumptions, inclusions, and exclusions
• Lead-time impact notes where materials or fabrication changed
• References to the revised sheets, details, or specification sections used for pricing

The level of backup can vary with the size of the issue. The important part is that the expectation is set before the request leaves the office.

For example, a hardware revision should tie the pricing to the revised hardware sets, affected openings, vendor input, and installation delta. A framing revision should tie the number to revised quantities, labor impact, and any related board or accessory changes.

The pricing number is not enough by itself. The usable record is the number plus the backup that explains how the number was built.

Hand the same record from estimating to project administration

The cleanest workflow is a relay where each role adds to the same record instead of rebuilding the issue from scratch. That keeps the scope story intact from intake to final change documentation.

Estimating

Estimating should define what changed, what trades are affected, and what needs to be measured or requoted. For bulletin-driven repricing, estimating often handles:

• Drawing and specification review
• Scope comparison against the current contract or buyout baseline
• Quantity takeoff or delta takeoff
• Trade pricing request packaging
• Initial quote leveling
• Identification of gaps, overlaps, and assumptions that need clarification

The estimator's job is not just measurement. It is also to structure the pricing exercise so returned numbers can be reviewed on a consistent basis.

Project management

Project management should carry the operational and commercial context forward. Once trade pricing returns, PM review usually focuses on:

• Alignment with current subcontract scope
• Site conditions and phasing impact
• Whether the item is owner-driven, design-driven, or coordination-driven within the project's workflow
• Priority for direction
• Internal review path before owner-facing change documentation

With the backup attached, PM review becomes a decision step instead of a reconstruction exercise.

Procurement

Procurement should review the item when the revision touches long-lead materials, released buyouts, vendor commitments, or delivery timing. That review helps the team confirm:

• Whether quoted material is still current
• Whether released purchase commitments are affected
• Whether revised scope changes delivery timing
• Whether purchasing notes should be attached to the change record

This matters most when the revision affects equipment, doors, glazing, roofing, specialty products, or other items already moving through submittals and purchasing.

Project administration

Project administration should convert the priced item into a durable downstream record. That usually includes:

• Updating change-log status
• Assembling backup in the required review format
• Maintaining revision naming consistency
• Tracking pending clarifications and response dates
• Carrying approved information into downstream billing or closeout files where needed

Documents are prepared within the contractor's established review and approval workflow.

Build the change log for traceability

A useful change log should show traceability, not just value. The team should be able to see what revision started the issue, where pricing stands, what backup exists, and what downstream actions are waiting.

A strong bulletin or ASI log entry usually tracks:

• Unique change ID
• Related bulletin or ASI number
• Short scope description
• Affected trade packages
• Date issued for pricing
• Date pricing received
• Internal review status
• Owner review status, if applicable
• Current value and latest revision value
• Backup status
• Procurement impact flag
• Submittal impact flag
• Schedule impact note, if the team is tracking it
• Final disposition

That structure helps when a revision is clarified later, repriced more than once, or split across multiple downstream changes. If the log holds only a subject line and a lump sum, the history is hard to follow.

The same principle applies to subcontractors returning pricing to a GC. A subcontractor record that ties the request to revised sheets, vendor backup, and scope assumptions usually produces a cleaner GC change file.

Carry the record into downstream change documentation

The same pricing record should continue into downstream change documentation, purchasing updates, and billing support. The file should not stop once trade numbers are received.

That means the original intake record should still be linked when the team reaches:

• Owner change request assembly
• Subcontract change review
• Purchase order revisions or vendor confirmations
• Updated submittal or product-data routing if material selections changed
• Billing backup where approved changes affect invoicing

This is where disciplined workflow saves time. When the same record carries the bulletin reference, pricing backup, quote dates, procurement notes, and log history, the team does not have to rebuild the file later.

If you want to review one post-award pricing workflow or discuss multi-trade change documentation support, Tribuild can help map the handoff.

Sources

• https://tribuildconsultancy.com