One template for all projects is a practical ideal that rarely survives contact with real bids. The appeal is obvious: a standardised BOQ structure means fewer decisions during each new takeoff, and decisions under bid pressure are where mistakes concentrate. The problem is that a bill of quantities is not just a counting document. It is the communication interface between the estimating team and every subcontractor and supplier who has to price against it, and the structural requirements of that interface differ substantially between high-rise and low-rise work.
Before I moved into product work I spent several years as a quantity surveyor, primarily on mid-to-large commercial projects in Korea. The single most consistent failure pattern I saw in BOQ preparation was teams applying the structure they knew well from one project type to a project type that needed something different. What follows is a breakdown of the structural differences that actually matter, and why getting them wrong costs money.
The Core Structural Problem: How to Organise by Location
In a two-storey commercial fit-out, location is simple. You have ground floor and first floor, and every element can be clearly attributed to one level. The BOQ can organise primarily by trade or element type, with level called out as a secondary descriptor within each section. This is how most general BOQ templates are structured, and it works fine for low-rise work.
In a 30-storey tower, location is the primary variable that drives almost everything else. Floor-to-floor heights change between podium, typical floors, and plant levels. Structural member sizes vary by zone. Facade systems are different at low levels, mid-tower, and the top. MEP riser dimensions change throughout. Applying a flat element-type-first structure to a high-rise BOQ creates a document where all 30 floors' worth of column concrete is aggregated in a single line item, which is useless for the structural concrete subcontractor who needs to know how the pour quantities distribute vertically to price formwork, crane time, and pump hire.
The correct primary organising principle for high-rise BOQs is zone, not trade. Typical zone divisions for a commercial tower: substructure (basement and foundations), podium (floors 1 to typically 5 or 6), typical residential or office floors (the repetitive band), plant floors, and roof. Each zone gets its own section in the BOQ, with trade breakdown within each zone. Yes, this creates a larger document with more sections. The larger document is the correct document for this project type.
Repetition and How It Changes the Count Method
Low-rise projects are usually non-repetitive. Each floor has a distinct layout. Counting elements means counting each floor independently, and the BOQ reflects that as individual line items per floor.
High-rise projects have a repetitive band of floors that are structurally identical or nearly so. For a 25-floor typical band in a residential tower, you do not count 25 floors separately; you count one floor, verify it against the drawings and the structural schedule, then multiply by 25 with a notation. The notation matters: the BOQ should show both the per-floor quantity and the multiplied total, not just the aggregate. A structural steel subcontractor pricing against an aggregate steel tonnage with no indication of whether it is repetitive or varied cannot price crane sequencing or connection labour accurately.
Where high-rise BOQs commonly fail is in the transition zones. The bottom few floors above podium and the top few floors below plant level are typically non-standard. Facade angles change, slab configurations differ, structural transfer levels introduce elements that do not appear in the typical floors. These non-standard zones need individual itemisation even when the bulk of the tower is handled as repetition-multiplied. A template that applies the repetition multiplier to the entire structure without isolating the non-standard zones produces a BOQ that looks efficient but systematically under-describes the most complex parts of the project.
Subcontractor Interface: What Each Trade Actually Needs to See
The structural difference between high-rise and low-rise BOQs becomes most visible when you think about specific subcontractor pricing. Consider three trades and what each needs from the BOQ.
Concrete. Low-rise: aggregating all column concrete across two floors in a single line item is workable. The formwork and pour sequence are simple enough to price from the total volume plus the drawings. High-rise: column concrete needs to show quantities by zone because the formwork system, pump configuration, and pour sequence change significantly between the ground-floor columns and the 20th-floor columns. An aggregate concrete volume figure forces the subcontractor to re-extract the information themselves, which means either they price a contingency into their bid or they miss something and come back with a variation.
Curtain wall and facade. Low-rise: area by orientation (north, south, east, west) with unit types called out. This gives the facade contractor enough to price fabrication and installation. High-rise: facade quantities need to break out by system type (spandrel panels, vision glass bays, corner units, special geometry zones at top and base) and by zone, because the lift access and installation sequencing for levels 1 to 6 are completely different from levels 20 to 30. A single aggregated facade area figure with unit types is inadequate for a tower facade bid; the subcontractor's installation cost varies significantly by height and system.
Lifts and vertical transport. In low-rise, vertical transport may not be a separate BOQ section at all, or it is a simple line item for a stair and a single lift. In high-rise, vertical transport is a major works package that requires its own section: number of lifts, travel range, speed, lobby finishes, machine room type, and provisional sums for testing and commissioning. The lift contractor and the general contractor's program team both need this information in a structured form. Burying lift specifications inside a general finishes section because the template does not have a dedicated vertical transport section is a structural error that shows up in programme misalignment later.
Where the Same Template Causes Specific Problems
The failure mode is not that a low-rise template produces an obviously wrong high-rise BOQ. It produces a BOQ that looks complete but is organised incorrectly for its purpose. The errors surface during tender analysis, when the estimator is trying to compare subcontractor bids and finds that two bidders have interpreted the scope differently because the BOQ did not clearly communicate which quantities belong to which zones. Or they surface during procurement, when the structural steel package is awarded and the programme team realises the BOQ does not separate the transfer plate from the standard floor structure, making it impossible to sequence the work correctly.
We are not arguing that low-rise templates are wrong. We are arguing that the organising logic that works for a two-storey fit-out, element-type primary, location secondary, aggregate where practical, is the wrong logic for a high-rise tower.
Adapting BOQ Structure for Mixed Projects
The harder case is a mixed project: a podium-and-tower development where the podium is effectively low-rise commercial and the tower above is repetitive residential. Both elements can be on the same structural system and construction programme, but they need different BOQ structures. The correct approach is to treat the podium and the tower as separate sections of the BOQ with their own internal organising logic, not to apply a single structure across both.
When FOBECON processes drawing sets for mixed-type projects, the zone-based output structure is explicit about this. The system identifies zone boundaries from the drawing set and organises element counts accordingly, rather than aggregating across the full building. The reason we structured the output that way is that we have seen the consequences of aggregated-across-zone BOQs during tender analysis too many times. The information loss is not recoverable at tender stage.
A practical test for whether your current BOQ template is structured correctly for a given project: can each of your three largest subcontract packages price the work accurately from the BOQ alone without re-extracting information from the drawings? If the answer is no for any of them, the template structure is not right for this project type.