Setting up Trainual for a 15-person team in one week

Trainual, a platform for writing up and assigning company process documentation with training-path tracking, is genuinely usable within a week for a team this size, but only if you resist the urge to document everything at once. Here's a day-by-day plan that prioritizes a small amount of genuinely useful, tested content over a large amount of untested content.

Day by day

• Day 1: pick your five highest-impact processes. Not the processes that are easiest to write, the ones that cause the most mistakes, questions or inconsistency when done wrong. For most 15-person businesses, this is a mix of a customer-facing process, an onboarding step, and one or two role-specific technical tasks.
• Day 2: set up the org chart and roles. Map who reports to whom and define your actual roles (not job titles, functional roles like "Field Technician" or "Office Coordinator") before writing content, since you'll assign training to these roles rather than to named individuals.
• Day 3 to 4: write the five processes. Use the template library as a starting structure for each, but write every step in your own words, based on how the work is actually done, not a generic version. Budget roughly half a day per process for a team this size, including a round of checking with whoever actually does the job. Screen-by-screen detail is in how to use Trainual.
• Day 5: build training paths and assign by role. Group the written topics into subjects, build training paths, and assign each one to the relevant role so it's automatically waiting for anyone currently or newly in that role. Assignment is explained in assigning training by job role automatically.
• Day 6: run a real test with two or three actual staff. Not a demo, have two or three real people actually complete the assigned training and flag anything confusing or wrong. This is the single most valuable day of the week, since it catches gaps that writing alone never surfaces.
• Day 7: fix what the test surfaced, and set a follow-up date. Fix the specific gaps from day 6, then put a date on your calendar, 30 to 60 days out, to check the completion dashboard and ask two or three staff whether the content still matches how things actually work.

What to write first: the five processes that cause the most mistakes

For a 15-person business, these five tend to repeat across industries: the first interaction a new customer or client has with your business, the step where money or a commitment changes hands (a quote, a contract, a payment), the most common support or complaint scenario, the handoff between two roles that most often goes wrong, and whatever safety or compliance step carries the most real risk if skipped. Writing these five well, with real detail and a tested round of feedback, beats a comprehensive but shallow attempt to document the entire business in the same week.

Adjusting the plan if your 15 people span several very different roles

The one-week plan above assumes your 15 people cluster into a small number of roles, which is true for most small businesses but not all. If your team genuinely spans several very different functions, say, five in sales, five in delivery, five in support, with little overlap in what they actually need to know, consider running the plan in parallel rather than sequentially: assign one person to own writing each role's highest-impact process simultaneously during days 3 and 4, rather than trying to have one person write content for roles they don't actually understand well. This keeps the one-week timeline realistic even for a more functionally diverse team, since the bottleneck becomes coordination rather than any one person's writing capacity. Fit for small teams is discussed in Trainual for small business.

Rollout and follow-up, beyond week one

Tell staff plainly during rollout that this is a living system, not a one-time project, and that flagging something confusing or outdated is expected and welcome, not a complaint. The businesses that keep Trainual genuinely useful build a small ongoing habit: whenever something goes wrong twice, someone updates the relevant topic once, rather than letting outdated content sit untouched for months. Check the completion dashboard roughly monthly for the first few months to confirm training assignments are actually reaching new hires as expected, since a misconfigured role assignment can silently mean someone never gets training they should have.

A worked example: a 15-person landscaping company's actual week

Say a 15-person landscaping company runs this plan. Day 1, the owner and two crew leads agree the five highest-impact processes are: the initial client walkthrough and quote, the new-client welcome sequence, the mowing and maintenance crew checklist, handling an on-site damage complaint, and the equipment safety checklist for new seasonal hires. Day 2, they map three real roles into the org chart: Crew Lead, Crew Member, and Office Coordinator, rather than individual names. Days 3 and 4, each of the five processes gets written by whoever actually owns it daily, the office coordinator writes the welcome sequence, a crew lead writes the equipment safety checklist, rather than the owner writing everything alone from a desk. Day 5, these get built into three role-based training paths. Day 6, two new seasonal hires starting that week go through the Crew Member path for real, and one genuinely catches that the equipment checklist skips a step about reporting a damaged tool, which gets fixed immediately. Day 7, that fix goes live, and a 45-day follow-up reminder goes on the calendar.

What to do if the week genuinely slips

If days 3 and 4 run long because the writing takes more real time than expected, which happens often since good SOP writing is genuinely harder than it looks, protect day 6, the real staff test, over finishing all five processes on schedule. Three well-tested SOPs are more valuable than five rushed, untested ones. Push the remaining processes into week two rather than compressing the test to keep an arbitrary one-week deadline, since the entire point of this plan is producing content people actually trust, not hitting a specific calendar date.

Common pitfalls specific to a team around 15 people

Two mistakes come up often at this size. First, letting one person, usually the owner, write everything alone rather than pulling in whoever actually does each job daily, which produces content that reads well but misses the real, lived details only a hands-on person would think to include. Second, skipping the role-based org chart step because "everyone just knows who does what" at 15 people, which works fine until the business hires three people at once and training assignment becomes a manual, easy-to-forget task instead of an automatic one. Both mistakes are easy to avoid by deliberately including days 2 and 6 in the plan above rather than treating them as optional. If something stalls, see Trainual not working.

How I'd approach this

I'd protect day 6, the real test with actual staff, above everything else in this plan. It's tempting to spend the whole week writing and skip the test to "save time," but an untested training path for a 15-person team can quietly fail in ways you won't discover until a new hire makes a real mistake. A focused week that includes a genuine test with real people, even if it means writing slightly less content, produces a system people actually trust and use.