Your people.
Your work.
Beautifully connected.

Clock in from anywhere. Know exactly who's working, right now.

Clock in/out with timestamp capture, a full monthly log, rotating 24×7 rosters built on 15-minute shift codes, week-off / comp-off / holiday-off handling, spreadsheet import for whole teams, and regularization when someone forgets to punch.

• Employees clock in and out with one tap — no punch cards, no paper registers
• Managers build rotating shift schedules using short codes (like "A1" for an 8:00 AM start) instead of typing out times for every person, every day
• Upload a whole team's schedule at once from a spreadsheet, instead of entering each person's shift one by one

No more spreadsheets and email chains for a leave request.

Configurable leave types and accrual policies, a clean apply-and-approve workflow, and a team calendar so managers see who's out before they plan around it.

• You decide the leave types your company offers — sick leave, casual leave, earned leave, or your own — and how many days each employee earns per year
• An employee taps "Apply for Leave", and their manager or HR approves or declines it with one click — no chasing emails
• Employees and HR read the same saved leave balances and request statuses; refresh the view to check subsequent changes

Joining documents, organized by employee.

Upload PDFs and images per employee — offer letter, ID proofs, bank details, certificates — with a submitted-vs-pending checklist and full timestamped history. Employees can view their own; images are compressed on upload to keep storage lean.

• Upload each employee's documents — offer letter, ID proofs, bank details, certificates — as PDFs or photos, all kept in one place
• Mark a document internal-only when it shouldn't be visible to the employee — everything else they can open themselves, any time
• Employees can view and download their own documents anytime, without having to ask HR

A clean, complete exit — nothing forgotten.

Owner-assigned exit checklists, outstanding equipment, recorded exit dates, and relieving or experience letters. Login deactivation, payroll review and final settlement remain explicit tasks for the responsible team.

• A checklist walks through everything that needs to happen when someone leaves, so nothing gets missed
• Open a leaver's checklist and anything they are still holding — laptop, headset, ID card — is listed on it, with a link to take it back. That is the single most common reason an exit is marked done and then is not
• Relieving and experience letters come out of your own wording with their dates, designation and length of service already filled in — and once issued the text is frozen, so improving the template never rewrites what somebody was handed last March

Score the call, share it, and let the agent argue with it.

Build the scorecard your process actually uses, audit against it, and give every agent a number they can see the working behind — with a right of reply, so a disputed score is settled on the record rather than in a corridor.

• Your own form: sections, points, and which parameters are fatal — edit it rather than working around it
• A parameter marked fatal in your scorecard makes that audit score zero; N/A parameters leave the applicable total
• Parameters that could not arise on a call are marked N/A and leave the total, so short calls are not punished

The numbers on arrival, and the spreadsheet when somebody asks.

Headcount, a fortnight of attendance, the department split and where leave stands — on the screen you land on. Then eleven registers that download as real Excel files, because somebody always asks for the sheet.

• Land on headcount, who is on the floor right now, what is waiting for your approval, and a fortnight of attendance as a trend rather than a number
• Attendance, shift summary, leave, payroll, bank transfer advice and the employee master — every one a proper .xlsx, not a CSV pretending to be one
• Quality scorecards and per-agent averages, the equipment register and what is out on loan, and a hiring funnel that keeps the people who did not make it, because a funnel that only lists the hires is not a funnel

Payroll and employee data, protected the way it should be.

Role-based access across Employee, Manager, HR-Admin and (for us) Super-Admin tiers, with every company's data isolated from every other's — enforced in the database, not just the screen. SSO/SAML is planned for Enterprise and scoped before commitment.

• Every person only sees what they're supposed to: an employee sees their own info, a manager sees their team, an HR-Admin sees the whole company
• Tenant isolation and role-based access are enforced by database policies as well as the interface; administrative and integration boundaries require ongoing testing
• Planned for Enterprise: sign-in with company Google or Microsoft accounts, subject to agreed implementation scope (called "Single Sign-On") — one less password to remember, and IT can control access centrally

Ask in your own words. Choose the record you mean.

Read-only answers from supported records your login can access, with a source screen and retrieval time. Maharishi also searches tutorials. It does not generate an unrestricted answer, perform actions or automatically read every uploaded document.

• Plain-English suggestions help distinguish a record question from a request to learn a workflow; common spelling variations and everyday phrases are supported
• Personal answers cover leave, attendance, corrections, rosters, payslips, profile information, letters, equipment, policies, tickets, goals, shared reviews, published quality audits, lifecycle checklists and employee-visible document metadata, subject to role and plan
• Authorized approvers can read company attendance and pending-approval summaries using the same sources as the Overview screen