RTO Policy Analysis.
Compliant before the first claim.
Leah analyzes return-to-office policies against employment contracts, collective agreements, jurisdiction-specific labour law, and individual accommodation arrangements. Gaps surface before rollout, not after the first tribunal filing.
Most RTO policies discover their compliance gaps when the claims arrive.
RTO rolled out before legal review
Mandates announced on a CEO timeline, not a legal one. Employment counsel sees the policy after the all-hands email goes out, and only then starts the work of checking it against contracts and labour law.
Collective agreements not cross-checked
Unionized populations sit under collective bargaining terms that govern hours, location, and change procedures. RTO policies routinely conflict with those terms because nobody reconciled the new policy against every active CBA.
Flexible work arrangements ignored
Individual contracts, offer letters, and side agreements grant remote and hybrid rights to specific employees. A blanket RTO mandate breaches those rights one signature at a time, and the breach is invisible until claims arrive.
Disability accommodation gaps surface via claims
Employees with documented accommodations for remote work get caught in the new policy. The first signal that the accommodation was overridden is usually an EEOC charge, an Equality Act complaint, or a tribunal filing.
Jurisdiction-by-jurisdiction analysis manual
UK works councils, EU member-state labour codes, and US state rules all impose different consultation, notice, and substantive requirements. Counsel reads each one by hand, country by country, and runs out of time before the policy ships.
Record-keeping fragmented
Contracts in one system, accommodations in HRIS, collective agreements in legal SharePoint, jurisdictional memos in counsel inboxes. When a claim lands, nobody can assemble a defensible record of what was reviewed and when.
From draft policy to structured rules
Leah ingests the draft RTO policy in whatever form it arrives. PDF, Word, intranet HTML, slide deck. She extracts the rules that govern people: who is in scope, where they must work, on which days, with what notice, under what exceptions. The policy becomes structured data the analysis engine can reason against.
“We loaded a 14-page policy and watched Leah turn it into a structured rule set in minutes. That used to be a paralegal week before any analysis even started.”
Head of Employment Law, FTSE 100 Retailer
Five steps to a defensible RTO rollout
Leah integrates with the systems you already run. No rip and replace. The full obligation perimeter assembled, then tested.
Connect
Leah integrates with your HRIS, contract management system, accommodations register, and CBA repository. The full obligation perimeter for the affected workforce is assembled in one place.
Ingest Policy
The draft RTO policy is parsed and structured. Scope, location requirements, days on-site, notice periods, and exception categories become queryable rules with the source text preserved.
Cross-Check Contracts
Each in-scope employee's contract, side letters, and applicable CBA are validated against the policy. Conflicts surface at the individual and unit level with the cited clauses.
Analyze Jurisdictions
The policy is tested against UK, EU member-state, and US federal and state law. Procedural duties and substantive risks are flagged with the supporting authority.
Flag Individual Gaps
Disability accommodations, religious accommodations, statutory flexible work requests, and caregiving arrangements are matched against the policy. Conflicts are routed to employment counsel for review before rollout.
Got Questions? Get Answers.
Counsel review still happens, and Leah does not replace it. What changes is the input. Counsel today sees a draft policy and a vague obligation perimeter, and tries to remember every contract, accommodation, and CBA that might conflict. Leah delivers a structured report that already cross-checked the policy against the full perimeter. Counsel time goes to the contested cases, not the assembly work.
No. Leah surfaces conflicts, gaps, and risks with the supporting authority cited. The legal judgment stays with employment counsel. The output is a structured analysis with full provenance, not an autonomous compliance ruling. Every flagged item links back to the contract clause, accommodation record, or statutory text that triggered the flag.
The rule library covers UK, all EU member states, and US federal and state employment law, with active maintenance as statutes and case law evolve. Coverage of additional jurisdictions, including Canada, Australia, and major APAC markets, is added on request and ships within the standard release cycle.
Active CBAs are ingested and mapped to the unionized populations they cover. Policy rules are tested against negotiated terms on hours, location, change procedures, and any specific remote or hybrid provisions. CBA versions are tracked over time, so the right agreement is applied to each affected employee.
Side letters, individual flexible work agreements, and offer letter commitments are first-class inputs. Many of these were signed during the pandemic and never made it back into a central register. Leah surfaces them as part of the contract cross-check, so the rollout team sees the actual obligation perimeter, not the assumed one.
Yes. Leah is deployed by enterprises with strict data security and privacy requirements, including FTSE-listed and Fortune 500 employers. Employee data does not train Leah's underlying models. Customer data is encrypted in transit and at rest. SOC 2 Type II, GDPR, CCPA, and ISO 27001 aligned. Private instance deployment is available for customers with strict data isolation requirements.
