Facts you already have
Enter a hire, import a roster CSV, collect answers on a survey, or post facts through the API. There is no live HRIS sync yet.
LEAN applies the leave program to the facts you have. Try a WA PFML example
LEAN applies state and employer rules to the facts you have, calculates entitlement and pay, and records the sources and reasoning behind the result.
For the people who have to defend a leave decision
Programs in the engine today include
FMLA, ADA, WA PFML, CO FAMLI, CA SDI / PFL / CFRA / PDL
Who it's for
Pick the page that matches how you work — or keep scrolling for how a determination is made.
Users
Leave specialists and administrators Open the timeline, the Why, and the citation. Send the survey when a fact is missing.Functional buyers
HR and benefits leaders The same rules on every employee. Policy changes go through draft, test, and approve.Executive buyers
Chief people officers and CHROs Risk, cost, and an audit trail. The waiting-period math stays in the engine.Market
PEOs and TPAs Call the Determinations API across employers. Each result still has a Why.Hire, roster, survey, or API — then one answer
Facts come in from hire, roster CSV, survey, or API. LEAN applies the program to what is known, holds when a fact is missing, and returns one decision with the reasoning attached.
What the team starts with
Hire · start date and employment Roster CSV · hours and earnings medical-certification.pdf employer-leave-policy.docx WA PFML · WAC 192-500-185 STD-offsets.xlsx Employee · leave dates Manager · work schedule What did we know last Tuesday?What LEAN returns
Why: Claim week is serving the waiting period. Hours are met and certification is on file.
Sources · hire · roster · certification · WAC
Product walkthrough
Navigator answers from the same determination the engine already computed. Each sentence can point at a citation. The timeline and the Why stay the source of truth.
Riley · WA PFML medical
Navigator
as of 2026-03-14
Why isn’t wage replacement covering Riley’s week of Feb 10? Job protection already looks granted.
Job protection is granted for that week. Wage replacement is denied because Riley is serving the program’s waiting period . Riley’s hours and certification are already satisfied .
WA does not pay benefits for hours claimed during the waiting period, and its ordinary weekly proration rule does not apply to that waiting-period week .
This is the same status explanation available from Engine’s timeline.
See it
Hire, roster CSV, survey, or API. The engine applies the program. When a fact is missing, the case holds and Navigator can ask for it.
Enter a hire, import a roster CSV, collect answers on a survey, or post facts through the API. There is no live HRIS sync yet.
Held means needs information. The survey asks for that fact. When it arrives, the engine runs again.
Job protection, wage replacement, and benefits each get a status, a citation, and a record of what was known at the time.
Engine
Navigator answers questions. The engine computes the leave. Open cases, review determinations, and watch the timeline from one desk.
Watch Riley’s case move through intake, employee questions, HR review, and timeline.
Weekly entitlement
Open the weekly breakdown: wage history, lookback, rate tiers, and payer offsets. The same Why that explains status also explains amount.
Stacked PFML, STD, and employer top-up is one weekly result. Open why to see each line, not a cell in a shared workbook.
LEAN computes gross entitlement. Paycheck withholdings stay in payroll.
Riley · week of Jan 5
$1,000 this week
open why · amount
Policy lifecycle
Draft the rule in language a policy expert can review, test it against saved cases, choose when it takes effect, and preserve the decisions made under earlier versions.
Build structured rule clauses using the terms your statute or handbook already uses.
Run reusable scenarios with expected outcomes before a policy change reaches live cases.
Save changes as a draft, put them through your review path, and set the effective date explicitly.
Return to an earlier date and see the facts and determination available at that time without replacing the recorded result.
The audit trail
Job protection and wage replacement can take different paths on the same week. The Why shows which rule fired, which facts were used, and what is still missing.
Each determination keeps the policy source, the facts, and the date they were known. You do not reconstruct the week from email.
The trail is written when the decision is made. Later facts do not rewrite what was known then.
Riley · week of Feb 10
Partial
open why · status
Trust
Chat should not invent eligibility. The rules compute the leave. Navigator answers from that result.
FMLA, ADA, WA PFML, CO FAMLI, and CA SDI / PFL / CFRA / PDL. More programs are added as packs, not as a count of statutes.
Draft the rule, test it on saved cases, approve it, and set the effective date. Earlier decisions stay with the version that made them.
Each fact keeps its source, timestamp, and the window it was valid. Replay as-of without replacing the recorded result.
Role checks and server-side masking keep compensation and medical facts off screens that should not see them.
The same engine that draws the timeline can be called from another product. Surveys, Why, and the recorded result stay attached.
We’ll model the decision, calculate the result, and show where each part came from.
No spam. We’ll reply with a calendar link.
We’ll model the relevant decision, review it on the timeline, and show you the rules and facts behind the result.
Book a walkthroughInteractive