From Takeoff to BOQ to Progress Tracking: A Small Contractor's Toolkit

A small contracting business lives or dies on three connected disciplines: pricing the work right, knowing what was agreed, and proving what was done. Big contractors run departments and enterprise software for each. A small contractor runs all three personally, usually at night, usually in a spreadsheet whose formulas nobody fully trusts anymore — and the gaps between the three are where the money leaks: the item measured but never priced, the variation built but never claimed, the progress payment argued from memory against a client arguing from paper.

The fix isn't enterprise software. It's a connected workflow where the takeoff feeds the BOQ, the BOQ feeds the tracking, and every number can answer where did you come from? Here's that workflow on two free browser tools — with your tender drawings and your pricing never leaving your own machine, which matters more in this trade than most.

Stage 1: The takeoff — measured, not guessed

Pricing starts with quantities, and quantities start with the drawings. In the Simple QTO Tool, load the tender drawings, calibrate each sheet against a written dimension and verify with a second (the sixty-second habit that protects everything downstream — full method in our calibration guide), then measure by trade: linear metres of wall and pipe, square metres of slab and finish, counts of doors and fixtures. Every measurement stays as a visible markup on the drawing and a line in the schedule, permanently connected.

Two habits turn a takeoff into a defensible takeoff:

Reference everything. Each quantity records its sheet and revision. When the drawings change at Revision C — and they will — you re-measure the deltas against your markups instead of starting blind, and when a quantity is challenged, you open the sheet and point.

Separate net from allowance. Measure the true quantity; apply waste, laps, and compaction as a visible, stated allowance on top. A reviewer (or a future you, pricing the variation) needs to see the raw number and the judgement as two things, not one blended guess.

Attach unit rates to the measured items and the takeoff extends into a priced bill. Export it two ways, because it has two jobs:

PDF — the issued, dated record: what you priced, from which drawings, at which rates. This is the document that anchors every future conversation about scope.

CSV — the working copy into your spreadsheet, where your real pricing happens: labour constants, supplier quotes, margins, the commercial judgement no tool should make for you. The point of the CSV isn't to replace your costing — it's that your costing now starts from measured, referenced quantities instead of typed-in numbers with no ancestry.

Pro tip: Structure the BOQ around how you'll claim, not just how you priced. Break items by building zone or level, not only by trade — "Blockwork, Level 2" rather than one project-wide blockwork line. It costs a little structure now and pays every month: progress claims become "Level 2 blockwork complete — 100% of item 4.2" instead of a negotiated percentage of one giant line, and variations slot in beside the affected zone. The BOQ's structure is your claiming strategy, decided on day one.

Stage 3: Tracking — the BOQ becomes the board

Here's the connection most small contractors never make: the priced BOQ is also the work breakdown. Every bill item is a parcel of work that will be started, finished, and claimed — which is exactly what a Kanban card is.

In Taskboard, set up the project board with the BOQ's zone-based items as cards and columns that mirror how work actually earns money:

Not Started → In Progress → Complete → Claimed → Paid

The two right-hand columns are the ones generic task boards never have and contractors need most. Complete but not Claimed is finished work you haven't billed — every card sitting there is your money resting in the client's account. Claimed but not Paid is your receivables, visible as cards instead of buried in an aging report. Flip to the Gantt view and the same cards show the programme: which zones run when, where the trades stack, which claim lands in which month.

Because the board saves as a JSON file, it lives in the job folder next to the BOQ and the drawings — snapshot it at every claim date and you hold a dated record of exactly what was complete when, which is precisely the evidence progress-payment disputes are won with.

Follow one number through the system and the point of the workflow appears. 62 m² of blockwork is measured on a calibrated, referenced sheet (Stage 1) → becomes priced item 4.2, Level 2, in the issued BOQ (Stage 2) → becomes a card that moves to Complete on the 14th, snapshot on file, claimed on the 15th (Stage 3). When anyone — client, engineer, your own accountant — asks about that item, the answer is a chain of evidence, not a recollection. Small contractors rarely lose money because they priced badly; they lose it because they couldn't show the chain. This workflow is the chain, and it costs nothing but the discipline to run it.

Both tools are free, account-free, and local-first — tender drawings and pricing are exactly the files that shouldn't be sitting on a third-party server:

Start with the Simple QTO Tool → — then put the BOQ on Taskboard.

Quantities, rates, and claims carry contractual consequences. Have tender pricing reviewed by a qualified estimator or quantity surveyor where stakes warrant, and ensure claims follow the measurement and notice requirements of your specific contract.