How Should You Onboard a Recovery Coach?

What belongs on a recovery coach onboarding checklist?

Include preparation before the start date, an explanation of the role, practice with everyday work, a named supervisor, and a review of what the coach can do with appropriate support. Give every onboarding item an owner and a way to demonstrate completion.

Start with a real workday. A new coach needs to know how a participant reaches the program, who assigns the work, where the next appointment appears, what to document, and whom to contact when a question cannot wait. A folder of policies may contain those answers, but onboarding should help the coach find and use them during the work.

How is onboarding different from certification and training?

Treat qualifications, organizational orientation, and readiness for assigned work as separate questions. Evidence that someone completed a course does not tell you whether they understand your program's records, handoffs, schedules, or support process.

The Substance Abuse and Mental Health Services Administration (SAMHSA) describes core competencies as knowledge, skills, and attitudes that can guide training, job descriptions, supervision, and continued development. Its guidance also says competencies should support entry and growth in the peer workforce. Our recommendation is to turn selected competencies into supported practice opportunities tied to the actual job.^[1]

An experienced coach joining a new organization may need less practice with introductions and more help with local partners, documentation, and coverage arrangements. A person entering the workforce may need a longer period of supported practice. Avoid using the same packet as proof that both people need exactly the same help.

Keep gaps visible without treating every gap as a personal failure. An unavailable account, an unclear referral policy, or a missing supervisor is an organizational problem. Record who will fix it and what the coach should do while it remains unresolved.

What should the organization prepare before the coach arrives?

Prepare the working environment as carefully as the orientation materials. The new coach needs a defined role, usable tools, a realistic schedule, and colleagues who understand how peer support fits into the program.

The University of Washington's Harborview Behavioral Health Institute toolkit addresses organizational readiness, role definition, onboarding, supervision, and avoiding role drift in crisis settings. That setting is specific. A useful planning lesson for other programs is to examine the organization's responsibilities alongside the new worker's learning needs.^[2]

• Name one onboarding owner who coordinates the process and one supervisor who is available for practice, questions, and feedback. Explain when those are different people.
• Prepare the approved role description, service model, orientation schedule, and current procedures. Label draft material clearly so it cannot be mistaken for approved guidance.
• Arrange the accounts, equipment, workspace, and communication channels appropriate to the assignment. Verify access using training records before expecting independent work.
• Tell the existing team what the coach will do, how participants can be connected, and which questions should go to the supervisor.
• Plan protected time for orientation, documentation practice, and supervision. Include travel and administrative work when discussing workload.

Do a simple readiness walkthrough before the first day. Can the coach sign in, find the next appointment, reach the supervisor, and locate the approved note form? If the answer depends on someone remembering to send a link, give that step an owner. A prepared environment makes it easier to distinguish a training need from a broken process.

How do you make the recovery coach's role clear?

Describe the support the coach provides, the decisions that belong to the participant, and the requests that need another role. Practice explaining those boundaries in ordinary language before the coach encounters a difficult handoff.

Create a one-page role map with the coach and supervisor. Include the program's purpose, everyday activities, referral routes, documentation responsibilities, and sources of support. Use examples from the setting: a recovery community center, a treatment-linked program, a residence, or an outreach team will have different day-to-day handoffs.

Do not rely on a new coach to negotiate organizational disagreements alone. If staff routinely ask coaches to act as security, complete clinical decisions, or take on unrelated coverage, the supervisor should resolve the role expectations with the team. The onboarding checklist can record that a concern was raised; leadership still owns the response.

Invite the coach to practice a short introduction in their own words. It should explain what support is available and how the participant can shape the conversation. A memorized script is less useful than an introduction the coach can adapt while preserving the program's boundaries.

What should the coach practice before a first conversation?

Practice opening the conversation, listening for the participant's priority, checking what help is wanted, and agreeing on a realistic next step. Use fictional scenarios so learning does not require exposing a real person's history.

Give the practice partner a small amount of information rather than a long case file. For example, Jordan wants to reconnect with a community activity but is unsure what to say when arriving. The coach can explore what Jordan wants from the activity, ask whether practicing an introduction would be useful, and let Jordan choose the next step. There is no required successful ending to the exercise.

• Opening: can the coach explain the role and invite the person's priorities without beginning with a checklist of problems?
• Listening: can the coach distinguish what the person actually said from assumptions about what would help?
• Options: can the coach discuss more than one possible next step without making the decision for the person?
• Agreement: can both people explain what was agreed, who will act, and whether another contact is wanted?
• Reflection: can the coach describe what felt useful, what was uncertain, and what they would discuss in supervision?

Repeat the exercise with a participant who does not want a next appointment. Practice respectful closure and the approved documentation process. A training exercise that always ends in a scheduled follow-up can accidentally teach staff that agreement is the only acceptable result.

How should you teach documentation without turning coaching into paperwork?

Use a short fictional session to practice recording the goal, support provided, participant response, and agreed next step in the approved form. Review whether the record helps the next authorized reader understand what happened.

Give the coach time to write before showing a polished example. Ask them to separate the actual contact from what was planned. If Jordan considered an activity but did not attend during the session, the record should not report attendance. If the coach offered a referral and Jordan declined, the note should preserve that choice.

Review the note together. Ask where the goal appears, which sentence describes the coach's work, and whether the response is supported by the scenario. Then show where the program records service facts, authorship, completion, and any required review. Avoid rewarding longer notes when a shorter accurate record communicates the work.

Include a correction exercise. Demonstrate how a draft is completed and how a later correction or reviewer question is handled under the program's process. The coach should know whom to ask before editing a record that has already been finalized. A practice session can also reveal confusing form labels that the organization needs to clarify.

What should the onboarding supervision plan include?

Specify who provides support, when planned conversations occur, how urgent questions are handled, and how feedback becomes a development action. Distinguish learning and reflective support from the administrative task of approving a note.

A new coach should not have to guess whether a question is worth bringing to supervision. Offer an initial agenda: role questions, a situation the coach wants to understand, documentation feedback, workload, and one development goal. Adjust the agenda with the coach rather than treating it as a universal supervision standard.

Make coverage explicit. If the primary supervisor is unavailable, identify the appropriate contact and the limits of that person's role. Explain how to reach help during field work or outside a scheduled meeting. Use your organization's applicable supervision requirements to set frequency, qualifications, and records; this guide does not prescribe them.

• Prepare: the coach identifies a question or learning goal and any necessary context through approved channels.
• Discuss: coach and supervisor examine the situation, including the participant's choices and the limits of the coach's role.
• Agree: identify one or two concrete actions, who will take them, and how they will be revisited.
• Follow through: check whether the action helped, whether the process needs clarification, and what support remains.

Keep the purpose and access of supervision records clear. A record of a meeting, an employment evaluation, a documentation review, and a reflective conversation can serve different needs. Have the responsible program owner decide how each is recorded and shared under current policy.

What could a first-week and 30/60/90-day plan look like?

Use phases to organize support and review progress, then adapt the timing to the person, role, and program. Calendar milestones are useful prompts for a conversation; passing a date does not establish readiness.

A part-time coach may encounter a particular workflow later than a full-time coach. A program may also need to resolve a prerequisite before any service assignment. Move activities according to actual opportunities and requirements. Do not translate this table into a promise that every coach can work independently by day 30 or must finish development by day 90.

Write down the expected evidence for each milestone before reviewing it. 'Understands documentation' is hard to discuss. 'Can complete a fictional note, explain the next review step, and locate the correction process' gives the coach and supervisor something concrete to examine.

End each review with a shared understanding of the next phase. A useful entry might say: Practice one missed-contact scenario with the supervisor next week; the operations lead will clarify the status labels before that exercise. That record assigns work to the organization as well as the coach.

How can a supervisor assess readiness fairly?

Review specific work with the coach, record what was observed, and decide what support is needed for the next assignment. Use a small set of clear criteria rather than a single score that hides the reasons for the decision.

For each area, use descriptions such as demonstrated in this scenario, needs more practice, or awaiting an organizational decision. Those descriptions should lead to action. They are not a credential determination or an automatic employment decision.

Ask the coach for their assessment first. They may have identified a recurring barrier that was invisible in the demonstration. Record relevant evidence and a review point, and use the organization's employment and supervision processes for formal decisions. Avoid treating familiarity with one software product as a substitute for the abilities required by the role.

How do state and program requirements fit into onboarding?

Maintain a source checklist for the specific role, setting, and funded service. Use state guides to locate relevant topics, then have the designated program lead verify current official requirements and unresolved questions before assigning affected work.

Begin with the actual job rather than a broad title. Record the state, program, service setting, employer, credential being evaluated, and any payer or contract involved. Two positions described as recovery coaching may need different evidence. Keep training completion, credential verification, supervision arrangements, and organization authorization distinguishable in the review.

• Source: save the official issuing body or program document and the relevant section.
• Applicability: explain which role or service the source applies to and what question it answers.
• Currency: record the effective date, when it was checked, and who owns the next review.
• Evidence: identify what the organization has verified and what still needs a decision.
• Assignment impact: document how an unresolved question affects work until the responsible lead resolves it.

This framework deliberately avoids a national list of training hours, supervision ratios, billing codes, or background checks. Use the current requirements that apply to the position. When an answer is unclear, identify the authority or program contact who can resolve it instead of copying a rule from a neighboring state.

What should you watch after the orientation packet is complete?

Continue reviewing workload, access, role clarity, and the coach's experience of support. Completing orientation does not remove the need to discuss difficult handoffs, changing assignments, or recurring administrative friction.

Ask the coach to walk through a recent working day using appropriate nonidentifying examples. Where did they wait for an answer? Which task required entering the same information twice? Did travel, groups, outreach, or coverage leave enough time for documentation and supervision? Those questions help leadership understand the work beyond a count of assigned participants.

Review how the organization responds when a coach asks for help. If every question is treated as a lack of independence, the team may learn to hide uncertainty. Agree on a clear path for questions, feedback, and workload concerns. Keep the process usable for part-time staff and coaches working away from the main office.

Include professional development in later reviews. The coach may want to strengthen group facilitation, resource navigation, documentation, or another approved part of the role. Select an activity, a source of support, and a time to discuss what was learned. Onboarding can establish that habit without pretending to replace a longer development program.

How can Smores Health support the day-to-day onboarding workflow?

Use a walkthrough to connect the coach's assignment, schedule, documentation, supervisor review, and follow-up. Smores Health supports these operational areas; your organization defines the onboarding plan and the requirements behind the work.

Smores Health's Operate and Document areas cover caseloads, schedules, tasks, structured notes, signatures, and supervisor review. During evaluation, ask to see how those parts fit your program's daily work. This guide's 30/60/90-day plan is a suggested planning worksheet, not a claim that Smores automatically runs a credentialing or onboarding program.^[3][4]

• Bring a blank approved note form and a fictional first assignment.
• Show how the coach finds the assigned participant, planned work, and relevant next steps.
• Complete a fictional note and walk through the applicable review process.
• Discuss how the supervisor sees work needing attention and how the team handles coverage.
• Confirm which parts fit the current configuration and which need a separate solution or process.

A small program can begin by mapping this workflow on paper. As assignments, supervisors, and sites grow, use the same map to evaluate where software would reduce repeated coordination. The objective is a coach who can find the information and support needed for the next step.

How do you put the onboarding checklist into use?

Download the editable worksheet, assign an owner, and review it with a coach and supervisor before using it for a new hire. Keep the approved version somewhere staff can find it and record when the program changes.

The worksheet includes a preparation checklist, practice scenarios, phased review prompts, a source-verification table, and space for development actions. Remove items that do not apply, add the current requirements for your setting, and replace generic role names with the people responsible in your organization.

Try it first with a fictional onboarding case. Give the reviewer an incomplete account setup, an unclear referral request, and a sample note needing clarification. Check whether the worksheet leads to a named owner and an actionable next step for each. If it only produces checked boxes, revise the prompt to ask what was demonstrated or what needs to happen.

Frequently asked questions

Sources and product pages

Sources support the specific guidance cited above. Program guidance is not a universal requirement. Product pages describe capabilities to verify against your organization’s needs.

1. Core Competencies for Peer Workers: Substance Abuse and Mental Health Services Administration. National peer-worker principles and uses of competencies for training, job descriptions, and development. Official indexed text checked October 9, 2026.
2. Integrating Peer Support in Crisis Care Settings Toolkit: Harborview Behavioral Health Institute, University of Washington. Official toolkit overview checked October 9, 2026. Its scope is crisis and emergency care; it is cited for organizational readiness and onboarding topics, not national requirements.
3. Operate: Peer Support Workforce and Caseload Management: Smores Health. Smores Health workforce, caseload, schedule, supervision, and task workflows.
4. Document: Notes, Assessments, and Supervisor Review: Smores Health. Smores Health structured notes, assessments, signatures, and review workflows.