Home›Blog›Construction Estimating

Construction Estimating

A construction estimating workflow from enquiry to submission

A tender enquiry lands with a deadline and a stack of drawings. What happens next decides whether the price holds up. This construction estimating workflow runs from sorting the enquiry to a checked, traceable submission.

A tender enquiry comes in with a deadline attached and usually a stack of drawings that need sorting before anything can be priced. What happens in the next few days decides whether the price you submit holds up, and most of it has nothing to do with rates.

A good construction estimating workflow is not complicated. It is a fixed order of steps, followed every time, so that the things that go wrong under deadline pressure get caught by habit rather than luck.

The enquiry lands, then what

Whether you price in-house or hand the work to outsourced estimating services, the first job is not pricing. It is working out what you have actually been sent, what is missing, and how much time is left before submission. Get this wrong and you spend the last two days of the tender period chasing information instead of checking the price.

  1. Log the documents. List every drawing, revision and specification section in the enquiry, and check it against the client's document schedule if there is one.
  2. Read the tender instructions. Form of contract, return date, pricing format, any mandatory qualifications or forms.
  3. Plan backwards from the deadline. Decide when quantities must be finished, when subcontract enquiries must go out, and when the price must be ready for checking.
  4. Send subcontract enquiries early. They take longest to come back, so they go out as soon as you know the packages.

Reading the job before pricing it

Before any rates go in, the scope needs breaking down properly: spatial extent, specification, and anything about the site or existing building that adds complexity. This is where a lot of tenders go wrong. The estimator starts pricing before anyone has actually read the whole set of drawings and flagged the awkward bits.

Look for the things that do not show as a quantity. Restricted access, a neighbour's party wall, a live building that stays occupied, a tight site with no room for materials. None of them are measured items, but all of them cost money, usually in preliminaries or in slower output.

A site visit helps if the job allows one. Photos, access routes, overhead cables, the state of the existing structure, where the skip will go. Twenty minutes on site can save a day of assumptions in the office, and it gives you a better feel for the programme than any drawing can.

Measuring and pricing on current information

Measuring what is there

Quantities get taken off measured to NRM2, with wastage and fixing allowances built into the rates rather than added as an afterthought. Anything ambiguous on the drawings gets logged as a query rather than guessed at, because a guess buried inside a rate is impossible to find again once the job is running.

Keep the query list live. Send the important ones to the client early enough to get answers. Anything still open at the end becomes a written assumption in the submission. It helps to measure in the order the job will be built, from substructure upwards, because it makes gaps easier to spot: if you have measured the walls but not the lintels over the openings, the sequence shows it.

Pricing the measured work

Rates go against the measured quantities using current subcontractor quotes and current material prices, not whatever was used on the last similar job. Where a package has not come back in time, it goes in as a provisional sum with a clear note, not folded into someone else's rate to make the numbers add up.

Preliminaries get priced against the programme you have planned for this job. Then overheads and margin go on top as separate lines, so the commercial decision about how keen to be is made on a clear view of cost.

Plan backwards from the deadline and leave room for the check. A price nobody has checked is still a draft, whatever the covering letter says.

A construction estimating workflow needs a check stage

Someone who did not build the price checks it against the drawings and against the enquiry documents before submission. This is where missed items, wrong quantities and duplicated allowances get caught. It is also the step that gets skipped when the deadline is tight, which is exactly when it matters most.

Build the check into the plan from day one. If the deadline is Friday, the price should be ready for checking on Wednesday, not Thursday night. A check done in twenty minutes at the end is not really a check.

Handing it over

The submitted price should stand up to questions from the client's QS without the estimator needing to reconstruct how a number was reached from memory. If the breakdown is traceable back to the drawings, that conversation is straightforward. Include your inclusions, exclusions, assumptions and the drawing list you priced from. Those four things protect you if the tender is accepted months later on a different set of drawings.

Keep the working file with the submission, too. Quantities, quotes received, the query log and the check notes. If the job is won, that file becomes the starting point for the control estimate and for buying. If it is lost, it is still useful the next time a similar enquiry lands.

Subcontractors run a version of the same process from the other side of the table, and how subcontractors price a package covers what changes when you are pricing one trade inside someone else's job.

One test for your own workflow

A simple test for your own construction estimating workflow: on your last tender, how many days before the deadline was the price ready for checking? If the honest answer is none, the workflow is not the problem to fix last. It is the problem to fix first.