A first month with a goal for every week and a name against every task.
A week-by-week onboarding plan for one new hire, built around a real piece of work they own by day thirty.
The usual first week is a laptop, a lot of introductions, and a reading pile. Then the manager gets busy, week two goes quiet, and the new person spends a month guessing what good looks like.
30-Day Onboarding Plan defines what success is at day thirty, gives each week one purpose, and assigns an owner to every setup task. It schedules the early check-ins, hands over a first real deliverable in week three, and ends with a structured review.
What it produces.
- →Two or three observable day-thirty outcomes
- →A four-week table with an owner against each task
- →A first deliverable with a reviewer and a standard
- →A recurring one-to-one and weekly note rhythm
- ✦Managers of small teams onboarding someone without a checklist
- ✦Owners hiring their first employees
- ✦Remote managers who need structure for a new hire they cannot see
This Playbook covers one new hire's first thirty days. It does not include the First 90 Days Plan Tool's stakeholder mapping, early-win selection, or do-not-touch list. First 90 Days Plan is for senior hires and new remits where the relationships and the first decisions matter most.
See the First 90 Days Plan Tool ($99) →- →30-day-onboarding-plan.zip: a native Claude Skill. Upload to Settings → Skills in Claude, or unzip to
~/.claude/skills/ - →30-day-onboarding-plan-skill.md: plain markdown. Works in ChatGPT Custom GPTs, Gemini, Claude Projects, agent system prompts, anywhere
- →A README inside the zip with install steps for Claude, ChatGPT, and Gemini
What it does with a real question.
I'm hiring a remote customer support specialist, Priya Nair, who starts Monday, March 3. She reports to our support lead, Dan, and will handle tickets in Zendesk and Slack. Our last two hires spent week one waiting on logins and shadowing nobody, so I need a week-by-week plan for her first thirty days.
The pattern in your last two hires tells you where this plan should start: nothing about Priya's first week should depend on anyone doing something on Monday. Make day one a non-event for IT. Zendesk seat, Slack workspace, macros access, and refund permissions should be live by Friday, February 28, with Dan owning that list and confirming it in writing. If a login isn't working Friday afternoon, that's your problem to fix before she's on the clock, not hers to chase.
Week one, then, is orientation with people attached: a named buddy who sits on live tickets with her for three sessions, plus a short reading list capped at what fits in one day. Week two moves her from watching to doing: ten real tickets answered with the buddy reviewing before send, and a thirty-minute check-in with Dan on day eight, March 10, asking what's unclear. Week three hands her one real deliverable with a due date and a reviewer, say rewriting the canned replies for your most common ticket type, with Dan reviewing a draft early rather than at the end. Week four compares her work to the day-thirty outcome and sets direction for the next sixty days.
Define that outcome now: Priya works her queue alone, and Dan spot-checks five tickets a week and finds no policy errors two weeks running.
Next move: ask Dan today to name the buddy and send you the access checklist by Wednesday.
The full Playbook runs the whole procedure and writes the complete deliverable, not this excerpt.
Written by claude-sonnet-5-5 with this Playbook loaded, 2026-10-11. Checked automatically for length and for copied framework text.
No subscription · free updates within v1.x
Works as a Claude Skill (.zip) and as a plain .md for ChatGPT, Gemini & every LLM
Delivered to your email within 60 seconds · Secured by Stripe
Price includes UK VAT where applicable
Before you buy.
How is this different from just asking Claude directly?
Asked cold, Claude produces a generic thirty-sixty-ninety checklist. This builds the month around your hire's role and your first real piece of work, names who owns each task, and checks that no week is left to chance.
How is this different from a Tool?
Playbooks are systematically produced to a fixed template and priced accordingly ($12.99). Tools are hand-built, one at a time, and go deeper ($39 to $199). A Playbook gives you a reliable method for routine work; a Tool is for when the judgment matters more than the format. This Playbook covers one new hire's first thirty days. It does not include the First 90 Days Plan Tool's stakeholder mapping, early-win selection, or do-not-touch list. First 90 Days Plan is for senior hires and new remits where the relationships and the first decisions matter most.
Will this work with ChatGPT, Gemini, and other LLMs?
Yes. You get a native Claude Skill (.zip) that auto-invokes in Claude, plus a plain .md you can paste into a ChatGPT Custom GPT, a Gemini system prompt, or any LLM. The procedure travels with the file.
Can I share this with my team?
It's licensed for your own personal and professional use. The output it produces is yours to circulate. To put the Playbook itself in the hands of a whole team, email hello@authority.md about team licensing.
What if it doesn't work for me?
If the file hasn't been delivered, or arrives defective or empty, we refund in full: see our refund policy.
People Playbooks are structuring aids. They are not legal or HR advice. Employment law differs between the US and the UK and between states and countries, so check anything touching dismissal, performance plans, pay, or protected characteristics with a qualified HR professional or employment lawyer.