Documenting a failed software implementation in Australia — how to preserve evidence and seek repayment

If a software implementation you paid for has failed, start by preserving contemporaneous evidence and checking whether the Australian Consumer Law (ACL) or your contract gives a remedy — you may be able to seek remediation, a refund, or damages depending on whether the ACL applies or whether the supplier breached the contract. The immediate practical priorities are (1) gather and secure the records that show what was promised and what was actually delivered, (2) follow any contractual dispute/notice process, and (3) decide the sensible next forum for a claim (negotiation, ADR or court/tribunal), keeping in mind state-by-state differences in tribunal limits and procedure.

The ACL sets service guarantees that can matter to businesses that qualify as "consumers"; read the guarantees in the federal text for the exact statutory language and scope. See the Australian Consumer Law in the Competition and Consumer Act 2010 for the guarantees that apply to services, including due care and skill and fitness for purpose: Schedule 2 — The Australian Consumer Law and the current compilation of the Act on the Federal Register of Legislation at Competition and Consumer Act 2010 - Federal Register of Legislation.

What evidence matters — a practical checklist and why each item helps

A court or tribunal will usually prefer contemporaneous records to reconstruct promises, performance and failures. The most useful categories of evidence are:

• Contract documents (SOW, acceptance criteria, milestones, payment schedule, variation/change control and any termination or dispute clauses). The contract frames the rights and obligations you will enforce.
• Acceptance-test records and technical outputs (UAT sign-offs, test reports, screenshots, error logs, deployment notes, build logs). These show whether deliverables met agreed criteria and when they failed.
• Communications and status reporting (emails, meeting minutes, chat logs, project-management tickets, vendor status reports). These prove what was said, when, and whether the vendor acknowledged problems or proposed fixes.
• Change requests and approvals, plus any invoices for variations. These separate agreed scope changes from alleged original failures.
• Financial records (invoices, payment receipts, bank records). These establish what you paid and when.
• A clear chronology or timeline with dated entries summarising contract milestones, missed deadlines, failed tests and remediation attempts. A concise timeline helps any mediator, adjudicator or judge follow the factual story quickly.
• Independent technical assessment or expert report (where the facts are technical and the sums justify the cost). A neutral expert can translate logs and failures into clear conclusions about whether the implementation met professional standards.

Why these items help: statutory guarantees under the ACL are expressed in legal terms (care/skill, fitness for purpose), but courts and tribunals decide breaches by comparing what the contract and project documents required with what the vendor delivered. Contemporaneous documents are therefore decisive evidence of both promises and performance.

How to decide whether the ACL applies or whether you rely on the contract

The ACL contains consumer guarantees that can require suppliers to fix, refund or compensate for defective services where the buyer is a "consumer". Whether your business qualifies as a consumer depends on the facts; many B2B software contracts for larger businesses do not meet the ACL's consumer tests, in which case your remedies will come from the contract and common law.

Consult the ACL text to confirm which guarantees might apply; the federal legislation contains the guarantees relating to services, including those about due care and skill. See Schedule 2 — The Australian Consumer Law and the Act compilation at Competition and Consumer Act 2010 - Federal Register of Legislation for the statutory language. If you fall within the ACL's definition of consumer, remedies can include having the service supplied again, a refund or compensation depending on whether the failure is major.

If you are not an ACL "consumer", focus on the contract: identify breaches of express promises (scope, timelines, acceptance criteria) and any implied obligations under common law. Also check whether the supplier’s conduct could attract a statutory claim for misleading or deceptive conduct under the Competition and Consumer Act; the Act's broader prohibitions may be relevant in some disputes.

Practical sequence: preserve evidence, notify, then escalate thoughtfully

1. Preserve evidence immediately. Export and back up logs, emails, chat histories and project data to a secure, read-only location (for example, PDF copies of emails and exported logs). Clearly label and time‑stamp files if possible.
2. Prepare a short chronology and an issues summary that links each failure to the specific contractual promise or acceptance test it breaches. This document is for internal use and later to attach to any formal notice.
3. Follow the contract’s dispute and notice procedures. Most contracts require written notice of breach and give the supplier a chance to remedy; complying preserves your contractual rights and supports a later claim if the supplier does not fix the issue. Set a reasonable remedial deadline—remember that statutory time limits and tribunal procedures vary by state, so do not assume a single universal deadline applies.
4. Attempt structured negotiation or ADR if the contract or local small-business commissioner suggests it. Mediation or expert determination can be faster and cheaper than court, particularly for mid-value disputes.
5. If unresolved, bring a claim in the appropriate forum: a state/territory tribunal for smaller sums or court proceedings for higher-value claims. Jurisdiction, monetary caps and procedures differ between states and territories, so check the relevant tribunal or court rules for your location.

The ACCC has commentary that helps explain the regulatory perspective on remedies for failed services; its guidance can be useful background on consumer protections and remedies. See the ACCC speech for further context: CEDA Speech | ACCC.

When to get an expert and when to seek legal advice

An independent technical expert is valuable when the dispute turns on whether the software met industry standards, when logs are complex, or when you must quantify consequential losses caused by the failure. If the sums are modest, weigh the expert’s fee against likely recovery.

Seek qualified legal advice when: the claim is large; the contract contains complex limitation or indemnity clauses; the supplier disputes the facts; or you are unsure whether the ACL applies. Legal advice is also sensible before starting formal court proceedings because state and federal rules about jurisdiction and limitation periods differ.

Using a written demand effectively (what it should do and why it helps)

A well-drafted written demand can crystallise the dispute, set out the factual basis for repayment or remediation, state the amount sought, and give the supplier a final chance to resolve matters before ADR or litigation. It does not guarantee payment, but it demonstrates you attempted to resolve the matter and provides a clear record of your position. If you choose professional help to prepare a demand, use a reputable service that prepares documents from your information while making clear you are responsible for the content; for example, consider if you want a professionally‑formatted demand letter prepared from your materials.

Final practical notes: preserve everything, act promptly on contractual notice requirements, and be realistic about costs. For many businesses, mediation or expert determination resolves technical disputes faster than litigation. For significant or contested claims, ensure you have a technical expert and legal counsel lined up before spending on court filings.

For help preparing a professional demand letter, BeforeSuit can help you prepare your next steps.