The Franchising Code of Conduct 2025 commenced on 1 April 2025, and many breaches carry civil penalties of up to 600 penalty units per contravention, according to the ACCC. Most franchisor exposure comes from records: late disclosure, wrong document versions, stale register entries and undocumented capital expenditure. AI-assisted extraction, reconciliation and deadline tracking make those records provable, with a person signing off.
This guide is for compliance leads, general counsel and operations directors at multi-brand and multi-outlet franchisors in Australia. It maps the Code's obligations to where AI reduces risk, and is clear about where the answer is a human decision, a lawyer or a policy.
Key takeaways
- The Franchising Code 2025 attaches real penalties to obligations that were once treated as paperwork.
- Most breaches are failures of timing, versioning and record keeping across a network. Intent is rarely the issue.
- AI helps with document extraction, register reconciliation, deadline tracking and capex record assembly.
- AI never approves a disclosure document, register update or capex requirement. A named person does.
- Start with deadline tracking: it is the cheapest fix with the most immediate protection.
What changed under the Franchising Code of Conduct 2025?
The new Code replaced the 2014 Code from 1 April 2025, with some transitional arrangements running later into 2025. The core obligations franchisors work with day to day:
- A prospective franchisee must receive the disclosure document, key facts sheet and proposed agreement at least 14 days before signing or paying non-refundable money.
- A 14-day cooling-off period applies after signing, during which the franchisor must repay money paid, less reasonable expenses set out in the agreement.
- The disclosure document must be updated within four months of the end of each financial year.
- Information on the Franchise Disclosure Register must be kept current.
- Significant capital expenditure must be disclosed and justified.
- Certain restraint of trade clauses cannot be enforced where a franchisee sought to extend and the franchisor declined.
- Many breaches carry civil penalties of up to 600 penalty units per contravention, per the ACCC, and the ACCC can issue infringement notices.
Check the current Code text and ACCC guidance for exact wording and transitional dates before relying on any summary, including this one.
Why is Franchising Code compliance a records problem first?
The instinct with a tougher Code is to send it to the lawyers, and legal review has its place. The day-to-day exposure sits in operations. A franchise network generates a continuous stream of documents and dates: disclosure documents sent to prospects, key facts sheets, signed agreements, cooling-off windows, annual updates and register confirmations. Each has a deadline, a version and a recipient, and each must be provably delivered at the right moment.
When that stream lives in shared drives, email folders and a spreadsheet one person maintains, the failure modes are predictable: the wrong version sent, an update that slipped past its due date, a register field nobody confirmed.
Take the 14-day disclosure period. Proving compliance means proving three things together: which version of the disclosure document was current on the day it was sent, that it reached the prospect on that date, and that no signature or payment was accepted inside the window. If any one of those lives in someone's memory, it is a latent breach waiting for a dispute.
The Franchise Disclosure Register raises the same issue. Keeping register data in step with the source documents it is drawn from is a data-matching task, which machines do reliably and people do inconsistently at volume.
| Assumed Cause | Common Real Cause | Impact | |
|---|---|---|---|
| Late disclosure | Deliberate delay | No delivery timestamp | Data issue |
| Wrong document version | Carelessness | No single source of truth | Versioning gap |
| Register breach | Oversight | Fields not confirmed on time | Tracking gap |
| Capex dispute | Bad faith | Missing written justification | Record gap |
| Cooling-off error | Rushed signing | Window not enforced in system | Process risk |
If most of your exposure is timing and version control, a reliable records pipeline is cheaper and faster than a wholesale legal rewrite, and it gives your lawyers a clean base.
Where does AI help with franchise compliance, and where can it not?
AI cannot decide whether a capital expenditure requirement is reasonable. It cannot draft your franchise agreement, interpret whether a restraint clause is caught by the Code, or sign off a disclosure document. It must never be the final approver of anything with penalty exposure. It can handle the volume, matching and deadline tracking that consume your operations team and produce most errors.
Document extraction. A disclosure document is long and structured, with many required items. AI-assisted extraction reads each agreement and disclosure document, pulls the key data points and flags where an item is missing or inconsistent with the register. A person reviews a short exception list instead of re-reading hundreds of pages.
Deadline orchestration. Every disclosure period, cooling-off window and annual update has a calculable due date once its trigger event happens. A rules-based system watches for triggers and raises alerts well before the deadline, turning silent failures into managed tasks. This is the discipline in our guide to automated compliance reporting, applied to franchising's calendar.
Consistency across the network. A franchisor with many outlets and several entities faces the same reconciliation problem as any multi-entity group: different templates, naming and people. AI-assisted matching compares each agreement with the register and master records and surfaces divergences a person would miss. Our piece on AI for multi-location franchise operations covers the wider operating patterns.
- IngestAgreements and disclosure documents
- ExtractAI reads required items
- ReconcileMatch against the register
- ScheduleTrack every deadline
- ReviewA person verifies exceptions and signs off
The pipeline ends with a person. AI narrows a large, error-prone dataset to a short list that needs human attention, which is the right split for anything with legal consequences. Our AI governance framework sets out the same principle.
How should franchisors handle capital expenditure disclosure?
The Code expects significant capital expenditure to be disclosed with its rationale, amount, timing, expected outcomes, benefits and risks. In plain terms, a franchisor cannot simply direct a franchisee to fund a major refit or new equipment without a documented justification that stands up to scrutiny.
This is where record keeping and good faith meet. A reasonable, well-communicated capex requirement that was poorly documented can still become a dispute, because recollections differ. Without a contemporaneous written record, the franchisor argues from memory.
AI-assisted document assembly helps in a narrow, useful way. When a capex requirement is being prepared, the system prompts for each element, checks none is blank and stores the completed record against the agreement. It does not decide whether the expenditure is justified. It makes sure whatever justification exists is captured and retained. The same tooling behind AI contract review for procurement and legal ops applies here.
- Disclosure documents checked for missing itemsFewer late or defective disclosures
- Register entries reconciled against source recordsLower infringement-notice risk
- Capex justifications captured in the required formDefensible position in disputes
- Deadlines tracked by the system, not by memoryDisclosure and cooling-off compliance
The value shows up mostly in contraventions that never happen because the gap was caught before the deadline.
How do good faith and the annual update fit in?
Good faith. The Code keeps the duty to act in good faith, applying to franchisor and franchisee across the relationship. Disputes about it are usually won and lost on the contemporaneous record. A franchisor who can show what was communicated, when and why is in a much stronger position. Good records do not create good faith, but they evidence it.
The annual disclosure update. The disclosure document must be updated within four months of each financial year end. For a single brand that is manageable. For a franchisor running several brands or entities, each with its own financial data, franchisee counts, supplier arrangements and site information, it becomes a group-wide data exercise under a fixed deadline. The treatment is the same as any multi-entity reporting task: pull source data programmatically, flag what changed since last year, and have a person confirm the final document instead of rebuilding it.
Dispute resolution. A franchisor that can produce a clean, dated record of a dispute's history, including notices given and steps taken, resolves matters faster and defends itself better. That is a records discipline first. Technology makes it sustainable across a large network.
What is a realistic Franchising Code readiness roadmap?
Attempting everything at once usually produces a stalled project. A staged approach protects you sooner and shows what your network needs before a larger build.
- Weeks 1-2Map obligationsList every deadline, document and register field the Code requires
- Weeks 3-4Fix the calendarStand up deadline tracking for disclosure and cooling-off periods
- Weeks 5-8Automate extractionAI reads disclosure documents and reconciles against the register
- OngoingReview and refinePeople review exceptions, rules tightened over time
Deadline tracking comes first because missed windows are the most common and most avoidable failures. Extraction and reconciliation follow once you know which items and register entries cause most trouble. Cross-entity matching comes after those foundations are stable.
What is your most likely first breach?
- Missed disclosure or cooling-off deadlinesStart with deadline orchestration
- Stale or unconfirmed register entriesStart with register reconciliation
- Disputed or undocumented capexStart with capex record assembly
- Inconsistency across many outletsStart with cross-entity matching
None of this removes the need for a franchise lawyer. It changes what the lawyer works on: judgement questions, from a clean and complete record, instead of chasing documents and rebuilding timelines.
What governance does franchise compliance automation need?
Any system touching franchisee data, disclosure documents or the register needs clear rules about who approves what, where data is stored and how a person stays in control of consequential decisions. Franchisee data includes personal and commercial information, which brings the Privacy Act 1988 into play alongside the Code.
Two principles keep this on the right side of the line. First, AI proposes and a named person approves: no disclosure document, register update or capex record is finalised without sign-off. Second, data stays where you can account for it, ideally on your infrastructure in Australia, with a record of where franchisee information is processed.
Franchisors with corporate staff should also remember the Code sits alongside other tightening obligations, such as those in our guide to Fair Work compliance automation. One well-governed records discipline pays off across all of them.
How Solve8 can help
Our team builds compliance records pipelines for multi-outlet franchisors: document extraction, register reconciliation and deadline tracking, running on your infrastructure with a person signing off every consequential step. See our process automation and custom AI development services, or talk to us.
This article is general information, not legal advice. Confirm your obligations under the Franchising Code of Conduct against ACCC guidance and qualified legal advice.
