The problem

Estimating isn't one job. It's six, stacked on top of each other: scope interpretation, quantity takeoffs, pricing judgment, risk assessment, proposal assembly, and follow-up. When vendors pitch "AI for construction estimating," they usually mean one of these six and assume the rest don't exist. That's how implementations go off the rails.

Where AI genuinely helps

Where it doesn't belong

The workflow pattern that works

The estimator reviews the RFP and makes initial scope decisions. AI assists with takeoff and extracts structured data. The estimator handles pricing. AI drafts the proposal from a template with past-project references. The estimator reviews, adjusts, and sends, then follows up personally. The human is the bookend. The AI is the middle.

Governance

The rule is simple: AI drafts, the estimator approves. The signed proposal carries the estimator's name, and the estimator did the work that justifies the signature. Get that distinction wrong and you'll find the problems the hard way.

What this doesn't fix

If the bigger problem is that you're bidding on jobs you shouldn't be chasing, AI won't solve it, it'll just help you produce more proposals for jobs you're going to lose, at speed. Bid/no-bid discipline comes first. The assessment is built to surface exactly this kind of sequencing decision.