arrow_back LawSnap / Contract Patterns / The Captive Gatekeeper

The Captive Gatekeeper/The Acceptance Gate

A decision that controls payment, performance, or rights sits with a party who faces no deadline and no consequence for delay. Drafters install it as quality control — a trusted expert in the loop before anything is accepted. Responders find themselves stuck, unable to proceed or get paid, while someone else holds the key.

Appeared in 33 corpus episodes across multiple industries

On this page chevron_right

What It Is

One party's payment, performance, or right to proceed is contingent on approval from a designated decision-maker — who has no deadline to decide, no objective standard to apply, and no consequence for delay or refusal.

Two Readings

The same clause. Two entirely different contracts.

edit The Captive Gatekeeper reads this as

You're buying something you can't fully evaluate yourself. Putting a trusted expert in the approval seat means work doesn't get accepted — and you don't pay — until it actually meets your standard. This is rational risk management, especially when the subject matter is technical or the stakes are high.

visibility The Acceptance Gate reads this as

You can complete every obligation perfectly and still not get paid. The gatekeeper controls your revenue with no obligation to act, no deadline forcing a decision, and no accountability for the costs of delay. You're dependent on someone who doesn't bear the consequences of their own inaction.

Recognition Signals

Contract language that signals this pattern is present.

  • "Subject to Client's acceptance" or "upon Client's written approval" with no timeline defined
  • "Architect's determination" or "Engineer's certification" required before payment
  • "At Company's sole discretion" controlling a right or payment trigger
  • Acceptance/approval provisions with no deemed-approval language
  • "Pre-launch review" or "compliance review" with no defined criteria or deadline

The tell: who bears the cost if the gatekeeper delays? If it's the party seeking approval, the clause is a Captive Gatekeeper.

What to Do

If you're the drafter

Define objective criteria so disputes become about standards, not feelings. The gatekeeper's authority is more defensible — and harder to challenge — when anchored to objective standards in an exhibit or schedule.

If you're the responder

Add four elements: (1) objective criteria for approval, (2) a response deadline (typically 10–15 business days), (3) deemed-approval language if the deadline passes without response, (4) an escalation or dispute mechanism for rejected work. Without all four, the clause is a weapon.

Where It Appears

Cross-industry appearances from the LawSnap corpus.

IndustryHow it appears
ConstructionArchitect controls change orders and payment certification — no deadline, no liability
SaaS / MSACustomer acceptance gates revenue recognition with no compulsion to decide
AI / PlatformPre-launch compliance review with no criteria, no timeline, no appeal
InsuranceInsurer controls defense counsel and settlement strategy
Real EstateLender's appraiser veto with no challenge mechanism
Oil & GasRoyalty payment contingent on operator's unilateral production calculations

LawSnap Contract Pattern Library

37 named structural patterns extracted from 107 attorney interviews and MCLE war stories across trucking, healthcare, SaaS, construction, and more. Lawyers across every industry were describing the same traps in completely different vocabulary. We cataloged them.

Browse all patterns arrow_forward

Get notified when new patterns are added.

We're cataloging all 37 patterns from the corpus. One email when new patterns go live — nothing else.

One email per update. No newsletter. Unsubscribe anytime.

Also on LawSnap