Selected cases

High Court of Australia · [2023] HCA 38

Real Estate Tool Box Pty Ltd v Campaigntrack Pty Ltd

A software developer copied protected code while building a replacement real estate marketing platform.

High Court of Australia6 Dec 2023

Plain-English explainers, not legal advice. Use the linked official source for section-level detail, and get advice for your situation.

Get legal help

Start here

Quick read

  • Commissioning software does not make a client automatically liable for a developer's hidden copying.
  • A software developer copied protected code while building a replacement real estate marketing platform.

Use this to check

  • Give developers an express written instruction not to copy third-party material
  • Ask where source code, libraries, data and templates came from
  • Use IP warranties, assignments, audit rights and indemnities

Decision snapshot

  1. What happened

    • Developer David Semmens had earlier copied Process 55 code when creating DreamDesk.
    • Campaigntrack later bought both systems and shut DreamDesk down.
    • Biggin & Scott wanted a replacement, and its director expressly instructed Mr Semmens to build one that did not breach anyone else's intellectual property.
    • Mr Semmens nevertheless copied DreamDesk code, database material and PDFs into Real Estate Tool Box.
  2. What the court had to decide

    • Had the businesses and directors sufficiently sanctioned, approved, countenanced or otherwise authorised Mr Semmens' copyright infringement, including through indifference after concerns emerged?
  3. What the court decided

    • The High Court unanimously allowed the appeal and held that none of the appellants authorised the infringing acts.
    • The developer remained liable for his own copying, but the facts did not support the additional inference that the businesses and directors had authorised it.
    • Authorisation is fact-sensitive and requires sufficient involvement, not liability imposed simply because the infringement benefited the business.

Practical impact

Practical read

  • Commissioning software does not make a client automatically liable for a developer's hidden copying.
  • However, a clear no-infringement instruction is only a starting point.
  • Businesses should test provenance, contract for ownership and warranties, and act promptly when warning signs become credible.

Useful next steps

  • Give developers an express written instruction not to copy third-party material
  • Ask where source code, libraries, data and templates came from
  • Use IP warranties, assignments, audit rights and indemnities
  • Investigate credible concerns rather than relying on repeated assurances
  • Keep version-control and licence records for commissioned software

One developer worked across competing platforms

Mr Semmens had worked on a real estate marketing system called Process 55. He later helped create DreamDesk and admitted in 2016 that he had copied Process 55 material. Campaigntrack bought the rights in both systems, shut DreamDesk down and encouraged customers to move to Campaigntrack.

Biggin & Scott did not want to return. Its director instructed Mr Semmens to build a new web-to-print platform that did not breach another company's intellectual property. That project became Real Estate Tool Box.

The replacement still contained copied material

Despite the instruction, Mr Semmens and developers under his supervision reproduced all or parts of DreamDesk source code, database and table works, and PDF works. Using Toolbox also reproduced a substantial part of the protected source code.

The developer did not appeal the orders against him. The High Court case was about secondary liability: whether the clients, companies and directors had gone far enough in sanctioning, approving or countenancing the infringement to be treated as authorisers.

QuestionEvidence a business should keep
Who wrote the code?Repository history and contributor identities
What was reused?Third-party software and content register
Who owns each contribution?Employment terms and contractor assignments
What licences apply?Licence text, version and compliance record

Why authorisation was not proved

Authorisation requires a close assessment of all the facts. Benefit from the infringement, a commercial relationship with the infringer or the ability to ask questions does not automatically establish liability.

The High Court restored the trial result for the appellants. The director's instruction was genuinely directed against infringement, he repeatedly sought assurances, and the evidence did not justify the inference that the appellants had sufficiently involved themselves in or accepted the copying. The Court also rejected an attempt to build authorisation from later indifference without the necessary factual foundation.

How to commission software with a clean IP trail

A written promise not to infringe is useful, but software provenance should be managed throughout the project. Ask for visibility over repositories and third-party dependencies, especially when the developer has worked on a competing product.

The contract should match the operational process. Ownership clauses do not transfer rights the developer never owned, and an indemnity may be worth little if the supplier lacks assets or insurance. Early evidence checks are usually more valuable than a claim after launch.

Key points

  • Define permitted reuse and prohibited source material
  • Require written disclosure of open-source and third-party components
  • Make IP assignment cover every employee and subcontractor contribution
  • Use staged delivery with repository access and code review
  • Stop release and investigate if provenance concerns arise
  • Preserve assurances, audit results and remediation decisions

Common questions

Did the High Court say the copying was lawful?

No. Mr Semmens' infringement was not disputed in the High Court. The appeal concerned whether the other businesses and directors had authorised his infringing acts.

Is telling a developer not to infringe always enough?

No. Authorisation depends on all the facts, including control, knowledge, steps available to prevent the conduct and the response to warning signs. The instruction was important on these facts but is not a universal defence.

What should a buyer ask for before acquiring software?

Ask for the source repository, contributor history, third-party component list, licence register, contractor assignments, infringement claims and warranties that ownership and use rights are complete.

Related topics

How Sprintlaw can help