Lynqpod › For groups

Several practices, without pooling them into one pot

Groups get told to standardise. In reality each practice has its own clinicians, its own pay terms and its own patients, and the group needs to see across them without merging them.

Separate by design

• A database per practice. Not a shared table with a practice column: a separate database, so one practice cannot see another's patients even by accident.
• An address per practice, with its own booking pages and its own branding.
• Its own terms. Commission rates, charges and appointment types belong to the practice, not the group.

What the group sees

• Which practices are live, what they are subscribed to, and what is switched on.
• Onboarding a new site as a guided process rather than a project.
• Billing per practice, with packages and add-ons.

Rolling out without a big bang

A practice can start read-only, producing payslips alongside the existing process for a month until the numbers agree. Booking, messaging and gap filling are separate switches, so a site can adopt them in whatever order suits it. In practice the order that works is pay first, because it is the job that hurts most and the one where agreement is easiest to check, then booking, then everything else.

Comparing practices without pretending they are the same

Group reporting usually fails in one of two ways. Either every practice is forced onto identical terms so the numbers can be added up, which the clinicians resent, or each practice reports in its own shape and nothing can be compared at all. Lynqpod takes a third route: terms stay local, and the measures that are genuinely comparable are computed the same way everywhere.

• Chair time used and chair time lost, in hours, which means the same thing in every practice regardless of pricing.
• How quickly a freed slot is refilled, which says more about how a front desk is running than any satisfaction score.
• Cost per booked appointment from advertising, per practice and per campaign.
• What each clinician produced, in the practice's own terms, without exposing one practice's rates to another.

Where a group is different from a single practice

Three things change when a second site appears. Staff start working across practices, so access has to be granted per practice rather than per person. Patients occasionally move between sites, and their record belongs to the practice that holds it, not to the group. And somebody has to be able to answer "which of our practices is losing the most chair time?" without logging into each one in turn.

Those are the three problems the group console solves, and it deliberately solves nothing else: clinical governance, HR and compliance belong in systems built for them.

Common questions

Can one person work across several practices?

Yes, with an account at each. Access is granted per practice, so leaving one does not leave a door open at another.

Can the group set pay terms centrally?

Terms are set per practice on purpose. A group standard can be applied when a practice is set up, and changed later by that practice.

Read next

• Pay and commissionAssociate pay computed from the record, with every total openable.
• Use casesEvery job Lynqpod is bought to do, in one list.
• Dentally integrationWhat Lynqpod adds on top of Dentally, and what it leaves alone.