Function
Automate More. Keep the Judgment.People Decide.
Payroll changes, refunds, contract terms: the work worth automating still has calls a person should make. Configure a guardrail to trigger human review, and the Worker pauses before the action, notifies the right user or group, and uses their decision to choose what happens next. Who was asked, what they saw and what they decided stays on the record.
Where Lemma Sits on the Autonomy Spectrum.
Pure control is just software, and pure autonomy is hard to defend. Human review is how Lemma holds the middle: a Worker acts on its own until a guardrail says a person decides, then waits for their answer.
- Pure control
Scripted
Deterministic, capped by what you wrote down.
- Where Lemma sits
Controlled Autonomy
Agents decide inside bounds you can inspect.
- Pure autonomy
Unbounded
Fast to demo, impossible to defend in an audit.
The Calls a Person Should Make, Kept With a Person.
A review step is where a Worker stops and asks a person. Configure a guardrail to trigger human review, and the run pauses before the consequential action, notifies the right user or group, and uses their answer to decide what happens next.
Give a person control when a guardrail trips.
Suppose payroll policy requires review for adjustments above $5,000. A Worker preparing a $7,500 adjustment reaches that check, opens a review and emails Payroll Operations. The payroll update sits after the review, so it waits for the decision: approval runs the payroll function, a correction goes back through the check, and a decline closes the request. The threshold and the routes are yours to configure.
- An over-limit amount, a missing approval or a result to check routes to a person
- The payroll update, payment or message waits for the decision
- Approve, correct, decline or ask for more, each on its own path
Coordinate decisions across people and teams.
Send each question to the person or team that owns it: a named user, or a directory group such as Payroll Operations. A recipient can come from the case itself, such as the number collected earlier in the run. One run can hold several reviews: HR verifies eligibility, Payroll reviews the amount with HR’s answer in front of it, and a later step uses both.
- A user or a group
- Notify a named specialist, or a directory group such as Payroll Operations.
- Recipients from the case
- Supported recipient values come from the run’s data, such as a contact number collected earlier.
- Several reviews, one run
- Each team receives the question it owns, with the earlier decisions already available.
Reach people where they already are.
Configure the channel, the recipients and the message for each review: email, SMS or WhatsApp. External recipients can respond to a single-field WhatsApp review without signing in, replying to the original message by text or by voice. Where a team works in another tool, a configured function extends the notification, for example by opening a service-desk ticket when the review opens.
- SMS
- Reply without a login
- Ticket through a function
Give reviewers the evidence and the tools to decide.
The review opens with the run’s data already in it: the proposed amount, the values extracted from the document, the answers given earlier, ready to confirm or correct. Decisions are structured fields that later steps read directly, and the form adapts to the answer. The supporting document sits beside the form, and the reviewer can attach a file of their own.
- Prefilled from the run
- Proposed amounts, extracted values and earlier answers, ready to confirm or correct.
- Structured decisions
- Required fields, choices, dates, amounts and notes that later steps read directly.
- A form that adapts
- Choosing Request changes reveals a field for the reason.
- Evidence beside the form
- A PDF or image beside the form, editable table or card fields, and a file upload.
Manage open reviews, and recover when nobody answers.
Operations work from a shared inbox of open, completed, timed-out and failed reviews across Workers. A deadline fails that step by default; an author can accept the timeout explicitly and route it to a backup reviewer or an exception process. Completed forms reopen read-only beside the run’s data and logs, and the exception path can be tested before rollout with mocked approvals, declines and timeouts.
- A shared inbox
- Open, completed, timed-out and failed, across Workers
- Deadlines
- Fail the step by default, or route onward
- Inspect
- A completed form, read-only, beside its run
- Test first
- Mock approvals, declines and timeouts in a draft
Builders and operators, in one governed workflow.
AI workflows are cross-functional, so a Worker is built to be shared. Builders lay out the steps and decide where a person reviews. The Worker carries the routine work, subject-matter experts make the calls that need their expertise, and operations keep every open review moving. Roles on the Worker keep each person to their part, and every contribution lands on the same record.
- Builders
- Design the steps in the Console or in code, and set where a person reviews and who is asked.
- Experts
- Get the question they own by email, SMS or WhatsApp, and answer with the run’s evidence in front of them.
- Operations
- Follow open, timed-out and failed reviews across Workers in one shared inbox.
- Security and compliance
- Grant each person a role on the Worker, and read who acted and what they decided.
Autonomy You Can Expand.One Gate at a Time.
Put a review before every consequential write on day one. Read the record, see which approvals never change the outcome, and move the gate with the evidence in hand. The authority stays with your people; the hours do not.
Put People Where They Matter.
See a review hold, escalate, and resolve with our team.
Request a Demo