Zoho Recruit: How the Hiring Pipeline Is Modelled, End to End

Hiring speed is usually blamed on candidate availability. In practice, most of the elapsed time in a slow process is spent waiting: for a panel member to reply, for an approval that has no route, for feedback that lives in an inbox.

The requisition, and why it belongs in the system

A requisition is the hiring equivalent of a deal: it has an owner, a budget, an approval and a status. Where requisitions exist only as conversations, two problems follow — nobody can say how many roles are genuinely open, and approval happens after sourcing has already begun. Zoho Recruit treats it as a record with its own approval route, which is what makes the pipeline countable.

Stages that describe a decision, not an activity

A stage should mark a decision someone made, not a task someone performed. “CV sent to manager” is an activity; “Manager shortlisted” is a decision. The difference matters because only decisions can be measured — you can ask how long a decision took, but not how long a sent email took.

Structured feedback beats written impressions

Interview feedback forms in Recruit let each panel member score against the same criteria and record a recommendation. Two things improve immediately: comparison across candidates becomes possible, and the decision stops depending on whoever writes most persuasively. It also removes the single most common source of delay, which is a panel member who has an opinion but no obvious place to put it.

The careers page and the source question

Recruit publishes a careers page and posts to job boards, and every application carries its source. That attribution answers a question most businesses guess at: which channels produce candidates who actually get hired, as opposed to candidates who merely apply. Volume by source is easy to obtain and mildly interesting; hires by source is the number that should decide where the recruiting budget goes.

The handover that is worth automating

When an offer is accepted, the candidate becomes an employee. Where Recruit and People share the estate, that record is created once and carries the joining date, role, department and reporting line with it. Where they do not, someone re-enters it — and the second version is where the payroll discrepancy is born.

Frequently asked questions

Do we need Recruit if we hire only a few people a year?

Possibly not as a standalone product, though the requisition and candidate record still solve a real problem. The volume threshold matters less than whether more than one person is involved in a decision.

Can agencies work in the same pipeline?

Yes — Recruit supports vendor access so agency submissions land in the same pipeline with their source recorded, rather than arriving as email attachments.

Where should offer approval live?

On the requisition, before the offer is drafted. Approving compensation after a verbal conversation is how hiring managers end up negotiating against their own company.

What is the most useful metric to start with?

Time between shortlisting and interview. It is almost always the largest controllable delay, and it is entirely within the business’s own hands.

Where to start

Take your last five hires and write down the date of each stage. The gap that surprises you is your process problem — and it is very rarely the candidate’s diary.

References

Topic inspiration: the HR and recruitment 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.