Hiring Your First Employee: What to Document Before Day 1

You have spent years running the business the way you run it. You know which supplier answers the phone on the first ring. You know that Tuesday mornings are the wrong time to call the bank. You know the invoicing sequence, the order-entry workaround, the customer who always pays late but pays eventually, and the six-step close that takes the team through end of day. None of it is written down because you have never needed it written down. It just works.

The employee who just quit didn’t steal your process — you just never wrote it down.

That realization tends to hit hardest not when someone quits, but when you hire your first person. Because the moment you bring someone else into the business, every process you have been running in your head becomes a dependency someone else cannot see. The new hire asks how to do something, you explain it, they do it slightly wrong, you re-explain it. Multiply that by every task you have never documented, across a 40-hour week, and you spend the first month being your own bottleneck.

This guide is for the founder at the point of first hire — hours or days away from the first onboarding problem — who needs to know what to document, in what order, before a new employee shows up.

The Core Problem: You Are the Documentation

When you run a solo business, the gap between “knowing how something is done” and “it is done correctly” is zero. You are the same person. The moment you add a second person, that gap becomes a problem.

The new hire cannot read your mental model. They can only follow the instructions you give them in the moment — which are often incomplete because you have automated the steps in your own head and no longer notice them. You say “just handle the customer inquiry the usual way” and they have no idea what the usual way is, because the usual way lives inside years of your own experience that you have never narrated aloud.

This is not a knowledge transfer problem. It is a documentation debt problem. You have been accumulating undocumented process since the day you started, and the bill comes due the day you hire. (per Made to Stick — Concrete: “the usual way” is not a process; “reply within 2 hours, use the template in the shared drive, cc the account owner” is a process)

The good news: you do not have to document everything before day one. You need to document the right things in the right order. The rest can follow.

What to Document Before Day 1

Not all documentation is equal urgency. Before your new hire arrives, there are five categories that matter — everything else can be built in the first 30 days.

1. The Day-1 Orientation Sequence

The first thing your new hire needs is not a job description. It is an answer to the question: “What do I do when I sit down?”

Document a Day-1 script that covers:

• Where to find everything they need (logins, tools, shared drive or wiki, physical location of supplies, who to ask for what)
• The first three tasks they will complete (start concrete and achievable — something they can finish and feel useful inside the first two hours)
• Who to contact with questions (and when — if you are heads-down in the morning, say so; if they should Slack and wait, say that; do not let them guess)
• What you will cover in the Day-1 check-in (so they know it is coming and they are not worried about being evaluated on things they have not been trained yet)

A Day-1 orientation document does not need to be long. It needs to be specific enough that a nervous new hire can follow it alone for 90 minutes without feeling lost.

2. The Core Revenue-Generating Process

Every business has one process that directly produces revenue. For a service business, it might be the client onboarding sequence. For a product business, it might be the order fulfillment workflow. For a professional services firm, it might be the client intake and project kickoff.

Document this process first — before anything else — because:

• It is the work you most need done correctly from the start
• It is the process most likely to involve customer-facing steps where errors are visible
• It is the one you will be most tempted to “just handle yourself” when it goes wrong, which defeats the entire purpose of hiring

Document the revenue-generating process at the step level. Not “handle the customer order” — the actual steps: log in to the order management system, verify the shipping address before confirming, check inventory before committing a delivery date, send the confirmation email using the template in the shared folder, enter the order into the billing system by end of business day. That level of specificity.

3. Communication Standards

One of the most common friction points in the first 30 days of a new hire is not task quality — it is communication defaults. The new hire emails when you expect Slack. They respond to a customer in a tone that is slightly more formal than your brand. They CC you on everything or CC you on nothing.

Document your communication standards before day one:

• Customer-facing communication: tone, response time expectation, what decisions they can make versus what needs your sign-off before going out, what templates exist and where
• Internal communication: which tool you use for what (Slack vs. email vs. text), when you expect real-time versus async, how to escalate something urgent
• Client communication policy: who communicates with clients, what happens when a client requests something outside scope, what they should do if a client is unhappy before you have been looped in

Communication standards are the process documentation that almost no founder writes before hiring because it feels like common sense. It is not common sense to someone who has never worked in your business.

4. Financial Handling Rules

If your new hire touches money in any form — invoicing, expense processing, taking payments, handling vendor bills — document the financial handling rules before they start:

• Invoicing: who generates invoices, in what system, on what cadence, with what payment terms, what happens when a payment is late
• Expense submission: what is approved without prior sign-off, what requires your approval first, how receipts are submitted, what the reimbursement timeline is
• Payment acceptance: how customer payments are received and logged, what change-of-method requests require verification, what to do if a payment bounces or is disputed
• Vendor payments: who has authority to approve a vendor bill, what purchase level requires your review, how recurring subscriptions are tracked

Financial handling errors are disproportionately expensive to recover from — not because the dollar amounts are always large, but because they create trust problems that are hard to diagnose and harder to fix. Write these rules down before day one.

5. The “Only I Know This” Inventory

Before your new hire arrives, do a fast self-audit: write down every process that only you know how to do. Do not try to document all of them before day one — you will not have time, and the list will be overwhelming. Just write them down as a list.

This list has two purposes: it tells you which tasks to keep off the new hire’s plate until the process is documented, and it becomes your first 90-day documentation roadmap.

A short example of what this list might contain: the vendor account login only you know; the way you handle the customer who calls once a month threatening to leave; the end-of-month reconciliation you run in the spreadsheet; the refresh sequence for the software that crashes every two weeks; the field in the system that has to be checked before you finalize anything for client X.

The act of writing this list is itself valuable — it is the first time you have seen the full shape of your undocumented knowledge. (per Content Inc — content tilt: documenting your own business is the same act as documenting for someone else; the founder is the first person who needs the manual)

Role-Specific SOPs: Two Examples

The right documentation for a new hire depends heavily on the role. Here are two examples — an office or operations admin role and a production or operator role — because these are the two most common first hires in a small business and they need different documentation.

Office or Operations Admin

An office admin’s role typically spans scheduling, customer communication, vendor management, invoicing, and a rotating set of one-off tasks. The risk of undocumented process here is diffuse — it shows up in small ways across many tasks rather than as one catastrophic failure.

The five documents that matter most for an office admin hire:

1. Scheduling and calendar rules. How appointments are booked, what lead time is required, how conflicts are handled, which blocks are protected, what the rescheduling policy is. If you have a booking tool, document the specific workflow inside it — not just “use Calendly” but which calendar it is connected to, what notifications trigger, what to do when a slot is double-booked.

2. Customer communication templates. Even if you only have three or four email templates, write them down. New hires default to their own communication style, which may not match yours. Templates are not constraints — they are the fastest way to get a new hire producing customer-facing work that looks like your brand from week one.

3. Vendor contact and reorder SOPs. Who are your vendors, what is the reorder trigger for consumable supplies, who is the contact, how do you place an order, where does the order get tracked. A new office admin who does not know this list will either interrupt you constantly or make a guess that goes wrong.

4. Invoicing and AR cadence. When invoices go out, what system they are created in, how the payment status is tracked, when a payment is considered late, and what the first-contact script is for a late payment.

5. End-of-week wrap. What tasks have to be completed before the week closes — open items that cannot carry, things to confirm, the state in which the office should be left for Monday.

Production or Operator Role

A production operator’s risks are different: quality, consistency, and safety. When a production step is not documented, the most experienced person does it their way and the new hire does it their way, and the output is inconsistent. Inconsistent output is a customer service problem before it is ever identified as a documentation problem.

The five documents that matter most for a production or operator hire:

1. Process sequence with tolerances. Every production step, in order, with the quality standard at each step. Not just “assemble the component” — at what tolerance, checked how, by whom, before moving to the next step. If there is a step where errors are irreversible, mark it.

2. Equipment operating SOP. For every piece of equipment the new hire will use: startup sequence, safe operating conditions, shutdown sequence, what to do if something looks wrong, who to notify before stopping. Operators who learn equipment from a colleague rather than a written SOP absorb the colleague’s shortcuts along with the correct procedure.

3. Quality inspection checklist. What a passing output looks like. What a failing output looks like. Who makes the call when it is ambiguous. How a defect is logged. What happens to a defective unit — rework, scrap, set aside for review.

4. Safety protocol for their work area. Which PPE is required, what the emergency shutdown procedure is, who the first safety contact is, where the relevant equipment is stored, what to report and to whom.

5. Escalation and stop-work criteria. When the new hire should stop what they are doing and come find you versus handle it themselves. Define this clearly — new hires typically err in one direction or the other (escalating everything or never escalating) and the right boundary is specific to your operation.

The Day-1-Through-Day-30 Onboarding Sequence

Documentation alone does not onboard an employee. The documents have to be introduced in the right order, at the right pace, with the right verification that learning has happened.

A simple structure that works for most first hires:

Days 1–3: Orientation and one complete process.

• Day 1: the orientation sequence (tools, logins, workspace, first tasks)
• Day 2: introduce and walk through the core revenue-generating process — not just read the SOP, but do it together once, then have them do it once while you observe
• Day 3: let them run the core process independently, with you available; note every question and gap — these become SOP additions

Week 2: Expand the scope.

• Introduce two or three secondary processes (support functions, communications, vendor workflows)
• Each introduced the same way: walk through together once, observe them independently once, document questions
• Do not front-load everything in week 2; the goal is understanding, not coverage

Weeks 3–4: Increased independence with check-in structure.

• The new hire handles most tasks independently
• Daily or every-other-day 15-minute check-ins focused on: “what came up that you weren’t sure how to handle?”
• Those situations are the best source of documentation gaps — write them down as they surface

Day 30 review:

• What tasks is the new hire fully confident in?
• What tasks still require your involvement?
• What did you realize you never documented?
• Write those gaps down and put them on the 30–90 day documentation roadmap

The 30-day review is not a performance review. It is a documentation audit. The best outcome is a list of what still needs to be written — not a judgment of how the new hire is performing.

The “I’m the Only One Who Knows This” Problem

Every solo founder has a set of processes they cannot hand off — not because the tasks are too complex, but because no one else has ever been taught them. These are the true bus-factor risks: if you are unavailable for two weeks, these tasks either do not happen or happen incorrectly.

The most common categories:

• System access and vendor relationships. You are the account holder. You are the primary contact. You have the login in your head. When a vendor calls with a billing dispute, you are the only one who can resolve it because you are the only one who knows the history.
• Exception handling. The way you handle customer escalations. The judgment calls you make when something breaks. The mental framework you apply when the normal process does not cover the situation.
• The institutional history. Why a certain customer gets a certain discount. Why you stopped using a certain vendor. Why the process is set up the way it is and not some other logical way.

The fix is not to document all of this before your new hire starts. The fix is to acknowledge that this knowledge exists and build a habit of narrating it whenever it surfaces. When you make a judgment call, write it down as a rule. When you handle an exception, write it down as an exception SOP. When you override a process, write down why.

Over the first 90 days, this habit produces a catalog of institutional knowledge that would take years to write in a single dedicated project. (applying StoryBrand: the founder is the guide, not the hero — the new hire is the one who needs to be able to operate; the documentation is the tool that makes that transfer happen)

What to Document in the First 90 Days vs. What to Defer

There is a failure mode where a founder, energized by the project of onboarding a new hire, tries to document everything and burns out before finishing anything useful. The resulting documentation is a half-written 40-page manual that no one ever opens again.

Document in the first 90 days:

• Any process the new hire will execute in the first 30 days
• Any process where an error has a direct customer or financial consequence
• Any process that only one person knows how to do (starting with yours, then moving to the new hire’s as they learn them)
• The exception-handling rules you apply most frequently

Defer beyond 90 days:

• Processes that run quarterly or less frequently
• Historical and contextual documentation (why the business is set up the way it is)
• Nice-to-have reference materials that do not affect daily execution
• Processes that are likely to change in the next six months

The 90-day documentation sprint should produce 10–15 solid, usable SOPs — not a comprehensive library. A small number of highly-used, accurate documents outperforms a large collection of half-finished ones every time.

When Not to Document: The Anti-Pattern

Not everything should be documented. There is a documentation anti-pattern that wastes significant time: writing SOPs for one-off situations that will never recur.

If a customer had a unique escalation that you handled as a special case and will never come up again — do not write an SOP for it. If a piece of equipment broke in an unusual way and the repair was a one-time workaround — document the equipment maintenance log entry, not a formal SOP. If you made a policy exception for a specific client — note it in the client record, not in your policies.

The test for whether to write an SOP: will a different person face this situation at least once per quarter? If the answer is yes, document it. If the answer is no, log it and move on.

Time spent documenting rare one-offs is time stolen from documenting the high-frequency processes your new hire will face this week. Prioritize ruthlessly.

The Founder’s Documentation Debt

Most founders discover their documentation debt at one of three moments: when they hire their first employee, when they are trying to take their first real vacation and realize they cannot, or when a key person leaves and the business discovers how much it depended on one person’s undocumented knowledge.

All three moments are the same problem. The hire is the earliest warning — which is why it is also the best time to start.

The documentation debt you accumulated running the business yourself is not a failure. It was rational: you were the process. Now you are building something larger than you can run alone, and the process has to live somewhere other than your own head.

The good news is that the debt compounds both ways. Every SOP you write now is a process you will never have to explain from scratch again. Every template you build is a standard you will not have to re-enforce through correction. Every onboarding document you create now works for the second hire, the third hire, and every hire after that without additional investment.

The founder who starts documenting at first hire builds an asset. The founder who defers it to “when things slow down” pays interest on the delay with every new employee they bring on without a system.

A Simple Starting Point

If you are days away from your first hire and feeling behind on documentation, here is the minimum viable set:

1. Day-1 orientation document (where things are, who to ask, what to do first)
2. Core revenue-generating process (step-by-step)
3. Customer communication standards (tone, templates, response times)
4. Financial handling rules (what needs sign-off, what doesn’t)
5. The “only I know this” inventory list (even as a rough draft)

Five documents. If they are specific and honest, they are worth more than a 100-page operations manual that describes the business as it should work rather than as it actually works.

Start there. Add to it every time a question surfaces that the documents don’t answer.

Ready to Start?

Download the free SOP template — a structured starting point you can fill in for each of the five documents above before your new hire arrives.

If you’re ready to move from individual documents to a system your whole team can access, search, and train against as you grow, see how What’s the Process For works for businesses at your stage — or start a free trial and build your Day-1 orientation document in the next hour.

Related Reading

• What Happens When an Employee Quits — the full cost of undocumented processes when your most experienced person walks out the door; the first-hire problem and the key-employee-departure problem are the same problem at different stages
• Employee Knowledge Transfer Template — the structured process for extracting institutional knowledge before a long-tenured team member leaves; useful to run in reverse when you are the long-tenured person handing off to a new hire
• Employee Onboarding Checklist — the day-by-day task list for the first 30 days once the documentation is in place
• Standard Operating Procedure Examples — specific SOP templates across industries if you want to see what a well-structured procedure looks like before you write your own

---

The best time to document your processes was before you hired. The second best time is right now. Start your free trial and get the documentation done before day one.