Spec says 350 tons. The drawing says 400.
Spec-versus-drawing conflicts are neither rare nor subtle. They are just distributed across two documents that nobody reads side by side.
A construction document set is not one document. It is at least two, written by different people at different times, coordinated at the end under schedule pressure, and issued together as though they agree.
The specification calls for 350 tons. The drawing schedule calls for 400.
Fifty tons of chiller is not a detail. It is equipment cost, electrical service, structural support, and a lead time, and every one of those belongs to somebody’s bid.
Why nobody catches it
Because catching it requires holding two documents open at once and comparing a value in a schedule against a sentence in a section, for every piece of equipment on the job, in a set that also contains the twenty-nine other documents you are responsible for.
Most estimators price from the schedule. Schedules are tabular, quantified, and legible; specifications are prose. That is a completely reasonable habit and it is exactly the habit this conflict exploits. The order-of-precedence clause in the front end usually says the specification governs — which means the number most people price from is the number that loses.
Most people price from the schedule. Most order-of-precedence clauses say the specification governs.
The window for an RFI is before pricing, not after
A conflict found during document review is a question. The same conflict found after the number is set is a problem, and after award it is a change order argument you may or may not win depending on what the precedence clause says and how sympathetic the owner feels.
So the value is not really in the detection. It is in the timing. ArosBid reads the specification sections and the drawing schedules as one comparison, flags where they disagree, and drafts the RFI while there is still time for the answer to affect the price.
Cited, or it does not count
Every conflict comes back with both sides: the section and paragraph, and the drawing and schedule. Two clicks, two documents, and the estimator decides whether it is a genuine conflict or a coordination note they already understand.
Some of them will be false positives. A system that only reports conflicts it is certain about will miss the ones that matter, so the honest design is to surface the disagreement with its evidence attached and let a person who knows the job make the call. That is a shorter conversation than it sounds like, because the evidence is already open.