
Build a new-hire onboarding plan
Give a new hire a real first 30, 60 and 90 days instead of a ride-along and good luck.
The plan is a document, so it can be reused for the next hire.
Each week becomes work on a board with an owner.
How it works
What Lana uses
- The role and where it reports, from your org chart
- Your existing SOPs, policies and training documents
- Job descriptions you have written
- Landscape-industry practice for roles you have not documented yet
What you get back
- A 30/60/90 onboarding plan in LeanDocs
- Week-one detail: paperwork, safety, tools, introductions
- Competency checkpoints at each milestone
- Cards on a board so the manager is accountable for it
You name the role
The position, and the crew or department it sits in.
Lana builds the arc
First week, first 30, 60 and 90 days, with what the person should be able to do at each mark.
It pulls in what you already have
Your SOPs, safety documents and policies become the reading and training steps rather than placeholders.
It becomes work, not a document
Each milestone can be pushed to a board with an owner and a date so onboarding actually happens.
What this looks like today
A good hire starts on Monday. The plan is that they ride with somebody for a while and pick it up.
Some of them figure it out. The ones who leave in ninety days usually leave because nobody ever told them what good looked like.
With LeanScaper AI and Lana
- A written plan per role, reused every hire
- Clear expectations at 30, 60 and 90 days
- Existing SOPs become the training material
- Onboarding shows up as work somebody owns
Pre-built prompts to get you started
You can either type or speak to Lana in English, or Español.
Complete request
“Build a 90-day onboarding plan for a new maintenance crew leader.”
Ask Lana thisShort version
“Onboarding plan for a crew leader.”
Ask Lana thisUsing your documents
“Build the onboarding plan from our existing SOPs and safety training docs.”
Ask Lana thisNarrower ask
“Just the first week for an office administrator.”
Ask Lana this
What needs to be true first
- A role in your org chart makes the plan specific; without one, Lana asks about the job.
- Existing SOPs and policies in LeanScaper make the plan yours rather than generic.
- Review the plan — expectations at each milestone are a management decision.
- LeanScaper does not run payroll or benefits enrollment.
Try these next

Knowledge management
Build an SOP by talking it through
Turn the process in your head into a written SOP your crew can follow without you.
You get: LeanDoc SOP
See how →

Knowledge management
Find an answer from your company documents
Get the answer your policy or SOP already gives, with the document it came from.
You get: Answer + source document
See how →

Operations
Set up a recurring board sweep
Get a standing report on stalled and overdue work instead of finding out by accident.
You get: Rhythm + notification
See how →

Build the plan for your next hire
You probably know who you are hiring next. Draft their first ninety days before their first Monday.

