10 Contract Red Flags to Watch For
Most contract disputes do not arise from unusual or exotic clauses — they arise from standard provisions that were poorly understood, inadequately negotiated, or simply not read carefully before signing.
Jump to section
Jump to section
Jump to section
Jump to section
Jump to section
Jump to section
Jump to section
Jump to section
Jump to section
Jump to section
Unlimited Liability
Unlimited liability means there is no ceiling on the financial exposure you can face if something goes wrong under the contract. In theory, a single incident could result in a claim worth many multiples of the contract value — covering the other party's lost profits, third-party claims, regulatory fines, and legal costs without any contractual limit.
Most well-drafted commercial agreements include a mutual liability cap — typically set at 12 months of fees paid or payable — to create financial certainty for both sides. The cap allows each party to understand and insure their maximum exposure before committing to the agreement.
The absence of any liability cap is a significant red flag, particularly in technology, services, and outsourcing contracts where a failure could cascade into very large downstream losses. Always check whether the contract contains a limitation of liability clause, what the cap is set at, and whether it applies to both parties equally.
Watch also for caps that are technically present but set so low as to be commercially meaningless — for example, a cap of one month's fees on a contract where a failure could cause weeks of operational disruption. A cap needs to be both present and set at a level that provides genuine protection.
Certain categories of claim are typically carved out of the cap even in well-drafted contracts — death and personal injury, fraud, and wilful misconduct should always be uncapped. But watch for indemnity obligations that are also carved out of the cap, as these can create significant uncapped exposure through a different mechanism even where the main liability cap looks reasonable.
One-Sided Termination Rights
A termination clause that allows only one party to exit the contract for convenience — without requiring proof of breach — creates a fundamental imbalance of power. The party with the unilateral exit right can walk away freely whenever the arrangement no longer suits them, while the other party remains bound and has no equivalent escape route.
This pattern is common in vendor-drafted agreements where the supplier reserves the right to terminate on short notice — for example, if the customer's payment history changes, if the vendor decides to discontinue a product, or simply at its discretion — while the customer can only exit by proving a material breach or waiting for the contract to expire.
The practical consequences can be severe. A customer who has built critical business processes around a vendor's platform may find themselves forced to migrate at short notice with no contractual right to transition assistance. A supplier who has invested heavily in serving a particular client may find the relationship terminated without compensation.
Always check whether termination for convenience rights are mutual. If they are not, push to make them so — both parties should have a clean exit right on equivalent notice terms. Also check notice periods: a very short notice period (7 or 14 days) in a complex services relationship is a red flag even if the right is technically mutual, because it provides no realistic time to transition.
Also watch for termination rights triggered by events outside your control — change of control provisions that allow the other party to terminate if your company is acquired, insolvency-adjacent triggers that activate before actual insolvency, or termination rights tied to financial covenants that you may not be able to guarantee.
Unilateral Variation Rights
A unilateral variation clause allows one party — almost always the vendor or the more powerful party — to change the terms of the contract, the price, or the service specification without the other party's consent. In a standard commercial relationship, any material change to agreed terms should require mutual written agreement. A clause that removes this requirement is a significant red flag.
Unilateral variation clauses appear in many forms. Some are explicit: 'We may update these terms at any time by posting a revised version on our website.' Others are buried in pricing clauses: 'Prices may be adjusted annually by up to the higher of CPI or 5%.' Others appear in service description clauses: 'We reserve the right to modify the features and functionality of the platform at our discretion.'
The risk is not just that terms will be changed — it is that you have no contractual basis to object when they are. If the vendor increases prices, removes a feature you rely on, or introduces new restrictions, a unilateral variation clause may mean your only remedy is to terminate rather than to enforce the original agreement.
When reviewing a contract, check every clause that uses phrases like 'we reserve the right to', 'at our discretion', 'from time to time', or 'subject to change'. These are signals that a unilateral variation right may be embedded in the provision.
Negotiate for a requirement that material changes require mutual written agreement, that price increases are subject to a defined cap and notice period, and that you have a right to terminate without penalty if a unilateral change materially adversely affects your position. At minimum, insist on meaningful advance notice of any changes so you have time to assess the impact and make alternative arrangements.
Broad Indemnity Obligations
An indemnity clause requires one party to compensate the other for specified losses — including losses caused by third-party claims. Unlike a standard damages claim, indemnity obligations often operate independently of fault and can bypass the usual legal rules on remoteness and mitigation, making them potentially far more valuable and far more dangerous than they initially appear.
The red flag is not the existence of an indemnity — indemnities are standard in commercial contracts — but the breadth of its scope. An indemnity triggered by any claim 'arising out of or in connection with' the contract is dramatically broader than one limited to claims arising from a material breach or proven negligence. The difference can be the difference between a manageable obligation and an open-ended one.
Watch particularly for indemnities that: run in one direction only (protecting the other party but not you); extend to affiliates, group companies, officers, and employees of the other party; include a duty to 'defend' as well as indemnify (creating a real-time obligation to fund litigation before any loss is established); are carved out of the limitation of liability cap entirely; or cover regulatory fines and penalties that your insurance may not cover.
Also check how the indemnity interacts with your insurance. Professional indemnity and public liability policies typically cover claims arising from your negligence, but many policies limit or exclude 'contractually assumed liability' — obligations you have taken on by contract that go further than your liability at law. Accepting a broad indemnity without confirming your insurance coverage can leave you contractually bound to pay sums your insurer will not cover.
The negotiating approach is to limit indemnities to third-party claims arising from material breach or proven negligence, ensure they are mutual, introduce a sub-cap on indemnity exposure even where indemnities are carved out of the main liability cap, and require notice and defence control provisions so you are not presented with a settled claim after the fact.
Auto-Renewal Without Adequate Notice
An auto-renewal clause automatically extends a contract for a further fixed term — often 12 months — unless one party actively serves a notice of non-renewal within a specified window before the current term expires. Miss the window by a day and you are locked in for another full term, with no right to exit without paying an early termination fee.
Auto-renewal clauses are extremely common in SaaS, software licensing, and services agreements, and are not inherently unreasonable — they provide continuity for both parties and avoid the need to renegotiate every year. The red flag is a combination of: a long renewal term (12 months or more); a short or narrow notice window (30 days or less, or a window that closes months before expiry); and significant early termination fees if you miss the window.
The practical risk is that renewal notices are easy to miss. The contract is signed, onboarded, and then forgotten about by the people responsible for managing it. The renewal date approaches, the notice window closes, and the contract auto-renews before anyone realises — committing the business to another year of fees for a service it may have already decided to move away from.
Before signing, check the renewal term length, the notice window for non-renewal, whether notice must be served in a specific form or to a specific recipient, and what happens if you miss the window. Negotiate for a longer notice window (90 days is preferable to 30), a shorter renewal term (month-to-month or 3-month rolling after the initial term), and confirmation that notice can be served by email.
After signing, implement a contract management process — diary the notice deadline at the point of signing, not when it approaches. Many businesses lose significant money each year simply because they fail to diarise auto-renewal notice deadlines when contracts are executed.
Vague or Absent Delivery Obligations
A contract that does not clearly define what the other party is obliged to deliver — in terms of scope, quality, timeline, and acceptance criteria — is one of the most common sources of commercial disputes. Without precise delivery obligations, it becomes very difficult to establish that a breach has occurred, to withhold payment, or to terminate for cause.
The red flag manifests in several ways: a service description that uses aspirational language ('we will endeavour to', 'we aim to', 'the parties will work together to') rather than binding commitments; a scope of work that is defined by reference to a proposal or sales document rather than a contractual schedule; delivery timescales that are described as 'indicative' or 'estimates'; and acceptance criteria that are absent or left to the vendor's sole discretion.
In technology and professional services contracts, vague delivery obligations are particularly dangerous because they allow a vendor to argue that whatever has been delivered constitutes satisfactory completion — regardless of whether it meets the customer's actual requirements. Without defined acceptance criteria, the customer has no contractual basis to reject a defective deliverable.
Always ensure that the contract — or a schedule attached to it — defines precisely what will be delivered, by when, to what standard, and how completion or acceptance will be determined. For software and technology projects, insist on a formal acceptance testing process with defined pass/fail criteria. For services, define the deliverables and the quality standard against which they will be assessed.
Also check whether the contract includes a change control mechanism — a formal process for agreeing changes to scope, timeline, and price. Without one, scope creep can be used to justify delays and cost increases that were never agreed, while disputes about what was and wasn't in scope can derail the entire project.
Intellectual Property Ownership Ambiguity
Who owns the intellectual property created under the contract is one of the most commercially significant questions in any services, development, or consultancy agreement — and it is one of the areas most frequently left ambiguous. Without a clear IP ownership clause, default rules apply, and those default rules often produce results that neither party intended or expected.
Under English law, the general rule is that the creator of an original work owns the copyright in it. This means that unless the contract expressly assigns IP to the customer, a contractor or agency that creates a website, software, marketing materials, or any other creative work retains ownership — even if the customer paid for it in full. The customer may have a licence to use the work, but they do not own it and cannot freely modify, sublicense, or transfer it.
The red flag is a contract that is silent on IP ownership, or that uses vague language such as 'all work product will belong to the client' without the formal assignment language required to actually transfer ownership under English law. An agreement to assign in the future is not the same as a present assignment — only the words 'hereby assigns' or equivalent language effect an immediate transfer.
Watch also for IP clauses that assign ownership of deliverables to the customer but carve out the contractor's pre-existing IP and tools — which is reasonable — while making the deliverables dependent on licences to that pre-existing IP that can be revoked or restricted. If the deliverables cannot function without the contractor's background IP, ownership of the deliverables alone may be commercially worthless.
Before signing any contract involving the creation of work product, confirm who owns the IP in deliverables, what licence rights are granted to pre-existing IP embedded in those deliverables, whether the assignment is immediate or merely an agreement to assign in the future, and whether the IP provisions survive termination of the contract.
Inadequate Data Protection Provisions
In any contract involving the processing of personal data — which includes almost any B2B services agreement where customer data, employee data, or end-user data is involved — the absence of adequate data protection provisions is a significant red flag, both commercially and legally.
Under UK GDPR and the Data Protection Act 2018, where a controller engages a processor to process personal data on its behalf, the contract between them must include specific mandatory provisions — covering the subject matter and duration of processing, the nature and purpose of processing, the type of personal data involved, the categories of data subjects, and the controller's instructions to the processor. Operating without these provisions in place exposes both parties to regulatory risk.
The commercial red flags go beyond legal compliance. Watch for: an absence of any obligation on the vendor to notify you of a data breach within a defined timeframe (UK GDPR requires notification to the ICO within 72 hours of becoming aware of a breach — you cannot meet that deadline if your vendor takes weeks to tell you); no obligation on the vendor to assist with subject access requests or other data subject rights; no restriction on sub-processing without your consent; no obligation to delete or return your data on termination; and no security standards defined or warranted.
Data protection indemnities — where the vendor agrees to indemnify you for losses arising from their breach of data protection obligations — are increasingly common and worth negotiating. However, they require careful drafting: the potential losses from a significant data breach (regulatory fines, notification costs, compensation to data subjects, reputational damage) can far exceed the contract value, and the indemnity is only valuable if the vendor has the financial capacity and insurance coverage to meet it.
Before signing any contract involving personal data processing, check that a compliant data processing agreement is either included in the contract or attached as a schedule, that the vendor's security obligations are defined and meet the standard required for the sensitivity of the data being processed, and that breach notification, subject rights assistance, and data return obligations are clearly addressed.
Unreasonable Non-Compete or Non-Solicit Restrictions
Non-compete and non-solicitation clauses restrict what you can do during or after the contract — who you can work with, what services you can offer, and which clients or employees you can approach. In the right context and with the right scope, they are a legitimate way to protect genuine business interests. Drafted too broadly, they can significantly restrict your commercial freedom for months or years after the relationship ends.
The red flag is a restriction that goes further than is reasonably necessary to protect the specific legitimate interest at stake. Common examples include: a non-compete that prevents you from working in your entire industry rather than just for named direct competitors; a geographic restriction that covers the whole world or entire countries when the actual relationship was limited to a specific region; a duration of 24 or 36 months for a short-term or low-value engagement; a non-solicitation clause that covers all of the other party's clients rather than only those you actually worked with; and restrictions that apply even if the contract is terminated due to the other party's own breach.
Under English law, non-compete clauses are restraints of trade and are presumed unenforceable unless the party relying on them can prove both a legitimate protectable interest and that the restriction is reasonable in scope, duration, and geography. Courts will not rewrite an overly broad clause to make it enforceable — they will simply strike it out entirely. This means a poorly drafted non-compete may create a chilling effect without actually being legally binding.
The practical risk is that many businesses comply with non-competes they would never need to — turning away clients, declining projects, or delaying new ventures — because they assume the clause is enforceable without taking legal advice. The cost of that compliance, in lost business and restricted operations, can be very significant.
Before accepting any post-term restriction, assess whether the other party has a genuine protectable interest, whether the scope is limited to the specific activities and relationships relevant to this contract, whether the duration is proportionate, and whether a narrower non-solicitation clause would achieve the same commercial purpose with far less impact on your business.
Governing Law and Jurisdiction in Unfamiliar Territories
The governing law clause determines which country's laws apply to interpret and enforce the contract. The jurisdiction clause determines which country's courts — or which arbitration tribunal — will resolve disputes. These clauses are often treated as boilerplate and ignored, but they can have a profound practical effect on your ability to enforce your rights and defend claims against you.
The red flag is a governing law or jurisdiction clause that selects a legal system you are unfamiliar with, that is geographically remote, or that is chosen primarily to favour the other party. A UK business signing a contract governed by the laws of Delaware and subject to the exclusive jurisdiction of courts in New York faces significant practical barriers to enforcing its rights — including the cost and complexity of engaging US lawyers, the need to understand unfamiliar legal concepts, and the difficulty of enforcing an English judgment against a US counterparty.
Mandatory arbitration clauses — particularly those requiring arbitration in a foreign jurisdiction — deserve special scrutiny. Arbitration can be an efficient and neutral dispute resolution mechanism, but it can also be expensive, slow, and inaccessible for smaller businesses. A clause requiring international arbitration under ICC or LCIA rules with a seat in Singapore may be entirely appropriate for a large cross-border transaction but completely disproportionate for a mid-market services agreement.
Also watch for jurisdiction clauses that are asymmetric — where the vendor can bring proceedings in their home jurisdiction but the customer must submit to exclusive jurisdiction elsewhere. These clauses can make it practically impossible for the customer to pursue a claim, which is often their purpose.
Where possible, negotiate for the governing law and jurisdiction to be your home jurisdiction, or a neutral jurisdiction that both parties are familiar with. For cross-border contracts, English law and English courts are widely respected and understood internationally — they provide a reasonable neutral choice for many international commercial agreements. Always consider the practical enforceability of any judgment or award before accepting a governing law or jurisdiction clause.
Ready to review your contract properly?
Upload your agreement and instantly understand risks, hidden clauses, and negotiation opportunities.