When Contracts Get Ignored: The Cost of an Unenforced Handshake

Opening Scene

A landlord and tenant sign a lease that clearly states rent is due on the first of the month and specifies a late fee after the fifth. For the first year, the landlord never actually enforces the late fee, even when rent drifts to the fifteenth a few times. By year two, “rent by the fifteenth” has quietly become the real, unspoken arrangement — until the landlord suddenly decides to enforce the original terms, and the tenant, blindsided, feels like the rules changed overnight, even though, on paper, they never did.

In Plain English

A data contract that exists only as a document, with nothing actually checking whether it’s being honored, tends to decay the same way that lease did: violations creep in, nobody stops them, and the written terms drift away from the real, lived behavior of the systems involved. The contract isn’t technically broken — it’s just quietly ignored, until someone finally tries to enforce it and discovers how far reality has drifted from what’s on paper. An unenforced contract is, functionally, not much better than no contract at all.

The Old Way

Before enforcement was treated as inseparable from the contract itself:

Teams wrote schemas and contracts as documentation, satisfied that the agreement existed, without ever wiring up anything that actually checked compliance. The document became a historical artifact rather than a living constraint.
Small violations went unnoticed and unaddressed for so long that they became the de facto norm, even though they directly contradicted the written contract. Reality and documentation diverged silently.
When someone finally did try to enforce the original contract, it broke things that had come to depend on the drifted, undocumented reality — making enforcement itself feel like the disruptive event, rather than the years of unchecked drift that preceded it.

Treating enforcement as part of the contract from day one — not an optional add-on — is the only way to avoid this slow decay.

What’s Changing (and Why AI Is the Reason)

Organizations increasingly measure and report on contract compliance as an ongoing metric, not a one-time check performed when the contract was first written.
This ties into the same monitoring discipline covered in this content library’s dedicated data quality and observability series, since detecting drift over time requires the same continuous vigilance that quality monitoring already depends on.
AI systems consuming a dataset don’t notice, complain about, or informally adapt to a slowly drifting, unenforced contract the way a human analyst eventually might — they simply keep consuming whatever arrives, which means silent contract drift can go undetected for far longer, and cause far more damage, once an AI system is on the other end.

The Metaphor, Fully Extended

The Unenforced Lease	Contract Enforcement Concept
A late fee written down but never actually charged	A contract term written down but never actually validated
Rent quietly drifting to the fifteenth, unchallenged	A schema quietly drifting from its documented version, unchecked
The written lease and the real arrangement slowly diverging	The written contract and the actual data slowly diverging
Enforcement, when it finally happens, feeling like the disruption	Enforcement, when finally added, breaking things built on the drift

For Beginners: What to Actually Do

Learn to ask, for any contract you rely on, whether it’s actually being checked automatically or just trusted on faith.
Practice noticing small, seemingly harmless deviations from a documented contract before they become the unspoken norm.
Get comfortable flagging drift early, even when it seems minor, rather than assuming someone else will catch it eventually.

For Practitioners and Leaders: The Deeper Layer

Treat an unenforced contract as equivalent to having no contract, and prioritize enforcement tooling accordingly.
Regularly audit real data against its documented contract to catch drift before it becomes the accepted norm.
When re-enforcing a drifted contract, plan for the disruption honestly — communicate it as fixing years of drift, not as a sudden new rule.

Quick Recap

An unenforced data contract tends to drift silently until it barely resembles what’s written down.
Small, unaddressed violations become the de facto norm, setting up a painful reckoning later.
Continuous, automated compliance checking is what actually keeps a contract meaningful over time.
AI consumers are especially prone to silently absorbing drift, since they don’t notice or complain the way a human eventually would.

Where This Fits in the Series

Article 13 covered contracts crossing organizational boundaries. This article covered what happens when any contract goes unenforced. Article 15 looks at a genuinely new kind of contract term, driven by a new kind of buyer: AI training data.