# Get a new hire doing real work in their first two weeks Version 1.1 ยท Kramaniti Kosh > How to use this file: fill in the Working template section below. It opens in any text editor, or you can paste the whole file into ChatGPT, Claude or Gemini and ask it to help you fill it in for your business. ## Intended outcome A written plan for a new person's first two weeks: the real tasks they do each day, the written steps they follow, who answers their questions and what a named person checks before their work reaches a customer, so they become useful quickly without the owner explaining everything twice. ## Before you begin - The new person's role, start date and working hours - A list of the tasks this role does in a normal week, written by whoever does them today - Any written steps, checklists or sample work you already have, even rough ones - One person who will be the new hire's go-to for questions, and a backup for when they are busy - Your notes on what the new person must not do alone yet, such as handling money, giving prices or talking to an upset customer ## How to use 1. Fill in the role details and the task list with the person who does the work today. Mark each task as something the new hire can watch, do with help or do alone, and note where its written steps are. If a task has no written steps, write "no steps yet" rather than leaving it blank. 2. If you like, paste your filled-in notes into an AI tool and ask it to draft the day-by-day plan in the layout below. Tell it to use only the tasks and steps you gave it and to mark anything it is unsure about. Then read the draft line by line with the go-to person and fix what does not match how the work is really done. 3. Give the new person the plan on their first day. The go-to person checks in at the end of each day for the first week and fills in the review notes at the end of each week. Any question the new person asks twice goes on the list of steps to write down. ## Working template ## Role and people Business: Role the new person is joining as: Start date: Working hours and days: Go-to person for questions: Backup when the go-to person is busy or away: Who signs off the plan before day one: ## What the role does in a normal week List each task. For each one, write how often it happens and where its steps are written down. Task 1: - How often: - Where the steps are (checklist, sample, video, "no steps yet"): - Who does it today: Task 2: - How often: - Where the steps are (checklist, sample, video, "no steps yet"): - Who does it today: Add more tasks the same way. ## What the new person does not do alone yet The new person asks the go-to person before doing any of these, until the go-to person says otherwise in writing. - Taking or returning money, or giving credit - Giving prices, discounts or dates to customers - Handling a complaint or an upset customer - Anything involving customer data, passwords or bank details - Add your own: ## Before day one - Login, tools and equipment ready (list them): - Written steps printed or shared: - Team told who is joining and when: - First task picked for day one: ## Week one, day by day For each day, write the tasks, whether the new person watches, does with help or does alone, and what the go-to person checks. Day 1: - Tasks: - Watch, with help or alone: - What gets checked, and by whom: Day 2: - Tasks: - Watch, with help or alone: - What gets checked, and by whom: Day 3: - Tasks: - Watch, with help or alone: - What gets checked, and by whom: Day 4: - Tasks: - Watch, with help or alone: - What gets checked, and by whom: Day 5: - Tasks: - Watch, with help or alone: - What gets checked, and by whom: ## Week two Tasks the new person should do alone by the end of week two: Tasks still done with help: Work that is still checked before it reaches a customer: ## Questions and how they get answered Where the new person writes down questions (notebook, WhatsApp group, shared sheet): When the go-to person answers them (for example at the end of each day): Questions that cannot wait, and who to call: ## End of week reviews End of week one: - What the new person can now do alone: - What still needs help: - Questions asked more than once: - Steps to write down or fix: - Reviewed by: End of week two: - What the new person can now do alone: - What still needs help: - Questions asked more than once: - Steps to write down or fix: - Reviewed by: - Decision on what they can now do without asking: ## Stop rules - The new person does not do anything on the "not alone yet" list without asking, however confident they feel. - If the plan names a task with "no steps yet", the go-to person shows it in person before the new hire tries it. - An AI-drafted plan is not used until the go-to person has checked every task and step against how the work is done today. - If the go-to person is away for a day, the backup takes over or the new person repeats tasks they already know. - Only the go-to person or the owner moves a task from "with help" to "alone", and they write it in the review notes. ## Demonstration This is an illustrative scenario, not a client case study or a measured result. Do not reuse its details as facts about your work. A sample multi-brand two-wheeler service garage in Bengaluru services scooters and motorcycles of several brands. The owner runs the front desk and the senior mechanic leads the workshop. They are taking on a new service advisor who will receive bikes, write job cards and update customers on WhatsApp. ### Sample inputs Demonstration inputs only. No real figures are used. From the owner and the senior mechanic: the advisor receives bikes in the morning, notes the customer's complaint and the odometer reading on a job card, takes photos of existing scratches, updates customers on WhatsApp when the bike is ready and hands over the bike with the bill. There is a written job card format and a photo checklist. There are no written steps for explaining extra work found during a service. The owner wants the advisor to stay away from giving prices for extra work and from handling payment disputes for now. ### Example output #### Role and people [Fact within this demonstration] Role: service advisor. Go-to person: the owner. Backup: the senior mechanic. Plan signed off by the owner before day one. #### What the new person does not do alone yet [Fact within this demonstration] No prices or approval for extra work, no payment disputes, no promises of ready times that the senior mechanic has not confirmed. #### Week one, day by day [Inference] Day 1: watch the owner receive bikes and write job cards using the written format. Day 2: write job cards with the owner checking each one before the bike goes into the workshop. Day 3: take photos with the checklist and write job cards, owner checks. Day 4: send "bike ready" updates on WhatsApp from messages the owner has approved, owner reads each before it is sent. Day 5: hand over bikes with the bill alongside the owner. Explaining extra work found during a service stays with the owner, because there are no written steps for it yet. #### End of week one review [Recommendation] The owner writes down the steps for explaining extra work to customers in week two, using the questions the advisor asked during week one, and checks the new steps with the senior mechanic before the advisor uses them. This recommendation is not the business's decision. ## Quality check Every task in the plan is one the role really does, and each one says where its steps are or says "no steps yet"; each day says whether the new person watches, works with help or works alone; the "not alone yet" list covers money, prices, complaints and customer data; a named go-to person and a backup are written down; any AI-drafted part was checked by the go-to person against how the work is done today; both weekly reviews are filled in and signed by a named person. ## Limits and human review The plan helps a new person learn the real work in a set order; it does not replace training on safety, legal or tool-specific rules, and it does not tell you whether someone is right for the job. A named go-to person checks the plan before day one, checks the new person's work as the plan says, and decides when each task can be done alone. If you use AI to draft the plan, it only arranges what you gave it; it does not know your business, and a person checks every line. Tasks with no written steps are a sign to write them down, for example with [Turn the founder's know-how into written steps](/kosh/founder-memory-sop-agent/). A filled template is not approval for the new person to handle money, prices or customers alone. Keep consequential actions with the named human owner. ## Edition notes New in Kosh at version 1.1. Provider-neutral Markdown instructions; no installation or platform compatibility is implied. Runtime behaviour has not been verified across AI providers. Reuse terms have not yet been published. Background reading: [Show the Support Route Before Rollout](/insights/show-the-support-route-before-rollout/). Helping a team keep its written steps, support routes and new-joiner plans current as the work changes is part of Kramaniti's [Complete Lifecycle Retainer](/retainer/).