Until recently, hiring at Vensar ran the way it runs in most multi-vertical construction companies: on email and spreadsheets. Requisitions sat with approvers for weeks with nobody chasing them. Resumes arrived by email and were lost or forgotten under the next day's mail.
Every screening call, document request, offer letter and joining reminder was manual — and every vertical did it slightly differently. Nobody at head office could say with confidence how many positions were open, how many candidates were in play, or where any single candidate actually stood.
Then the entire process, requisition to joining day, moved into one system built around Vensar's own rules rather than a generic template. This is what that took, and what it changed.
Where the hours actually went
It is tempting to blame slow hiring on slow people. That was not the problem. The HR team worked hard; the work itself was structured against them, scattered across inboxes, spreadsheets and phone calls that no amount of diligence could hold together.
A manpower requisition needed approvals from a chain of senior people who spend much of their time on project sites. The file moved only when someone remembered to chase it, and chasing a senior manager is a job nobody volunteers for. So files waited, and open positions stayed open.
Meanwhile resumes flowed in from consultants, referrals and portals. Some were screened the day they arrived. Others were buried and never read at all. A candidate rejected for one role might have been exactly right for another vertical — but there was no shared pool where anyone would find them again.
Then came the coordination: calls to schedule screenings, emails to request documents, negotiations tracked in personal notes, offers sent as attachments, joining dates confirmed by phone. Multiply that across five verticals and every designation tier, and hiring became a full-time exercise in follow-up.
Built around Vensar's rules, not a template
We did not start by writing software. We started by mapping how Vensar actually hires — the approval hierarchy for manpower requisitions, the hiring policy for each designation tier, and the exceptions that an off-the-shelf product would have flattened out.
Five verticals meant five legitimate variations on the same process, and every variation existed for a reason. The system had to carry all of them — every designation tier, every exception — without forcing anyone into a workflow that was not theirs.
That mapping became the ATS. Requisitions now route through Vensar's own chain of command, in the order the company already uses, with automatic reminders to whoever holds the file. No approval sits on a desk because nobody wanted to nag a senior manager.
One encoded rule deserves particular mention. Before any new hiring spend is approved, the system checks whether surplus staff on other projects can be redeployed instead. Hiring became the second option rather than the reflex — and redeployment stopped depending on somebody happening to remember a name.
One pipeline from requisition to joining day
Once a requisition clears its approvals, every candidate moves through the same pipeline: screening → document verification → salary negotiation → offer → joining. Each stage has a clear owner and a clear next step, so no candidate can quietly fall between two people's responsibilities.
The handovers that used to depend on memory now run themselves. When screening is complete, the document request goes out. When documents are verified, negotiation begins with the full record in front of the negotiator. Nothing waits for someone to remember an email.
Candidates feel the difference directly. From first contact to joining day, they are kept informed automatically over email and WhatsApp — screening confirmations, document requests, offer status, joining reminders. The long silences that used to lose good people simply stopped happening.
Management, meanwhile, gained a single view of hiring across all five verticals. Open positions, candidates by stage, requisitions pending approval, joiners due this month — questions that used to mean phone calls and guesswork became a dashboard that is simply true.
Offers, resumes and a pool that compounds
Offer letters used to be attachments — forwarded, edited, impossible to track. Now every offer is shared as a private accept/decline link: trackable, revocable and fully audited. HR sees when a candidate opens it and when they decide, and an offer that must be withdrawn can genuinely be revoked rather than living on in an inbox.
At the front of the funnel, every resume that reaches Vensar is captured in the system — 100% of them, evaluated rather than lost. Duplicates are merged, so one person arriving through two consultants becomes one clean record with a full history.
And promising candidates who narrowly miss one role no longer vanish. They are pooled, searchable and ready when the next requisition opens. Each hiring cycle now makes the next one easier, because the talent pool compounds instead of resetting to zero.
What 70% actually means
The measured result: 70% less time and effort in hiring, end to end. That number is not a projection or an industry benchmark — it is what happened at Vensar when chasing, tracking and reminding stopped being human work.
The second result is quieter but just as important: 100% of resumes captured and evaluated. Hire quality followed, because Vensar now selects from its full talent pool rather than from whichever emails happened to surface in the week a role opened.
Notice what did not change. Managers still decide who gets screened, what salary is offered, who joins on which date. The system took over the work between the decisions — the reminders, the routing, the record-keeping — and left the judgement exactly where it belongs.
The decisions stayed human; the distance between them disappeared.
What this means for your organisation
Very little of Vensar's old hiring problem was unique to Vensar. Any organisation that approves through a hierarchy, hires across divisions and coordinates by email will recognise the sitting files, the lost resumes and the silent candidates.
What made the difference was not software in the abstract. It was software built around the company's own rules — its real approval chain, its real designation tiers, its real exceptions — rather than a template the company had to bend itself around.
That is how we build everything at Stedvio: start with your process, build it complete, hand it over properly so your team runs it confidently long after go-live. Vensar's hiring did not get faster because people worked harder. It got faster because the busywork finally ran itself.