People Operations

Monday’s new starter. Friday’s loose ends.

Connect the paperwork, equipment and access needed for someone to start or leave. A lemming, your AI colleague, follows up with each responsible person and keeps the manager informed.

For teams coordinating employee administration.

Try the workflow
Lemming · AI colleagueExampleIs the laptop ready for Monday’s new starter, and who will hand it over?
A new starter
Interactive example · fictional data
AlexIT coordinator
Team workspace

New starter · Monday

Joining paperwork is complete. Laptop handover is unconfirmed.

Try an example replyScripted demo
Example companyOffice view
ONBOARDING 012Readiness check

Check Monday’s readiness

People Operations

Start
Monday
Paperwork
Complete
Laptop
Unconfirmed
Handover
Unassigned
Lemming

Ask IT about laptop readiness.

Paperwork is done. Equipment still has an open handoff.

A scripted example. Try both replies to see the different outcomes.

Module scope
The responsibilities

Give the routine
work an owner.

Configure a lemming around your procedure: what starts it, what it needs and when a person takes over.

01

Coordinate joining and leaving

Turn your agreed checklist into assigned work, including handoffs across the team.

02

Collect employee documents

Ask for missing items using appropriate access and a controlled document route.

03

Follow equipment and access

Track the named approver and implementer, and keep incomplete requests visible.

Intended module scope. Available steps and connections are confirmed before implementation.

What stays with your team

Employment decisions, sensitive personnel information and access authorization stay with designated people. A lemming coordinates the process; it does not make hiring or dismissal decisions.

Part of the same platform

Keep the next team
in the picture.

An onboarding can create a restricted document case and an internal equipment request. The manager sees readiness without gaining access to every private document.

Before you start

A few practical
questions.

Does this include payroll?

Not in this module’s proposed scope. Payroll data or system handoffs need their own definition, permissions and supported connection.

Who sees employee documents?

Access is set by role and document scope. Knowing that a document is pending does not automatically give someone permission to read it.

Can it grant system access?

Only if that specific action has a supported connection and explicit authorization. Otherwise it coordinates the request with your authorized team.

All nine modules

Your starting point

Start with one
ordinary workday.

Choose an area. Describe a recurring task and the people involved. That is enough to start defining a useful first setup.

This preview builds a brief on your device. Nothing is submitted.

Start with one ordinary workday.

What does someone keep asking for, looking up or passing on? Describe that—not a software wish list.

One example is enough. Leave out names, contact details and sensitive documents.

This preview prepares the brief on your device. It does not send, track or store your answers.