Troubleshooting

Specific fixes for issues you’re likely to hit. Each entry names the symptom, the cause, and the fix.

Imports

A price came in 100× too high (e.g. €4500 instead of €45.00)

A missed decimal during extraction. The review screen highlights outliers in amber for this exact reason — edit the value in place and re-confirm. Don’t re-upload — manual corrections take seconds, re-extraction takes minutes.

See: Importing price sheets — tips.

Pack qty / UOM is wrong on every row

Almost always a wrong default at the top of the review screen, or a column was mis-mapped during extraction. Fix the defaults before confirming — the unit rate is computed from pack qty and UOM, so if those are wrong every downstream estimate will be wrong.

Imported in the wrong currency

Switch the Currency dropdown at the top of the review screen before confirming. Prices are stored normalised against the company’s base currency, so post-confirm fixes mean deleting the imported prices and re-importing.

The import sat in “Extracting” for a long time, then failed

Vision-based extraction can stall on very large PDFs or scans with poor contrast. Split the file into 10–20 page chunks and re-import, or re-scan at higher contrast / 300 DPI.

Assemblies

“Delete is blocked”

The assembly is in use — applied to an estimate line or a takeoff group. Deleting it would break those lines. Options:

Edit in place for non-destructive tweaks (preferred).
Duplicate-and-replace: copy the assembly, modify the copy, swap it in where it’s used, then delete the original.

UOM mismatch warning when applying

The assembly’s output UOM (e.g. m²) doesn’t match the BOQ line’s UOM (e.g. m). Almost always this means the wrong assembly was picked — cancel and choose again, or fix the line’s UOM first.

AI suggestions don’t include the right assembly

Two likely causes:

The line description (or takeoff group name) is too vague. “Slab” doesn’t tell the AI much. See naming groups well.
The assembly name describes the recipe rather than the output. Rename it to match what an estimator would search for — “150 mm Reinforced Slab”, not “Concrete + rebar”.

`Unknown variable` error when saving an assembly

The expression references a {variable_name} that doesn’t exist, or has a typo. Open the Variables tab, confirm the exact name (lowercase, underscores, no spaces), and either fix the expression or create the missing variable.

Takeoff

Every measurement on the page is wrong

The page scale is off. Click Set Scale and re-pick two points of known distance — all shapes on the page recompute against the new scale.

A group has zero shapes but its line is still in the estimate

Deleting shapes leaves the BOQ line with quantity 0 rather than removing it (so you don’t accidentally lose a priced line). Delete the line manually if it’s genuinely no longer needed.

Re-measuring a shape didn’t update the estimate

Group quantity → estimate line is automatic. If the estimate still looks stale, refresh the page. If it’s still stale, the line’s rate or quantity has been manually overridden — check the line for an “edited” indicator and clear the override.

Estimates and exports

My export is in the wrong currency

Exports use your company’s base currency (set in Company Settings). There’s no per-export override — change the base currency, then re-export.

Last week’s exported file looks out of date

Expected behaviour. Each export is a snapshot — the file you sent doesn’t update when rates change later. Re-export to produce a fresh version.

Subcontractor pack accidentally includes my rates

Re-export with Rates and totals unchecked and Component breakdowns off. See Tender vs. client vs. internal.

Still stuck? Contact support.