Onboarding in Zoho People: The Workflow Behind the First Ten Days

Onboarding is one of the few processes where the cost of doing it badly is obvious and the cause is almost always the same — the work is spread across HR, IT, finance and a manager, with no single place that shows what has been done.

The joining date as the anchor

Every task in an onboarding template is expressed relative to the joining date: five days before, on the day, end of week one. That relative model is what makes the template reusable — one definition serves every hire, and a joining date that moves drags every dependent task with it rather than leaving a trail of stale reminders.

Documents, and the acknowledgement problem

Collecting documents is easy; proving that a policy was read is the part that matters later. Zoho People handles both as part of the same flow: the new joiner uploads what is required, acknowledges the policies that apply to their role and location, and both are stored against the employee record with a timestamp. When a question arises two years later, that record is the answer.

Access, and the case for provisioning from the HR record

The last row is the security one, and it is the strongest argument for driving access from the HR record rather than from requests. An exit that removes access automatically is worth more than any policy document about offboarding.

Copying permissions, and why it goes wrong

“Give them the same access as her” is the most common provisioning instruction in any business, and it accumulates quietly: the colleague being copied has permissions from two roles ago, and every new joiner inherits them. Role-based access — permissions defined for a role, assigned when the role is assigned — is the alternative, and it is the only version that stays correct as people move.

The part the product cannot do

Provisioning is administration. What decides whether a new joiner is productive in a month is the second column of the diagram above: clear expectations for the probation period, a named person to ask questions of, and a first feedback conversation that happens on a date rather than when someone gets round to it. Zoho People can schedule all three and record that they happened. It cannot make them good.

Frequently asked questions

How many tasks should an onboarding template have?

Enough to cover the administration and the first conversations, usually fifteen to twenty-five. Templates that reach fifty become a compliance exercise that everyone learns to tick through.

Should different roles have different templates?

Usually one base template with role-specific additions, rather than an entirely separate template per role. Divergence is expensive to maintain.

Can candidates complete documents before joining?

Yes — a pre-joining portal is the standard pattern, and it moves paperwork out of the first week where it competes with actual work.

What about offboarding?

The same mechanism in reverse, driven by the last working day: access removal, asset return, final settlement and knowledge handover. It is the same template model and it is far more often neglected.

Where to start

Ask your last three joiners what took longest to arrive. The answer is nearly always an access or an account, and nearly always because someone had to be asked rather than the record being the trigger.

References

Topic inspiration: the HR and people coverage on the Zoho Blog. This article is Kelevo Software’s own analysis and wording, written from our implementation experience; no text has been reproduced from Zoho’s publications.