Contradiction detection is the systematic search for statements within an organisation's own document estate that conflict with one another. It is the inverse of search: instead of finding documents that mention a topic, it finds documents that disagree about one.

Why this goes undetected

Search doesn't find it. Two documents that both match a query and contradict each other are simply two results. Version control tracks changes within a document with no view across documents. Reviews are scoped to a document, a department, or a renewal cycle exactly the boundary a contradiction crosses.

Where contradictions concentrate

Time periods (notice periods, payment terms, retention windows), thresholds (approval limits, discount ceilings), named responsibility (two documents assigning the same duty to different roles), definitions (business day, delivery, acceptance defined differently in different agreements), obligations to customers, and security and data claims (a questionnaire response that overstates what the policy actually requires a live exposure the moment a client audits you).

What a sweep produces

A ranked list of conflicts with a judgement about which one is authoritative. Each finding carries the conflicting statements with source documents and dates, the nature of the conflict, which should govern, the exposure, and the fix (amend, supersede, or withdraw).

Precedence has to be declared, not guessed

Before any sweep runs, state the hierarchy: executed customer contracts, then regulatory commitments, then board-approved policy, then departmental procedure, then internal guidance, then marketing material.

When it's worth doing

Before a certification audit, before or during due diligence, after a merger, after rapid growth, or following a dispute.