Take-It-or-Leave-It Term Audit¶
Coercion-focused review — instantiates Access-Conditioned Bundle Decoupling
Stress-tests a nonnegotiable package for whether 'leave it' is a real choice — probing the affected party's dependency, hidden add-ons, excessive waivers, and the absence of any exit.
A per-condition screen asks whether each term is necessary; it can pass every term and still miss the real problem, which lives in the offer, not the clauses. The Take-It-or-Leave-It Term Audit examines the package as a take-it-or-leave-it proposition to a party that may have no real ability to walk away. Its defining move is to make realistic refusal the object of study: it profiles how dependent the affected party is — how essential the access, how few the alternatives, how high the switching costs — and asks whether "leave it" is a genuine option or an empty one. Where the checklist evaluates clauses, this audit evaluates whether apparent acceptance reveals preference or captivity, and whether any exit exists at all.
Example¶
A delivery platform hands couriers a single nonnegotiable agreement: accept mandatory arbitration, a class-action waiver, unilateral changes to the pay formula, near-exclusive availability expectations, and broad data collection — in full, or you cannot work. The audit refuses to read those as freely accepted just because couriers clicked "agree." It first profiles dependency: for many couriers this is primary income, and in their city one platform dominates, so alternatives are thin and switching costs high — meaning "leave it" is barely a choice. It then reads the package against that captivity: the broad data collection is an add-on unrelated to dispatching a delivery; the waivers are heavy relative to what the work requires; and there is no way for a courier to carry their ratings and job history to a rival, so exit is effectively blocked.
The finding is not "these clauses are individually illegal" but "these terms are riding on the leverage of essential income access offered take-it-or-leave-it, and the lack of ratings portability means refusal isn't real." It flags which terms exploit the dependency and calls for the exit route that would make refusal possible.
How it works¶
- Profile the dependency first. The audit characterizes how captive the affected party is — essentiality of the access, availability of substitutes, switching costs — because that is what decides whether "leave it" means anything.
- Read the package against captivity. Terms are judged not in isolation but as demands made under that leverage: hidden add-ons unrelated to the core access, waivers excessive for what access requires, and unilateral powers that a party with real alternatives would never accept.
- Test for a real exit. It asks whether the affected party can actually leave — whether a substitute is reachable and whether history, data, or standing can be ported out — treating the absence of exit as the strongest sign that acceptance was coerced.
- Distinguish captivity from standardization. It separates terms that are merely nonnegotiable for efficiency from terms that exploit the party's inability to refuse.
Tuning parameters¶
- Dependency weighting — how heavily the affected party's lack of alternatives counts. Weight it high to protect captive parties, but too high and it flags ordinary standard-form contracts as coercive.
- Refusal-realism bar — what qualifies as a genuine ability to walk away: existence of substitutes, exit costs, and portability of what the party would leave behind.
- Add-on sensitivity — how aggressively to flag conditions that have nothing to do with the core access but are folded into the same accept-or-nothing offer.
- Waiver scrutiny — the threshold at which a rights-waiver counts as excessive relative to what the access legitimately needs.
- Remedy orientation — whether the audit only flags exploitation or also prescribes the fix (decouple this term, provide that exit).
When it helps, and when it misleads¶
Its strength is catching the coercion that per-clause review structurally misses: every term can survive a necessity test while the package, offered take-it-or-leave-it to a dependent party with no exit, is still extracted rather than agreed. It reframes "but they accepted it" from an answer into a question.
Its failure mode is over-reading. Plenty of contracts are nonnegotiable for sound efficiency reasons, and treating all standard-form terms as coercive would freeze ordinary commerce — the audit has to tell captivity from mere standardization. Its classic degeneration is collapsing into a disclosure check — "the terms were shown, so they were accepted" — which misses that being told a term is not the same as being able to refuse it. The discipline that keeps it honest is anchoring on genuine dependency and the absence of alternatives or exit — the substance of an unconscionable contract of adhesion, not the mere fact of one[n1] — rather than on whether the paper was signed.
How it implements the components¶
The audit realizes the coercion-diagnosis side of the archetype — it characterizes the affected party's position and whether escape exists, rather than testing individual conditions or building the alternative:
affected_party_dependency_profile— its core: the read on how captive the affected party is (essentiality, substitutes, switching costs) that determines whether "leave it" is a real option or an empty one.exit_and_portability_support— the audit makes a realistic exit — reachable substitutes, and the ability to port out history or data — the operative test of whether refusal is possible, and flags its absence as a decoupling failure to be remedied.
It does not test each condition's necessity (Necessity/Proportionality Checklist), build the unbundled option a party would refuse into (Standalone Base-Service Path), or sever the exploitative term it identifies (Severability Clause and Review Rule).
Related¶
- Instantiates: Access-Conditioned Bundle Decoupling — the audit is what tells coerced acceptance apart from genuine agreement to the package.
- Consumes: a read on the affected party's dependence and alternatives (from an Access Dependency Heat Map).
- Sibling mechanisms: Standalone Base-Service Path · Necessity/Proportionality Checklist · Severability Clause and Review Rule · Rebundling Drift Audit · Purpose-Bound Security Condition Record · Coercion Safeguard Review
Editorial Notes¶
Form Classification¶
Form family: Assessment, Review & Assurance
Rationale: Take-It-or-Leave-It Term Audit operates as a bounded evaluation of existing evidence or work that produces a finding or disposition because it stress-tests a nonnegotiable package for whether 'leave it' is a real choice — probing the affected party's dependency, hidden add-ons, excessive waivers, and the absence of any exit.
Independent corroboration: The frozen evidence defines Take-It-or-Leave-It Term Audit as 'Stress-tests a nonnegotiable package for whether 'leave it' is a real choice — probing the affected party's dependency, hidden add-ons, excessive waivers, and the absence of any exit', so its operative form is Assessment, Review & Assurance.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Law & Governance
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Universal
Rationale: Take it or leave it term audit derives most directly from law and governance's rule, authority, accountability, and due-process tradition; its defining operation is to stress-tests a nonnegotiable package for whether 'leave it' is a real choice — probing the affected party's dependency, hidden add-ons, excessive waivers, and the absence of any exit.
Related originating lineages:
- Economics & Finance — Economics, finance, and mechanism-design practice supplies a parallel or contributing lineage for the mechanism's defining operation: stress-tests a nonnegotiable package for whether 'leave it' is a real choice — probing the affected party's dependency, hidden add-ons, excessive waivers, and the absence of any exit.
- Public Administration & Policy — Public administration's program, regulatory, and service-governance tradition provides a formative adjacent lineage for the same take it or leave it term audit operation.
Review resolution: Both blind reviewers independently select law_governance as the primary historical origin for the concrete operation—Stress-tests a nonnegotiable package for whether 'leave it' is a real choice — probing the affected party's dependency, hidden add-ons, excessive waivers, and the absence of any exit. The queued differences concern alternate origin disagreement, origin mode disagreement, encyclopedia synthesis disagreement, not the primary lineage. I retain every alternate that either reviewer explains, without a numeric cap, and choose origin_mode=cross_disciplinary_synthesis because the reviewers' combined evidence identifies material construction from multiple disciplines. domain_reach=universal records later portability rather than multiplying historical origins; confidence=high is the conservative shared evidentiary level, and encyclopedia_synthesis=true preserves either reviewer's affirmative synthesis finding.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
This audit diagnoses coercion but cures none of it: making refusal real is the job of the Standalone Base-Service Path (something to refuse into) and the Severability Clause and Review Rule (a way to cut the exploitative term). Its whole value rides on one distinction it must never blur — nonnegotiable is not the same as coercive. Standard forms exist for good reasons; the audit earns its keep only by separating those from terms that exist because the other side could not say no.
[n1] A contract of adhesion is a standardized, take-it-or-leave-it agreement offered by the stronger party without room to negotiate. Such contracts are not automatically invalid — courts intervene on grounds like unconscionability, which typically requires both an absence of meaningful choice (procedural) and terms unreasonably favorable to the drafter (substantive). The audit mirrors that two-part test: dependency/no-exit on one side, exploitative terms on the other. ↩