Import a GAEB tender into a priced BOQ

Save the GAEB file the client issued into the project files alongside the invitation, so the version you priced is the version on record.

原因: Tenders get reissued. Filing the exact file you worked from means a later query about which revision you priced has a one-click answer instead of an argument.

Import the GAEB into a new bill. The groups, positions, quantities, units and long text come across intact, so you have an empty priced-out column to fill and nothing else to retype.

原因: Retyping a bill of a few hundred positions is where transposed quantities and dropped items creep in. Importing keeps your offer tied to the client's exact wording and numbering.

Match each position to a rate from the cost catalog or an assembly, adjusting for the wording where the standard rate does not quite fit, until every line carries a unit price.

原因: A rate pulled from a maintained catalog is defensible and fast. Reading the position text as you price it is where you catch the qualification hidden in a description that would otherwise cost you on site.

Run the bill through validation to catch any position left at zero, a quantity that does not tie, or a GAEB structure rule the return file must honour.

原因: A single unpriced position can void a submission or hide a loss you carry all the way to site. Validation turns a last-minute scramble into a green light you can trust.

Export the priced bill back to GAEB and issue it as your offer, so the client reads your prices straight into their evaluation without touching a keyboard.

原因: An offer that loads cleanly into the client's system is easier to award. Returning the same open format you were given is a small courtesy that keeps your bid at the front of the pile.