The outcome.
A new colleague arrives on Monday and the plan is already there: the first week day by day, and a clear picture of productive at day 30, 60 and 90, written as work the colleague will be doing.
Most companies have one manager who plans a start like this. This capability gives every hiring manager that standard, built from their own role and training material. The people lead sets it once and every start gets it. That is 10X what a small people team can do alone.
The manager adapts the plan and judges progress. The new colleague shapes it in week one.
Who starts the work, and when.
The hiring manager starts it once the start date is confirmed, ideally two weeks before day one. The people lead owns the company-wide parts: required training, first-day arrangements and the check-in rhythm. Manager and new colleague read it together on day one, and the manager updates it after each check-in.
What they supply.
- The role’s agreed responsibilities.The role brief agreed before recruiting, or a current job description.
- The team’s training material.Procedures, system guides and recorded walkthroughs, each with its date.
- The start date and working pattern.Hours, site and any remote days.
- The people to meet.By role, including the buddy.
- The company’s onboarding standard.Required training and first-day arrangements, set by the people lead.
What comes out.
A draft plan in four parts: what to confirm before day one, the first week, milestones at day 30, 60 and 90, and the check-ins. Every gap goes to the manager by name, such as a responsibility with no training material or a guide past the team’s age limit.
Access, equipment and invitations stay with the teams that own them. The capability never assesses the new colleague and never drafts an offer letter or other employment document.
Illustrative example with invented data. An invented 120-person freight and warehousing company.
Onboarding plan · Customer operations coordinator · Starts Monday 16 November 2026
- Prepared for
- The customer operations manager, as hiring manager.
- Before day one
- Confirm with IT that order-system and carrier-portal access is requested. Confirm the buddy, a senior coordinator. Write and send the welcome note.
- Week one
- Monday: people lead welcome, site tour, safety induction. Tuesday: read the shipment-exception procedure; shadow the buddy on status calls. Wednesday: order-system guide on the training account. Thursday: meet the transport desk lead and a warehouse shift manager. Friday: answer five routine inquiries with the buddy reviewing each; first check-in.
- Day 30
- Answers routine shipment-status inquiries alone. The buddy reviews five each week.
- Day 60
- Handles carrier delay exceptions to the agreed procedure. The manager reads each customer message before it goes.
- Day 90
- Owns day-to-day inquiries for 20 accounts and writes the night-desk handover note on their shifts.
- Check-ins
- Weekly for four weeks, then at days 30, 60 and 90: what went well, what got stuck, the next milestone, the support needed.
- For the manager
- Responsibility 5, “Raise damage claims with carriers”, has no training material. Name who teaches it and when. The order-system guide is dated March 2025, past the team’s 12-month limit. Confirm it matches the current screens before Wednesday.
A draft for the hiring manager, who adapts it and judges progress at each check-in. The new colleague adds to it in week one.
Where it fits.
- Logistics and trade: shifts, several sites and procedure-heavy roles.
- Manufacturing: safety induction and supervised practice need a sequence and an owner.
- Professional services: the day-30 expectation must be explicit when time is billed.
- People and HR: one standard, set by the people lead, for every hiring manager.
- Recruiting and hiring: the agreed role brief becomes the plan’s starting point.
- Growth & scaling: ten managers hiring at once, every start planned with the same care.
- Acquisitions & integration: a joined team learns new systems on one plan.
What has to change for your company.
Set the standard first: the check-in rhythm, the age limit for training material, the training every start completes and how productive is written for your roles. Training material usually covers the routine case; capture the exceptions experienced colleagues handle with SOP exception capture.
Map the handoffs to IT, facilities and the buddy so every confirmation has an owner. Prove it on one real start, then roll it out. Fully Powered works across ChatGPT, Claude, Copilot and Gemini, at your pace, and your company keeps control of how the work gets done.
What has been checked.
Fully Powered AI wrote this capability template. It was editorially reviewed on 9 November 2026. It has not yet been tested in a client environment. It has not yet been tested as a packaged version in ChatGPT, Claude, Copilot or Gemini.
Testing in your environment means running it on your roles and training material against cases written in advance, such as a responsibility with no training or an unconfirmed start date. The hiring manager and the people lead judge each draft against the expected behavior. Pilot acceptance-test preparation sets those cases up, and what we test before we call an AI workflow ready describes the record we keep.
Next step.
Bring one role you are hiring for and the training material its team uses today.
Related capabilities.
- Manager feedback preparation: the check-ins at day 30, 60 and 90 become prepared conversations.
- SOP exception capture: the exceptions your training material leaves out.
- The worked example: Recruit, train and develop: a capability map for the people function.