Condition Precedent Clauses in Australian Contracts

Alex Solo
byAlex Solo13 min read

A condition precedent can decide whether a contract actually takes effect, whether a party has to perform, or whether a deal can fall over without liability. Businesses often get caught by this when they sign too early, assume a verbal assurance is enough, or fail to spell out who must do what to satisfy the condition. Another common mistake is treating a condition precedent like a vague milestone, then discovering there is a dispute about timing, evidence, or whether the obligation was ever triggered.

If you are reviewing a supply agreement, commercial lease, asset sale, shareholder deal or services contract, this clause deserves real attention before you sign.

The practical questions are simple: what exactly must happen, who is responsible for making it happen, when must it happen, and what if it does not? The legal effect can be much less simple. This guide explains how a condition precedent in contracts works in Australia, what founders and SMEs should check, and the mistakes that most often create expensive disputes.

Overview

A condition precedent is an event or requirement that must be satisfied before a contract, or a particular obligation under it, becomes binding or enforceable. In Australian contracts, the wording matters a lot because it affects whether parties must perform immediately, later, or not at all if the condition is not met.

  • Identify whether the condition applies to the whole contract or only a specific obligation.
  • Check exactly what must occur, including documents, approvals, finance, consents or other objective steps.
  • Confirm who must satisfy the condition, who pays the cost, and whether both parties must cooperate.
  • Set a clear deadline, evidence requirements, and a process for giving notice that the condition has been met or waived.
  • State what happens if the condition is not satisfied, including termination rights, refund arrangements and ongoing obligations.

What Condition Precedent in Contracts Means For Australian Businesses

A condition precedent is usually a legal switch: until the condition is met, a party may not have to proceed.

In plain English, the clause says that something has to happen first. Only then does the contract commence fully, or only then does a particular promise become enforceable. That “something” might be finance approval, landlord consent, board approval, a licence being granted, due diligence being completed, or a third party signing a related agreement.

This matters because many business owners assume signing the contract means everything is locked in from that moment. Often it is not. Sometimes the contract is binding straight away but performance is suspended until the condition is met. In other cases, the contract only becomes operative once the condition is satisfied. The exact wording decides the outcome.

Common examples in business contracts

Condition precedent clauses appear in many everyday commercial documents. You will often see them in:

  • business sale agreements, where completion depends on finance, due diligence or landlord consent
  • commercial leases, where entry may depend on development approval, fitout approval or the landlord completing works
  • supply and distribution agreements, where obligations start after product certification or minimum onboarding steps
  • shareholder and investment documents, where funding depends on documents being signed or corporate approvals being obtained
  • service agreements, where commencement may depend on access credentials, onboarding information or regulatory clearance

Condition precedent versus condition subsequent

A condition precedent happens before an obligation takes effect. A condition subsequent is different: it is an event that can bring an existing obligation to an end if it occurs later.

That distinction matters before you sign. If a clause is drafted loosely, parties can end up arguing about whether they were already bound and in breach, or whether the obligation never started in the first place.

Does the condition need to be objective?

Yes, as much as possible. A condition precedent works best when it can be clearly proved.

For example, “subject to the purchaser being satisfied with due diligence” is much riskier than “subject to the purchaser confirming in writing by 5 pm on 30 June 2026 that due diligence is satisfactory in its absolute discretion”. The second version gives a deadline, a method and evidence.

If the condition is vague, the parties may disagree about whether it has been met, whether a party acted reasonably, or whether the clause is even enforceable. This is where founders often get caught when they rely on a provider's standard terms or copy wording from another deal.

Must parties try to satisfy the condition?

Usually, yes, if the contract says so or if cooperation is implied by the deal.

Australian contracts commonly include an obligation on one or both parties to use reasonable endeavours, best endeavours, or all reasonable steps to satisfy a condition precedent. Those phrases are not identical. Their practical effect depends on context and drafting.

If the contract says a party must use reasonable endeavours to obtain landlord consent, that party cannot usually sit back and do nothing. They may need to prepare documents, answer follow-up questions and respond within a reasonable time. If they fail to do that, the other side may argue the condition was not met because of that party's own inaction.

Can a condition precedent be waived?

Sometimes, but only if the contract allows it or the condition exists for the benefit of the party seeking to waive it.

For example, a finance condition in favour of a buyer may sometimes be waived by the buyer. A condition requiring regulator approval may not be capable of simple waiver if the approval is legally necessary for the transaction. The contract should say:

  • whether waiver is permitted
  • who may waive the condition
  • whether waiver must be in writing
  • whether waiver of one condition affects any others

Before you rely on a verbal promise that “we will just waive that later”, check the actual clause. Many disputes start with informal assumptions that never made it into the signed document.

The key legal issue is not whether a condition precedent exists, but whether the clause clearly allocates responsibility, timing and consequences.

Before you sign a contract with a condition precedent, you want to know exactly what the clause does in real life. If the condition is not met, can you walk away? Do you recover your deposit? Are you still bound by confidentiality, exclusivity, restraint, or costs provisions? Is the other party obliged to help satisfy the condition, or can they quietly let the deal expire?

1. What exactly is the condition?

The clause should describe the required event with enough detail that an outsider could tell whether it happened. Broad phrases create room for argument.

Look for specifics such as:

  • the document, consent or approval required
  • the person or body who must issue it
  • any standard that must be met
  • the date by which it must occur
  • the evidence needed to confirm satisfaction

If the clause simply says “subject to approvals”, that is usually too vague. Which approvals? From whom? For what purpose? By what date?

2. Who is responsible for satisfying it?

The contract should nominate the responsible party, and sometimes both parties.

For example, if a lease assignment needs landlord consent, the outgoing tenant may need to request consent, the incoming tenant may need to provide financial information, and the landlord may need to respond under the lease process. Without a clear allocation, each party may blame the other if the deadline passes.

It also helps to state who pays for the process. This often matters with external advisers, application fees, searches, certification or third party legal costs.

3. What standard of effort applies?

A party should not be left guessing whether they must merely try, try hard, or exhaust every realistic option.

The drafting may use phrases such as:

  • reasonable endeavours
  • all reasonable endeavours
  • best endeavours
  • promptly do all things reasonably necessary

These phrases can lead to different expectations. If the deal is important, define practical steps rather than relying only on abstract effort standards. For example, require a party to submit the application within a set number of business days, answer information requests promptly, and provide copies of correspondence.

4. Is there a clear deadline and notice process?

Every condition precedent should have an expiry date and a notice mechanism.

Without a deadline, the contract can drift. That creates uncertainty for staffing, cash flow, stock orders and parallel negotiations. The contract should say when the condition must be satisfied, whether the period can be extended, and how notice must be given if the condition is met, waived or not satisfied.

Good drafting often covers:

  • the sunset date
  • how and when a party notifies satisfaction
  • what evidence must accompany the notice
  • whether time can be extended by agreement
  • what happens if neither party gives notice by the deadline

5. What happens if the condition is not met?

This is often the most commercially important part of the clause.

The contract should deal with the consequences directly. Otherwise, parties may argue about termination rights, repayment of money already paid, and whether any ongoing obligations survive.

Check whether the contract says:

  • the agreement ends automatically, or only if a party gives notice
  • either party may terminate, or only one party
  • deposits, prepayments or setup fees must be refunded
  • confidentiality and other protective clauses continue
  • a party loses rights if it caused the failure of the condition

If you are about to spend money on setup before the condition is met, this section matters even more. A business can end up paying for fitout, onboarding or supplier commitments on the assumption the deal will proceed, only to find the triggering condition never occurred.

6. Is the condition legally necessary, or just a commercial protection?

Some conditions are there because the deal cannot lawfully proceed without them. Others are there to protect one party's commercial position.

That difference affects whether waiver is realistic. If a transaction requires a statutory approval, you may not be able to proceed lawfully without it. If the condition is only there for your comfort, such as internal board approval or finance approval, the contract may allow you to waive it if you choose.

Before you accept the provider's standard terms, check whether a so-called condition precedent is actually masking a broader risk allocation issue.

7. Are there Australian law issues sitting behind the clause?

The clause does not operate in a vacuum. Other legal issues can affect how useful or risky it is.

Depending on the deal, you may also need to consider:

  • whether the counterparty has authority to sign
  • whether required licences, permits or registrations are actually obtainable
  • whether a landlord or franchisor consent process has mandatory steps
  • whether misleading statements were made about how easily the condition would be met
  • whether Australian Consumer Law issues arise in pre-contract representations

A well-drafted condition precedent does not fix inaccurate assumptions. If the other party assured you that approval was “just a formality”, you still need the contract to deal with the possibility that it is delayed or refused.

Common Mistakes With Condition Precedent in Contracts

The biggest mistake is treating a condition precedent like boilerplate when it often controls whether the deal lives or dies.

Founders and SMEs usually run into trouble in familiar ways. The clause looks simple, the commercial relationship feels cooperative, and everyone wants to move quickly. Then timing slips, approvals stall, or money is spent before the legal trigger is met.

Using vague wording

Words like “subject to approval” or “subject to satisfactory due diligence” are often too loose on their own. They do not say whose approval, what counts as satisfactory, or how the decision is communicated.

The main risk is uncertainty. A vague clause can invite an argument that one party is acting unreasonably, while the other argues the condition was always discretionary.

Failing to allocate responsibility

If no one is clearly tasked with obtaining the consent or approval, the deal can stall through inertia. This is common in property, procurement and multi-party transactions.

For example, a supplier agreement may depend on a customer providing technical access information. If the contract does not say the customer must provide that information by a specific date, the supplier may be blamed for missing a commencement deadline it could not control.

Spending money too early

Businesses often commit funds before the condition is satisfied because they are trying to keep momentum. That is commercially understandable, but legally risky.

Common examples include:

  • ordering stock before finance is approved
  • booking contractors before landlord consent is received
  • hiring staff before a key client agreement becomes unconditional
  • paying a deposit without clear refund wording

Before you spend money on setup, check whether the contract allows recovery if the condition fails. If not, you may be carrying that risk yourself.

Relying on verbal assurances

A party may say the approval is routine, the consent will be quick, or the clause is “just there for formality”. Those statements can be misleading, but proving what was said later is not easy.

The safer approach is to put the process, deadline and consequence in the contract. Before you rely on a verbal promise, ask for the clause to reflect the real commercial understanding.

Ignoring waiver mechanics

Some parties assume they can simply waive the condition if they want to proceed. That is not always true.

If the clause requires written waiver, follow that process. If the condition benefits both parties, one side may not be able to waive it unilaterally. If the condition concerns legal compliance, waiver may not solve the underlying issue.

Missing the sunset date

Deadline management sounds administrative, but it often decides the legal outcome. If the condition is not met by the sunset date, rights may expire automatically or a termination right may arise.

This can be especially messy if parties continue acting as if the contract is on foot after the deadline. Their conduct may create fresh disputes about variation, waiver, estoppel or whether obligations continued informally.

Forgetting survival clauses

Even if the condition is not met and the contract ends, some obligations may survive. Confidentiality, intellectual property protections, exclusivity, costs, return of information and dispute resolution clauses are common examples.

Check the termination and survival wording together. A failed condition precedent does not always mean the parties walk away with no continuing obligations.

Copying a clause from another deal

A condition precedent that worked in one transaction may be a poor fit for another. A lease consent process is not the same as a software onboarding dependency or an investment completion step.

This is where generic precedent wording can cause real trouble. The clause needs to match the deal, the timing, the evidence available, and the commercial risk each side is accepting.

FAQs

Is a contract binding if it contains a condition precedent?

Sometimes yes, sometimes only partly. A contract can be signed and binding, but performance may be suspended until the condition is satisfied. In other cases, the contract may not become fully operative until the condition occurs. The wording is crucial.

Can a party deliberately stop a condition precedent from being met?

Usually not, especially if the contract requires that party to use reasonable endeavours or cooperate. A party that causes the failure of the condition may lose the right to rely on that failure, depending on the drafting and circumstances.

What happens if the condition precedent is never satisfied?

The contract should say what happens. It may terminate automatically, allow one or both parties to end it by notice, or continue if the parties extend the deadline or waive the condition. Refunds and survival obligations should also be checked.

Can a condition precedent be waived in Australia?

Often yes, but only if the contract permits waiver or the condition exists solely for the benefit of the party seeking to waive it. A written waiver process is best, and some legally required approvals cannot simply be waived.

What is a simple example of a condition precedent?

A buyer signs a business sale agreement, but completion only occurs if finance approval is obtained by a stated date. Until that approval is received, the buyer may not be required to complete the purchase, depending on the contract wording.

Key Takeaways

  • A condition precedent is a trigger that must be satisfied before a contract, or a specific obligation under it, takes effect.
  • The wording matters because it determines what must happen, who is responsible, when it must occur, and whether the condition can be waived.
  • Before you sign, check the clause for objective drafting, a clear deadline, notice requirements, effort obligations, and consequences if the condition is not met.
  • Common business mistakes include vague wording, spending money too early, relying on verbal assurances, and missing the sunset date.
  • The safest approach is to tailor the clause to the actual deal rather than copying generic precedent wording.

If you want help with contract review, drafting contract clauses, negotiating termination rights, reviewing approval and consent requirements, and checking refund and risk allocation terms, you can reach us on 1800 730 617 or team@sprintlaw.com.au for a free, no-obligations chat.

Official Sources to Check

Rules and regulator guidance can change. Check the current official material most relevant to this issue before relying on the article:

Alex Solo
Alex SoloCo-Founder

Alex is Sprintlaw’s co-founder and principal lawyer. Alex previously worked at a top-tier firm as a lawyer specialising in technology and media contracts, and founded a digital agency which he sold in 2015.

Need legal help?

Get in touch with our team

Tell us what you need and we'll come back with a fixed-fee quote - no obligation, no surprises.

Need support?

Need help with your business legals?

Speak with Sprintlaw to get practical legal support and fixed-fee options tailored to your business.