From Structural Drawing to Approved BOQ — Without a Single Spreadsheet Formula

The Spreadsheet That Nobody Fully Trusts

It is 10pm. The structural drawings for the ground floor slab arrived that afternoon. The QS has opened them alongside the spreadsheet they use for bar bending schedules — the same one they have been refining for three years, with formulas built up layer by layer until no single person fully understands every cell.

They start entering bar marks. T16 at 150mm centres in the bottom layer. T12 distribution bars. U-bars along the slab edges. Each one goes into the spreadsheet, the cutting length formula runs, the weight calculates. After two hours, the ground floor BBS is done — 47 bar marks, total reinforcement weight confirmed in tonnes at the bottom of the page.

Then they notice that cell F23 has a slightly different formula from F22. It has been that way for months. It does not look wrong. But looking at it now, at nearly midnight, they cannot be entirely certain it is right. They check it. It is fine. But the fact that they had to check — that the doubt was there at all — says something about the fragility of a workflow where a single mistyped formula can corrupt every weight calculation that follows from it.

This is the BBS problem that every QS who works with reinforcement quantities knows intimately. Not dramatic failure. Quiet uncertainty. The kind that makes you check things twice at midnight and still wonder on the way home whether you missed something.

Where the Spreadsheet BBS Actually Breaks Down

The bar bending schedule is one of the most calculation-intensive documents a QS produces. Every bar mark requires the cutting length to be derived from the structural drawing — accounting for the member dimensions, the cover requirements, the bend allowances, and the lap lengths. Each of those inputs goes into a formula. The formula produces a cutting length. The cutting length multiplies by the number of bars. The result multiplies by the unit weight for that bar diameter. The product is the weight for that bar mark.

Repeat that process for every bar mark on every structural element across every floor level of the project. On a medium-size reinforced concrete building, that is hundreds of bar marks. Each one a chain of calculations. Each link in the chain an opportunity for an error that propagates silently downstream.

The specific points where spreadsheet BBS workflows fail most consistently:

•       Formula inconsistency: Rows copied from earlier bar marks carry the wrong cell references — the formula looks right but calculates from the wrong input

•       Unit weight errors: The density value for a bar diameter entered incorrectly in one row — every weight calculation for that diameter in the schedule is wrong

•       Bend allowance omissions: Hooks and bends not accounted for in the cutting length formula — the total weight is understated by the accumulated allowances across all affected bars

•       Manual transfer to BOQ: The BBS total weight retyped into the BOQ reinforcement item — a transcription error at this step means the cost plan and the reinforcement schedule no longer agree

•       Version confusion: Multiple saved versions of the BBS spreadsheet as the design develops — the BOQ ends up referencing a different version from the one the procurement team used to order steel

None of these failures announce themselves. They sit in the document until someone asks a question that requires tracing a number back to its source — and discovers that the source and the output no longer match.

What PlanEsti's BBS Tool Does Differently

When we built the BBS feature inside PlanEsti, the starting point was a simple question: what is the QS actually doing when they prepare a bar bending schedule, and where does the process create risk?

The answer was consistent. The QS reads the structural drawing, extracts the bar dimensions, applies the standard calculation rules for cutting length and weight, and produces a schedule. None of that requires a custom formula. The calculation rules are standardised — they are the same for every bar mark on every project. What varies is the input data: the dimensions, the bar diameters, the number of bars, the bend types.

So that is what PlanEsti asks for. The QS reads the structural drawing and enters the values — member dimensions, bar diameter, spacing or count, cover, bend type. The platform applies the correct cutting length calculation and the correct unit weight for that diameter automatically. No formula to write. No cell reference to check. No density value to enter and potentially mistype. The QS provides the inputs from the drawing. The platform handles the calculation.

The output is a complete bar bending schedule with every bar mark listed, cutting length calculated, weight in kg shown per bar mark, and the total reinforcement weight summarised in both kg and tonnes. The summary is generated from the data — it does not require a separate tab or a manually built total.

The Part That Changes Everything: From BBS to Approved BOQ

A bar bending schedule on its own solves the calculation problem. What PlanEsti connects is the step that follows — how the reinforcement weight gets from the BBS into the BOQ, and how the BOQ gets from the QS to the client.

In the traditional workflow, these are three separate activities. The BBS is produced in one spreadsheet. The BOQ is maintained in another. The QS reads the total reinforcement weight from the BBS and types it into the BOQ reinforcement item. Then the BOQ is exported as a PDF, attached to an email, and sent to the client with a request for review and approval. The client replies by email — or does not reply, and the QS follows up.

In PlanEsti, the BBS total weight feeds directly into the BOQ reinforcement quantities. There is no transfer step. The number does not move between documents — it is the same number in both, because both are part of the same platform. When the BBS changes because the structural drawings have been revised, the reinforcement quantity in the BOQ updates accordingly.

When the BOQ is ready for client review, the QS sends an invitation directly from the platform. The client receives an email with a secure link. They open the BOQ in their browser, review the quantities and descriptions, and can approve or raise comments directly inside the platform. The QS sees the response immediately. There is no email chain to manage, no version confusion about which PDF the client reviewed, and no uncertainty about whether the approval covers the current version of the document.

The Old Workflow vs PlanEsti — Side by Side