Mobile clock-in
Record check-ins and check-outs on mobile, with capture requirements set by your attendance policy.
PLETOX / ATTENDANCE & SHIFTS
Bring attendance, shift schedules, and corrections into one view. Help employees see their records and give HR a clear path from daily punches to payroll-ready inputs.
YOUR TEAM, THROUGH THE DAY
| Employee | Shift | Check-in | Check-out | Status |
|---|---|---|---|---|
| ASAsha ShahOperations | General | 09:02 AM | 06:03 PM | Present |
| RPRohan PatelSales | Evening | 02:00 PM | Missing | Needs review |
| MRMeera RaoDesign | General | - | - | On leave |
| RDRiya DesaiCustomer success | General | 08:58 AM | 06:01 PM | Present |
| Employee | Mon 21 | Tue 22 | Wed 23 | Thu 24 | Fri 25 | Sat 26 | Sun 27 |
|---|---|---|---|---|---|---|---|
| Asha Shah | General | General | General | General | General | General | Off |
| Rohan Patel | Evening | Evening | Evening | Evening | Evening | Evening | Off |
| Meera Rao | General | General | General | General | General | General | Off |
| Riya Desai | General | General | General | General | General | General | Off |
General: 09:00 AM - 06:00 PM Evening: 02:00 PM - 10:00 PM
A CONNECTED VIEW OF THE WORKDAY
Keep the schedule, the attendance record, and the review together, without rebuilding the picture at month-end.
Record check-ins and check-outs on mobile, with capture requirements set by your attendance policy.
Connect supported device punches to employee records with device mapping and sync visibility.
Use configured site locations and attendance boundaries for location-aware mobile punches.
Plan date-wise employee shifts and bring monthly assignments in through roster imports.
Match punches to the nearest eligible shift when no roster assignment already exists.
Set working times and assign shifts to the people and teams who follow them.
Account for non-working days and configured weekly-off patterns when reviewing attendance.
Let employees request a new entry or correction with the details reviewers need.
Resolve pending items and confirm attendance records before they are used in payroll.
THE CONTEXT BEHIND EVERY PUNCH
See when someone checked in, which shift they followed, and whether the record needs attention before drawing conclusions.
Bring web, mobile, or supported device records into the attendance workflow configured for your team.
Review punches with the assigned shift, leave, and working-day rules instead of isolated times.
Identify missing punches and disputed entries so the right person can review them.
Capture methods depend on your setup. Device connections, location permissions, and connectivity are confirmed before rollout.
Punch span is not payable time. Breaks, eligibility, and attendance rules determine the reviewed result.
WORKING PATTERNS WITH STRUCTURE
Give every attendance record a schedule to work against. Keep shift times, assignments, and weekly offs connected.
Set shift start and end times so attendance is reviewed against the expected day.
Keep employee assignments visible across departments and locations as team schedules change.
Use regular weekly offs or week-number patterns to reflect how your organization works.
Shift times and weekly-off patterns follow your configuration. Confirm overnight shifts and other special policies during setup.
Sunday off / Every week
MOBILE CLOCK-IN & GEOFENCING
Let employees record their working day from their phone, with location and capture requirements shaped around your attendance policy.
Give employees a convenient way to record attendance through the Pletox app.
Configure the location and radius used for geofenced attendance at your office or site.
Enable location or selfie capture where your policy requires it, with appropriate device permissions.
Geofenced attendance is not continuous location tracking. GPS accuracy, permissions, connectivity, and employee-specific settings affect location checks.
BIOMETRIC INTEGRATION
Bring supported biometric punch logs into Pletox so device attendance joins the same employee and shift workflow.
Confirm the integration method and device access before enabling attendance synchronization.
Link device identifiers to the correct people so incoming punches have a clear owner.
Check device, employee, punch time, and synchronization status when investigating a missing record.
Compatibility and sync frequency depend on the device and integration. A connected device does not guarantee instant or uninterrupted delivery.
Resolve unmatched device users before treating their punches as employee attendance.
ROSTER PLANNING
Keep date-wise shift assignments together so teams know which working pattern applies to each employee.
Plan employee shifts across the roster instead of relying on a single default schedule.
Use the shift roster template to import monthly assignments and validate the uploaded data.
Give punches an assigned shift to follow and make schedule changes visible in the roster.
Roster assignments take precedence over automatic shift mapping for future punches. Review changes before recalculating historical attendance.
| Employee | M | T | W | T | F | S | S |
|---|---|---|---|---|---|---|---|
| Asha Shah | G | G | G | G | G | G | Off |
| Rohan Patel | E | E | E | G | G | G | Off |
| Riya Desai | G | G | G | E | E | E | Off |
| Neha Patil | G | G | G | G | G | G | Off |
G / General: 09:00 AM - 06:00 PM
E / Evening: 02:00 PM - 10:00 PM
AUTOMATIC SHIFT MAPPING
When no roster assignment exists, map an employee's punch to the nearest eligible shift start under their active policy.
Define which shifts the policy can consider and which employees it covers.
Compare the punch time with eligible shift starts when the employee has no existing roster assignment.
Future punches preserve existing roster assignments. Historical remapping is a separate, deliberate review.
Policies have effective periods. Historical remaps include safeguards for locked, open, specialized roster, and overnight-review records.
Automatic mapping uses the nearest eligible start, not a guarantee of attendance approval or payable overtime.
A MISSED PUNCH NEEDS A REVIEW
Handle missing or incorrect punches through a clear request flow, with proposed times and a reason attached to the record.
The employee selects the attendance date and shares the requested times and explanation.
The responsible reviewer checks the original record and proposed correction before deciding.
Approved changes feed the attendance record under your configured rules and period controls.
Submitting a request does not approve it. Review permissions and closed attendance periods still apply.
I missed my check-out after finishing the evening shift. Please review the requested end time.
FROM DAILY RECORDS TO PAYROLL INPUTS
Bring attendance, approved leave, and reviewed exceptions together before they affect the pay run.
Check working days, leave, and non-working days against the attendance period your team uses.
Review corrections and overtime eligibility instead of treating unverified records as final inputs.
Use attendance period locks and authorized review to protect the records used for payroll.
Attendance review is separate from payroll approval. Pay calculations follow your salary rules and approved inputs.
Calendar-day totals illustrate attendance categories, not payable-day calculations.
PART OF THE SAME WORKDAY
Keep working-day records connected to the people, requests, and payroll workflows around them.
BEFORE YOUR NEXT SHIFT
Understand the records, rules, and reviews behind a connected working day.
Book a demoAttendance can use the web, mobile, or supported device sources enabled for your organization. We confirm capture methods, permissions, connectivity, and any location requirements during setup.
Yes. Define shifts and assign employees to the relevant working pattern. Weekly offs can follow a regular schedule or configured week-number patterns. Special requirements, including overnight shifts, should be validated during setup.
Compatibility depends on device access, supported APIs, or export formats. Employee mapping, duplicate checks, and synchronization expectations are confirmed before enabling a connection.
Employees can submit a new-entry or correction request with the attendance date, proposed times, and reason. The authorized reviewer checks the request before approval. A missing punch should be reviewed rather than treated as an automatic pay deduction.
Leave and eligible overtime are reviewed alongside attendance and shift rules. Entitlements, eligibility, approval responsibilities, and payroll treatment depend on your configured policies; extra time does not automatically become payable overtime.
Yes. Configure the attendance location and radius for employees covered by the policy. Location checks depend on device permissions, GPS accuracy, connectivity, and any configured exceptions. A clock-in location check is separate from continuous location tracking.
For employees covered by an active policy, an incoming punch is mapped to the nearest eligible shift start when no roster assignment exists. Existing roster assignments are preserved for future punches. Historical remapping is a separate reviewed action with safeguards for protected records.
Yes. Maintain date-wise employee shift assignments and use the monthly shift roster template for imports. Review validation results and confirm assignments before use. Existing roster assignments take precedence over automatic mapping for future punches.
HR reviews the attendance period, resolves exceptions, and confirms the inputs used for payroll. Period locks help control later changes. Payroll calculations and final approval remain separate and follow your salary rules.