# Employee onboarding plan: example and records An employee onboarding SOP defines how a team prepares, welcomes, trains and supports a new colleague. Its checklist records who does each task, when it is needed and what shows it is complete. A welcome session, a training score and a successful practice task each provide different evidence. This example covers a customer success coordinator learning an administrative account handoff. All names, IDs, observations and decisions are fictional teaching examples, not employee assessments or customer results. Adapt the sequence to the role and your approved people processes. This guide covers operational learning, not the full set of hiring or statutory requirements. ## Define the outcome and the people responsible - **Procedure:** ONB-001 · Customer success coordinator onboarding · version 1.0 - **Maintaining owner:** Customer success manager - **Start condition:** Role, start arrangements, manager and required access approvals confirmed. - **Completion condition:** Manager reviews the agreed practice evidence, resolves or assigns open items and records the next supported responsibility. - **Related instructions:** HND-014 · Administrative customer handoff · version 1.2, used for the fictional practice below. ### Assign a person to each responsibility - **Manager:** Owns the plan, sets the practical checks and records the readiness decision. - **Access administrator:** Processes authorized requests and helps the learner verify only the access needed for the role. - **Procedure owner:** Maintains the approved instructions and resolves unclear steps or exceptions. - **Trainer or buddy:** Demonstrates the task, observes practice and records specific feedback. - **Learner:** Finds the instructions, practices, asks questions and identifies unresolved work. ## Build a checklist from preparation to review The timing is a planning example. Choose real dates, named people and support arrangements before assigning work. If a prerequisite is missing, record the item, its resolving owner and the next check. Change the plan instead of marking the task complete. ### Before arrival · prepare the plan **Responsible role:** Manager **Evidence or decision:** Role outcome, buddy, first meeting, current procedure references and review dates agreed. ### Before practice · verify approved access **Responsible role:** Access administrator and learner **Evidence or decision:** Learner opens the permitted sample workspace. Unresolved requests have an owner; no shared credentials or unnecessary permissions are used. ### First day · find people and instructions **Responsible role:** Manager and learner **Evidence or decision:** Learner finds current HND-014, its maintaining owner, receiving role and question channel. ### First week · learn the assigned version **Responsible role:** Trainer and learner **Evidence or decision:** Record the version studied and explain the handoff decision. Keep reading acknowledgment or quiz results separate from observed practice. ### First week · practice the ordinary case **Responsible role:** Learner, observed by trainer **Evidence or decision:** Demo Account 104 has confirmed contact and scope, a named receiver, a next action and explicit receipt. ### First week · practice the exception **Responsible role:** Learner and procedure owner **Evidence or decision:** For Demo Account 105, recognize the missing contact, keep the handoff open and record resolving owner and follow-up. ### Before independent work · review evidence **Responsible role:** Manager **Evidence or decision:** Compare both records with the agreed checks. Record what can proceed, limits, open items and further support. ### After the first supported assignment · improve **Responsible role:** Manager, learner and procedure owner **Evidence or decision:** Discuss unclear steps, assign corrections and choose the next review. Retain the original practice and training context. ## First day: make the work and support easy to find Show where to find the current procedure and its maintaining owner. Ask the learner to locate the receiving person and explain the expected handoff. Introduce the buddy and agree a question channel and check-in. For a remote colleague, verify the same route works from their approved setup before practice. ### If access or a reviewer is unavailable Record the blocker and the person resolving it. Assign another appropriate sample activity or reschedule the review. Do not use another person's account, bypass an approval or treat a missing prerequisite as complete. If the receiving owner cannot accept a handoff, keep it open until the documented exception is resolved. ## First week: practice the ordinary path and an exception Give the learner HND-014 version 1.2 and two fictional records. The task is to prepare and hand over an administrative account record. It does not authorize a commercial commitment or a message to a real customer. The trainer demonstrates the decision, then observes the learner using the instructions. 1. Check account reference, contact reference and agreed scope against the sample source. Identify missing information before handing work over. 2. Name the receiver and record one concrete next action and its agreed follow-up point. 3. Ask the designated receiver to confirm receipt in the practice record. Keep unresolved work open and name who resolves it. 4. Review the record together. Ask the learner to explain what they would do if the contact or receiving owner were unavailable. ### Two completed fictional practice records #### Demo Account 104 · ordinary path - **Participants:** Avery, learner; Morgan, trainer; Jules, receiving owner. - **Recorded work:** CONTACT-104 and scope confirmed. Next action: Jules checks the prepared kickoff brief at the next agreed practice review. - **Receipt:** Jules confirms account reference, scope and next action in the sample record. - **Observed outcome:** All ordinary-path checks are present. One practice observation does not authorize every responsibility. #### Demo Account 105 · missing contact - **Initial observation:** No contact reference in the source. Avery marks the handoff pending and assigns the question to Eli, the procedure owner. - **Follow-up:** At the agreed follow-up, Eli supplies sample CONTACT-105. Avery rechecks the source; Jules accepts receipt. - **Record retained:** Initial blocker, resolving owner, correction and later receipt remain visible. - **Observed outcome:** The exception is resolved before closure. Nothing was accepted while the required reference was missing. ## Review readiness with an observable result Agree the checks before practice. A completed checklist or quiz informs the conversation; the manager still observes the task and discusses questions. Use role-relevant evidence and explain the scope of the decision. - Find the current procedure and explain who maintains it. - Produce the required ordinary-case evidence and identify the receiver. - Recognize missing information and follow the exception without inventing a completed result. - Explain the next action, open items and how to ask for help. ### Fictional readiness review - **Review reference:** ONB-001 / Avery / first practice review - **Evidence inspected:** HND-014 v1.2 learning record; Demo Accounts 104 and 105 practice notes and receipt. - **Decision by Morgan, manager in this example:** Continue with one supervised administrative handoff. The checks were demonstrated in sample work; broader responsibilities remain outside this decision. - **Next support and review:** Buddy available for the first assignment; manager reviews its record before expanding responsibility. - **Learner feedback:** The original instruction did not clearly say where to record a missing-contact question. Eli owns the clarification. ## Respond to feedback and procedure changes The procedure owner reviews a correction before publishing it. If HND-014 changes from version 1.2 to 1.3 during onboarding, record the change and decide whether explanation, another practice task or a new training assignment is appropriate. Retain the earlier assignment and attempt's original content context. Do not relabel old evidence as if the learner used new instructions. In SOPFlow, assigned training retains a procedure snapshot and version reference; the learning attempt records its result. A separate run records the particular task. Use these records alongside the manager's practical review. Product records do not automatically establish readiness for every part of a role. ## Maintain the plan and download the example Review the plan after an onboarding cycle and when the role, tools or supporting instructions change. Record the question, resolving owner and next review instead of simply extending a checklist. Distinguish the company welcome, role-specific learning and individual practice records. ## Blank onboarding plan and review record - **Role and permitted first responsibility:** __________ - **Learner reference:** __________ - **Manager, buddy and procedure owner:** __________ - **Procedure/version references:** __________ - **Task, resolving owner and agreed date:** __________ - **Completion evidence or blocker:** __________ - **Ordinary-case practice observation:** __________ - **Exception-case practice observation:** __________ - **Manager decision, scope and support:** __________ - **Learner question and correction owner:** __________ - **Next review:** __________ https://sopflow.io/blog/employee-onboarding-sop/