Drawings

Specifications

Estimator+ deliberately does not store specification documents. Drawings are the source of truth — for you and for your AI — and written specs are handled differently on purpose.

Why specs don't get uploaded

Specification text is general. The same clause about, say, waterproofing membranes gets reused word-for-word across unrelated jobs by the same consultant, and most of a 300-page spec has nothing to do with what's actually priced on this job. Indexing all of it alongside the drawings doesn't sharpen your AI's scope drafting — it dilutes it: generic clauses compete with what the drawings actually show, and the result skews.

So if you drop a PDF that reads as a written specification, Estimator+ says so before uploading it — and recommends leaving it out. You can override and file the pages as ordinary drawings, but the warning is the advice.

What to do instead

Give the spec to your AI directly: attach the PDF in the same conversation where your agent is connected to Estimator+ (see What the AI Connector is). It reads the whole document with the project open in front of it, keeps only what matters for this job — named products, standards, PC and provisional sums, performance requirements that change cost — and discards the boilerplate. What it keeps, it carries into the project in its own words, where its scope drafting picks it up.

That's a better spec reading than an indexed search ever was: selective, project-aware, and already in the shape your agent needs later.

Drawings win

When a specification and a drawing disagree, or when a spec seems to call something up that the drawings don't show, drawings take precedence. Your agent treats specs as supporting reference, never the final word on what's actually being built.