From Offer Letter to First Leave Request: Automating Onboarding, Attendance and Leave

The quickest way to see where HR processes break is to follow one person through them. In this guide we track a fictional new analyst, Priya, from the day she accepts an offer to the day she applies for her first leave, and look at where employee onboarding software, attendance tracking and leave workflows make each step smoother. Along the way we will be clear about what should be automated and what still needs a person.

Before day one: preboarding

Priya accepts her offer on a Wednesday and starts in three weeks. In many companies, nothing happens in between except a nervous wait. That gap is a missed opportunity.

SHRM's guide to the onboarding process describes four components: preboarding, orientation, foundation-building and mentoring or buddy systems. It suggests engaging new hires after they accept and before they start, for example by sending company information or pairing them with a buddy who can answer practical questions.

Here is where a structured system helps:

• A joining checklist is created automatically when the offer is marked as accepted, with tasks for HR, IT, the hiring manager and Priya herself.
• Document requests go out early. Priya uploads identity proofs, address details and bank information through a secure link rather than by email.
• IT and facilities get notice. Laptop, email account and access are requested with a due date tied to her start date.
• A buddy is assigned and introduced before day one.

1. Offer acceptedStatus change triggers the onboarding checklist.
2. Documents collectedPriya completes her profile and uploads documents via self-service.
3. Accounts requestedIT and facilities tasks are created with due dates.
4. Buddy introducedA colleague is assigned and sends a short welcome note.
5. Day-one plan sharedPriya receives her schedule, location and first-week agenda.

Day one and the first week: orientation

On her first morning, Priya's laptop is ready, her email works and her employee record already exists. The difference between this and a day spent filling in forms is noticeable, and it is almost entirely down to what happened in the previous three weeks.

What the onboarding workflow should handle

• Policy acknowledgements. Priya reads and confirms key policies, such as the code of conduct, leave policy and data protection guidelines, and the confirmation is stored against her record.
• Mandatory training tracking. Required sessions are listed with completion status.
• Probation dates. Her probation end date is calculated from her joining date and a reminder is set for her manager ahead of it.
• Asset records. Her laptop and access card are logged against her name, which makes eventual exit handovers straightforward.

What it should not try to replace

SHRM's guide notes that orientation is best spread over several days rather than crammed into one, and that absorbing culture and ways of working takes much longer. No checklist replaces a manager who explains how the team actually works, or a buddy who shows Priya where people eat lunch.

The first month: attendance becomes routine

By week two, Priya is checking in each morning. Attendance management is where small inconsistencies cause disproportionate friction: forgotten check-ins, client visits, work-from-home days and late shifts all need a fair, consistent treatment.

Set rules once, apply them consistently

The most useful thing an attendance system does is apply the same rules to everyone. That means defining, in advance:

• Working hours and shift patterns for each group.
• Grace periods and what counts as a late arrival or early departure.
• How field visits, client meetings and remote work are recorded.
• Who approves corrections, and within what window.

Regularisation without the email chain

Priya forgets to check out after a long client workshop. Rather than emailing HR, she raises a regularisation request from her phone with a short note. Her manager approves it in the same place, and the record updates. The history of the request stays attached to the day, which matters if questions come up later.

When the probation review arrives

A few weeks before Priya's probation ends, her manager receives the reminder that was set on her joining date. The review form is pre-filled with her role, joining date and any onboarding tasks still open, so the conversation can focus on how she is settling in rather than on admin. Once the outcome is recorded, her confirmation date updates on her record, any policy that changes after probation, such as leave eligibility, applies automatically, and the confirmation letter can be generated from a standard template for HR to check and send.

The point is not to automate the review itself. It is to make sure the review happens on time, with the right information in front of the manager, and that its outcome flows through to everything that depends on it.

Attendance data feeds directly into payroll inputs, which is why getting approvals done before month-end matters so much. Our HRMS software guide explains how HR records support payroll coordination, and for finance teams the GST and TDS accounting workflows guide covers the month-end side.

The first leave request

Three months in, Priya wants a long weekend. This is her first encounter with leave management, and it is a good test of whether the system was set up well.

Policy as configuration

Before any request is possible, someone has to translate the written leave policy into rules the system can apply. Typical decisions include:

1. Which leave types exist, such as earned, casual, sick or other categories your policy defines.
2. How each type accrues: upfront at the start of the year, monthly, or after probation.
3. Whether new joiners receive a pro-rated allocation.
4. Rules for carry-forward, encashment and lapsing, where your policy provides for them.
5. Whether certain types need documentation or advance notice.
6. Which holidays apply to which locations.

If the written policy is unclear on any of these, resolve it before configuring. Software applies rules precisely, which means vague policy becomes visible very quickly.

What Priya sees

Through employee self-service, Priya opens her leave balance, sees how much she has accrued since joining, picks her dates and submits. The system shows her manager who else on the team is away that week. The manager approves, Priya gets a notification, and her balance updates. Nobody has to open a spreadsheet.

Accurate balances and accrual95

Clear approval routing85

Team availability view for managers75

Holiday calendars by location70

Detailed analytics30

HR automation: where to draw the line

HR automation is most valuable for work that is repetitive, rule-based and date-driven. It is least appropriate where judgement, empathy or confidentiality are central. A useful test for any proposed automation is whether a reasonable employee would be comfortable receiving the outcome without a person involved.

Good candidates:

• Creating checklists and tasks from status changes.
• Sending reminders for pending approvals, probation reviews and document expiries.
• Calculating leave balances and attendance summaries.
• Routing requests to the right approver.

Poor candidates:

• Decisions on disputed attendance or unusual leave situations.
• Anything involving health, grievances or disciplinary matters.
• Communicating changes to someone's role or pay.

• Onboarding checklist triggered by offer acceptance
• Documents collected securely through self-service
• IT and access tasks with owners and due dates
• Probation reminders set from joining date
• Attendance rules and grace periods written and configured
• Regularisation requests approved in the system
• Leave types, accrual and holidays configured from written policy
• Managers can see team availability before approving
• Month-end attendance and leave summary ready for payroll

A note for teams with field staff

Research and fieldwork businesses often combine office staff with interviewers, recruiters and project coordinators who work variable hours across locations. Attendance and leave rules for these groups may differ, and projects depend on knowing who is available. If that describes your organisation, it is worth linking HR availability to project planning, as discussed in our guide to multi-country research projects.

Where Sampledge fits

SampCrew is the HRMS module in the Sampledge ecosystem, covering employee records, recruitment, attendance, leave and payroll coordination. It gives teams one place to run the onboarding, attendance and leave workflows described here, with self-service for staff and approvals for managers. Because it sits alongside Talk2Tax for accounts, month-end HR inputs and finance records can be kept in step.

To see how SampCrew would handle your own joining, attendance and leave rules, request a demo, create a workspace or browse frequently asked questions.