Ambiguous Contract Language: 12 Real Examples
Certain phrases show up in contract after contract because they sound reasonable and commit to almost nothing. Here are 12 of the most common, what makes each one risky, and what to write instead.
July 20, 2026 · By ScopeWise Team
Undefined effort and quality standards
"Reasonable efforts" and "best effort" commit a party to trying, not to a result -- and "reasonable" is judged after the fact, often in a dispute, rather than defined up front. "Industry standard" has the same problem: standards vary by industry and by who you ask, so the phrase resolves nothing on its own. Write instead a specific, checkable standard -- a named framework, a response-time SLA, a defined process -- so both sides can independently verify whether it was met.
Open-ended scope qualifiers
"As needed" and "as appropriate" attached to scope or obligations leave the trigger for action undefined -- needed by whose judgment, appropriate by what standard. "Including but not limited to" turns a specific list into an open-ended one, since anything arguably similar to a listed item can be claimed as covered. Write instead a closed list with explicit exclusions, or a defined trigger condition ("if X occurs, then Y") rather than a discretionary qualifier.
Placeholders and vague timing
"TBD" left in a signed contract means a term was never actually agreed -- it should be resolved before signature, not carried into the executed document. "Approximately" attached to a date, quantity, or price introduces a range without stating what the range is. "Promptly" has no enforceable meaning without a number attached to it -- promptly could mean same-day to one party and two weeks to another. Write instead a specific date, a stated range with bounds, or a defined number of business days.
Conditional and discretionary phrases
"As applicable" quietly makes an obligation conditional without stating the condition, letting either party argue later that it did not apply. "Mutually agreed" for a term that was never actually negotiated defers a real decision to some future point, often under worse conditions than exist during the original negotiation. "From time to time" describing frequency of an obligation (reporting, audits, updates) sets no actual cadence. Write instead the specific condition, the agreed term itself, or a stated frequency.
Undefined breach and satisfaction standards
"Material breach" used without a definition leaves what counts as material -- and therefore what triggers termination rights -- open to interpretation exactly when it matters most, mid-dispute. "Satisfactory to client" as an acceptance standard is fully subjective and gives one party unilateral, unreviewable discretion over whether the other party gets paid or the contract proceeds. Write instead specific examples or thresholds that define a material breach, and objective, checkable acceptance criteria in place of a subjective satisfaction standard. ScopeWise's ambiguous-language scan is a deterministic rule-based check that runs against every uploaded document and flags exactly these phrase patterns -- not an LLM guess, but a direct scan for the language above -- see how it fits into a full SOW review.