The new hire no system recognized yet

He starts on a Monday. By Wednesday he still cannot open the drawing he was hired to work on.

It is not that nobody wants to give him access. It is that the file system needs IT to add him, IT needs HR to confirm he is actually on the payroll, and HR is waiting on the signed offer letter to be scanned and filed, which is sitting in someone's inbox behind eleven other things. Nobody is slow on purpose. Each of them is just waiting for a different office to finish its own version of the same fact: that he works here now.

So for three days he learns the plant the way everyone learns it when the system has not caught up — a colleague walks him through the drawing on a shared laptop, over someone else's shoulder, because that is faster than waiting for his own login.

Why we build it this way

Every company already has one fact about a new hire that matters more than any other: that they exist, and from what date. HR software asks for that fact and stores it. The project tool asks for it again, in its own form, so it can issue a login. The gate system asks a third time, so it can print a card. Payroll asks a fourth time, so it knows who to pay.

Each of those is a separate guess at the same underlying fact, kept by a different department, on its own timetable. They do not update together, so they drift — HR has the join date, the project tool has whichever name someone remembered to invite, the gate log has whatever the security desk typed that morning. A new hire's first week is spent waiting for four separate departments to each notice, on their own schedule, a fact that was true the moment he signed.

Buying a bigger HR system does not fix this. It just adds a fifth place that asks the same four questions and still needs someone to type the answer in by hand. The actual problem is treating "who works here" as a lookup each system performs for itself, instead of one fact the whole company already shares.

How it works, roughly

VarahiConverse puts HR on the same identity model as the rest of the work, so attendance, leave, onboarding and appraisals are not a separate list kept by a separate department:

• Onboarding reads from one entry, not six. The day someone is marked as joining, that is the fact every module sees — mail, files, the project tool — instead of each one waiting to be told separately.
• Leave and attendance are logged by voice, not a form. A site engineer says he is taking Thursday off; it reaches the same record a manager checks before promising a delivery date, and it works with no signal, syncing once the phone is back.
• An appraisal reads the year's actual record, not a manager's memory of it. The calls, the approvals, the work already logged are there to look at, instead of five boxes filled in from whatever the manager happens to recall in March.

None of this removes the person from the decision. A manager still approves the leave, still signs the appraisal, still decides who is cleared to start. What changes is what they are deciding from — the actual record of the work, not a memory of it, and not four separate systems each a few days behind the other three.

VarahiConverse · drag to turn