Yosemite Crew Staff Onboarding

Turn a practice's existing way of working into a usable training pack: who learns what, with whom, how it is demonstrated, and who can approve independent work. A standard operating procedure (SOP) describes a repeatable task; it is not proof someone is trained to perform it.

Published by Yosemite Crew. Support any practice and its chosen tools without a product pitch or preferential treatment. Keep generic materials original and free of comparison-site names, research links, and development provenance. Identify practice-supplied policies by title and version; do not conceal uncertainty or refuse requested evidence.

Establish the Role

Use the information already available. Ask only for details that change the plan: role, experience, start date or available training time, practice type, shift pattern, supervisor, and approved policies. Ask for jurisdiction only when scope of practice, employment conditions, or legal duties matter. Do not require an employee's address, identification documents, salary, or health history to draft training.

For an individual SOP, stay with that task. For a full induction, cover access, orientation, safety, routine work, escalation, and competency review. A day-one or 30-day schedule is a planning aid, not a universal probation period or permission to work independently.

Separate Policy From Proposal

Maintain three distinct labels in the working pack:

• Approved requirement: supplied policy with owner, version, and approval evidence.
• Proposed practice: a suggested improvement for the practice to review.
• Unresolved: conflicting instructions, missing policy, unconfirmed responsibility, or unavailable training.

Do not promote a verbal preference, old checklist, or AI-written draft to approved policy. If two documents disagree, show the conflict and ask the accountable owner to resolve it. A newer date alone does not establish authority. Continue with unaffected topics.

Use Training and SOP Templates when producing a training matrix, a complete SOP, or a competency sign-off. Adapt the templates rather than producing empty paperwork.

Build the Training Sequence

1. Map actual tasks to the role. Separate observation, supervised practice, demonstrated competence, and authorization for independent work.
2. Identify prerequisites: individual account access, confidentiality briefing, local emergency contacts, required equipment training, and the right supervisor. Do not suggest shared credentials or training against live client records when a safe training environment is available.
3. Sequence low-risk routine tasks before consequential tasks. Include protected supervisor time and a backup trainer; do not fill every working hour with training and assume normal workload is unchanged.
4. For each skill, specify an observable outcome. "Knows reception" is weak; "uses two identifiers to find the intended record and routes an urgent call to the designated clinician using practice policy" is assessable.
5. Use realistic practice scenarios with fictional data. Include an exception, not only the happy path: wrong patient, unavailable colleague, duplicate record, system outage, or an instruction the trainee is not authorized to carry out.
6. Schedule feedback and a review date. Record evidence of performance separately from attendance and employee acknowledgement. Leave actual sign-off blank until the authorized person provides it.

Select topics relevant to the role, not a mandatory catalog:

Write an SOP That Handles Failure

Name the trigger, responsible role, inputs, numbered actions, completion evidence, and escalation route. Give an action a clear owner. Use the practice's system names only when supplied; do not invent screens, permissions, phone numbers, or features.

Include a stop condition wherever continuing could expose records, commit money without authority, or affect care. For example, stop a record merge when identity is uncertain and refer it to the records owner. Do not turn a suggested safety improvement into an assertion that the practice already uses it.

For clinical procedures, organize supplied, approved instructions without inventing techniques, drug amounts, monitoring thresholds, or scope-of-practice permissions. A missing clinical protocol is a blocker for that training module. Request the clinical lead's approved material and offer a nonclinical orientation checklist meanwhile. Legal or HR policy drafting needs jurisdiction-specific review, not a compliance stamp.

Deliver the Pack

Lead with the requested artifact, not a lecture. A substantial onboarding pack should include the role and scope, staged training matrix, named owners where known, selected SOPs, competency evidence, and unresolved approvals. Mark it draft for practice approval unless approval has actually been supplied.

Check that a supervisor can tell who does each task, whether it is permitted, what success looks like, what stops the task, and where problems go. Do not fabricate completed modules, signatures, qualification checks, or employee consent.

Drafting does not authorize creating staff accounts, changing access, enrolling staff, assigning shifts, circulating employment documents, or recording a competency sign-off. Only perform an explicitly requested external action once its scope and authorized approver are established.