What documents form the contractual framework besides the contract
The document signed as 'contract' rarely exhausts what binds the parties. The accepted proposal sets the price and conditions on which it was negotiated; the budget details items and units; the drawings and their latest revision define what must be built; the technical and administrative specifications set qualities, tests and procedures; annexes incorporate particular conditions that sometimes contradict the general body; the schedule or work program sets milestones with contractual effect, and award communications may include conditions that never made it to the final document.
Each of these documents may have its own emission date and its own revision. A drawing dated March and another dated June are not interchangeable even if they describe the same area: if the contract does not expressly state which prevails, the discrepancy must be documented as an open matter, not resolved by applying the criterion of whoever detects it first.
How to build the document table with precedence
The minimum table has five columns: document, emission date, revision number, subject matter it governs and precedence (if the contract itself defines it, or 'undefined' if not). Completing it is not a preliminary formality before the work but the reference consulted every time a question arises about which version applies. Without that table, each responsible party ends up applying the version they have saved in their folder, which is not always the latest.
When the contract does define a precedence order, common in public works specifications, less frequent in private contracts between owner and builder, that order must be transcribed literally to the table, not interpreted. When it does not define it, the operating criterion is to register the most recent emission date as a presumption of validity, and explicitly mark it as a presumption, not a contractual rule, so whoever must resolve the discrepancy knows it requires confirmation.
Typical contradictions between documents and how to address them
The most frequent contradictions appear between drawings of different disciplines (architecture vs. installations at the same constructive joint), between description and drawing (the description specifies a finish the detail drawing does not reflect), and between budget and technical specifications (an item measured one way in the budget and defined with a different measurement criterion in the specifications). None of the three are resolved by applying common sense on site: all three require a formal query to whoever has authority to decide which prevails.
The mistake that costs most later is allowing the contradiction to be resolved de facto, executing according to the document the site manager had at hand, without recording that the discrepancy existed. If later it is necessary to justify why something was executed one way and not another, the absence of that record leaves the builder without defense even though the decision made was reasonable.
What to do when a new revision of a document arrives
Each time a new revision of a drawing, an annex or the contract itself arrives, update the table with the new date and revision without deleting the previous entry: you need to be able to reconstruct later what version was in effect at the date a specific decision was made. A revision change that arrives mid-execution of an item is the situation where that history is most needed, because part of what was executed may correspond to the prior version.
It is also advisable to record who communicated the new revision and by what channel, and confirm receipt explicitly. A revision circulating only through a site WhatsApp group does not have the same value as evidence as one formally sent with signed receipt, if later it is necessary to prove from when it was required to apply it.
How Bloqbase supports joint reading of contractual documents
Bloqbase allows using the Contract Analysis module together with document management to maintain each document in the contractual framework, contract, annexes, drawings, specifications, budget, identified with its date and revision within the work context, rather than distributed across email folders and local versions.
The tool does not decide which document prevails or replace the legal interpretation of a contradiction: it organizes versions and dates so whoever must resolve the discrepancy, supervising architect, legal counsel, works with complete information from the beginning, instead of reconstructing it document by document.