A Complete Guide to Employee Leave, Shift and Attendance Management with eHajira

A Complete Guide to Employee Leave, Shift and Attendance Management with eHajira

Leave, shifts and attendance are often managed in separate files, messages and registers. That can leave HR unsure whether a leave request was approved, whether the employee’s roster changed, or whether the day’s attendance should count as present, late, half-day or absent. A connected process makes these decisions easier to review and gives payroll a more consistent source of approved time data. This guide explains how Bangladesh employers can organise the three processes together and where eHajira fits, while keeping policy decisions and product availability clear.

The market context supports a practical, mobile-aware approach. BTRC reported 131.42 million internet subscriptions in April 2026, including mobile and ISP/PSTN subscriptions; BTRC defines an internet subscriber by recent access, so this is not a count of unique people or a guarantee of stable workplace connectivity. The Bangladesh Bureau of Statistics’ Economic Census 2024 reports on economic units, persons engaged, location, size and information-technology use. Together, these sources point to a varied employer base: small offices need uncomplicated approvals and attendance, while factories, schools, hospitals, service firms and multi-branch businesses may need roster controls and clear reporting.

Why manage leave, shifts and attendance together?

Each function changes the meaning of the others. A shift defines when an employee is expected to work. Leave explains why the employee may be away. Attendance records what was captured on the day. If one record changes but the other modules do not reflect it, the system can show a false absence, calculate late arrival against the wrong start time or pass an incorrect day status into payroll.

For example, an employee may submit a leave request that is approved after a supervisor has already marked the date absent. If the approved leave does not update the attendance record, HR must repair it manually. A night shift may begin on one calendar date and end on the next; assigning the punches to separate workdays can distort hours. A manager may change a roster but fail to tell the attendance processor. These are workflow issues as much as data-entry problems.

A joined-up system creates a sequence: define the employee and work rules; publish the roster; receive leave requests and approvals; collect device or authorised mobile punches; calculate the day; route exceptions; approve corrections and overtime; then close the period for payroll. Each step should retain the decision, reason and approver where relevant.

Build a clear employee leave process

Start with a written leave policy. It should state the leave categories the organisation recognises, eligibility, accrual or allocation method, required notice, supporting documentation, carry-forward rules, holidays, weekly rest and approval authority. The exact policy differs by employer and employee category. Software should implement the employer’s approved policy rather than decide entitlements on its own.

A typical digital leave workflow begins when an employee selects a leave type, dates and a reason. The system checks available balance if that rule is configured, then routes the request to the authorised manager or HR reviewer. The reviewer approves, rejects or requests clarification. Once approved, the leave appears in the employee record and relevant attendance calendar. The system should show the request status, date range, decision-maker and any comment so employees and supervisors have a shared reference.

Partial-day leave, overlapping requests, public holidays and weekly rest days need deliberate handling. For example, a two-day request may cross a holiday; the system must follow the company’s configured counting rule. If an employee requests leave during a rostered night shift, the organisation must decide which work date the leave consumes. Test these examples before launch, because small differences in date boundaries can change leave balances and attendance status.

Good leave reporting helps managers plan coverage. HR should be able to review pending requests, approved leave by date, leave balances and patterns by department or branch. A calendar view can help avoid approving too many absences in one team at once. Employees should be able to see their own balances and request history only if their account and plan include that access.

Plan shifts before attendance is calculated

A shift schedule converts a general working policy into a specific expectation for each employee and date. Employers may use fixed day shifts, evening or night shifts, rotating schedules, split shifts, flexible start times or different schedules by department. Each shift should define its start and end, applicable breaks, grace period, weekly rest and overtime approval rules.

For rotating or multi-branch teams, roster publication matters. The approved eHajira roster design follows a Draft → Publish → Lock lifecycle: planners prepare a draft, publish the approved assignments and lock the roster against routine changes. It also specifies no overlapping shift assignments for the same employee, company-defined minimum rest where configured, mandatory overtime approval and a distinct rule for excess breaks. These are documented design decisions; confirm their behaviour in the customer’s production build and plan before relying on them.

When a published roster must change, the organisation should record who made the change, when it takes effect and why. Employees need enough notice to understand their schedule. Supervisors should be able to see unassigned coverage and conflicts before the roster is published. A shift change should also trigger recalculation of relevant attendance records where the system permits it, without silently changing a payroll period that has already been closed.

Cross-midnight shifts deserve a dedicated test. If an employee works from 10 p.m. to 6 a.m., the system must connect the related punches to the right shift and work date. Breaks, late arrival and early departure should be calculated from that assigned shift, not from midnight boundaries. Test daylight-saving assumptions only if the deployment spans locations that use them; for Bangladesh-only operations the organisation should use its configured local time zone consistently.

Capture and review attendance consistently

Attendance can come from a biometric terminal, a supported card or a configured employee self-service method. Keep original punch events available to authorised reviewers. A terminal’s model, firmware and connection method determine what data it can send and which synchronisation features are available. Do not assume that every device from one brand supports the same protocol or employee-template functions.

The attendance engine compares punches with the assigned roster and calendar. It can then identify present, late, absent, incomplete punch, early departure, break exception or possible overtime according to configured rules. The system should make the source and result understandable: what time was recorded, which shift was applied, what rule produced the status and whether a person changed or approved it.

Attendance corrections should use a request and review path. If a worker forgets to punch or a device fails, the employee or supervisor should provide a reason and supporting information. An authorised reviewer accepts or declines the correction. Preserve the source event and record the change as an adjustment with the actor, time and reason. This gives HR a way to correct genuine mistakes without obscuring the original record.

Recent eHajira update notes describe several useful attendance reporting and payroll controls: late is counted from the Late field under configured rules; a late waiver appears as a distinct status and is excluded from late-based payroll treatment; reports include early-leave and break information; and half-day settings can define when short working hours count as half-day. Approved leave can replace a manually entered Absent status through attendance recalculation. These rules depend on configuration and should be checked in the customer’s build with real records before payroll is closed.

Connect approved time to payroll

Payroll should use reviewed attendance, not raw punches alone. Before closing a period, HR should resolve missing punches, leave conflicts, shift changes, late waivers, early departures and overtime approvals. The payroll configuration should document how paid and unpaid leave, half-days, early-outs, overtime and deductions affect salary. An employee should be able to understand the source of a pay adjustment, while payroll staff should retain an audit trail for changes.

A payroll parallel run is a practical control. For at least one representative pay period, calculate results using the new workflow and compare them with the existing approved method. Review edge cases such as a night shift, approved leave after an absent mark, a waived late, a half-day, overtime and a manual attendance correction. Resolve differences before the system becomes the authoritative payroll input.

Bangladesh workplace and market considerations

Bangladesh employers operate across offices, retail branches, education, healthcare, manufacturing and field services. Each needs a different balance of rules. A small office may need a simple leave calendar, one attendance device and basic reports. A garment or manufacturing site may need multiple shifts, break rules and roster coverage. A school or hospital may require department-specific schedules. An ISP may need to coordinate technicians who begin the day at customer sites. Product configuration and rollout should match the real workflow rather than forcing all sectors into one template.

The Bangladesh Labour Act and subsequent amendments contain requirements relating to worker registers, working-time notices, hours, rest intervals and leave. Applicability can depend on the type of establishment, employee status and current amendments. Employers should review their rules with a qualified HR or legal adviser. Attendance and leave software can support consistent records, but it does not itself guarantee legal compliance.

Connectivity also needs to be treated as an operating condition. Mobile apps can be useful for field or branch staff, but an internet subscription statistic does not guarantee continuous coverage at every site. Establish a fallback for device or network outages. Clarify whether the product supports offline attendance punching or only stores other data for later upload; those are different capabilities. For eHajira, location buffering during an internet interruption should not be described as offline attendance punching.

How eHajira supports the workflow

eHajira by Trimatrik IT Ltd brings together employee records, attendance, leave, shifts and payroll workflows for Bangladesh employers. Its documented capabilities include leave request and approval, leave balance and history, attendance exception review, shift and roster functions, reports and payroll summaries. The roster design covers draft, publish and lock controls, conflict checks and approval rules. Recent update notes also describe attendance recalculation after approved leave and reporting distinctions for late waivers, early leave and breaks.

The implementation should confirm which functions are enabled for the tenant, plan and release. Verify exact device model and firmware compatibility. Confirm the company’s leave categories, shift patterns, weekly rest, grace periods, overtime approval and payroll rules. For any mobile feature, demonstrate the actual workflow and explain requirements such as app access, phone permissions, connectivity and location availability. A guided demo should follow an employee from roster assignment and leave request through attendance review and the resulting payroll record.

A reliable rollout includes employee data cleanup, device mapping, manager training, a pilot roster, a parallel attendance and payroll run, and a documented route for corrections. Communicate the purpose of employee data collection, access roles and retention practices. When people know how to request leave, view a decision and report an attendance issue, adoption is more likely to support accurate records.

Implementation checklist

Before launch, document leave categories and approval routes; define shift and break rules; identify weekly rest and holiday calendars; verify device and mobile capture methods; test overnight shifts; confirm how approved leave changes daily attendance; test half-day, late-waiver, early-leave and overtime rules; assign permissions; run a payroll parallel check; and train employees and managers. Record unresolved issues with an owner and decision date.

Conclusion

Leave, shift and attendance management works best as one governed workflow. A published roster tells employees when they are expected; approved leave explains planned absence; attendance captures what happened; and reviewed exceptions create dependable payroll inputs. For Bangladesh employers, the right system is the one that reflects the organisation’s approved policy, handles real schedules and makes decisions traceable. eHajira can support this approach when its package, device compatibility and configured rules are confirmed for the customer’s specific operation.

Frequently asked questions

1. What is employee leave management software?

It records leave requests, approvals, balances and history according to an employer’s configured policy.

2. How does digital leave approval work?

An employee submits dates and a leave type; the request is routed to the designated manager or HR reviewer, who approves, rejects or requests more information.

3. Can approved leave update attendance automatically?

A system can update the day status after approval if that workflow is supported and configured. Test recalculation with existing attendance marks before payroll.

4. What happens if an employee is marked absent before leave is approved?

The employer should configure how later approval affects the day. eHajira’s recent update notes describe approved leave replacing a manually entered Absent status through recalculation; verify this on the deployed build.

5. Can leave software calculate employee balances?

It can calculate balances when eligibility, accrual, carry-forward, holidays and leave-counting rules are configured correctly.

6. How should a company handle half-day leave?

Define the permitted duration, approval route, attendance status and payroll treatment in the policy, then test those rules in the system.

7. What is a shift roster?

A roster assigns employees to specific work schedules on specific dates, including shift times, breaks and rest days.

8. Can one system manage day and night shifts?

Yes, if the system supports the required schedules and is configured to connect cross-midnight punches to the right shift and work date.

9. How should rotating shifts be planned?

Use a published roster with clear effective dates, conflict checks, employee communication and an approval route for changes.

10. What does Draft, Publish and Lock mean?

Draft is a work in progress; Publish makes the approved roster visible; Lock prevents routine edits after publication. Changes after locking should follow the company’s amendment process.

11. Why prevent overlapping shifts?

Overlaps can assign an employee to incompatible duties and create incorrect attendance or overtime calculations.

12. Should minimum rest between shifts be fixed in software?

It should follow the employer’s approved policy and applicable law. The system should not apply an unreviewed default.

13. How are overtime hours approved?

The organisation should specify who approves overtime and require approval before the hours are treated as payable, where that is the configured policy.

14. What is an attendance exception?

It is a record needing review, such as a missing punch, late arrival, early departure, break issue or device-sync problem.

15. How should attendance corrections be recorded?

Keep the original punch and log the requested correction, reason, approver and timestamp rather than silently replacing the source event.

16. Can biometric devices integrate with eHajira?

eHajira documents biometric attendance workflows, but exact support depends on the device model, firmware, connection method and tenant configuration. Confirm the specific setup.

17. Can mobile staff apply for leave and record attendance?

Mobile and employee self-service capabilities vary by release and package. Have the provider demonstrate the exact employee workflow before rollout.

18. Does offline GPS tracking mean offline attendance punching?

No. Storing location points during an internet interruption is a separate capability from capturing and later synchronising attendance punches.

19. How does attendance data affect payroll?

Approved daily statuses and overtime may feed salary calculations according to the employer’s configured policies. Review exceptions and test sample payrolls before closing a period.

20. Which reports are useful for HR managers?

Common views include pending leave, leave balances, daily attendance, late and early-leave records, breaks, overtime, shift rosters and payroll summaries, depending on the product configuration.

21. Does eHajira guarantee compliance with Bangladesh labour law?

No software should be treated as a legal-compliance guarantee. Employers should confirm applicable requirements with qualified advisers and configure their policies accordingly.

22. What should an employer test before launching eHajira?

Test leave approval, roster publication, overnight shifts, device syncing, attendance recalculation, corrections, half-days, late waivers, early departures and a payroll parallel run.

23. Can the same workflow support factories, schools and offices?

The core workflow can be adapted, but each organisation needs its own shifts, holidays, leave policy, approval roles and reports.

24. Where can a Bangladesh employer learn more about eHajira?

Visit www.ehajira.com or contact 0185-3330354 or 0185-3330353 to discuss the required workflow and confirm package and device details.