How to use Trainual: your first subject, topic and training path

Trainual, a platform for writing up and assigning company process documentation, organizes everything around three nested concepts: subjects, topics and training paths. Getting these three right for your first real process matters more than exploring every feature, so this walkthrough focuses on one worked example rather than a full feature tour. If you are still deciding whether you need it, see Trainual vs Notion for SOPs.

Plain steps, with a worked example

Say you're setting up onboarding for a new customer service hire. Here's the practical order.

• Pick one real process first. Not "customer service training" broadly, something specific and concrete, like "how to handle a refund request." A specific first topic is easier to write accurately and gives you a real test of the platform.
• Write the topic. A topic in Trainual holds the actual content, text steps, checklists, embedded video or screen recordings. Write it the way you'd actually explain the process to a new hire standing next to you, including the judgment calls and exceptions, not just the clean, ideal-case steps.
• Group related topics into a subject. Once you have a handful of related topics written, "handling a refund," "handling a complaint," "escalating to a manager," group them under one subject, something like "Customer Service Procedures." A subject is the folder-level container; topics are the actual documents inside it.
• Build the subject into a training path. A training path is the assignable, trackable unit, a sequence of subjects and topics someone works through in order, with optional quizzes and sign-off steps along the way.
• Assign it to a role, not a person. Assigning a training path to a role, like "Customer Service Rep," rather than to named individuals one at a time, means every new hire in that role automatically gets the training without you having to remember to assign it manually each time.

Assigning people and roles properly

Trainual's org chart feature lets you map roles and who reports to whom, and tying training paths to roles rather than individuals is the single biggest time-saver once you have more than a handful of staff. The setup cost is upfront: defining roles clearly and building them into the org chart, but it pays off every time you hire someone new into an existing role, since the right training is already waiting for them rather than something you have to remember to assign. The same idea works in other tools: assigning training by job role.

A common structural mistake to avoid early: subjects that are too broad

A frequent early mistake is building one giant subject, "Company Operations," and dumping every topic into it regardless of how related the content actually is. This makes the content harder to navigate and harder to assign cleanly by role, since a training path pulling from an overly broad subject ends up including irrelevant topics alongside the relevant ones. A better pattern: keep subjects narrow enough that everything inside genuinely belongs together and would reasonably be assigned to the same role, "Customer Service Procedures" rather than "Operations," "Warehouse Safety" rather than "All Policies." If you're unsure whether a subject is too broad, check whether you could assign the whole thing to a single role without including anything irrelevant to that role; if you can't, it's a signal to split it into narrower subjects.

Tracking completion properly

Trainual's completion dashboard shows who's started, finished and signed off on each training path. The part worth being deliberate about: add a short quiz or an e-signature step anywhere a mistake would genuinely matter, a refund policy, a safety procedure, a client-facing script, since "opened the document" and "actually understood it" are different things, and only a quiz or explicit sign-off distinguishes between them. For low-stakes topics, simple completion tracking without a quiz is enough.

A practical note before you build everything

Resist the urge to document your entire business before assigning anything. Build one real subject and training path, assign it to one real new hire or existing staff member, and watch what happens: does the completion tracking catch a real gap, do they finish it without getting stuck, did a quiz step actually confirm understanding. That one real test tells you more about how to structure the rest of your content than a week of planning would. For a full week-by-week plan, see setting up Trainual for 15 people.

A worked second example: building out from one subject

Once your first subject is working well, the natural next step is usually role-based rather than department-based. Instead of building one giant "Operations" subject covering everything, build separate subjects per role, "Customer Service Rep," "Warehouse Associate," "Office Manager," each with its own training path. This keeps each new hire's onboarding focused on exactly what their role needs, rather than making them sit through content meant for a different job, which is the single most common structural mistake I see businesses make when they first set this up.

Writing a topic that actually holds up once a real person uses it

A topic that reads well to the person who wrote it often fails the moment someone unfamiliar with the process tries to follow it, because the writer unconsciously skips steps that feel obvious to them. A reliable fix: after writing a topic, read it line by line and ask, at every step, "would someone who's never done this know exactly what to do next, with no outside knowledge." Common gaps this catches: an unstated tool or login the person needs before they can even start, a judgment call presented as if it were automatic ("check if the order is urgent" without defining what makes an order urgent), and a missing "what to do if this goes wrong" step for the most common failure point in the process.

A worked example of a full training path structure, start to finish

Continuing the customer service example: a complete "Customer Service Rep" training path might open with a short welcome topic covering team structure and who to ask for help, then move into the core process topics, handling a refund, handling a complaint, escalating to a manager, each with a short quiz checking understanding of the judgment calls rather than just the mechanical steps. It closes with a short "shadow and confirm" step, where the new hire handles one real case under supervision and a manager marks it complete manually, combining the platform's automated tracking with an actual human check on day-one performance. This structure, welcome, core content with quizzes, a supervised real-world check, scales down to a two-topic path for a very simple role and up to a much longer one for a complex role, without changing the underlying shape.

How I'd approach this

Start with the one process that currently causes the most confusion when someone new has to do it, write that topic first, and get it in front of a real person within the first week rather than spending that week on structure alone. The platform's structure, subjects, topics, training paths, is simple enough to adjust later; getting your first real content written and tested is the part that actually matters early on. If you're mid-setup and hitting a specific UI question this guide doesn't answer, Trainual's own help center documents the current click paths more precisely than a general guide can, since the interface does change over time. Use the trial period to test exactly this, as the Trainual free trial guide suggests.