On this page
  1. What breaks first
  2. What to centralise and what to leave local
  3. Permissions: role first, branch second
  4. Shared patient history: what should follow the patient
  5. Reporting: one pack, two views
  6. Pricing: one list, written exceptions
  7. Staffing: rotate carefully
  8. Opening a new branch: the sequence that works
  9. A 90-day rollout plan
Operations cover for Multi branch dental clinic management: a 90-day playbook
Quick answer

Multi branch dental clinic management works when clinical standards, pricing rules, reporting and patient identity are central, while scheduling habits, staff rosters, local vendors and community relationships stay with each branch. Roll it out in 90 days: define the standard, pilot it at one branch, then extend.

The second branch is where a clinic finds out which of its habits were systems and which were the owner's memory. At one location, the front desk knows that Dr Rao does not like new patients after 6 pm. At two locations, that knowledge has to live somewhere other than a person's head.

Most groups expand for a good reason: the first clinic is full and the waiting list is long. The problem that follows is rarely clinical. It is that the same question gets answered differently at each branch, and nobody can tell whether the group is doing well or just busy.

What breaks first

Three things, in this order.

The patient record. A patient treated at branch one walks into branch two and is registered as new. The charting, the allergy note, the pending crown and the unpaid balance are all missing.

The price list. Branch two quotes ₹14,000 for a crown that costs ₹12,000 at branch one, because the manager set fees from a local competitor. The patient finds out.

The report. Head office asks for last month's numbers and gets three spreadsheets with three definitions of "new patient".

None of these is a software problem in the first instance. Each is a decision that nobody wrote down.

What to centralise and what to leave local

Swipe the table to see every column
Area Central Local
Clinical protocols Yes: record structure, consent, sterilisation log Technique and case discussion
Fee list Yes, with written exceptions Discount approval within a limit
Patient identity Yes: one record per patient across branches Contact preferences per branch
Appointments Templates and rules Session timings, local holidays
Billing and GST Yes: same invoice format and tax logic Payment modes offered
Stock Formulary and approved suppliers Order quantities and local vendors
Staffing Roles, pay bands, leave policy Roster, hiring shortlist
Marketing Brand, offers, budget Local events, camps, school tie-ups
Reporting Definitions and monthly pack Branch review meeting
Community Nothing Everything

The right-hand column is not a concession. A branch manager who cannot adjust a roster or approve a ₹500 discount will stop making decisions and start sending emails. The left-hand column is what makes the group one business rather than three shops with a shared logo.

Permissions: role first, branch second

Write the roles once, then attach people to branches. A typical set for a dental group:

  • Dentist: own patients, own branch, clinical notes, plans, prescriptions.
  • Assistant: chairside records, stock issue, no billing access.
  • Front desk: appointments, registration, payments, recalls for the branch.
  • Branch manager: everything at the branch, plus local reports and discount approval.
  • Owner or clinical director: all branches, consolidated reports, fee list, audit log.

Two rules keep this useful. Default to the branch the person works at, and grant cross-branch access for a named reason, such as a dentist covering a leave. And log who opened a record from another branch. A patient consented to treatment, not to being read by anyone in the group.

Shared patient history: what should follow the patient

A dentist at branch two needs the charting, the medical history, the allergies, the current treatment plan, the lab cases in progress and the recent radiographs. That is the clinical minimum.

Billing is different. A patient may prefer to pay at the branch where they were treated, and mixing the balance across branches creates arguments at the counter. Show the balance from the treating branch, and let the local desk decide how to settle it.

Contact preferences belong to the patient, not the branch. If someone asked not to receive promotional messages, that preference should not reset when they visit a different location.

Reporting: one pack, two views

The branch view answers: is this location healthy this month?

The group view answers: where should the next rupee go?

Use the same eight numbers at both levels: production, collections, case acceptance, no-show rate, chair utilization, recall rate, outstanding balance and new patients. The KPI guide has the formulas. What changes at group level is the comparison: branch against branch, and each branch against its own last twelve months.

Resist ranking branches on a single number. A branch with a high-value implant practice will beat a branch in a residential colony on production per chair, and the comparison tells you nothing about which is run better. Compare each branch with its own trend, then ask why the trend differs.

Pricing: one list, written exceptions

A single fee list is the default. It makes the group comparable, stops patients from shopping between your own branches, and simplifies the accounts.

Exceptions should be written and approved: a branch in a higher-cost area, a satellite clinic with a different cost base, a corporate tie-up with a negotiated rate. Each exception gets a date, an approver and a review. Informal local pricing is how a group ends up with four fee lists and no way to explain them.

Staffing: rotate carefully

Rotating dentists between branches spreads skills and covers leave. It also breaks the relationship a patient has with a dentist, which is the main reason patients stay.

A workable rule: rotate for cover and for training, not for convenience. Tell the patient in advance who they will see, and keep the note detailed enough that the covering dentist does not repeat the history.

Opening a new branch: the sequence that works

  1. Decide the patient record structure and the fee list before the site is fitted out.
  2. Appoint the branch manager and give them written authority limits.
  3. Set up the branch in the system as an empty branch, with roles assigned.
  4. Train the front desk on registration, billing and the day book before the first patient.
  5. Open with a reduced service list: check-ups, fillings, extractions, referrals out for the rest.
  6. Run daily huddles for the first month and a weekly review with head office.
  7. Add services once the basics are steady, not in week one.

Opening with everything is the most common mistake. A new team learning implants and a new billing system in the same month usually learns neither.

A 90-day rollout plan

Swipe the table to see every column
Days Focus Output
1 to 15 Audit what each branch does today A list of differences that matter
16 to 30 Write the standard: record, fees, roles, reports One document, signed by the owners
31 to 45 Configure and clean patient data at the pilot branch Duplicate records merged, roles assigned
46 to 60 Train and run the pilot Daily huddles, issues logged
61 to 75 Fix what the pilot exposed Revised standard, version two
76 to 90 Extend to the remaining branches Same report pack in every branch
Day 90 First group review Decisions on price, staffing, next branch

The pilot month is not optional. A standard that has never met a busy Saturday will not survive four branches.

IvoryCRM is built around branches rather than seats: one patient record with branch-level permissions, a shared clinical history, and a consolidated report across locations. The multi-branch page sets out what each plan covers, and the product tour shows the branch switch. If you are still choosing between tools, compare the reporting before the features, because reporting is what a group actually runs on.

Frequently asked questions

Should all branches of a dental clinic charge the same fees?

Usually yes for the same procedure, with a written exception for a branch in a different market or with a different cost base. One price list makes the group comparable and stops a patient from being quoted differently at two branches. Local discounts should need approval and be recorded against the branch.

How do branch permissions work in dental software?

Roles are defined once for the group, such as dentist, assistant, front desk, branch manager and owner. Each role gets a set of actions, and each person is assigned to one or more branches. A dentist at branch two should see branch two's schedule by default, with cross-branch access granted only where the clinical record needs it.

Should patient records be shared across branches?

The clinical history should follow the patient, because a dentist treating someone at a second branch needs the charting, allergies and previous treatment. Billing and contact permissions can stay branch specific. Record who viewed a cross-branch record, since the patient gave consent for treatment and not for unlimited internal access.

How long does it take to standardise a small dental group?

About 90 days for a group of two to five branches: 30 days to define the standard and fix the patient record, 30 days to pilot at one branch, and 30 days to extend and review. Rushing the first month is the common mistake, because a standard written in a hurry gets abandoned at the first busy week.

What should a new branch get on day one?

The same patient record structure, the same fee list, the same consent and billing formats, a branch manager with defined authority, and a named person at head office for escalation. Equipment can arrive in phases. A branch that invents its own record format creates a migration project later.

See it with your own clinic day.

Book a walkthrough and follow a patient from booking through charting, treatment and billing. No patient data is needed.