Decide what ready means for the first week
Do not begin by listing every system, policy, and exception in your practice. Begin with the work the person should be able to handle after the first few shifts.
For a front desk or scheduling role, that might mean they can:
- open the practice and find the day's schedule;
- recognize who is expected to arrive and when;
- create, move, or cancel a booking within your rules;
- answer common questions about location, timing, and preparation;
- route billing or clinical questions to the right person; and
- close their shift without leaving an unexplained loose end.
For a new practitioner, the list will be different. It may include checking their schedule, finding the right room, reviewing assigned forms, documenting a completed appointment, and knowing who handles payments or rescheduling.
Keep the first-week outcome narrow. Ready does not mean they have seen every screen or memorized every exception. It means they can complete the ordinary work safely and know when to pause.
Separate access from training
Account setup often gets mixed into the first lesson. Someone cannot find a page, so a teammate signs in for them. A role feels too limited, so they are given broader access for the afternoon. A shared password becomes the fastest way past a blocked step.
That solves the moment and creates a harder problem later.
Prepare access before the first shift whenever you can. Give each person their own account. Choose the role that matches the work they are expected to do, then confirm the invitation, sign-in, and basic navigation before a client-facing task depends on it.
Treat a missing permission as a setup question, not a reason to borrow someone else's access. If the new person cannot do something you expected, write down the exact action and review whether the role or the workflow needs to change.
Access also does not replace training. A person may be able to open an invoice, client profile, or clinical page without knowing what they are allowed to change. Your checklist should say both where the work lives and what the person is responsible for doing there.
Build the checklist around a real shift
A tour of menus is hard to remember because the new person has no reason to connect one page to the next. A shift has a natural sequence.
Walk through the day in the order it actually happens:
- Before the door opens: sign in, check the calendar, notice changes, and prepare the shared space.
- When a client arrives: confirm what your practice normally confirms, then follow the handoff you use for the appointment.
- When the schedule changes: apply the cancellation or rescheduling rule, record the outcome, and tell the people who need to know.
- When a question falls outside the role: pause, keep the message short, and route it to the named owner.
- Before leaving: finish assigned tasks, flag anything unresolved, and leave the next person a clear status.
This turns the checklist into a map of the job instead of an inventory of software.
If your practice has unusual steps, place them where they happen. A door code belongs in the opening section. A room reset belongs between appointments. An end-of-day payment check belongs in closing. The closer the checklist follows the shift, the less translation the new person has to do.
Practice with neutral examples
The first time someone learns a workflow should not require them to experiment on a real appointment, payment, message, or clinical record.
Use a training or demo environment if you have one. If your practice has an approved test record, make it obviously fictional and keep it free of copied client details. Otherwise, talk through the steps with a fictional scenario and stop before saving a change.
Choose examples that reflect ordinary decisions:
- a client wants to move an appointment to next week;
- someone asks whether a service is available online;
- an intake form has not arrived before the session;
- a payment question needs the owner; or
- a practitioner is running ten minutes late.
Ask the new person to show you what they would do and where they would stop. You are not testing whether they remember your exact wording. You are looking for whether they understand the sequence, the owner, and the boundary of their role.
Write down the stop points
Good onboarding does not only teach action. It teaches restraint.
Name the situations where the person should not improvise. Your list may include:
- a client shares new health information;
- a payment appears twice or cannot be matched;
- someone asks for access to another person's record;
- a cancellation falls outside the usual policy;
- an appointment needs a different practitioner or service; or
- a message sounds urgent, unsafe, or outside the practice's scope.
Beside each stop point, name the next person or route. "Ask someone" is not enough when the practice is busy. Write "send this to the owner," "leave this for the treating practitioner," or "use the billing question route."
The goal is not to make a new person nervous about every decision. It is to remove the pressure to guess when guessing would create more work.
Give setup work an owner and a date
A staff onboarding checklist often contains tasks that belong to several people. The owner sends the invitation. An admin prepares the workspace. A practitioner explains a handoff. The new team member completes a practice run.
If everything sits under the new person's name, the list hides the work the practice still owes them.
For each item, write:
- what must be ready;
- who is responsible;
- when it should be complete; and
- how you will know it worked.
"Set up calendar access" is vague. "Jordan sends the team invitation by Tuesday; Sam signs in and opens Wednesday's schedule before the first shift" is checkable.
Use dates for the setup steps that can block the day. Optional reading can wait. Account access, room access, schedule visibility, and the first training hour should not.
Check in twice, then revise the checklist
Plan one short check-in after the first hour and another before the person leaves.
After the first hour, ask:
- What were you trying to do when you had to pause?
- Did anything appear missing from your access?
- Which instruction did not match the real workflow?
At the end of the shift, ask what still feels unclear and what they would want in front of them tomorrow. A new person will notice missing steps that experienced staff stopped seeing years ago.
Update the checklist while the details are fresh. Keep the core version about the role, not the individual. Personal notes can live separately, but the reusable checklist should work for the next scheduler, practitioner, or admin who joins.
You are finished when the list is short enough to use during a real day, clear enough that two trainers would teach the same process, and specific enough that a new person knows both what to do and when to ask.
If you use Stillpoint, the Team page lets owners and admins invite people and choose the access role that fits their work. Stillpoint Tasks can carry an assignee and an optional due date, which gives each onboarding step a visible owner without turning the first day into a larger project than it needs to be.
