Execution is only valuable when the document being executed accurately records the decision that was made.
The Week 4 mistake materials distinguish two very different problems. One is signing a document without reading it. The other is where both parties actually reached an agreement, but the written document fails to record that agreement correctly.
The first problem is primarily one of signature discipline. The second may engage rectification.
For leaders, both are contract-control failures.
The Strategic Context
Complex contracts are assembled from multiple sources:
- heads of agreement;
- tender responses;
- negotiation mark-ups;
- schedules;
- technical specifications;
- pricing tables;
- approval papers;
- execution versions.
A transaction can be commercially agreed and still be documented incorrectly.
The Week 4 notes use Joscelyne v Nissen to illustrate rectification where the written contract omitted household expense obligations that the parties had actually agreed.
The PowerPoint also refers to unilateral mistakes in written terms and the equitable response in Taylor v Johnson.
Current Australian rectification doctrine requires independent verification. [FACT CHECK REQUIRED]
What Leaders Commonly Misread
The first mistake is assuming signature eliminates document error.
A signed contract may still contain a drafting mistake, missing schedule or incorrect number.
The second is assuming “I did not read it” is normally enough to escape the document. The Week 4 notes use L'Estrange v Graucob to emphasise the general importance of reading what is signed, while also introducing the separate doctrine of non est factum.
The third is confusing rectification with rewriting a bad bargain. Rectification is presented in the source as a mechanism for correcting the written instrument so it reflects an agreement already reached.
The fourth is failing to preserve negotiation evidence. If the organisation cannot prove the prior common intention, correction becomes more difficult.
Reframing the Issue
The strategic question is:
Can the organisation prove that the executed document is the same commercial decision that was approved?
That requires traceability between:
- negotiated position;
- internal approval;
- final drafting;
- execution copy.
If any of those states diverge, governance has failed.
Strategic Analysis: The Contract Version Problem
Large programs create version risk.
A pricing schedule may be updated while the scope schedule remains old. A negotiated liability clause may disappear during document consolidation. A unit price may be entered incorrectly. A technical requirement may remain in a draft but not the signed copy.
These problems are often treated as administrative mistakes. They are actually failures in decision integrity.
Hypothetical example: A project board approves a supplier variation based on a unit price of $1,250 per item. The executed document accidentally records $12,500. Both parties had negotiated and approved the lower amount, but the error is not discovered until invoicing begins.
Whether rectification is available depends on current law and evidence. The management lesson is immediate: document control must demonstrate what the agreed position was before signature.
The same principle applies to omitted obligations. If both parties agreed that the supplier would provide commissioning support but the final contract omitted it, the project needs evidence of the common intention and should escalate immediately rather than relying on assumption.
Decision Framework
Before execution, verify:
Commercial baseline
What position was finally agreed by authorised negotiators?
Approval alignment
Did internal decision-makers approve that same position?
Document completeness
Are all referenced schedules and attachments included?
Version integrity
Is the execution copy the approved final version?
Error resolution
What process applies if a discrepancy is discovered?
Evidence
Are negotiation records and approvals retained?
For high-value contracts, these should be independently checked by someone other than the primary drafter.
From Strategy to Execution
Immediate action: introduce a pre-execution reconciliation for major contracts. Compare final commercial terms against the approved negotiation summary.
Medium-term capability building: establish controlled document versioning and a single execution repository. Eliminate local copies being treated as authoritative after signature.
Long-term strategic positioning: integrate contract data digitally so key obligations, pricing and risk positions can be compared automatically with approval records.
The objective is not administrative neatness. It is preventing a documentation error from becoming a material commercial dispute.
Governance Implication
For portfolio leaders, document error should be tracked as a recurring control failure rather than an isolated drafting problem. Repeated discrepancies between approved terms and executed documents can indicate overloaded commercial teams, weak version control or fragmented accountability between technical, procurement and legal functions. The corrective action is therefore systemic as well as contractual.
Signals to Monitor
Warning signs include missing attachments, multiple files labelled “final”, manual transcription of prices, execution packs assembled under severe time pressure, negotiators not reviewing the final copy, and project teams operating from a draft rather than the executed agreement.
Questions for the Leadership Team
- How do we prove the executed contract matches the approved commercial decision?
- Who performs the final reconciliation?
- How are schedules and referenced documents controlled?
- Can we reconstruct the parties' prior agreement if an error is discovered?
- Are teams using the executed version after handover?
- What material contracts currently contain unresolved drafting inconsistencies?
Closing Perspective
A contract is not secure merely because it has signatures.
It is secure when the organisation can demonstrate that the executed document accurately carries the decision, risk allocation and obligations that leadership intended.
Related article: Contract Certainty: Why Vague Agreements Transfer Control Away From the Parties
Related article: Terms or Talk? Why Pre-Contract Statements Can Change Commercial Exposure
About EraNorth Insights
EraNorth Insights publishes practical analysis on strategy, projects, operations, transformation and decision intelligence for professional and organisational use. About EraNorth.