Starter · Part of Onboarding
Template creation, versioning, and lifecycle
Build an onboarding template once per LOB (Line of Business: a distinct client program or queue within an operation.), version it, and the system runs new hires through the right version automatically. When you change the template, in-flight onboardings keep their original version — no more retroactive surprises mid-flow.
Onboarding template library — every active and archived template with version, status (draft / active / archived), and the LOBs it targets. Tenant-managed; ops adds new templates without engineering.
1 / 2
For the operator
Build an onboarding template once per LOB with the right tasks, documents, policy acks, and gates; the system runs each new hire through the version of the template that was active when they were hired. Update the template and in-flight onboardings keep their original version — no retroactive surprises mid-flow. New LOBs spin up by cloning an existing template and editing the deltas; you stop rebuilding from scratch.
Business impact
Onboarding inconsistency across LOBs is what creates the ramp-time variance that wrecks client SLA (Service Level Agreement: a contractual performance target, e.g. answering X% of calls within Y seconds.) on launch — agents who got the wrong checklist hit the floor unready and you eat the productivity gap. A versioned, LOB-specific template engine standardizes ramp time across the operation and gives compliance the audit answer for 'what onboarding did this employee actually complete?' on demand.