PLETOX / ATTENDANCE & SHIFTS

Every shift.
A clearer working day.

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.

PletoxAcme Industries Attendance workspace

YOUR TEAM, THROUGH THE DAY

A clear view. Before the follow-ups.

22 Sep / Sample day
Sample team
4
Present
2
On leave
1
Needs review
1
EmployeeShiftCheck-inCheck-outStatus
ASAsha ShahOperationsGeneral09:02 AM06:03 PMPresent
RPRohan PatelSalesEvening02:00 PMMissingNeeds review
MRMeera RaoDesignGeneral--On leave
RDRiya DesaiCustomer successGeneral08:58 AM06:01 PMPresent
Weekly shift overview21 - 27 September / Sample assignments
EmployeeMon 21Tue 22Wed 23Thu 24Fri 25Sat 26Sun 27
Asha ShahGeneralGeneralGeneralGeneralGeneralGeneralOff
Rohan PatelEveningEveningEveningEveningEveningEveningOff
Meera RaoGeneralGeneralGeneralGeneralGeneralGeneralOff
Riya DesaiGeneralGeneralGeneralGeneralGeneralGeneralOff

General: 09:00 AM - 06:00 PM Evening: 02:00 PM - 10:00 PM

Review exceptions before payrollIllustrative preview / Sample data

A CONNECTED VIEW OF THE WORKDAY

Know who is working.
See what needs attention.

Keep the schedule, the attendance record, and the review together, without rebuilding the picture at month-end.

Mobile clock-in

Record check-ins and check-outs on mobile, with capture requirements set by your attendance policy.

Biometric integration

Connect supported device punches to employee records with device mapping and sync visibility.

Geofenced attendance

Use configured site locations and attendance boundaries for location-aware mobile punches.

Roster planning

Plan date-wise employee shifts and bring monthly assignments in through roster imports.

Auto shift mapper

Match punches to the nearest eligible shift when no roster assignment already exists.

Shift assignments

Set working times and assign shifts to the people and teams who follow them.

Weekly offs & holidays

Account for non-working days and configured weekly-off patterns when reviewing attendance.

Attendance corrections

Let employees request a new entry or correction with the details reviewers need.

Payroll inputs

Resolve pending items and confirm attendance records before they are used in payroll.

THE CONTEXT BEHIND EVERY PUNCH

More than a timestamp.
A working-day record.

See when someone checked in, which shift they followed, and whether the record needs attention before drawing conclusions.

  • Capture from your enabled sources

    Bring web, mobile, or supported device records into the attendance workflow configured for your team.

  • Read attendance in context

    Review punches with the assigned shift, leave, and working-day rules instead of isolated times.

  • Keep exceptions visible

    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.

Asha Shah / Daily attendanceIllustrative preview / Sample data
AS
Tuesday, 22 SeptemberGeneral shift / Nashik office
Present
Check-in09:02 AM
Check-out06:03 PM
  1. 09:00 AM / Shift beginsGeneral shift assigned to Asha
  2. 09:02 AM / Check-in recordedMobile attendance / Source recorded
  3. 06:03 PM / Check-out recordedBoth punches available for review
Scheduled time
09:00 AM - 06:00 PM
Elapsed punch span
9h 01m

Punch span is not payable time. Breaks, eligibility, and attendance rules determine the reviewed result.

WORKING PATTERNS WITH STRUCTURE

Different teams.
The right shift rules.

Give every attendance record a schedule to work against. Keep shift times, assignments, and weekly offs connected.

  • Define the working window

    Set shift start and end times so attendance is reviewed against the expected day.

  • Assign people to their shift

    Keep employee assignments visible across departments and locations as team schedules change.

  • Make weekly offs explicit

    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.

General shift / Working patternIllustrative preview / Sample data
General shiftOperations / Nashik
Assigned
Starts at09:00 AM
Ends at06:00 PM

Weekly working pattern

MonWork
TueWork
WedWork
ThuWork
FriWork
SatWork
SunOff

Sunday off / Every week

People on this shift

ASAsha ShahOperations manager
NPNeha PatilOperations executive
RDRiya DesaiCustomer success

MOBILE CLOCK-IN & GEOFENCING

A simpler check-in.
With the right location context.

Let employees record their working day from their phone, with location and capture requirements shaped around your attendance policy.

  • Clock in and out on mobile

    Give employees a convenient way to record attendance through the Pletox app.

  • Define the attendance boundary

    Configure the location and radius used for geofenced attendance at your office or site.

  • Capture the context you need

    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.

Mobile attendance / Location checkIllustrative preview / Sample data
AS
Good morning, AshaGeneral shift / 09:00 AM - 06:00 PM
Clock-in recorded09:02 AM
SourceMobile app
Nashik officeWithin configured attendance boundary
Inside
Attendance radius
150 metres
Recorded distance
42 metres from site
Location permission
Granted
Capture method
Mobile + location
  • Location check completedAttendance boundary checked for this punch
  • Check-in savedAvailable in the daily attendance record

BIOMETRIC INTEGRATION

Keep the device.
Connect the attendance record.

Bring supported biometric punch logs into Pletox so device attendance joins the same employee and shift workflow.

  • Connect supported devices

    Confirm the integration method and device access before enabling attendance synchronization.

  • Map device IDs to employees

    Link device identifiers to the correct people so incoming punches have a clear owner.

  • Review incoming logs

    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.

Biometric logs / Nashik entranceIllustrative preview / Sample data
Office entrance deviceDevice ID / NSK-01
Connected
Sample punches3 received
Employee mapping2 matched
  • Asha ShahDevice user 014 / 09:02 AM
    Matched
  • Riya DesaiDevice user 028 / 08:58 AM
    Matched
  • Employee not linkedDevice user 091 / 09:07 AM
    Needs mapping

Resolve unmatched device users before treating their punches as employee attendance.

ROSTER PLANNING

Plan the week.
Make each assignment clear.

Keep date-wise shift assignments together so teams know which working pattern applies to each employee.

  • Assign shifts by date

    Plan employee shifts across the roster instead of relying on a single default schedule.

  • Bring in a prepared roster

    Use the shift roster template to import monthly assignments and validate the uploaded data.

  • Keep plans connected to attendance

    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.

Team roster / 21 - 27 SeptemberIllustrative preview / Sample data
Operations teamGeneral and evening shifts
EmployeeMTWTFSS
Asha ShahGGGGGGOff
Rohan PatelEEEGGGOff
Riya DesaiGGGEEEOff
Neha PatilGGGGGGOff

G / General: 09:00 AM - 06:00 PM
E / Evening: 02:00 PM - 10:00 PM

Monthly roster importTemplate-based assignments / Review before use

AUTOMATIC SHIFT MAPPING

A punch comes in.
The policy finds the shift.

When no roster assignment exists, map an employee's punch to the nearest eligible shift start under their active policy.

  1. 01

    Choose eligible shifts

    Define which shifts the policy can consider and which employees it covers.

  2. 02

    Match the incoming punch

    Compare the punch time with eligible shift starts when the employee has no existing roster assignment.

  3. 03

    Keep planned assignments intact

    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.

Auto shift mapper / Policy matchIllustrative preview / Sample data
RP
Rohan PatelActive policy / Operations shifts
Eligible
Incoming punch01:57 PM
Existing rosterNone
  • General / 09:00 AM4h 57m from punch time
  • Evening / 02:00 PM3m from punch time
    Nearest
Mapped to evening shift02:00 PM - 10:00 PM / Eligible policy shift

Automatic mapping uses the nearest eligible start, not a guarantee of attendance approval or payable overtime.

A MISSED PUNCH NEEDS A REVIEW

Let people explain.
Give reviewers the context.

Handle missing or incorrect punches through a clear request flow, with proposed times and a reason attached to the record.

  1. 01

    Submit the correction

    The employee selects the attendance date and shares the requested times and explanation.

  2. 02

    Review the request

    The responsible reviewer checks the original record and proposed correction before deciding.

  3. 03

    Use the reviewed outcome

    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.

Attendance correction / Request reviewIllustrative preview / Sample data
RP
Rohan Patel22 Sep / Evening shift
Pending
Employee's reason

I missed my check-out after finishing the evening shift. Please review the requested end time.

Original record02:00 PM - MissingCheck-out not recorded
Requested correction02:00 PM - 10:00 PMAwaiting approval
  1. Request submittedProposed time and reason received
  2. Manager reviewOriginal record and request checked together
  3. Attendance updateOnly after the required approval

FROM DAILY RECORDS TO PAYROLL INPUTS

Close the gaps.
Then close the period.

Bring attendance, approved leave, and reviewed exceptions together before they affect the pay run.

  • Review the full period

    Check working days, leave, and non-working days against the attendance period your team uses.

  • Resolve outstanding items

    Review corrections and overtime eligibility instead of treating unverified records as final inputs.

  • Control changes after review

    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.

Asha Shah / Attendance period reviewIllustrative preview / Sample data
AS
01 - 30 September30 calendar days / General shift
In review
Present
24 days
Approved leave
2 days
Weekly offs
4 days
  • Attendance records checkedDaily records reconciled for the period
  • Leave and corrections reviewedApproved outcomes included
  • Final HR reviewConfirm readiness before locking the period
  • Payroll handoffReviewed inputs, not an automatic pay decision

Calendar-day totals illustrate attendance categories, not payable-day calculations.

BEFORE YOUR NEXT SHIFT

Your attendance questions,
answered.

Understand the records, rules, and reviews behind a connected working day.

Book a demo

Attendance 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.

Book a demo