From policy to approval route

Tell us the policy. We'll draft the workflow.

Describe the policy in one sentence. Review the draft, approve it, and it is live. No ticket, no chasing.

Request access →See where AI fits

Assistant

Leave over 5 days needs the manager. Everything else approves automatically.

Done. Ready for your review.

Unpaid leave also needs finance. Change the threshold to 10 days.

Added Finance Approval. Threshold now 10 days.

Describe a process…

• STARTENTRY

Leave Request

Submitted by employee

◆ CONDITIONRULE

Duration > 5 days?Duration > 10 days?

Branch on duration

TRUE

■ NORMALAPPROVAL

Manager Review

Target: direct manager

FALSE

■ NORMALNO TARGET

Short Leave

Approves on submit

■ NORMALAPPROVAL

Finance Approval

Target: finance group

✓ COMPLETETERMINAL

Balance Updated

Route ends

● VALID/5 states6 states/4 transitions5 transitions/0 errors

Three steps from policy to route.

You describe it. We draft it. You approve it.

01 / SAY

Say it in one sentence

“Leave over 5 days needs the manager.” That is the whole brief. Nothing to learn, no ticket to file, no diagram to draw yourself.

02 / APPROVE

Approve the draft

The route appears with every approver in place. Fix anything with a click, then publish. Nothing goes live without your sign-off.

03 / TRACK

Never chase again

Every request finds its approver on its own. You always see where things stand. Nothing stuck, nothing lost, nobody to nudge.

Where AI fits in Oasis HR.

In build. Three places, and nowhere else.

01 / RETRIEVE

Read the rule

HR policy already lives in documents and intranet pages. AI retrieves the rule that applies to the process the manager describes.

02 / DRAFT

Draft the flow

It returns a workflow draft: states, conditions, approval chain, and the edge cases the document mentions. The manager edits it on the canvas.

03 / APPROVE

A human signs off

Nothing publishes itself. The manager reviews the draft, fixes it, and approves it before it becomes a live route.

AT RUN TIME. FIXED GATES DECIDE, AI DRAFTS CONTEXT, HUMANS SIGN.

Masked exception summary plus a draft review note for finance.Payroll →

Justification text mapped to the rule plus a draft context note.Overtime →

Receipt fields extracted plus a draft category for the reviewer.Expense →

Model choice. We build on Claude. It is the only model in our AI layer, and it is not a placeholder we plan to replace later.

Flexible at design time. Deterministic at run time.The model never decides inside a running workflow. It proposes a draft, a human approves it, and the engine executes fixed rules. The same input always produces the same route. That repeatability is the only way an HR process can be audited. Oasis HR gives no legal, medical, or financial advice and makes no automated decisions. It routes requests to human approvers. Built for workplace HR teams.

One sentence, any process.

The same engine reads every domain. Only the sentence changes.

“Over 5 days the manager sees it, over 10 days the director too.”Leave · 2 tiers

“Anything over 2,000 TL goes to finance before the manager.”Expense · 2 tiers

“New hires get IT, payroll and a manager buddy in that order.”Onboarding · 3 tracks

“A rejected candidate needs a reason before HR closes the case.”Recruitment · denied path

One engine, core HR domains.

Each module ships its own states, fields, and conditions.

Leave

Annual, medical, and parental requests with balance fields.

Expense

Claim review, budget thresholds, and finance queues.

Recruitment

Offer stages, approval gates, and rejection paths.

Onboarding

Task sequences across IT, payroll, and the hiring manager.

Performance

Review cycles with self, manager, and calibration steps.

DOCUMENT-LED EXAMPLES. EACH ONE STARTS FROM A FILE, NOT A BLANK FORM.

01 / PAYROLL

Private by design

Payroll review without the spreadsheet hunt

“March payroll locks only after finance signs the SGK totals.”

Input: March bordro.pdf · 214 pay lines

Design time, with AI: drafted from your sentence plus last month template. You approve before anything runs.

RUN TIME: FIXED GATES + AI ASSIST

• STARTENTRY

Payroll File In

Trigger: bordro.pdf attached

■ NORMALEXTRACTION

Map Fields

Method: field.map, fixed schema, no AI

◆ CONDITIONRULE

SGK complete?

Missing code or outlier amount

■ NORMALAPPROVAL

Finance Approval

Target: finance group, AI drafts review note

✓ COMPLETETERMINAL

Payroll Locked

Route ends after sign-off

ENGINE CHECKS, NO AI

Totals matched against February, fixed rule
Missing SGK codes flagged, fixed rule

AI ASSIST

Exception summary for finance, masked values only
Draft review comment, finance edits and signs

AI never sees the full salary table, only flagged exceptions. Finance signs before anything locks. Pilot example.

02 / OVERTIME

Overtime that checks itself against policy

“Weekday overtime over 2 hours needs the manager. Weekend work needs the manager plus HR.”

Input: weekly timesheet export or clock PDF

Design time, with AI: drafted from your sentence plus the policy threshold. You approve before anything runs.

RUN TIME: FIXED GATES + AI ASSIST

• STARTENTRY

Timesheet In

Trigger: clock export PDF

■ NORMALEXTRACTION

Parse Timesheet

Method: field.parse, fixed schema, no AI

◆ CONDITIONRULE

Over threshold?

Weekday over 2h, any weekend

■ NORMALAPPROVAL

Manager Review

Target: direct manager, AI drafts context

✓ COMPLETETERMINAL

Sent to Payroll

Route ends after sign-off

ENGINE CHECKS, NO AI

Weekday and weekend split, threshold if
Weekend work auto-routes to HR, fixed rule

AI ASSIST

Justification text mapped to the rule, manager confirms
Draft context note for the manager review

Fixed gates plus AI context drafts. No hours approve themselves. Pilot example.

03 / EXPENSE

Receipts read before they reach finance

“Receipts over 2,000 TL go to finance before the manager.”

Input: receipt photo or expense PDF

Design time, with AI: drafted from your sentence plus the receipt fields. You approve before anything runs.

RUN TIME: FIXED GATES + AI ASSIST

• STARTENTRY

Receipt In

Trigger: photo or PDF

■ NORMALEXTRACTION

Read Receipt

Draft method: ocr.extract, amount date vendor

◆ CONDITIONRULE

Over 2,000 TL?

Branch on amount

■ NORMALAPPROVAL

Finance Review

Target: finance group, AI drafts category note

✓ COMPLETETERMINAL

Payout Queued

Route ends after sign-off

AI READS

Amount, date, vendor and category extracted
Blurry or missing fields sent back to the employee

AI ASSIST

Draft category and review note, reviewer confirms

Draft only. Finance and manager still sign. Pilot example.

What is built, what is not.

We would rather you read this than find out on a call.

Visual canvas, six state typesReact Flow canvas with drag, drop, and inline editing.Pilot build

Transition conditions and routingNamed conditions per transition, denied and fallback paths.Pilot build

Approval targets and field requirementsTyped targets, action forms, and payload validation.Pilot build

Workflow templatesSearchable library with categories per HR module.Pilot build

Backend persistence and runtime executionState is held in the browser today. Actions do not fire yet.In progress

AI: policy document to workflow draftRetrieval over company documents, draft generation on canvas.In progress

AI: document extraction from PDF and receiptsDeterministic gates plus AI review assistance. A human verifies every value.In progress

Immutable audit trailRequired before any compliance claim. Not built.Planned

Walk through the live build with us.

We run the product on a call, from an empty canvas to a published route. If it is not a fit for your HR team, you will know in ten minutes. Write to [email protected].

Request access →