Revisions

Estimate revision tracking: change the bid without losing the old one.

Addenda, value engineering, a GC who wants the number again by Friday. In ScopeDive every change becomes a revision of the whole bid. The old one is kept, and any two can be compared side by side, down to each cost bucket.

ScopeDive revision comparison: project totals for two revisions side by side, including base bid, final bid, direct cost, every cost bucket and alternates, with the change and the percentage change

The revision model

Every revision is a snapshot of the whole estimate.

The first submitted number is REV00, the base, and it is locked. When something changes you revise the whole bid: REV01, REV02 and so on. Each revision is a full snapshot of the project estimate (scopes, takeoff, rates, markup, alternates), not a list of edits layered on top of each other.

That matters for two reasons. First, you can always answer "what did we send them on the 14th?" exactly, because that revision still exists. Second, the new revision starts from the old one, so nobody rebuilds an estimate from scratch to change three scopes.

Revision locking and estimate documentation are built in, so a number that was sent stays the number that was sent. If ScopeDive AI drafts changes from an addendum, they arrive in their own AI draft revision for the estimator to accept, edit or reject. See ScopeDive AI.

ExampleA typical revision history
RevisionWhy
REV00Base bid, as submitted. Locked.
REV01Addendum 1: two stairs gain an extra landing.
REV02Addendum 2: guardrail finish changed; lobby breakout priced as Alternate 1.
REV03GC asks for a value-engineering option on the canopy.

Each revision keeps the full estimate. Compare REV00 with REV03 to show the GC exactly what moved and why.

Compare revisions

See what moved, by how much, and where.

Pick any two revisions and compare them: project totals, cost buckets and scopes, each with the change and the percentage change. Affected items are highlighted in every scope, with the % change, so the review goes straight to what is different.

This is the conversation estimators have every week with project managers and GCs. "Why did the number go up 6%?" becomes a screen, not an afternoon. Material went up here, field erection went up there, Alternate 1 is new. The answer is in the comparison.

For an owner, the comparison is also a control. Before a revised number goes out, the reviewer can see every scope that moved and by what percentage, and question anything that was not part of the change. A revision that touches three scopes should not move a fourth.

Team reviews work the same way: a review round lists each changed scope with its value before and after and what changed. See team and tasks.

ScopeDive team review: a review round listing each changed scope with its value before and after and what changed, above the project's scope list

Revisions, alternates and addenda

Three things that change a bid, kept apart on purpose.

Spreadsheets tend to blur these together. ScopeDive keeps them separate so each can be explained on its own.

Keeping them apart is what lets you answer the GC in one sentence: the base moved because of Addendum 2, Alternate 1 is new and optional, and nothing else changed. In a single spreadsheet tab, those three facts tend to arrive mixed together, and somebody has to untangle them under pressure.

  • Revision

    A new version of the whole bid

    Used when the documents or the deal change. The old revision is kept, and any two can be compared.

  • Alternate

    A priced option beside the base

    Alternate add or alternate deduct, numbered and priced as its own scope. Never inside the base bid. See the glossary.

  • Addendum

    A change to the documents

    The reason for most revisions. Track addenda against the bid and price them into a new revision. See our guide on addenda.

See it on your work

Price your next bid in ScopeDive.

Book a 20-minute tour and bring a bid you recently priced. We will show you how your library, your rates and your cost structure would look in ScopeDive.