The counter-instinct to resist: most documentation advice says to write things down after you see what the new hire struggles with. That’s backward. The documentation that shortens ramp time is written before the hire starts, when you still know things they will spend their first month discovering.
Most of what a new hire needs in their first thirty days is known before they begin: the role’s tasks, the tools, the relevant relationships. All of it is in someone’s head. None of it is organized in one place.
The cost of not documenting it before day one isn’t zero just because the hire eventually figures it out. Every hour spent figuring it out is an hour not spent doing the job, and the cost lands on the existing team, not just the new hire.
The Day-One Ready Documentation Set builds this documentation before the hire arrives. It connects directly to the milestone plan from How to Build a 30-60-90 Day Onboarding Plan That Actually Gets Used: the plan sets the milestones; this set gives the hire what they need to reach them.
Why Documentation Gets Done Reactively
The obvious reason documentation happens after: it’s written in response to a question. The new hire asks something, the owner realizes it should have been written down, and it gets written down. Eventually.
The less visible cost is that reactive documentation is incomplete. The things a new hire asks about are the things they know they don’t know. The things that actually slow ramp time are the things they don’t know to ask about. The confusing process, the client relationship with unexplained history, the tool being used differently than its label suggests.
Reactive documentation captures the visible gaps. Pre-start documentation captures the invisible ones.
The owner writing documentation before the hire begins knows both what needs to be known and what the hire won’t think to ask. That combination disappears after day one, when the dynamic shifts to answering questions rather than anticipating them.
The Day-One Ready Documentation Set
The set has four documents. None is long. Together they give the new hire a starting point rather than a blank page.
Document 1 is the access and setup list
Every new hire needs access to tools, accounts, and systems before they can begin working. The access list is a simple inventory: the tools, the accounts, the logins or contact for each, and in what order to set them up.
Writing this list takes thirty minutes and eliminates one of the most common sources of day-one friction. The new hire who arrives to find a setup guide can configure their working environment independently. The new hire who arrives to find no guide spends day one interrupting the owner or the existing team.
Document 2 is the role brief
The role brief is the translation of the hiring process materials into onboarding materials. It frames the success definition and non-negotiable traits as day-one orientation: what this person was hired to produce and what defines success.
The role brief answers the question the new hire will not ask out loud on day one: “Do I understand why I’m here?” When that question is answered before it’s asked, the hire starts oriented rather than searching for orientation.
Document 3 is the context record
The context record is the history the new hire cannot get from looking at the present state. Why a certain process works the way it does. Which clients need particular handling and why. What was tried before the current approach and why it was abandoned.
This document is the hardest to write because it requires the owner to surface knowledge that is so embedded it feels obvious. Nothing in the context record is obvious to someone who has never been in the role. Writing two to three pages of context before the hire begins saves three to six months of accumulated discovery.
Document 4 is the day-one agenda
The day-one agenda is a literal schedule: what happens in what order, who the hire meets, what they read. It ends with one specific thing they should have done by close of day one.
A new hire’s first day sets the tone for the entire onboarding experience. A first day with a clear agenda signals that the business was prepared for them. A first day without one signals the opposite, even if everything eventually goes well.
How the Living Library Builds Your Pre-Start Documentation
Before a new hire existed at this business, there was a first one. That hire required the same set: access list, role brief, context, and agenda. The Living Library holds what was built for that hire, including what was learned when it wasn’t quite right.
The Living Library is the part of the Kiluma platform where your accumulated onboarding knowledge is organized and maintained. The Conductor, Kiluma’s context-aware AI, reads from the Onboarding Collection to build the Pre-Start Documentation Set for each role from the materials of prior hires.
When the next hire is confirmed, you open the platform and find the set already assembled. The access list reflects current tools, the role brief reflects the last 30-day check-in, and the context record includes what the prior hire’s observations added. The day-one agenda reflects what has worked.
The owner doesn’t compile the pre-start documentation from scratch. They review what the Library has maintained and approve it before day one.
Write Document 3 This Week
The hardest of the four documents is the context record, and it’s the one most likely to be left undone. Write it this week, before a hire is imminent.
Open a document and write for thirty minutes without stopping. What does a new person need to know about the way things work here that they wouldn’t know from looking at the job? What has been tried and abandoned? What relationships have history that affects how they should be handled?
The first draft doesn’t have to be complete. It has to exist. The next hire will have a foundation.
The Blank Page, Before and After
The new hire who arrives to a blank page spends their first month discovering what a document could have told them in an hour. The one who arrives to the Day-One Ready Documentation Set starts oriented. Both will ask questions; only one starts from something. Try Kiluma free for 14 days at kiluma.ai.