AI for Construction Cost Estimator

Tip: Type each sub's exclusions as a quick bulleted list. You don't need to write in full sentences. Ask the AI to add a "Risk" column flagging any scope item that more than half the subs excluded, as those are likely legitimate scope disputes.

Tip: Paste the sections you're most concerned about plus any you don't fully understand. Don't try to pre-filter. Ask it specifically about liquidated damage caps, consequential damage waivers, and indemnification scope since those are where estimators most often get surprised. This is a first-pass review, not legal advice. Flag anything it identifies for your PM or legal team.

Tip: Division 01 is the spec section most estimators skim. Use Claude for this since it can handle the full section without losing context midway through. Tell it to flag "anything that adds time to the schedule" separately from "anything with a direct cost" so you can address both in your GC estimate.

Tip: Add "formal but direct tone" to match how your company sounds. If you want to exclude specific scope items upfront (e.g., controls, BAS), list them in your scope summary. The AI will include them as stated exclusions so subs can't come back later claiming they weren't notified.

Tip: Tell the AI what answer you're hoping for (e.g., "we want confirmation that the structural engineer covers connection design, not us"). It will write the RFI to get that answer without being leading. For bid-phase RFIs, add "keep it short enough to get a fast answer" since design teams often deprioritize long questions.

Tip: Include the project's owner type (e.g., private developer, hospital system, municipal) in your prompt. The AI will filter out VE options that wouldn't be acceptable to that owner. For healthcare or education projects, add "no alternatives that affect infection control or life safety ratings."

Tip: Summarize each proposal in 3-5 bullet points before pasting if the full text is very long. This gives the AI cleaner material to work with. Flag any verbal scope clarifications separately.

Tip: Include everything you'd want to say in the kick-off meeting in writing here. This memo protects you and the company if scope disputes arise later. Even bullet points work as input; the AI will turn them into prose.

Tip: Be specific about unusual project conditions: tight urban site, occupied building renovation, aggressive schedule, complex phasing. Generic project descriptions produce generic risk lists; specific conditions get you risks you'll actually recognize.

Tip: Copy-paste the addendum text directly. The AI reads structured specification language well. Ask a follow-up question like "Which subcontractors need to be notified?" to get a ready-made notification list.

Tip: Run this check the morning of bid day, not the night before. You'll need time to either get a last-minute sub quote or carry the gap with an allowance. A missed scope item can wipe out your margin on a project.

Tip: Specify whether it's your first, second, or final notice. The AI will calibrate the tone accordingly. Adding the project name and your contact information in the prompt gets you a ready-to-send email.

Tip: Paste one division at a time for cleaner results. If a spec section is especially long, break it into subsections. The AI gets more precise with smaller chunks.

Tip: Ask for the list in order of impact so you can prioritize which options to actually price. Specify any constraints upfront (e.g., "owner won't change the building footprint" or "MEP systems are already designed") to avoid unusable suggestions.

Tip: List your exclusions explicitly. The AI won't assume them, and a vague scope letter invites subs to price the minimum. Add one sentence about any unusual site conditions or access restrictions.