Amatya

Coaching franchise agreements: 12 clauses to get right

By Kriti S, Builder, SIDDHI xSYS · 15 July 2026 · 3 min read

A coaching franchise agreement needs 12 things settled in writing: territory, brand usage, fee and royalty structure, who owns student data, the mandatory systems stack, quality standards and audit rights, certificate issuance authority, marketing duties, reporting, term and renewal, exit and non-compete, and dispute resolution. Most franchise fights trace back to one of these left vague.

Franchising a coaching brand — or buying into one — usually starts warmly and goes wrong at the paperwork. Both sides sign a two-page "MOU" in the honeymoon, and eighteen months later discover it answers none of the questions that now matter. This walkthrough covers the 12 clauses that do. (Operating experience, not legal advice — have a lawyer draft the final document.)

The commercial core

  1. Territory. Exactly which area is exclusive — named localities or pin codes, not "the Gaya region". Include what happens when the franchisor wants a second centre in a growing city.
  2. Brand usage. What the franchisee may use (name, logo, materials) and where; who approves local hoardings and pamphlets; what happens to signage on exit.
  3. Fees & royalty. Upfront fee, recurring royalty (flat vs. percentage of collections), and — critically — percentage of what: billed fees or collected fees, verified how. This single ambiguity causes more disputes than any other.
  4. Payment mechanics. When royalty is due, on whose report, with what audit right.

The operational core

  1. Student data ownership. The clause almost every coaching agreement misses. Who owns enrolments, contact data and academic records — per centre? On exit? Write it down, and mind the data-protection era: parents' data is not a bargaining chip. (A franchise-native system with per-centre isolation makes the technical side enforceable — this is precisely how Amatya's franchise console is designed.)
  2. Systems mandate. Which software, fee process, receipt format and reporting the franchisee must use. "Same system, per-centre isolation, owner-level visibility" is the governance model that scales; the alternative is phone-call auditing.
  3. Quality standards & audit. Teacher qualification floor, batch size caps, syllabus pacing — and the franchisor's right to inspect (announced or not).
  4. Certificate authority. Who issues certificates, in whose name, against which records. For job-oriented brands the certificate is the brand — verifiable issuance (QR-checked, centrally controlled) protects every centre from one bad actor.

The relationship core

  1. Marketing duties. What the franchisor funds (brand campaigns, result publicity) vs. the franchisee (local marketing, GBP, demo weeks) — with minimum local spend named if it matters.
  2. Reporting cadence. Which numbers, how often, from which system. If reporting is a WhatsApp forward of a register photo, neither side will trust it by year two.
  3. Term, renewal & exit. Duration, renewal conditions, and the exit choreography: signage down, materials returned, student data handled per clause 5, ongoing batches taught out (students must never pay for the divorce).
  4. Non-compete & dispute resolution. Reasonable radius and duration for non-compete (overreach is unenforceable and poisons goodwill), and arbitration city named — deciding where you would fight is cheaper before the fight.
The one-question test for any franchise agreement: if this partnership ends badly in three years, does the document answer — who keeps the students, who keeps the data, who serves the running batches, and what comes off the walls? If yes, everything else is negotiation.

If you are building the franchisor side, the operating half of the deal — one console, isolated centres, uniform receipts and certificates, cross-centre reporting — is what Amatya for franchise networks provides out of the box; worth seeing before you write clause 6.

See the franchise console — live demo

Per-centre isolation, owner visibility, uniform certificates — the enforceable version of clauses 5–8.

Common questions

Should royalty be on billed fees or collected fees?

Collected, verified by a shared system — royalty on billed fees makes the franchisee owe money on fees they never received, which breeds under-reporting. But "collected" only works when collections are visible to both sides, which is why the systems clause and the royalty clause must be written together.

What is a reasonable franchise territory in coaching?

Small enough that the franchisor can still grow, large enough that the franchisee’s marketing does not feed a neighbour: in metros, a named cluster of localities; in district towns, often the town itself. The mechanism matters more than the size — name the boundary precisely and define the second-centre process.

Written by
Kriti S · Builder, SIDDHI xSYS

Runs a computer-education institute and built Amatya to run it. Everything here is written from the counter, not a content calendar.

Keep reading