Order of precedence when the drawing and the specification conflict

Neither governs by default. Precedence between drawings and specifications is a property of the contract for this project, and standard forms take opposite positions on it. Until somebody has read the precedence clause on this job, any statement about which document wins is a guess, and any tool that ranks conflicts is ranking them against an assumption nobody signed.

That is an inconvenient answer for software, because the ranking becomes configuration rather than logic. It is also the only answer that survives a dispute, and encoding it per project is a smaller job than most teams expect.

Two positions, and how to tell which one you are under

• Complementary documents. The general conditions in widest use across North American practice state that the contract documents are complementary, and what is required by one is binding as if required by all. That resolves silence, not contradiction: a requirement appearing only in the specification still applies, and the wording deliberately does not rank.
• An explicit hierarchy. Owner-drafted agreements, public-works contracts and international forms such as the FIDIC conditions commonly carry a priority-of-documents clause listing the agreement, conditions, specification and drawings in a stated order. Where one exists, it is the answer.
• A discrepancy procedure instead of a rank. Forms in the NEC and JCT families handle it procedurally: the contractor gives notice, the contract administrator instructs, and the instruction resolves it. There is no ranking to encode — what you encode is the notice obligation and its timescale.
• Conventions printed on the set. 'Figured dimensions govern over scaled dimensions' and 'large-scale details govern over small-scale' are common general notes. They bind because they are printed there, not because they are universal, so confirm they are on your set before relying on either.

Turning the clause into a lookup a system can use

The artefact is one table per project, filled in from the contract before any document tooling is switched on. It has to be readable by a person and loadable by a system, because the same table settles arguments in a meeting and ranks findings in a queue.

Rank 4 is the row that decides whether the table is usable, because a drawing has to be classified before it can be ranked, and the classification comes off the sheet itself. Which of those fields can be trusted across consultants is the subject of the title block is the metadata layer of a sheet set.

What conflict detection can and cannot do

• Detection is mechanical. Same object, two values, both machine-readable — a door schedule naming one hardware set and a spec section naming another is a finding a system can raise without knowing anything about precedence.
• Ranking is not mechanical. It needs the project's table loaded, and without it every finding is 'these disagree', which a project engineer already knew.
• Most apparent conflicts are complementary. The specification sets performance and the drawing sets location; a tool that flags every such pair produces a queue nobody works.
• Detection needs both documents readable. On a scanned set the failure is upstream of precedence entirely, for the reasons in extraction is clean on issued PDFs and useless on scans.

Where addenda, RFI responses and field records sit

Later documents of the same class usually govern earlier ones, but again only because the contract says so — write that rule into the table rather than assuming it. The trap is the RFI response, which in most arrangements is a clarification and not a contract document: it does not change scope, and an answer phrased as an instruction can create a claim, which is why drafting an RFI response that answers the question and nothing else is a discipline in itself.

The same rule reaches the field. A markup that resolves a conflict is only worth anything if it records which document was followed and under what authority — the metadata set out in what a field markup has to carry to become an as-built. And the same logic runs at the gate: when a delivery ticket names one product and the specification names another, what actually arrived is settled by the receiving record the site keeps for itself, not by the ticket.

A conflict-detection tool with no precedence table is a tool that tells you two documents disagree. Everybody on the job already knew that.

Loading a precedence table, classifying documents against it and running a findings queue a project engineer will actually work is the kind of internal system we scope under internal tools and ops. The rest of this silo sits under drawings, specs and document intelligence, inside our construction and contracting work.

• contract documents
• specifications
• document ai
• conflict detection