CadreOnboarding
Ready before they are. Build the plan once. It gets assigned, worked through and filed without anybody chasing it.
The plan, before the person. Built by the people who know what a first week needs.
A plan per team with the organization’s default behind it, made of four kinds of step in the order you choose; your own questions, in your own words.
- A plan per team, and an organization default behind them
- Four kinds of step: do, answer, upload, attest
- Ordered, and each marked required or optional
- Your own questions, in twelve shapes
- Policy documents attached to the step that asks for them
It starts itself. Four things, none of which anybody has to remember.
- The offer is countersignedThe employee record is created from their application, with the start date carried across and the signed contract filed to their documents.
- The start date arrivesCadre checks each morning and starts anyone whose first day has come. Approve a hire on the morning they start and theirs begins right then, not tomorrow.
- The plan is matchedTheir team’s plan if it has one, otherwise the organization default. If neither is published, they simply have nothing assigned. The hire is never blocked on it.
- They get their inviteTo the free self-service area, where the plan is waiting. Running it twice changes nothing.
What they fill in stays useful. Instead of becoming a form nobody opens again.
A manager’s correction always wins and stays put: onboarding never quietly writes over it again.
- Answers become standing fields on the record
- Emergency contact, dietary needs, whatever you ask
- Every value remembers whether it came from onboarding
- A manager’s edit stays put, permanently
- Uploads land in the employee’s own document file
And it’s all on the record. Attested, answered, uploaded, with a name and a time on each.
Answers become the record
Map a question to an employee field and its answer becomes a standing attribute (emergency contact, dietary needs) rather than a form nobody opens again.
A manager’s correction sticks
Once somebody updates a field by hand, that value holds. Onboarding never writes over it again.
Uploads land in their file
A document the employee uploads goes straight into their own document file, where they can find it again.
Attestations are recorded
A policy acknowledgement keeps who attested and when, not a tick box that forgets.
Onboarding doesn’t sign anything. That already happened, next door.
Give a first week a shape. The beta is open now.
No. Onboarding runs in the free self-service area: the same place they later request time off and open their own documents. Seats are for the people running hiring and HR.
Then a new hire simply has nothing assigned and HR can assign one whenever it is ready. Hiring someone is never blocked on the plan existing.
Yes. Assign it directly from their record. A manual assignment overrides the team match and is marked as such.
No, and deliberately. Onboarding collects uploads and records policy acknowledgements: who attested, and when. Signing a contract is the offer’s job, and by the time onboarding starts the signed contract is already in their file.
Not today. A plan is an ordered list the new hire works through, with required steps marked as such. Per-step assignees, due dates and reminders are not in this version: worth knowing before you plan a first week around them.