Skip to content
EN
Open agent
Menu

By role

AI for cost estimating: trace quantities before pricing them

The useful output is a quantity or cost line you can trace to a drawing, measurement rule and price source. Start there before asking for a project total.

ARAI editorial teamUpdated 3 min read

Ask ARAI about your project

Contents · 5

Separate measurement, work scope and price

AI can help an estimator extract schedule rows, reconcile take-offs and identify gaps between a contractor's proposal and the design. These jobs become useful when each line retains its source. A plausible quantity and rate without that connection are difficult to check and expensive to correct later.

Start with one trade or work package. Define whether you need an extracted quantity, a measured geometric quantity or an accepted bill quantity. A floor outline can give a plan area; the bill may use a different measurement rule for openings, returns, waste or deductions. Keep those transformations visible.

Pricing is a separate step. Supply an approved rate library, current quotations or another identified price source. State the project location, currency, price date and scope basis. An assistant should return a missing price as unresolved rather than invent a local rate or a catalogue code.

Build a quantity record that survives review

For each item, retain the drawing or model revision, sheet, object or contour references, measurement expression, units and exclusions. If the geometry comes from Revit, preserve export settings and the source model revision. A DWG export does not automatically carry the model's material quantities or construction layers.

Check whether repeated details represent repeated work or the same work shown twice. A plan and an enlarged detail should not both add the same paving region. Likewise, a schedule may include future phases that are outside the current package. Ask for duplicate and scope checks before totals.

Distinguish net material, installed work and purchased material. Waste, laps, cutting allowances, bulking or compaction depend on the item and the adopted method. They should be named adjustments with a source or approved assumption, not unexplained multipliers.

A paving example

Suppose a marked courtyard has a gross plan area of 820 m² and a planted exclusion of 40 m². The geometric paving area is 780 m² if the outlines are valid and share the intended scope. That result alone does not specify excavation depth, sub-base thickness, edge restraints or disposal requirements.

Measure the marked paving regions in drawing revision B. Confirm drawing units, return each included contour and exclusion, and compare the net areas with the supplied take-off. Keep open or overlapping contours unresolved. Then list work-scope information needed for pricing; do not choose rates or add waste allowances.

Verify one known length and an independently measured region before accepting the total. Keep the area calculation separate from volume calculations. Multiplying 780 m² by an illustrative 0.15 m layer gives 117 m³ of geometric volume, but the layer extent and thickness must first be confirmed from the design.

Estimate fieldRequired basis
QuantityTraceable measurement and rule
UnitExplicit unit and any conversion
RateIdentified source, date and currency
Included workMaterial, labour, plant and scope description
AdjustmentsNamed allowance with approved basis
ExclusionsWork assigned elsewhere or still undefined

Compare proposals without losing their differences

Contractor descriptions rarely match the designer's item names exactly. Ask AI to propose a mapping, retaining both original descriptions and the reason for each match. Review uncertain matches before comparing amounts. Similar wording may conceal different thicknesses, grades or installation methods.

Normalize units only where the conversion is justified. A price per tonne cannot become a price per square metre without a supported mass-per-area basis. Record whether tax, delivery, access equipment, temporary works and testing are included. Keep provisional sums separate from measured work.

Use a reconciliation table showing design scope, proposal line, quantity difference, rate difference and unresolved qualification. A lower total may reflect omitted work rather than a better rate. Ask for the effect of each confirmed difference before presenting a revised forecast.

Accept a usable estimate package

Check arithmetic deterministically in the estimating tool or spreadsheet and inspect the actual formulas. Reconcile subtotals, currency conversions and rounding. Maintain a short assumptions register with owners and dates so that an early allowance does not silently become a tender commitment.

For a revised drawing, rerun the affected quantities and explain the delta by source object or scope change. Preserve the previous issue for comparison. The review should show which lines changed and why, rather than replacing a total without an audit trail.

ARAI can support a bounded DWG quantity question, starting with units and selected geometry. Prepare a quantity-check request. For the geometric basis, see AI for site planning.

Ask ARAI about your project

The question opens in the agent as a draft — you can edit it before sending.

Prepared by ARAI’s editors with AI assistance. Product information was checked against official sources as of the update date. Report an error at hello@arai.build.

ARAI

Try it on your own project

Attach a DWG and PDF, ask ARAI for a specific check, then review the result against your drawing.

Open ARAI
Contact us

Message the ARAI team

Telegram@arai_supportWhatsApp