Move HR Requests and Approvals Into a System
HR process automation is the work of turning an agreed HR process into connected digital workflows. Employees and managers raise and approve requests in one system, reminders replace the follow-up call, letters generate from approved templates, and management reads a dashboard instead of waiting for a file. It is configuration work rather than a purchase, and it only works on a process that has been settled first.
HR Process Automation in brief
HR process automation is the work of turning an agreed HR process into connected digital workflows. Employees and managers raise and approve requests in one system, reminders replace the follow-up call, letters generate from approved templates, and management reads a dashboard instead of waiting for a file. It is configuration work, not a purchase.
- GullyHR is an HR consulting, HR services, training and software company based in Bengaluru, working with Indian startups and small and medium businesses.
- Scope covers process mapping, workflow design, approval routing, notifications, employee and manager self-service, document generation, dashboards, HRMS configuration and integration with the systems you already run.
- Automation follows process design. We do not configure a workflow around a process that has not been agreed, because the software then encodes the confusion instead of removing it.
- The workflows can be built in the GullyHR platform or configured in your existing HR and payroll systems, whichever is the sensible option for your situation.
- Scope and sequence are agreed after a consultation, based on which of your processes are stable enough to automate and which need design work first.
The starting point
Is HR Running on Chat, Email and Spreadsheets?
Manual HR is not a problem at a small size; it is simply how a business starts. It becomes a problem when the effort outgrows the headcount that justifies it, and when the same information has to be typed into three places to stay current.
We map the process, assign a system action to each step, configure it and test it on real cases.
You may be experiencing:
- Leave requests arriving by chat, email and occasionally on paper, reconciled by hand before payroll.
- A request sitting unapproved for a fortnight, with the first reminder being an employee complaint.
- The same joining details typed into a spreadsheet, a payroll sheet and a letter template, drifting apart within a month.
- A day lost assembling headcount and attrition out of files whenever management asks.
- Employees writing to HR for a leave balance, because there is no way to look it up.
- A tool bought and half-configured, which people now work around rather than through.
- A biometric device, a payroll package and a spreadsheet each holding a version of the same person.
- Joiners waiting for system access or an email ID because nobody passed on the joining date in time.
- Exit clearance tracked on a paper form passed between desks, with nobody sure which department still holds it.
- Letters drafted from an old Word file, so the wording differs from one employee to the next.
- An approval given by phone and recorded nowhere, so the history lives in one manager's memory.
What we can help with
Our HR Automation Services
Automation Readiness Check
Whether each process on your list is genuinely agreed and stable, or whether it still needs design work first. Configuring a workflow around an unsettled process moves the confusion rather than removing it.
Process Mapping
Steps, decision points, approvers and records drawn in enough detail that a workflow can be built directly from the map, which is where the exceptions every business has surface.
Approval Workflows
Multi-level routes for leave, expense, requisition, movement and exit requests, with escalation for anything that sits too long, so approvals move through the system instead of through follow-up calls.
Reminders and Alerts
Automated alerts for pending approvals, confirmation dates falling due, documents about to expire and regularisations not raised, so following up stops being a person's job.
Employee Self-Service
Leave balance, attendance record, payslips, policy documents and personal detail updates available to the employee directly, so HR stops answering what somebody could look up.
Manager Screens
Approvals, team attendance, leave planning and performance actions on a manager's own screen, so a manager can act on their own team without routing everything through HR.
Letter Generation
Offer, appointment, confirmation, revision and transfer letters produced from approved templates and employee data at the moment the approval completes, rather than drafted separately days afterwards.
Dashboards and Integration
Headcount, attrition, attendance exceptions, pending approvals and confirmations due drawn from the records the workflows produce, with a defined data route where an existing device or payroll package needs the same information.
The scope
What the Consulting Covers
Automation touches every point where a request, an approval or a record moves between people. These are the parts of that work we can review or configure. The scope is agreed with you and can take all twelve areas or only some.
Process Inventory and Readiness
Which HR processes run today, how stable each one is, and which are settled enough to configure first.
Process Mapping and Workflow Design
Steps, decision points, approvers, records and exceptions drawn so that a workflow can be built directly from the map.
Employee Master and Data Preparation
The employee fields, department and grade lists and reporting lines the workflows depend on, and the correction of existing records before they are loaded.
Approval Routes and Escalation
Who approves what, at which level or value, who covers when an approver is away, and what happens when a request waits too long.
Leave, Attendance and Regularisation Requests
Requests, balances, corrections and approvals arranged so that closed records reach payroll input.
Joining, Movement and Exit Workflows
Onboarding tasks, transfers, promotions, resignations and clearances moving through owners and due dates instead of reminders.
Employee and Manager Self-Service
The actions employees and managers can take directly, and which of them to start with.
Notifications and Reminders
The alerts for pending approvals, dates falling due and tasks left open, and who receives each one.
Letters and Document Templates
Approved templates, merge fields and the point in each workflow where a letter is generated.
Roles, Access and Approval Limits
Who can view, edit and approve which records, with sensitive categories restricted separately.
Device and Payroll Software Integration
How attendance devices, payroll packages and other tools share data with the workflows, or where a manual step remains.
Testing, Training and Go-Live Review
A trial on real cases, user briefings, support through the first live cycle and a review afterwards.
Working together
Ways to Work With Us
Readiness Assessment
A review of which processes are stable enough to automate as they stand and which need design work first, ending in a prioritised automation sequence.
Single-Process Automation
One process, such as leave and attendance or onboarding, mapped, designed, configured, tested and trained end to end before anything else is opened.
Full System Implementation
The platform configured across the lifecycle: records, attendance, payroll inputs, performance, documents, exits, self-service and reporting.
Ongoing Automation Advisory
A continuing arrangement that extends automation to further processes over time and adjusts existing workflows as your structure, headcount or policies change.
Access rules and approval limits are decisions you take. We set out the options with their trade-offs, then configure exactly what you approve.
The deliverables
What You Receive
Depending on the scope of your engagement, deliverables can include:
- A process map for every process taken up for automation, drawn as a step-and-approval flow.
- A workflow design document naming the system action, approver and notification for each step.
- Configured approval workflows for the processes in scope.
- Employee and manager self-service screens for the actions agreed, with the access rules you approved.
- Automated letter and document generation linked to the relevant approval workflows.
- Management dashboards covering headcount, attrition, attendance exceptions and pending approvals.
- A tested configuration, including user roles, letter templates and the report set.
- An employee and manager training session, with support through the first live cycle.
- A readiness register listing each process, how stable it is and the recommended order of automation.
- A data preparation list naming the employee records, department names and approver details to be corrected before loading.
- An integration note stating what moves between your attendance device, payroll package and the system, and which steps stay manual.
Step by step
How We Work
Check Readiness
We look at whether each process on your list is genuinely agreed and stable. Where it is not, design work comes first, because automating an unsettled process hard-codes the confusion into a system.
Map and Design the Workflow
The agreed process is drawn as steps, decision points, approvers and records. Each step is then assigned a system action, with approval routes, escalation rules and the notifications that keep things moving.
Settle Access and Approvals
Who can see what, who can approve what, and where something escalates by value or level. We put the options in front of you with the trade-offs, and you take the decisions before anything is built.
Configure and Test on Real Cases
Workflows, approval routes, notifications, letter templates, self-service screens and reports are configured, then run against real employee cases and the awkward ones: a mid-month joiner, a transfer, an employee on notice.
Train, Go Live and Review
Employees and managers are shown how to raise and approve requests before the workflow opens to everyone. We stay through the first live cycle, then adjust whatever did not survive contact with your actual month. Where it is included in the engagement, we also run a pilot with one team or location before the workflows open to everyone.
The difference
What Automation Actually Changes
Configured workflows help you:
We do not promise outcomes. We record a baseline before work starts, covering how long approvals currently take and how much manual reconciliation each cycle needs, and report against it, so you can see what changed and what did not.
- Move leave, attendance, movement and exit requests through one system instead of across chat, email and paper.
- Keep approvals moving, because reminders and escalations do the chasing a person used to do.
- Let employees find their own leave balance, payslip and policy documents without writing to HR.
- Issue letters at the moment the approval completes rather than drafting them separately afterwards.
- Give management headcount, attrition and pending items as a standing view rather than a file assembled on request.
- Enter employee data once and carry it into attendance, payroll and reporting instead of retyping it.
- Know which HR processes are ready to automate and which need design work first.
- See who holds a pending request and for how long, instead of asking around.
- Keep a dated record of each approval alongside the request it belongs to.
- Hand over a configuration that your own team can understand and change.
Find your fit
Who This Service Is For
Companies Running HR Manually
Businesses still on chat, email and spreadsheets, where the manual effort has outgrown what the headcount justifies.
Businesses With Underused Software
Companies that bought an HR system and never configured it properly, so employees work around it rather than through it.
Companies Adding Scale
Businesses opening a second location or adding headcount, where manual approval and record-keeping will not hold at the new size.
Owners Waiting for Numbers
Businesses where management routinely waits days for a workforce figure that ought to be available on demand.
Companies With Disconnected Systems
Businesses running a device, payroll software and a spreadsheet that do not share data with one another.
Businesses With Settled Processes
Companies that have already done the design work and are ready to configure a stable, agreed process.
Companies Moving Off Spreadsheets
Businesses planning to move employee records and approvals into an HR system, and wanting the process settled before the move.
HR Teams Answering the Same Queries
Teams spending much of the week on leave balances, letter requests and status calls that a workflow could handle.
Good to know
From Request to Record: How a Workflow Runs
Raise and route
- Request: an employee or manager raises it in one place, with the details the process needs.
- Route: the request goes to the approver named in the approval matrix, and on to the next level where the rules require it.
- Remind: pending items trigger reminders and move to a named person if they wait too long.
Approve and record
- Approve: the decision, the approver and the date are kept with the request.
- Generate: a letter or update is produced from the approved template and the employee record.
- Report: the record carries into attendance, payroll input and the management view.
Each step has an owner, a due time and a defined route for exceptions.
Good to know
Track Whether the Workflows Are Working
Speed and use
- Approval turnaround: how long requests wait at each level.
- Share of requests raised in the system: how far chat, email and paper have been replaced.
- Pending items past due: where reminders and escalation need adjusting.
Effort and quality
- Re-keying steps per joiner: how many times the same detail is still typed.
- Payroll input build time: how much manual reconciliation each cycle still needs.
- Exceptions handled outside the workflow: which cases the design does not yet cover.
- Self-service use: which employee actions are used and which are ignored.
Measures use agreed definitions and a baseline recorded before work starts.
Good to know
Scope and Service Boundaries
Your engagement defines
The processes, employee categories, locations, systems, workflows, user roles and training included.
Requires a separate agreement
- Software licences and hosting, where a platform is chosen.
- Custom software development beyond configuration.
- Replacement of attendance devices or other hardware.
- Large or poorly structured data migrations.
- Payroll calculation and statutory filings.
- Legal opinions and policy drafting.
- System administration after handover.
Access rules and approval limits are your decisions, and employment decisions remain with your management. Policies, letters and formal actions need review by a qualified professional before they are configured.
Good to know
Timeline and How to Prepare
Timeline
The schedule depends on how many processes are in scope, how settled they are, the locations and employee categories covered, and the condition of your employee data. We confirm it after the readiness check.
Useful inputs
- A list of your HR processes and who runs each one.
- Current forms, letter templates and approval routes.
- Employee master data as it stands, in whatever format.
- Leave, attendance and holiday rules.
- Details of the HR, payroll and attendance systems in use.
- A sample of recent requests, including the awkward ones.
- Names of approvers and their deputies.
If your processes are not documented we can begin with discussions and map them together.
Good to know
Confidentiality and Employee Information
Handled by agreement
Automation work involves employee records and approval histories. Before work begins we agree the data required, who may access it, how it is shared and how test data is handled.
Access in the design
The workflow design also sets out user roles, approval limits and which records are restricted, so access follows what each role needs.
Good to know
Frequently asked questions
It is the work of turning an agreed HR process into connected digital workflows: requests and approvals in one system, reminders instead of follow-up calls, letters generated from approved templates, and a management view drawn from the same records. It is configuration work, not a purchase.
We would not recommend it. Automating an unsettled process hard-codes the confusion and makes it harder to change later. The readiness check establishes which processes are stable enough as they stand, and design work is done first where it is not.
No. The mapping, workflow design and access decisions apply to whatever system you run, and we configure in it. Where you prefer, the same design is set up on the GullyHR platform. Existing devices and payroll packages do not have to be replaced.
Process consulting designs what the process should be. Automation configures an agreed process into a system. Many engagements include both, in that order, and the readiness check is where we establish which one you actually need first.
That depends more on design than on technology. Keeping employee-facing actions to a few common ones, making them available in the languages your workforce reads, and training before go-live matter far more than the sophistication of the system.
Access is configured by role, so people see what their work requires and no more, and sensitive categories are restricted separately. Your platform's own security and hosting arrangements apply, and we work within whatever rules your business has set.
It depends on how many processes are in scope and how settled they are. A single process is a short engagement; a lifecycle implementation runs considerably longer. The timeline is stated in the proposal after the readiness check rather than estimated beforehand.
Yes, and the training step depends on it. Your team tests the configuration against real cases, learns it before go-live and owns it afterwards. Configuration that only the consultant understands fails the first time something needs changing.
After the readiness check. The scope lists which processes are being automated, in which system, with which self-service actions and reports, and whether training and first-cycle support are included. It is agreed in writing before configuration starts.
An HRIS or HRMS is the software that holds employee records and modules. HR process automation is the work of configuring agreed processes in it: routes, reminders, letters and views. Software without that work can end up as a database that people work around.
Usually the process that is used most often and costs most when it goes wrong, such as leave and attendance or onboarding. The readiness check ranks your list and you decide the order.
Usually yes. We map what each one holds and agree how data moves between them, and where a connection is not possible we say so and state which manual step remains.
Listing the fields each process needs, correcting names, dates and reporting lines, loading a trial set and checking it with your HR team before go-live. The fields to carry across are agreed with whoever handles your payroll.
Not here. The workflows we configure follow rules you approve, such as who approves what, when a reminder goes out and which template a letter uses. Decisions about people stay with your managers.
We settle the cover arrangement during design: a named deputy, or escalation to the next level when a request waits too long. It is tested against an absence case before go-live.
Your HR team, once they have been trained to adjust routes and templates. Continuing support for further processes or changes can be agreed as a separate advisory arrangement.
Pricing depends on the number of processes, locations and employee categories in scope, the condition of your data and the support required. Share your requirements and we will send a tailored proposal.
Put the Agreed Process Where the Work Happens
Turn settled HR processes into configured workflows with approvals, reminders, generated letters and a live management view, tested on real cases before anyone relies on them.
Prefer to talk first? Call +91 80958 58589 or write to hello@gullyhr.com.
Book an Automation Consultation
Tell us which HR processes you want to move into a system.
