1. Confirm the hire
Receive the person, role, manager, location and agreed start date from recruiting or HR.
Map the trigger, package generation, cross-team work, exception recovery, human readiness decision and first-week follow-up as one visible flow.
Automation should handle repeatable routing and reminders. Managers and HR still own material decisions, exceptions and the quality of the new hire’s experience.
Free for up to five users. No credit card required.
Adapt fields, workflows, and dashboards without code. Explore 1,000+ app templates and use cases
A workflow is more than a sequence of reminders; each transition needs an accepted input and result.
Receive the person, role, manager, location and agreed start date from recruiting or HR.
Choose tasks, owners and due-date offsets based on role, department, location and worker type.
HR, manager, IT, facilities and training work in their own queues while dependencies remain visible.
Return incomplete inputs, escalate late ownership and approve documented alternatives where appropriate.
A human reviewer accepts readiness, accepts conditions or returns exact corrections.
Verify first-week access, role clarity, training and unresolved issues before closing onboarding.
Classify each behavior before building it.
Employee facts, manager plan, completion evidence and exception details come from the accountable owner.
Generate tasks, calculate relative dates, send reminders, update health and surface overdue work.
Accept handoffs, decide readiness, approve conditions and return incomplete work.
A flow with only the happy path is a diagram, not an operating system.
Reschedule incomplete dependent work while retaining completed evidence and the reason for change.
Reassign the work through an explicit escalation path; do not leave it attached to a generic team.
Record impact and recovery action, then route a conditional-readiness decision if an acceptable alternative exists.
Return the exact missing context to its source and keep the current owner visible.
A practical flow includes accepted source event, transition creation, task-package selection, parallel owner work, exception recovery, readiness review, day-one verification and early follow-up.
Automate repeatable task generation, due-date offsets, reminders, health signals and escalation. Keep readiness, sensitive exceptions and policy decisions with accountable people.
Retain the old date and reason, recalculate incomplete dependent tasks, preserve completed evidence and notify only affected owners.
No. It begins when recruiting or HR confirms the hire and coordinates the work that follows. The HR system remains the source of record for employment and statutory data.
Yes. A trained Jodoo administrator can change task generation, conditions, reminders, reviews and views without a development deployment, then validate both the corrected and blocked outcomes.
Use the sample joiner whose access decision is blocked, then test the return, escalation and readiness decision in your own pilot.