Files and columns
Breakdown columns, breakdown view, and scoped comparisons
Understand how to compare a whole project, split results by breakdown, or scope a report to selected ISOs, floors, areas, levels, phases, or work packages.
Common questions this answers
- What does breakdown mean?
- Can I compare only one area or floor?
- What is the difference between breakdown view and comparison scope?
- Can I compare by ISO, level, phase, work package, or package?
What a breakdown column is
A breakdown column is the project context column that says where or how a material line belongs. Common examples are ISO, Area, Floor, Level, Zone, Phase, Work Package, Package, Assembly, System, Drawing, or Location.
Total parts vs breakdown view
- Total parts combines the same item and unit into one line for the selected scope.
- Breakdown view keeps the same item separate by the selected breakdown value.
- Use total parts when purchasing wants a single buy quantity.
- Use breakdown view when prefab, VDC/BIM, staging, or field teams need to know where the change happened.
Comparison scope
Comparison scope controls which breakdown values are included in the report. Use it when the uploaded files contain a full project, but the current review or order is only for selected ISOs, floors, areas, levels, phases, zones, work packages, or packages.
Scope options
- Entire project: compare every row in the uploaded files.
- Only selected: compare only the breakdown values you select.
- Exclude selected: compare everything except the selected breakdown values.
- The report audit summary records the selected scope so forwarded reports make the boundary clear.
Important review note
The original and revised files should use equivalent breakdown names. If one file uses different naming for the same area or package, normalize the source export or choose the matching values carefully before relying on a scoped report.

