FrontLine HR — purpose-built for multi-client people operations.
From hire to onboard to probation to off-boarding. Confidentially scoped per client. PIPEDA-ready by design. The same record system handles a 50-agent fintech queue and a 2,000-agent retail account.
HR Dashboard
Acme BPO · 247 agents · 4 clients
Active probations
12
Open HR cases
5
Active PIPs
3
Pending approvals
7
Probation pipeline
This week
Day 30
4Jordan W.
Aisha O.
Day 60
5Tyler B.
Maya P.
Day 90
3Liam S.
Noor F.
Recent HR activity
Probation review submitted · Jordan W. · Day 30
5m ago
Case status changed · Inv. #218 → Hearing
1h ago
Private-info change requested · Aisha O. · SIN update
3h ago
PIP milestone reached · Tyler B. · M2 done
Yesterday
Recent change requests
5m ago
Promotion
Tyler B.
Pending HRPay grade
Maya P.
ApprovedDepartment
Liam S.
Pending managerTermination
Noor F.
Pending HRWhat's hard about HR at a multi-client BPO
Generic HRMS tools were built for a single employer with a single workforce. The friction shows up immediately in BPO ops.
One misconfigured filter from a cross-client breach
An HR generalist working Acme's people is one permission-filter mistake from surfacing TelcoCo's roster. One bad query, one stale role binding, one new HRIS field nobody scoped — that's all it takes.
One HR generalist, six clients, eight LOBs
One HR generalist owns 200–500 agents across 4–8 clients and 6–12 LOBs, each with their own reports, probation cadence, policy library. The day disappears into context-switching — no hours left for actual case work.
Probation washout hits at week 8, not week 1
Agent attrition concentrates between weeks 4 and 12, long after onboarding wraps. The team lead notices on day 65 that the 30-day check-in never happened. By day 70 the agent is gone — and you're paying re-recruit cost.
Direct-edit private-info fields are a privacy incident waiting to surface
National identifiers, banking, emergency contacts — directly editable means a typo is one keystroke from a privacy breach. The audit log shows the field changed but not who requested it or why. Regulators read that as 'no control'.
PIPEDA, Law 25, CCPA — at the same time
When a regulator asks 'who accessed Sarah Chen's record in Q1', the clock starts. If the answer lives across HRMS, ATS, and payroll, you spend two weeks reconciling timestamps. Regulators read delay as opacity.
Multi-jurisdictional employment law, in 13+ rule sets
Agents in Quebec, Ontario, US states, Mexico — each with different leave entitlements, holiday calendars, probation lengths, notice periods. Miss one rule and the employee is short; over-apply one and you burn margin.
What FrontLine does for your HR team
Seven HR-specific surfaces, each engineered with the multi-client guarantee built in. Deeper than the generic HRMS playbook — and a lot more honest about what BPO HR actually has to do.
Feature 01
Approval-gated record changes — no silent mutations
Critical employee record changes (manager assignment, position, pay grade, department, work location) don't apply directly. They route through a configurable multi-step approval workflow with delegation, escalation, effective-dating, and a complete audit trail.
- Multi-step approval chains. Chain N approval steps per change type. Each step can require a role, an explicit person, or both — and the chain itself is configurable per LOB.
- Effective-dated changes. Schedule a change to apply on a future date (e.g., a promotion effective Jan 1). The current record stays untouched until the date hits; the future change is visible to anyone planning ahead.
- Back-dated changes. Capture a change that already happened (e.g., a pay correction). The audit log preserves the actual time of entry alongside the effective date — you can't quietly rewrite history.
- Delegation. An approver on leave delegates their queue to a designate. Delegation is itself audited so the trail of accountability stays intact.
- Bulk changes. Apply the same change to N employees with one approval ladder — re-orgs, location moves, mass pay adjustments. Each row still gets its own audit record.
Change request · CR-4128
Position change
Jordan Whitfield · CSR-04218
FROM
CSR
Grade 2 · $19.25/hr
TO
Sr. CSR
Grade 3 · $22.50/hr
Approval ladder
Step 2 of 3Manager · Sam Chen
Approved · May 17, 14:02
HR review · Pat Rivera
In review since May 17
Finance · Jordan O.
Pending
Each step writes an immutable audit event · ae-4128 · ae-4129
Feature 02
Probation that runs itself — 30 / 60 / 90 milestones, no nudging required
Templated reviews auto-scheduled at hire. Manager submits inline; HR confirms, extends, or terminates. An immutable decision chain. Catches the agent washout that costs you the most — the one that would otherwise hit at month 3.
- Configurable templates. Per position family + department, with rating-group, free-text, and overall-recommendation section types. Active-scope uniqueness ensures one template owns each cohort.
- Auto-scheduling at hire. Probation milestones materialize the moment the employee record is created. No manual calendar work; no slipped reviews.
- Manager submission drawer. Inline on the employee record — no separate app, no email back-and-forth. Rating inputs, free-text, overall-recommendation gating.
- HR decision panel. Confirm routes employee status → active. Terminate routes into off-boarding workflow. Extend resets the clock with the audit chain intact.
- Overdue detection. Reviews not submitted by the milestone date surface red on the HR dashboard. The agent washout problem is, fundamentally, the un-actioned review problem.
Probation pipeline
Active probations
12
across 4 clients
Due this week
3
1 overdue
Decisions YTD
84%
confirmed
Day 30
4Jordan W.
Due Fri
Aisha O.
Due Mon
Liam S.
Due next wk
Day 60
5Tyler B.
Today
Maya P.
Due in 5d
Noor F.
Due May 27
Day 90
3Devon R.
Due Jun 2
Priya K.
Due Jun 4
Marc D.
Decision
Reviews auto-scheduled at hire · manager submits in-app · HR decision audit-logged.
Feature 03
Private Info + Compliance — PIPEDA-aware by default
National identifiers, banking, emergency contacts — all behind an approval workflow, every read logged separately, every access investigable in one query. The PIPEDA / Law 25 / CCPA defense posture, built in, not bolted on.
- Approval-gated mutations. Any change to a PII field routes through the same multi-step approval engine as other sensitive record changes. No silent mutations, ever.
- Per-read audit. Every PII read writes its own audit event with actor, target, timestamp, and scope. Filter by any of those when a regulator asks.
- Investigative-grade access log. The compliance officer queries the PII access log by actor, target employee, action, or date range to investigate a concern. Volume-threshold alerting ("alert if any one actor reads 5+ national IDs in an hour") is on the Atlas roadmap as a deferred phase of spec 36.
- DSAR fulfillment in one workflow. When a subject invokes their PIPEDA access right, the workflow assembles their data across every module via the DSAR collectors — the 30-day statutory clock is tracked automatically with deadline alerts at 7d / 3d / day-of.
- Right-to-erasure executor. Erasure runs as a coordinated anonymization across modules while preserving statutory-retention records. The compliance evidence is itself audited.
Private info compliance
SIN update · pending approval
Aisha Olufemi · submitted May 17, 09:42
FROM
••• ••• 412
TO
••• ••• 875
Recent PII reads · 24h
47 eventsPat Rivera (HR)
national_id.read
→ Aisha O. · Change request review
09:43
Sam Chen (Manager)
emergency_contact.read
→ Jordan W. · Incident escalation
08:21
Maria L. (Payroll)
banking.read
→ Tyler B. · Pay correction
Yest 16:30
Pat Rivera (HR)
salary.read
→ Marc D. · Probation review
Yest 14:12
1 active alert rule: any actor reading 5+ national IDs in 1 hour.
Quiet 24hFeature 04
Leave Management — accrual engine, jurisdiction-aware entitlements, mid-leave check-ins
A leave system designed for BPOs that operate across provinces, states, and clients. The accrual engine handles bank-style balances by leave type; the entitlement engine respects each jurisdiction's law; the check-in scheduler keeps extended absences from going dark.
- Bank-style accrual engine. Per-leave-type balances (vacation, personal, sick, parental) with configurable accrual rates, carryover rules, and tenure-tier bonuses. Different rates per jurisdiction, position, and contract type — all driven by data, not custom code.
- Jurisdiction-aware entitlements. Rule-pack framework with Quebec (LNT) and Ontario (ESA) defaults out of the box. Additional provinces / US states are configured per tenant requirement at onboarding; custom rules layer on top without breaking the defaults.
- Calendar conflict detection. Overlapping requests in the same LOB get auto-flagged so coverage holes don't slip through. Approval is gated on visibility, not just role.
- Scheduled mid-leave check-ins. For extended leaves (parental, medical, bereavement) HR sets a check-in cadence — e.g., 4 / 8 / 12 weeks. Each check-in is a tracked event with notes; nothing falls through.
- Dual-pane note model. Medical / personal context lives in a confidential note pane only HR sees; the operational pane (return date, coverage handoff) is visible to the manager. Privacy without process friction.
- Return-from-leave handoff. When leave ends, the system surfaces re-onboarding tasks to the manager: schedule sync, training updates, role changes during absence. The agent isn't dropped back into chaos.
Leave management
Active leave
5
2 ext. (parental)
Returning
2
this week
Pending req.
8
awaiting mgr.
Accrual · Jordan W.
QC (LNT) · Grade 2 · 8 mo tenureVacation
12.5d
+1.25 / mo
Personal
3.0d
+0.5 / mo
Sick
5.0d
Annual reset
Bereavement
3.0d
Per LNT
Aisha Olufemi · Parental leave
May 21 → Aug 15 · 12 wks · Returns to RetailCo / EN support
Mid-leave check-ins · structured
Jun 12
Settling well
Jul 14
Scheduled
Aug 11
Return-prep
Feature 05
HR Case Management — warnings, investigations, hearings, appeals on one timeline
One case file from verbal warning to final appeal, with complete chain of custody, attached documents, and an immutable audit trail. Built for the supervisor defending a termination and the regulator who'll demand to see the file.
- Five case types out of the box. Verbal warning, formal investigation, suspension, hearing, appeal — each with its own workflow, visibility rules, and required evidence types.
- Confidential timeline. Every event, every document, every status change captured with actor + timestamp. Nothing edits in place — the trail is forensic-grade.
- Linked to discipline policy. Cases reference the policy version in effect at the time of the alleged conduct — critical when policies have evolved since the events.
- Multi-party access. The subject, the manager, HR, and (when needed) external counsel each see the slice of the case they're entitled to. The rest stays sealed.
- Hearing scheduler. Hearings get their own sub-event with attendees, agenda, and outcome captured inline. No external calendar app needed for the formal proceeding.
- Appeal lifecycle. Appeals link back to the original case; the chain of audit events spans both. A regulator asking "how did this conclude" gets the full story in one screen.
HR case · INV-218
Conduct investigation
Subject: Jordan Whitfield · CSR · RetailCo
Opened May 12 · Lead investigator: S. Chen
Verbal warning issued
Apr 12 · Sam Chen
Formal investigation opened
Apr 24 · S. Chen + Pat R.
Subject statement received
May 03 · 12-page response
Hearing scheduled
May 19, 10:00 · HR + counsel
Decision
Pending
Evidence & references
Linked policy: Confidentiality & Multi-Client Conduct v4.1
In effect at the timeStatement.pdf
Subject statement
12 pp
Call-sample-082517.wav
QA evidence
4:21
Witness-email-thread.eml
Witness
3 msgs
Multi-party access: Subject · Manager · HR · External counsel — each sees only their entitled slice.
Feature 06
Performance Improvement Plans that actually close — not PIPs-by-PowerPoint
PIPs with milestone reviews, manager check-ins, and decision gates. Plans close as confirmed / extended / terminated with the supporting evidence captured at every milestone — and the QA team's coaching plan stays in sync, not in a parallel document.
- Configurable milestones. Typical 30 / 60 / 90 but fully tunable per role family. Each milestone is a tracked review with required evidence types and a decision gate.
- Coaching plan linkage. A PIP can attach to the agent's coaching plan in the QA module — manager's PIP and coaching team's plan stay coupled, not parallel.
- Evidence capture. Every milestone review accepts evidence (call samples, QA scores, attendance metrics, customer feedback) attached to the case file. The decision rests on data, not on memory.
- Manager + skip-level visibility. The agent's manager AND their manager's manager see the PIP — kills the "I didn't know my report was on a PIP" failure mode.
- Decision gating at the final milestone. The system enforces confirm-or-terminate at the end. You can't let a PIP just expire without action — every plan reaches a decision.
- Linked to off-boarding. A terminate decision auto-triggers the off-boarding workflow with reason-coded "PIP termination." Separation analytics inherit the cause without manual coding.
Performance plan · PIP-87
Tyler Brennan · CSR · RetailCo
Started Mar 18 · Manager: Sam Chen · Skip-level: J. Williams
Apr 17
May 17
Jun 16
Evidence captured
5 call samples · QA avg 72%
Up from 64% baseline
4 call samples · QA avg 78% · 1 escalation
On track
Evidence collection in progress
Awaiting final reviews
Linked QA coaching plan: Tyler B. · Manager and coaching team see the same evidence.
QA-CP-128Feature 07
Policy Manager — author, distribute, capture acknowledgements
One workspace for HR and compliance to publish policies, target them at the right roles, and collect acknowledgements that hold up in a regulator's inbox. The morning workflow for your compliance lead and the safety net for your operations team.
- Authoring + versioning. Markdown-style policy authoring with full version history. Previous versions stay readable after publish — important when a case references a policy that has since evolved.
- Targeted distribution. Scope a policy by role, client, LOB, or jurisdiction. Agents only see policies that apply to them — no global noise, no missed obligations.
- Re-acknowledgement on material change. When a policy changes substantively, the platform can require fresh acknowledgement from everyone in scope — not just new hires.
- Compliance dashboard. Who's acknowledged, who's overdue, who hasn't started. Drill into any cohort for a regulator or internal audit.
- Bilingual platform UI today. Every Policy Manager surface — author, distribution, acknowledgement, dashboard — renders in EN or FR per the user's locale. Policies are authored in the language your HR team writes in; per-policy EN ↔ FR sibling-row pairing (so a French policy structurally links to its English source and stale-flags when the source changes) is on the Atlas roadmap.
Policy distribution
Confidentiality & Multi-Client Conduct
v4.2 · published May 12 · supersedes v4.1
Outstanding acknowledgements
Sorted by overdueMia Lefebvre
CSR · TelcoPro
Carlos Diaz
Sr. CSR · RetailCo
Priya Kumar
Supervisor · TelcoPro
Lara Bennett
CSR · RetailCo
Noor Farhan
CSR · TelcoPro
Material change detected: v4.1 → v4.2 requires fresh acknowledgement from all 247 agents in scope.
Onboarding — from offer signed to day-1 ready
Onboarding sits at the seam between Recruiting and HR. The candidate Recruiting hands off becomes the employee HR builds the record around. A single workflow runs that handoff — document collection, background-check orchestration, system provisioning, day-1 plan to the manager — and surfaces in both teams' views simultaneously. One source of truth, two team perspectives.
- Workflow instance per hire. An onboarding workflow kicks off automatically the moment the offer is signed in Recruiting. No manual handoff, no spreadsheet handed across teams.
- Document collection orchestration. All required documents (PIPEDA acknowledgement, banking info, emergency contact, T4 / W-4, sector-specific compliance forms) collected with templated reminders and per-document audit.
- Background-check gate. Vendor-agnostic BGC orchestration with a webhook + adverse-action workflow. Onboarding cannot progress past this checkpoint until the result clears — protecting both compliance and the manager's day-1 expectations.
- System provisioning hooks. Identity, scheduling, training enrollment, and per-client tool access all fire off the same workflow. IT, Training, and HR each act on their slice without coordination overhead.
- Day-1 plan handoff. When onboarding completes, the manager receives a curated day-1 plan with system access confirmed, schedule synced, training enrollment, and a fresh-hire checklist for the first 30 days.
- Cross-team visibility, single source. Recruiting sees the candidate move from "Hired" → "Day-1 ready." HR sees the document-compliance side. The manager sees the day-1 readiness side. Same workflow, three role-tuned views.
Jordan Whitfield
CSR · RetailCo · EN supportHire date May 20 · Day-1 in 4 days
Day-1 readiness
3 / 5 stepsWorkflow steps
Background check
Verified May 14
Document collection
7 of 7 forms received
PIPEDA acknowledgement
v4.2 · May 16
System provisioning
Identity · scheduling · KB
Day-1 plan handoff
Manager receives Mon 9:00 am
Cross-team handoff: Recruiting sees “Hired → Day-1 ready”; HR sees document compliance; Manager sees readiness.
Business outcomes for the people running the BPO
What this looks like in margin terms for the COO or owner.
Daily 5-minute review instead of quarterly fire-drill
Every PII read separately logged. DSAR workflow runs end-to-end in-product (PIPEDA 30-day window automatic). Right-to-erasure executes as a coordinated anonymization pass across every module. The artifacts your auditor wants generate on demand.
Catch the week-8 washout that costs you the most
Structured 30 / 60 / 90 reviews put manager attention on the probation curve where a meaningful share of attrition concentrates — magnitude depends on your hiring profile. The agents you catch in week 4 are the agents who'd otherwise leave in week 12 — and those are the most expensive to replace.
One system instead of five
Replaces a typical HR stack of HRIS + spreadsheets + ticketing + e-signature + manual audit prep. Per-agent cost drops; per-HR-headcount span of control rises. See the math on the BPO Margin Calculator.
PIPEDA, CCPA, Law 25 — built in, not bolted on
Bilingual platform UI today (every screen renders in the user's locale). PIPEDA-grade retention engine with statutory floors enforced server-side. CCPA and PIPEDA DSAR workflow with deadline tracking + legal-hold precheck.
What HR actually gets back
Directional outcomes — real magnitude depends on your current workflow baseline, jurisdiction mix, and case load.
Hours back per generalist, every week
Replaces the spreadsheets + email follow-ups + manager nudging cycle for probation. Magnitude depends on your prior workflow.
Minutes, not hours
Filter the unified audit log by actor + date range. One query instead of a multi-system reconciliation.
On a workflow, not a marathon
The DSAR workflow assembles the subject's data across modules via collectors, tracks the statutory clock, and packages the response. Replaces the half-day-per-request manual exercise.
Five trackers → one source of truth
Probation tracker, leave bank, policy-ack list, change log, PIP file — all collapse into a single record-of-truth in FrontLine.
Regulatory posture
FrontLine HR vs. a generic HRMS
Six things BPO HR teams notice in their first month away from BambooHR / Rippling / Workday.
| FrontLine HR | Generic HRMS | |
|---|---|---|
Multi-client confidentiality enforced at the database layer (RLS) Generic HRMS uses app-layer permissions — leakage-prone under bugs or admin error. | ||
Native 30 / 60 / 90 probation workflow with templates + decision audit Custom-build via forms or manual spreadsheets is the norm. | ||
Approval-gated private-info changes with per-read audit Workday has some; BambooHR / Rippling lack the per-read log. | ||
Bilingual platform UI (EN ↔ FR) for policy distribution + acknowledgements Policy Manager UI is fully bilingual today. Policy bodies are authored in the language your HR team writes in; per-policy EN ↔ FR sibling-row pairing is on the roadmap. | ||
PIPEDA + CCPA DSAR fulfillment workflow built in Generic tools require manual data assembly across multiple systems. | ||
Multi-jurisdictional accrual engine (LNT · ESA · US states) Some support US states; few handle Canadian provincial differences natively. |
In production today
All seven HR surfaces are shipped and running on customer tenants today. See the technical status, full feature list, and weekly progress on the Atlas.
Questions HR directors actually ask before signing
Pulled from real fit calls. Short, direct answers.
Can my HR generalist configure probation templates without involving IT?+
What happens to in-flight probations and PIPs when we migrate from a generic HRMS?+
Can agents see the platform in their preferred language?+
How do I export all our employee data tomorrow if we need to?+
Do you ship with a starter library of policies, or do we author everything?+
Ready to see it in your environment?
Two ways to take the next step.
Other teams using FrontLine
Your operation isn't only HR. Here's what the rest of FrontLine looks like from the team next door.