Most small businesses spend more effort writing the job description than documenting the role. The job description is for people who haven’t joined yet. The role documentation is for the person who just did. Almost no small business has the second one.
New hires who struggle in their first sixty days are almost always failing at undocumented expectations. The work they were hired to do makes sense to the person who explained it once during onboarding. It does not yet make sense to the new hire who heard it once while distracted by everything else that was also new.
Role documentation is what closes that gap. It is not a training manual. It is a structured record of what the role requires, what success looks like, how decisions get made, and who to ask.
The Role Documentation Set gives you the structure to build this before the next hire starts.
Why New Hires Fail at Undocumented Expectations
The obvious problem: you explained everything during the first week. The new hire nodded. Six weeks in, they’re still asking the same questions.
What looks like a memory problem is usually a documentation problem. The expectations, the processes, the decision rights, and the communication norms were never written down. They were transmitted verbally once, under conditions where the new hire was processing everything as new. Verbal transmission is not documentation.
The less visible cost is what this does to your time. An undocumented role makes you the new hire’s primary reference. Every question that belongs in a written document comes to you instead. When the first few weeks cost as much of your time as doing the work yourself, the role was not documented.
The deepest problem is that undocumented roles rebuild from scratch with every hire. What the last person figured out, what worked, and what needed to change lives nowhere. The next hire starts from the same uncertainty.
The Role Documentation Set
The set has four documents. None is long. Together they give the new hire what they need in their first thirty days and in the thirty after that.
Document 1 is the role brief
The role brief is one page. It states the role’s primary output, the two or three non-negotiable traits, the scope of decision-making authority, and the 90-day success definition.
If you built the Role Success Standard from How to Define What Success Looks Like Before You Post a Single Job and the scorecard from The Role Scorecard That Makes Hiring Decisions Clearer and Defensible, the role brief is largely already written. It converts those hiring tools into onboarding references.
The new hire reads it on day one and knows exactly what they were hired to produce and what success looks like at day 90.
Document 2 is the how-things-work record
Every role operates inside unwritten assumptions: which tools to use, which decisions to make independently, which require sign-off, and where files live. Most of this exists only in the founder’s head.
The how-things-work record writes all of it down in one place.
This is the document that eliminates the majority of early questions. It is not a policy manual. It is a practical reference a new hire can consult before coming to you.
Document 3 is the context record
Every role sits inside a history. The how-things-work record covers the current state. The context record covers the relevant past: decisions made, approaches tried and abandoned, and what the prior hire learned that shouldn’t need re-discovering.
This document is short. Two or three pages at most. It is written once and updated when something significant changes. Its purpose is to give a new hire the context they would otherwise take months to accumulate.
“We tried X last year and stopped because of Y” is one sentence. Without it, the new hire might try X again, discover Y, and spend six weeks solving a problem that was already solved.
Document 4 is the first-30-days guide
The first-30-days guide is not a training schedule. It is a list of the things a new hire needs to accomplish, understand, or access in their first month.
Who do they need to meet? What do they need to read? What does a typical week look like? What is the one thing they should own completely by day 30?
Answering these questions before the person starts is the difference between an onboarding process and a hope that things work out.
How the Living Library Assembles Your Role Documentation
The first time you document a role, you’re working from what you know. The second time, you’re working from what the last hire taught you.
The Living Library is the part of the Kiluma platform that holds your business’s accumulated knowledge and maintains it over time. Every time you add a hiring note, a 30-day check-in record, or a process update, the Library reads it. It assembles the Role Documentation Set for each role from those inputs and keeps it current.
When the role opens again, you open the platform and find the documentation already updated from what the last hire’s tenure produced. The how-things-work record reflects the current tools and processes. The context record includes what was learned in the last two years. The 90-day success definition has been sharpened by what actually predicted success.
The Conductor, Kiluma’s context-aware AI, can answer specific questions from that documentation. Ask it what the last person in this role struggled with, or which part of the how-things-work record needs updating before onboarding. It reads the accumulated record and returns what the documentation shows.
Write Document 2 This Week
Before you think about job descriptions or scorecards for the next hire, write the how-things-work record for the role you’re most likely to hire for next.
List the tools, the decision rights, the communication norms, and where files live. Keep it to one or two pages. Don’t try to make it exhaustive. Make it accurate as of today.
That document is more useful than any amount of onboarding conversation, because it is still there on day fifteen when the new hire has a question and you’re in a client meeting.
From Blank Page to Role System
A chapter that began with the question of why the wrong candidates keep applying ends with the documentation that lets the right hire succeed. The progression runs:
- A problem-and-diagnosis of the job description (Why Your Job Description Is Attracting the Wrong Candidates)
- A rewrite approach that filters in the right people (How to Write a Job Description That Filters In, Not Just Out)
- A comparison tool that makes the decision evidence-based (The Role Scorecard That Makes Hiring Decisions Clearer and Defensible)
- A documentation set that gives the hire the context to succeed (this article)
These are not four separate hiring projects. They are one role definition system: the same role knowledge, organized for four distinct purposes. The business that builds it stops starting from a blank page every time it hires. Try Kiluma free for 14 days at kiluma.ai.