Employee information is scattered.
Contracts, roles, managers, locations, documents and changes live across files, inboxes and payroll sheets.
People & HR systems
Give every employee a reliable journey from hiring to exit.
We design HRMS and people operations systems for distributed, mission-led teams. Bring recruitment, employee records, onboarding, leave, attendance, payroll inputs, performance, expenses and offboarding into one clear lifecycle.
What breaks today
People operations become invisible work.
HR teams spend their time chasing forms, updating duplicate records and reconciling attendance or payroll inputs instead of supporting people and managers.
Every month restarts the chase.
Attendance, leave, expenses and payroll inputs depend on reminders and manual consolidation.
Employees cannot answer simple questions themselves.
Requests, policies, balances, goals and documents require an HR team member to look them up.
See it working
Three screens your people team would use every week.
An HR system earns its place when an employee, a manager and the HR lead each open it and find what they need without sending a message to ask.
SESample employeeEMP-0381 · field coordinator · Pune
Joined, offer letter and ID documents verifiedComplete
Bank details pending for payrollMissing
Probation review due with reporting managerHuman decision
12 days balance under the state policyCurrent
One employee record. Role, location, documents, leave and history in one place instead of files and inboxes.
3 requests waiting for approvalDue
2 missed check-ins from field visitsCheck
4 travel claims with bills attachedReady
1 probation decision this monthDecide
Only their team, only what needs them. Routine requests in one queue, decisions flagged early.
112 / 118employee records ready for this month’s payroll
- Ready
- Attendance, leave and changes approved
- Exceptions
- 6 waiting on a manager
- Cut-off
- 25 September
- Hand-off
- To the payroll process
Exceptions before the cut-off. HR chases six records, not one hundred and eighteen.
Illustrative screens with sample data. Not a live partner record.
Employee lifecycle
One journey, with clean ownership at every stage.
Not every organisation needs every module on day one. The sequence should follow the workload and risk your HR team carries now.
- Workforce plan and recruitment
- Offer, joining and onboarding
- Employee records and self-service
- Leave, attendance and expenses
- Performance, growth and payroll inputs
- Transition, exit and alumni record
Core HRMS
Start with the employee record, then earn the complexity.
We configure the system around real policy, approval and payroll boundaries rather than copying a generic enterprise setup.
Recruitment and joining
Roles, candidates, interviews, decisions, offers, document collection, checklists and accountable onboarding owners.
Employee master and self-service
Organisation structure, employment history, documents, policies, requests, letters and the fields employees can safely maintain.
Time, leave and expenses
Attendance patterns, holidays, leave policy, approvals, travel or expense requests and exception handling.
Performance and growth
Goals, check-ins, review cycles, feedback, learning, role changes and manager visibility without turning people into scores.
Payroll and statutory inputs
Validated monthly inputs, changes, deductions, reimbursements and handoffs to the organisation’s payroll and finance process.
Exit and institutional memory
Clearance, asset return, access removal, knowledge handover, final documents and an auditable employment history.
The handoffs that matter
HR does not operate on an island.
People data touches programme delivery, project staffing, grant allocations, expenses, finance, access control and organisational learning. We connect only the records each team legitimately needs.
HR ↔ finance
Payroll inputs, reimbursements, cost centres and approved changes, with a clear source of truth.
HR ↔ grants and projects
Staff allocation and role information where budgets or delivery plans require it, without exposing private HR data.
HR ↔ access and security
Joining, role changes and exits trigger the right account, device and permission actions.
Employee ↔ manager
Self-service for routine needs and timely prompts for the decisions only a manager can make.
How a project runs
What you get at each stage.
Every people system follows the same ImpactOS stages and sign-off points, so you always know what is being decided, by whom, and what you will have at the end of it.
- 01
Listen
We follow one employee from joining to their first payroll with the people who run it.
You getA map of the employee lifecycle and every hand-off between HR, managers and finance - 02
Scope
Policies, roles and approval routes first, then the records and fields behind them.
You getA locked data model, an honest estimate and what we won’t do✓ Scope agreed - 03
Deliver
Employee records, attendance and leave first, tested with real managers and locations.
You getA working first release, migrated employee data with a transformation log, and training in context✓ Design locked✓ Tested - 04
Close
We track whether requests and approvals move through the system, not just logins.
You getHandover, documentation and 30 to 60 days of hypercare after go-live✓ In use - 05
Learn
A retrospective on what worked and what the next release should be.
You getA roadmap for payroll, expenses, reviews or recruitment in sequence
People systems are often an early release in a wider roadmap. See the five-stage transformation pathway →
Results
Distributed HR operations, brought into one system.
The pattern transfers; the exact policies, roles and approval routes change with each organisation. The full case lives on edzola.com.
Child protection · Zoho People7 statesone HR system for 100+ staff
Each person sees only what their role needs, with leave rules per state. Time spent on attendance fell from six hours a month to two.
Read the case study ↗
Youth employabilityAntarang Foundation
HR operations brought into one system. Not yet published as a case study.
The nonprofit HRMS guide
A maintained introduction to streamlining HR processes with Zoho People.
Read the guide ↗“From weekly meetings to prompt availability and quick resolution of issues, their team has been reliable, proactive and true to their word.”
Payroll, employment and statutory processes vary by organisation and jurisdiction. System configuration must follow policies reviewed by the organisation’s authorised HR, payroll and legal advisers.
Adding AI
When the employee record is solid, AI can take on the chasing.
Our own products plug into a people system once records, roles and policies are clear. People keep every decision about someone’s job, pay or performance.
DozAI · Run
Missing documents
Document completeness is one of the missions we are shaping: chase every missing joining or compliance document and hand unclear cases to HR.
Explore DozAI → ZolaShield · ProtectStaff data and DPDP
See where employee and volunteer data carries risk, from shared sheets to WhatsApp groups, with a 180-day plan to fix it.
Explore ZolaShield → Claude · coachingAI for HR teams
Claude coaching for leaders, and AI agents on your own data, with a person still in charge of every decision.
Explore AI for nonprofits →Not sure where AI belongs in people operations yet?Start with AI for nonprofits →
Questions
What teams usually ask first.
If yours isn’t here, bring it to the first call. We’d rather answer it honestly than have it surface halfway through a build.
Zoho People or a custom system?
Most organisations start on Zoho People and extend it with Zoho Creator only for programme-specific roles. We’ll recommend the smallest setup that fits your policies.
We have different leave rules in different states. Can it handle that?
Yes. Aangan Trust runs leave rules per state for staff across 7 states in one system. We configure the policies you have approved rather than a generic template.
Do you run payroll?
No. We make sure payroll inputs are validated and approved on time, then hand them to the organisation’s payroll and finance process.
Who can see salary and personal records?
Only the roles that need them. Access is set by role, team and location, and we review it with you before go-live.
What will it cost to run, not just to build?
Cost follows records, roles, integrations, migration and support. We show expected running costs, including licences, up front. Eligible nonprofits can access subsidised delivery through the Built for Impact Programme.
Will AI make decisions about staff?
No. AI can draft, summarise or chase missing documents. A named person makes every decision about someone’s job, pay or performance.
Go deeper without duplicating
Prepare the organisation, not just the software.
These resources help teams clarify readiness, responsibilities and adoption before configuration begins.
Technology assessment
Evaluate what you already have
Decide what to keep, repair, connect, replace or retire before buying another tool.
Read on edzola.com ↗ReadinessMission-rich, systems-poor
Why process clarity and organisational support matter as much as the software.
Read the essay →Leadership and adoptionWarmth is how standards travel
How clarity, visibility and humane leadership help new ways of working stick.
Read the essay →Connected verticals
People power every other system.
Connect the HR record to the work, costs and access decisions that genuinely need it.
Review the employee lifecycle.
Bring your HR forms, monthly payroll checklist, leave policy or onboarding flow. We will identify repeated work, system boundaries and the first release worth making.