A gloved skin clinician giving a client a facial treatment

For multi-location businesses

Run every location consistently and reliably

A customer should get the same experience at every site. Wikidoc documents how your best location runs, trains every site on it, and keeps the record of each opening and closing check.

Example

A group of eight skin clinics finds that one location has more no-shows than the others. Head office checks whether the reminder procedure is being followed there, finds the procedure itself has a gap, and updates it. Every clinic gets the new version, staff retake the short module, and the next month shows whether it worked. The improvement becomes part of how every clinic runs, not one manager's habit.

Common questions

Can each location have its own manager and approvers?

Yes. Set each location up as a department with its manager, and name that manager as the approver on the site's checklists. Managers see training for the people in the departments they manage.

Can head office see every location at once?

Admins see training completion, quiz scores and checklist activity across the whole organisation, and can export them. Site managers see their own teams.

Can a site have a local version of a procedure?

Yes. Keep the shared standard as one document and add a separate procedure for what is genuinely local, such as a building or a local rule, so the common part never splits into copies.

Do part-time and casual staff need seats?

Everyone who signs in to your workspace is a member, and on the Team plan each member uses a seat. See pricing for how seats work. People outside your business can use a portal without a seat.

Does Wikidoc replace our POS or booking system?

No. Keep the systems that take payments and bookings. Wikidoc covers how each site is run: the procedures, the training and the checks.

Run every location like your best one.