From Process to Playbook: How to Build Role-Based Training Automations With Trainual

A practical field guide from Automation Ace.

Most small businesses run on knowledge that lives in a few people's heads. When someone new joins, they shadow, ask questions in Slack, and slowly piece together how things work. When someone leaves, part of the business leaves with them. A playbook fixes that: one place that documents how the business works, organized so each person sees what their role needs.

Trainual is a tool for building that how-to guide for your business. This guide shows how to go from undocumented processes to a role-based playbook, then automate the busywork around it: inviting new hires, assigning training by role, moving people through onboarding phases, reacting to test results, retraining when processes change, and removing access when people leave.

Why role-based training beats one big manual

• Relevance: a support rep does not need the commission policy, and a sales rep does not need the refund workflow. People finish training that is clearly about their job.
• Automation: when training is attached to roles, assigning a role is one step. Without roles, someone has to remember which 14 documents each new hire needs.
• Accountability: mapping responsibilities to roles shows who owns each process and exposes gaps where nobody does.
• Change management: when a process changes, you know exactly which roles need to relearn it.

What Trainual is

Trainual is a training and documentation platform for documenting processes, policies, and standard operating procedures (SOPs), then assigning them to the right people. Based on its published features at the time of writing, it includes:

• Structured content: documentation organized into subjects (collections of related content), topics, and steps, with text, images, video, and embeds.
• Roles and responsibilities: roles that bundle responsibilities and training, plus an org chart view.
• Assignment and tracking: assign content to people, roles, or groups, set due dates, and track completion.
• Tests: quizzes that check understanding.
• AI assistance: in-app AI that helps draft documentation.
• Integrations: including a Zapier integration with triggers and actions for users, roles, subjects, and tests.

Names, features, and limits vary by plan and change over time, so confirm current details in Trainual before designing around a specific feature.

From process to playbook in five steps

1. Inventory the work. List the recurring processes each team runs: weekly, monthly, per customer, per hire. A short process mapping workshop surfaces most of them in an hour.
2. Assign an owner to each process. One person is accountable for keeping each document accurate.
3. Document the current way, then improve it. Capture how the work happens today before redesigning it; see current state vs future state process mapping.
4. Attach processes to responsibilities, and responsibilities to roles. This is the step that turns a document library into a playbook.
5. Add checks. A short test or manager sign-off for anything where mistakes are costly.

Document exceptions as well as the happy path. The exception inventory technique works just as well for training as for automation.

Build the role map

A role map connects people to the content they need. Start with a simple table like this, then mirror it in Trainual:

Tips for role design:

• Roles describe work, not people. One person can hold several roles; a small-business owner might be Sales Rep, Office Manager, and Team Lead.
• Keep a shared base role (All employees) for company-wide content.
• Add-on roles such as Team Lead or Safety Officer let you layer training without duplicating it.
• Map job titles to roles in one lookup table. Every automation that assigns training should read that table, not hard-code roles.

Design content people will actually finish

• One process per topic. “How to issue a refund” is a topic; “Support” is a subject.
• One action per step, naming the exact tool, screen, and field.
• Show, then tell. A short screen recording plus written steps beats either alone.
• Lead with why. One sentence on why the process exists helps people handle cases the document does not cover.
• Add a definition of done so people know when the task is finished.
• Put a review date on every subject and assign it to the process owner.

Use AI to document faster

The slowest part of building a playbook is writing. AI can turn raw material (a screen recording transcript, meeting notes, an old Google Doc) into a structured first draft. Trainual offers in-app AI for drafting; you can also use your own AI tool with a prompt like this:

You are documenting a business process for [Company].
Input: a transcript of someone doing the task and explaining it.

Write:
1. Purpose (one sentence) and who does this (role).
2. When it happens (trigger) and how long it takes.
3. Numbered steps. One action per step. Name the exact tool and field.
4. Exceptions: what to do when something is missing or wrong.
5. Definition of done.
6. Three quiz questions that check understanding, with answers.

Rules: Use only what is in the transcript. Mark anything unclear
as [CONFIRM] instead of guessing. Plain language, short sentences.

The process owner then reviews every [CONFIRM] marker, tests the steps by following them, and publishes. Never publish AI-written policy without a person checking it. The same approach works for documenting automations themselves; see using AI to document Zapier code steps and automation documentation and handoff.

Trainual events and actions you can automate

Trainual's Zapier integration exposes training events as triggers and user, role, and subject changes as actions. At the time of writing, Trainual's help center lists:

Check the current list in Trainual and Zapier when you build, since integrations change. Trainual also includes built-in settings for assignment and notifications; use those first and automate what they do not cover.

Automation 1: New hire to assigned training

The first automation most teams build: when someone is hired, they get a Trainual account with the right roles before day one.

Trigger: new hire marked "Offer accepted" in your HR system, ATS,
         or onboarding tracker (Airtable, Google Sheets, monday.com)

1. Formatter: lowercase and trim the work email
2. Lookup:    map job title -> Trainual role(s) using a lookup table
                "Support Specialist"  -> Customer Support Rep
                "Account Executive"   -> Sales Rep
3. Trainual:  Invite new user (name, work email, title)
4. Trainual:  Assign roles (all employees + mapped role)
5. Trainual:  Assign subjects (any location- or team-specific extras)
6. Slack:     DM the manager with start date and assigned roles
7. Tracker:   write "Training invited" and the date back to the record

Use the work email as the key across systems, and create it before the Trainual invite runs. If the hire starts in two weeks, schedule the invite for a few days before the start date so pre-boarding content (paperwork, welcome video, first-day logistics) is waiting. For the broader onboarding sequence, see onboarding automation for agencies and the Google Workspace automation guide for account creation.

Automation 2: Promotions and role changes

When someone's title changes in your HR system or tracker:

1. Look up the old and new roles in your title-to-role table.
2. Assign the new role in Trainual; unassign roles that no longer apply.
3. Notify the person and their manager with what was added and the due date.
4. Log the change so you can report on time-to-ready after promotions.

Decide on purpose whether to remove old roles right away or after a handover period. Someone moving from support to sales may still need support content for a few weeks while they cover tickets.

Automation 3: Phased onboarding on completion

Assigning everything on day one overwhelms people. Release training in phases instead:

• Phase 1 (week 1): company, policies, tools. Assigned at invite.
• Phase 2: core role processes. Assigned when phase 1 subjects are completed.
• Phase 3: advanced processes and edge cases. Assigned when phase 2 tests are passed.

A “subject completed” trigger plus a filter for the subject name can assign the next subject and notify the manager. Completion can also unlock real work: add the new hire to the support queue or grant access to a tool only after they finish the matching training. For access handling, see access management for contractors.

Automation 4: Test results to coaching

• Test passed: record the certification in your HR system or an Airtable operations base, and post a quick congratulations.
• Test failed: create a coaching task for the manager, include which test was failed, and reassign the related subject. After repeated failures on the same test, ask the process owner whether the content is unclear.
• Patterns: monthly, review which questions new hires miss most. Frequently missed questions usually point to unclear documentation, not weak hires.

Automation 5: Onboarding complete handoff

When the “all subjects completed” trigger fires:

• Update the employee record or onboarding tracker to “Training complete” with the date.
• Notify the manager and schedule a 30-day check-in.
• Post a short celebration in the team channel; see Slack automation for operations teams.
• Send a short feedback form: what was unclear, what was missing.

Automation 6: Process updates and retraining

Documentation goes stale the moment a process changes. Build a light loop to keep it current:

1. Keep a list of subjects with owners and review dates (in Trainual or a tracker).
2. On a schedule, remind owners of subjects that are due for review.
3. When a process changes materially, reassign the updated subject to the affected roles so people relearn it, and say what changed.
4. When an automation changes how work is done, update the matching subject in the same change; an out-of-date SOP describing a manual step that is now automated causes duplicate work.

Automation 7: Offboarding

When someone leaves, archive their Trainual user as part of the same offboarding automation that removes other tool access. Before they go, make sure every process they own has a new owner and that the documentation is current. If they built automations, review what happens to automations when someone leaves so nothing breaks when their accounts are deactivated.

Automation 8: Contractors, partners, and clients

The same pattern works beyond employees. Agencies and franchises can invite contractors or partners, assign a limited role (for example, brand standards and delivery process), and only grant access to client systems after the test is passed. Keep these users in clearly named roles so they never see internal-only content, and archive them automatically when the contract ends.

Documented, role-based processes are also what AI agents need to do a job well; see writing a job description for an AI employee.

If you sell training to customers rather than running it internally, see building an automated learning funnel with LearnWorlds.

Where AI fits and where it does not

When AI output becomes official policy or affects someone's employment, add a review step. Human in the Loop is one way to require approval inside an automation.

Guardrails for training automations

• One source of truth for job titles (usually your HR system), and one lookup table from titles to roles.
• Email as the key. Normalize it, and make sure personal and work emails never get mixed up.
• Search before invite so rehires and returning contractors are not duplicated; see why Zapier creates duplicate records.
• Least access by default. New users get the base role plus their mapped role, nothing more.
• Alert on failures. A failed invite means a new hire starts with nothing; see the Zapier error handling playbook.
• Document the automations too. Keep a short record of what each training Zap does and who owns it; see the automation requirements doc template.

Metrics to track

• Time to invite: days between offer accepted and training assigned (target: before day one).
• Time to complete onboarding by role.
• Time to productivity: days until a new hire handles real work unassisted, as judged by their manager.
• Test pass rate on first attempt and the most-missed questions.
• Documentation coverage: share of responsibilities with a current, owned process.
• Stale content: subjects past their review date.

Capture a baseline before you change anything; see defining success metrics before you automate.

A practical rollout order

1. Weeks 1-2: inventory processes, define roles, and write the title-to-role table.
2. Weeks 3-4: document the base role and your highest-turnover role first, using AI drafts and owner review.
3. Week 5: automate new hire invites and role assignment.
4. Week 6: add phased onboarding, test-result handling, and the onboarding complete handoff.
5. Then: role changes, offboarding, review reminders, and contractor or partner training.

Ready to build your playbook? Start with Trainual, document one role end to end, and automate new hire invites first. If you want help mapping processes and connecting Trainual to your HR and operations tools, Automation Ace can design it with you.

Frequently asked questions

What is Trainual?

Trainual is a training and documentation platform for building the how-to guide for your business. Teams use it to document processes, policies, and standard operating procedures, organize them by role, assign them to people with due dates, check understanding with tests, and track completion.

What is role-based training?

Role-based training assigns documentation and courses based on the roles a person holds instead of giving everyone the same manual. Each role bundles the responsibilities and processes it needs, so assigning a role gives a person exactly the training for that job.

Does Trainual integrate with Zapier?

Yes. At the time of writing, Trainual lists Zapier triggers for subject completed, topic completed, all subjects completed, test passed, and test failed, and actions such as inviting a new user, assigning and unassigning roles and subjects, and archiving a user. Check Trainual and Zapier for the current list.

How do I automatically assign Trainual training to new hires?

Trigger a Zap when a new hire is added in your HR system, applicant tracking system, or onboarding tracker. Normalize the work email, look up the Trainual roles for the job title in a lookup table, invite the user in Trainual, assign the roles, and notify the manager.

Can AI write SOPs for Trainual?

AI can draft SOPs from screen recording transcripts, meeting notes, or existing documents, and Trainual offers in-app AI for drafting. Have the process owner review every draft, confirm unclear steps, and test the process before publishing.

How do I keep training content up to date?

Give every subject an owner and a review date, send owners automatic reminders when reviews are due, and reassign updated subjects to the affected roles when a process changes materially. Update documentation in the same change whenever an automation alters how work is done.

What should happen in Trainual when an employee leaves?

Archive the user as part of the same offboarding automation that removes other tool access. Before they leave, reassign ownership of any processes they maintained and confirm the documentation is current.

How do I measure whether training is working?

Track time from offer accepted to training assigned, time to complete onboarding by role, time to productivity, first-attempt test pass rates, the most-missed test questions, documentation coverage, and the number of subjects past their review date.