Dental software for multi branch clinics should give every branch one patient record, restrict what each role can see and edit by branch, and roll up collections, outstanding balances and recalls at group level. Roll it out one branch at a time, and pay per branch rather than per user so rotating associates do not raise the bill.
By the time a dental group reaches five branches, it will have met the same patient twice under two spellings of her name, with a crown recorded at one location and no record of it at the other. Nobody did anything wrong. Each branch was keeping a correct record of its own work in its own system.
The problem is arithmetic. Five separate databases produce five partial histories, and the patient is the one who has to remember which branch knows what.
What breaks first when a second branch opens?
Not the clinical work. The handoffs between branches.
A patient calls the new branch, gives a phone number, and the front desk cannot find her because she registered at the old branch under her husband's number. A dentist at branch two plans a crown without seeing that one was fitted at branch one last year. The owner asks for monthly collections and gets four spreadsheets in four formats.
These are the three costs of separate systems: repeated patients, incomplete clinical history, and reporting that takes a person a day to assemble.
What is a shared-record model?
One database, one patient identity, many branches. The alternative is a separate database per branch, sometimes with a manual export at month end.
Swipe the table to see every column| Question | Shared record | Separate databases |
|---|---|---|
| Patient visits two branches | One history, visible at both | Two partial histories |
| Duplicate patients | Reduced by phone and name checks | Common, and hard to merge later |
| Branch privacy | Role and branch permissions | Strong by default, but by isolation |
| Group reporting | Built from one source | Rebuilt from exports |
| New branch opening | Add a branch and users | New database, new setup, new bill |
| Patient moves cities | Record moves with them | Record stays behind |
| Contract exit | Export everything at once | Export branch by branch |
| Cost of growth | Predictable per branch | Often per instance plus per user |
The shared model is not automatically better. A group that acquires clinics and must keep each one's data legally separate has a reason to isolate. For most Indian dental groups, shared history with strict permissions is the more useful default.
How should branch permissions work?
Permissions need two dimensions: what a person can do, and where.
A receptionist at one branch needs to see that branch's schedule, take payments there and look up a patient's history from another branch. She should not be able to edit another branch's clinical notes, change its price list or delete its appointments.
A dentist needs the full chart for any patient they treat, including history from other branches, and should be able to add a note to the record from their own branch.
The clinical director and the owner need cross-branch views. The owner's view is financial and operational; it does not have to include every clinical note.
Ask for a demo with two logins, not a permissions matrix on a slide. The matrix always looks sensible. The screen is where you find out whether "view only" actually prevents an edit.
What does consolidated reporting need?
Four numbers, by branch and for the group:
- Collections for the period, split by cash, UPI and card.
- Outstanding balance, with the age of the debt.
- New and returning patients, counted once per patient.
- Recalls due, contacted and booked.
Chair utilisation and treatment mix are useful next, once the first four are trusted. The test of a group report is whether the owner can answer "which branch is behind on collections this month?" without calling anyone.
Reports also need a consistent definition. If one branch counts a patient as new on every visit and another counts them once, the group total is fiction. Set the definitions before the rollout, write them down, and make sure the software applies them the same way everywhere.
How should the rollout go?
Branch by branch, with a pause between each.
- Pick the pilot branch. The busiest is the honest test; the newest is the easiest. Choose based on whether you want to find problems or build confidence.
- Fix the foundations there: price list, chairs, roles, tax settings, patient list, and the rule for old records.
- Run it for two to four weeks, including a full month-end close.
- Write down what changed: which fields people actually used, which report was wrong, which permission was too tight.
- Open the next branch with the same configuration, and let its team train on the pilot branch's data.
- Add group-level reporting and cross-branch permissions last, once the branch data is clean.
- Review at 90 days with the branch heads in the room as well as the vendor.
A group that starts with head office reporting usually gets a dashboard of numbers nobody trusts. Clean branches first, consolidation second.
Why should price follow branches?
Because that is what a group buys: locations with schedules, stock, staff and records. Per-seat pricing charges for the roster, which in dentistry rotates constantly. An associate who works two Saturdays a month, a visiting implantologist, a receptionist on the evening shift: each one is a seat under per-user pricing and none of them is a branch.
IvoryCRM prices by branch. A group of up to five branches pays ₹5,999 a month, with shared patient history, branch-level permissions and full reporting. Larger networks get a custom scope with a rollout plan and a named contact. The pricing page shows the tiers, and the security page covers how access is controlled.
What should be in the contract?
Four sentences worth getting in writing before a group signs.
- The export includes every branch, with patients, visits, plans, invoices, payments and files, in a format another system can read.
- A new branch is added at a stated price, not a new negotiation.
- If the group sells one clinic, that clinic's records can be separated and handed over.
- Data residency, access and breach notification terms are named, because each clinic in the group is a Data Fiduciary for its own patients under the DPDP Act.
The last one is easy to forget when the contract is signed by a holding company. The duty sits with the clinic that treated the patient. Our note on multi-branch clinic management goes through the operating routine once the system is live.
Start with the patient who has two files. Merge or link those records first, at the pilot branch, and see how the system handles it. That single case tells you more about the group's next five years than any feature list.
Frequently asked questions
Should branches share one patient database?
Yes, for patient history. A patient who visits two branches should have one record, so the chart, the plan and the balance travel with them. What should not be shared is edit access: a receptionist at one branch should not be able to change another branch's schedule or take its payments. One database with branch-level permissions gives both.
How do branch permissions work in practice?
A person has a role and a branch. The Koramangala front desk sees the Koramangala schedule, patients and day book, and can look up a patient's history from another branch without editing it. The clinical director sees all branches. The owner sees the consolidated reports. Ask a vendor to show this split with two real logins, not a slide.
How long does a multi-branch rollout take?
Plan for one branch at a time, with two to four weeks between branches so problems are fixed before they multiply. The first branch takes longest because the price list, roles and migration rules are set there. Later branches copy a known configuration. A group that tries all five in one weekend spends the next month correcting data.
Why is per-user pricing bad for a dental group?
A group has rotating associates, part-time specialists and front desk staff on shifts. Per-user pricing charges for each login, so the bill grows with the roster rather than the work. Pricing per branch is predictable, and it makes the cost of opening a new location visible before the lease is signed.
Can each branch keep its own branding and pricing?
It should be able to. Branch name, address, invoice header and price list can differ while the patient record stays shared. That matters when an acquired clinic keeps its local name, or when a metro branch charges more than a tier-2 branch for the same crown. Ask how the invoice picks the right header.
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.