The product

NABU Compare

Compares two issues of a construction project: tender against contract, contract against construction, or any two stages. Runs on the project's own files. Delivers one report.

Inputs

What it reads

Stage folders
The drawings, models, specifications, bills, addenda and other documents of each stage, as issued. Sources are never changed.
Drawing registers
The register workbook of each stage: number, title, revision, date, discipline, review status.
Drawing files
PDF sheets, including copies inside stamped archives. One document, several copies, one record.
Specifications
Specification volumes of both stages, compared whole.
Bills of quantities
Read only, priced or unpriced, so each finding can be tied to the item it affects.

Modules

Three comparisons today, two in development

Each module answers the same question for one part of the project. Every finding, whichever module raised it, is linked to the bill of quantities items it affects.

1

Documents register

  • Every document of both stages: register and file, register only, file only.
  • Revision and date from the register and from the title block; every mismatch listed.
  • Change per document: matched, revision changed, date changed, one stage only, not compared.
  • Same revision but changed file: always listed.
  • Per-discipline table that reconciles to the totals.
2

Drawing comparison

  • Sheet against sheet, at a resolution that reads text and dimensions.
  • Each finding named by element and placed with a pin on the sheet.
  • Graded Major, Medium or Minor by what is drawn.
  • Evidence crop per finding: first stage left, second stage right, same window and scale.
  • Tags: category, zone, disciplines touched, repeated on N levels, BoQ item.
3

Specification comparison

  • Whole volumes compared section by section between the two issues.
  • Within one issue: codes used on drawings exist in the specification; specified items have a drawn use; values that disagree are listed.
  • Quotes as printed.
4

Model comparison In development

  • Two issues of a building information model, per discipline or federated.
  • Elements added, removed and modified; geometry, placement and property changes.
  • By level and category, with the changed elements shown in place.

Sample of the intended output

5

Model-derived quantities In development

  • Concrete, formwork, reinforcement, blockwork, finishes, doors and windows, by level and category.
  • Each difference traced to the elements that caused it.
  • Feeds the same bill of quantities links as the drawing findings.

Sample of the intended output

The link to the bill of quantities

  • One finding may affect several bill items: a wall extended by two metres changes blockwork, plaster, paint, skirting and the door schedule.
  • Each link names the item code and its unit; repeats on N levels are counted per level.
  • The BoQ items stand in the report beside Impact, Effect and Tags, and in the Excel export.

Outputs

The report

One self-contained HTML file. Opens offline. Phone-friendly. Plain English.

On the page

  • A volume summary: what each stage contains, what the comparison covers, how each volume was checked.
  • Cards and a per-discipline table; each one filters the document list.
  • Search, filters, sort, "N matching", Reset filters.
  • Findings with pins, chips and evidence; Major first; one switch hides Minor.
  • Select findings and export or copy only those.
  • Four switchable designs, each light and dark.

Excel, exported from the page

  • From a template: title block, project and stage lines, styled header, frozen panes, autofilter, column widths, banded rows.
  • Cover sheet with the volume summary; summary per discipline; one sheet per exception list.
  • Why and Reference columns on every reason.
  • Findings with Impact, Effect, Tags, the BoQ items affected and the evidence image.
  • Exports follow the active filters and design.

Rules it keeps

What you can rely on

Nothing dropped
Each register row and each file is in the list or in a named exception.
Every reason has a reference
Register file, sheet and row; folders searched; page where a revision was read.
No vague labels
The actual finding is named, with its count and reference.
Sources untouched
Project files are read, never moved, renamed or edited.
Cost kept apart
Cost indications are optional, encrypted inside the report, and opened only with the owner's password.
Engineering text only
The report carries the engineering content, the preparation date and "made with NABU". Nothing else.
How a comparison is done Ask about a project