LekhaHR

Attendance management system for India

Attendance software that shows the reason behind every day status.

Capture explicit punches, apply the policy that was effective that day, resolve exceptions and pass reviewed inputs forward—without background location tracking.

  • No base fee
  • Per active employee
  • GST extra
Product workflow previewFrom punch evidence to an explainable decision.

The same status explanation follows the employee, manager review and HR audit instead of becoming a mysterious present/absent label.

Real released UI screenshots remain required before public indexing.

Quick answer

What does an attendance management system do?

It records when people work, evaluates those records against shifts and attendance policies, helps employees correct mistakes, and gives managers and payroll teams reviewed—not guessed—attendance facts.

One traceable workflow

A punch should end in a reason, not just a status colour.

Every step keeps its source visible so a correction can change the outcome without rewriting history.

Explainable attendance workflowA punch is stored as evidence, evaluated by the effective policy, explained as a day status, and sent for review when correction is needed.1Punchtime + optional location2Policyeffective shift and rules3Becauseexplainable day status4Reviewcorrect only exceptions
Sensors add evidence; they do not silently erase a punch. Corrections remain reviewable and auditable.

Because, not just “half day”

Let employees see what the policy evaluated.

A day detail can show punch times, effective hours, grace window, policy version and the exact rule that produced the current status—then place the correction action beside it.

Illustrative verdictNeeds review
Punch evidence
Available
Effective shift
Applied
Policy reason
Visible
Next action
Fix or request exception
Structural example; not employee or customer data.

Product scope

The everyday attendance jobs, connected.

01

Web and mobile punch

Capture explicit check-in and check-out with optional punch-time location evidence.

02

Versioned shifts and calendars

Evaluate each day against the effective shift, weekly-off and holiday inputs.

03

Explainable day status

Show the punches, hours and policy reason behind present, late, half-day or exception states.

04

Regularization with context

Employees propose a correction with the original verdict attached for manager review.

05

Exception-first manager view

Focus attention on missing, queued or disputed records instead of reviewing every clean day.

06

Reviewed payroll inputs

Approved time and leave become traceable inputs; Attendance does not invent payroll amounts.

Resilient state

A weak network should create a visible state—not a vanished punch.

  1. QueuedThe operation remains on the device with the same identifier.
  2. SyncedThe server confirms the authoritative punch.
  3. Needs reviewA conflict stays visible instead of being silently double-counted.

Privacy boundary

Location evidence at the punch—not throughout the day.

A configured scheme may capture location at explicit check-in or check-out and evaluate the office geofence.

At a punch

Optional coordinate evidence, accuracy and geofence result.

Between punches

No background movement, routes, distance or continuous monitoring.

Transparent pricing

See what attendance management costs without a platform minimum.

Operations starts at ₹79 per active employee/month billed annually. Business starts at ₹119. GST extra.

Attendance FAQ

Questions buyers ask before replacing spreadsheets or devices.

What is an attendance management system?

It is software that records employee attendance, evaluates time against shifts and policies, handles corrections and provides reviewed attendance inputs for HR and payroll workflows.

Can employees punch from a mobile phone?

The planned LekhaHR workflow supports web and mobile punch. A configured capture scheme may request punch-time location or an optional selfie. Publication remains gated until the release evidence is approved.

Does LekhaHR track employees continuously?

No. Location evidence may be captured when someone explicitly checks in or out. LekhaHR does not build background movement, route or between-punch location history.

What happens if a punch cannot sync immediately?

The PWA keeps a stable operation identifier and shows queued, synced or needs-review state. It retries on resume or connectivity; closed-app background execution is not promised.

Can an employee correct a missed punch?

A regularization request can propose corrected times and a reason within the configured policy window. The manager sees the original day explanation with the request.

Does attendance automatically calculate salary?

No. Attendance produces reviewed time and day-status inputs. Payroll owns money calculation, review and any later adjustment.