Back to Resources
General Information

Restraint Clauses in ICT Contracting

Plain-English general information on restraint clauses in ICT contracting, what they are intended to do, and what factors may be relevant when they are considered in practice.

Restraint clauses can serve legitimate commercial purposes when they are reasonable in scope and properly applied. This page is intended to help contractors understand the relevant considerations in a balanced way, not to suggest any particular response or outcome.

This page is provided for general information only. It is intended to help contractors understand the topic at a high level, not to encourage any particular course of action, and not to replace legal advice on a specific contract or situation.

The short version

Restraint clauses are standard in many contractor agreements and can be reasonable when they are properly drafted and applied to protect legitimate business interests.

That said, whether a particular clause is likely to apply, and how it may be treated in practice, will usually depend on the specific wording, the surrounding facts, the timing, and the commercial context of the engagement.

For that reason, restraint clauses are best approached carefully and calmly. It is usually sensible to understand the clause properly, consider the relevant timing, and obtain advice if the issue is important or unclear.

What restraint clauses are generally trying to protect

Depending on the contract, a restraint clause may be intended to protect matters such as:

  • client relationships
  • confidential information
  • goodwill
  • the benefit of introductions or placement efforts
  • continuity of commercial arrangements

Not every clause will be appropriate in every situation, but it is important to recognise that these clauses can serve legitimate purposes when they are proportionate and properly framed.

What may matter in practice

When a restraint clause is considered, relevant factors often include:

  • the exact wording of the clause
  • how broad or narrow it is
  • the length of the restraint period
  • the activities it restricts
  • the role, client, or engagement it relates to
  • whether it is directed to a legitimate business interest
  • the bargaining context in which the contract was entered
  • the facts at the time the issue arises

Small differences in wording or circumstances can make a material difference. General commentary should not be treated as a substitute for reviewing the actual agreement.

Questions worth asking before drawing conclusions

  • What does the clause actually say, in full?
  • What conduct does it seek to restrict?
  • For how long does it operate?
  • Is it tied to a specific client, role, or opportunity?
  • What business interest is it trying to protect?
  • What are the current facts and timing of the engagement?
  • Is there any correspondence or conduct that may affect the position?

These questions do not answer the issue on their own, but they can help frame it more clearly.

A practical and balanced approach

If a restraint clause may be relevant, contractors often take a measured approach such as:

  • reading the actual contract wording carefully
  • avoiding assumptions based only on labels or summaries
  • considering whether the timing is appropriate for raising or reviewing any issue
  • keeping written records of relevant communications
  • obtaining independent legal advice if the clause is important, unclear, or contested

The aim should usually be to understand the position properly before making decisions, rather than reacting too quickly or relying on general impressions.

If contact is made about the clause

If a current or former agency raises a restraint clause, it is often sensible to:

  • take time before responding
  • read the clause and any correspondence carefully
  • keep communications factual and professional
  • avoid making broad assertions without checking the contract
  • seek advice if the issue carries legal or commercial risk

It is usually less helpful to assume that a clause is either automatically enforceable or automatically ineffective. Outcomes are rarely that simple.

Timing matters, but context matters too

Timing can be relevant, but it should be considered in a neutral and practical way.

The appropriate timing for any review, discussion, or decision will depend on the contract, the engagement stage, the procurement context, and the commercial circumstances. What may be manageable in one situation may not be appropriate in another.

For that reason, timing should be assessed case by case rather than treated as a universal rule.

A measured takeaway

Restraint clauses are common in ICT contracting and can be legitimate when properly applied. Equally, their effect will depend on the contract and the facts, not just the heading or the existence of the clause itself. The most sensible approach is usually to understand the wording, consider the specific context, and get appropriate advice if needed. This page is intended to inform contractors about the issue in plain English, not to encourage any particular action.

General information only. This page does not constitute legal, procurement, employment, or commercial advice for your specific circumstances. Nothing on this page should be relied on as advice about what you should do under a particular contract. If a restraint clause may affect a live decision, is disputed, or has been raised formally, independent legal advice should be obtained on the specific wording and facts.