Private beta Access by invitation

Onboarding and offboarding, with nothing forgotten.

ClearHand turns every start and exit into one plan with clear owners. HR, IT, managers and office work on it — not around it.

Request early access See how it works

Data hosted in Switzerland

ClearHand: Jamie Schneider's onboarding in progress — readiness, coordinator findings and tasks per team Sample data

Sample data — this is what a running onboarding looks like in ClearHand

Who it’s for

For companies where HR and IT are separate teams.

From around 30 employees, every start and exit runs across several departments. That is the point where you need one shared plan — not another email thread.

HR

You open the case. That’s it.

Name, job, department, date — the rest comes from your job profiles and checklists. You can always see who still owes what.

IT

You hear about it first, not last.

Accounts, licences, devices and access show up as tasks with due dates on your board. On exit, access removal is marked critical and formally signed off.

Managers

You decide from an email link.

Approvals, buddy, first-week plan: everything only you know arrives as a question — no login, no new tool.

How a start runs

A start date becomes a plan.

You enter the essentials. Job profiles and automations do the routine. People still make the decisions.

The “New onboarding” form with name, role, department, start date and location The generated checklist with tasks for HR and IT, due dates relative to day one The HR team's task board across all cases, with owner and due date Sample data
  1. 01

    Open the case

    Name, job, department, location and start date. The job profile is suggested from the job title.

    Five fields
  2. 02

    ClearHand builds the checklist

    Job profile and department produce tasks with team, owner and due date — counted back from day one. Automations add what applies only to this case: remote? Ship it instead of setting up a desk. Admin rights? The manager approves.

    Tasks for HR, IT, manager and office
  3. 03

    Each team does its part

    Every team sees its own board. Reminders and escalations run on their own. The coordinator flags gaps and risks — only what someone accepts gets done.

    Every decision in the log

What’s included

Built lean. Everything included.

No modules, no consulting days. Six building blocks that carry the whole process together.

01

Job profiles

What a job receives: access, equipment, training, approvals. Picked from the catalog and matched to the job title automatically.

02

Checklists & automations

Standard checklists per department, due dates relative to the first or last day. Rules extend the plan before anyone has to ask.

03

Approvals without a login

Managers approve, decline or ask back through a secure email link. Every decision is recorded.

04

Task board & reminders

My tasks, all tasks, comments with @mentions. Daily digest, early warning before the start date, escalation after three days overdue. Complete a task straight from the email.

05

Coordinator

Spots missing tasks, unclear ownership and risks, and suggests. It never acts on its own: accepting or dismissing stays with you.

06

Slack, Teams, email

Daily overview and team update where your team already reads. English and German all the way into every email.

Control

Clarity without giving up control.

The coordinator keeps watch. People decide. The record stays complete.

01 / Ownership

One person. One real date.

Every task has an owner and a due date. If it slips, ClearHand reminds — and after three days escalates to the case owner.

02 / AI

Suggestions, not actions.

The AI only sees pseudonymised cases — “person_1”, never a name — and runs on Azure OpenAI in Switzerland. It neither creates accounts nor grants access.

Offboarding

The last day is a security event.

Accounts that outlive an exit are not a cosmetic problem. ClearHand marks access removal as critical, gets the manager’s approval for the mailbox handover — and the case cannot close until an admin has signed off the final access removal.

  • Formal sign-off“Final access removal” is a sign-off by an admin — not a checkbox someone can skip.
  • A complete recordApprovals, activity and every decision in one audit log. Proof instead of a silent ending.
  • Data minimisationStatus instead of documents. Configurable retention, automatic anonymisation of former employees.
Milan Roth's offboarding: critical IT tasks and the admin sign-off of the final access removal Sample data

Sample data — critical tasks are marked, and an admin signs off the final access removal.

Privacy & security

Built for Switzerland.

For Swiss and European companies that want to know where their data lives and what happens to it.

Data location Zurich
Database and storage with Supabase in Zurich.
AI in Switzerland
Azure OpenAI, region Switzerland North. Names are replaced with placeholders before every call.
Status instead of documents
ClearHand stores whether a document exists — not the document. No salary, health or bank data.
Retention & anonymisation
You define how long completed cases stay. After that, personal data is anonymised automatically.
Audit log
Every approval, every assignment, every AI suggestion — with time and person.
Access
Invitation only. Microsoft 365 login, permissions by role and team.
DPA at the push of a button
The data processing agreement is generated for your company — under Swiss DPA and GDPR, sub-processors included.
The AI never touches your systems
The AI reads cases and suggests. Creating accounts, granting access, blocking sign-in — people do that, in your systems.

Private beta

Start with one real hire.

We set up your job profiles and checklists together with you and walk the first onboarding or offboarding through from start to finish.

  • 01 Guided setup
  • 02 Your own templates and rules
  • 03 A direct line to the founder

We use your details only to get in touch with you. Privacy