policy · Company
Attendance Policy
Attendance Policy
Purpose
Define Blinto's expectations for attendance, punctuality, late arrival, attendance communication, required-meeting attendance, and attendance records.
The normal workday itself is defined in Office Hours Policy. Work beyond normal hours is governed by Overtime Policy.
Attendance Expectations
Team members are expected to:
- attend work according to their applicable approved schedule;
- normally aim to be present by 8:30 AM for the shared morning routine;
- arrive within the applicable arrival window;
- be ready for required meetings and commitments on time;
- return from breaks within the applicable schedule;
- communicate foreseeable absence or significant delay as early as reasonably possible;
- attend required meetings and client commitments unless excused; and
- keep the responsible lead informed when attendance may affect delivery or team coverage.
Approved leave, remote-work arrangements, emergencies, and other authorized exceptions should not be treated as unexcused lateness or absence when properly handled through the applicable process.
Punctuality
Under the standard office schedule, the normal arrival window is 8:30–8:45 AM.
Arrival after 8:45 AM is tracked as late unless an approved exception applies.
Punctuality also includes being ready for scheduled meetings, returning from breaks on time, and respecting time-sensitive team or client commitments.
Automatic Late Allowance
Each team member may use the current automatic late allowance for up to 2 days per month, with each such late arrival limited to up to 1 hour.
This allowance exists for occasional unavoidable situations. It is not an alternative work schedule and should not be treated as an entitlement to routinely arrive late.
After the two automatic late-allowance days are used, additional late arrivals in the same calendar month follow the HRMS-managed escalation below.
Automated Monthly Late-Arrival Escalation
HRMS should automatically apply the following monthly attendance sequence for late arrivals that are not covered by an approved exception:
| Late arrival in the calendar month | HRMS treatment |
|---|---|
| Late #1 | Automatic late allowance |
| Late #2 | Automatic late allowance |
| Late #3 | Automatic reminder to the employee |
| Late #4 | Automatic coaching/escalation notification to the employee, Team/Department Lead, and People Operations |
| Late #5 | Automatic formal attendance warning, recorded in HRMS and visible to People Operations |
| Late #6 and onward | Automatic escalation for People Operations and manager review under Attendance-Specific Use |
The late-arrival count resets at the start of each calendar month.
HRMS should retain the historical attendance and warning record even after the monthly counter resets so repeated patterns across multiple months can be reviewed when necessary.
An approved leave, approved schedule exception, attendance-record correction, or other valid exception must be excluded from this automatic escalation.
Where a formal HRMS warning is generated automatically, People Operations may correct or withdraw it if the underlying attendance record is inaccurate or an approved exception was not recorded in time.
This automated attendance ladder applies specifically to punctuality after the monthly late allowance. It does not replace the flexible, case-based corrective-action framework used for performance, conduct, or other employee matters.
Absence & Delay Communication
When a team member knows they will be absent or materially delayed, they should inform the appropriate lead/People Operations as early as reasonably possible using the current approved communication/attendance process.
If an emergency prevents advance communication, the team member should communicate as soon as reasonably possible afterward.
Attendance Records
People Operations maintains or oversees the official attendance record/process.
Attendance records should distinguish, where applicable, between:
- normal attendance;
- approved leave;
- approved schedule exceptions;
- late arrival;
- early departure;
- absence; and
- other relevant attendance statuses.
Required-meeting attendance or punctuality may also be recorded when the company has an approved operational need to track it.
Overtime records are maintained under Overtime Policy rather than duplicated as ordinary attendance data.
Disputed attendance records should be raised with People Operations for review rather than informally altered.
Recurring Attendance Issues
Repeated lateness, absence, missed required meetings, early departure, or failure to communicate attendance issues should be treated as a pattern requiring review rather than handled indefinitely as isolated events.
The responsible lead and People Operations should:
- identify the underlying issue;
- communicate the expected standard;
- coach the team member toward improvement;
- document material or repeated concerns where required; and
- follow Attendance-Specific Use in the Corrective Action & Performance Improvement Policy if the pattern continues.
The purpose of attendance correction is improvement and reliability, not punishment.
For late arrival specifically, Blinto uses the automated monthly HRMS sequence defined above after the two automatic allowance days are exhausted. Other attendance issues—such as repeated absence, missed required meetings, or early departure—remain subject to the progressive, proportionate framework in Attendance-Specific Use.
Recognition
Blinto may recognize strong attendance and punctuality through the company's Rewards & Recognition program.
This policy does not define award names, eligibility criteria, prizes, or monthly winners. Those details are maintained in the canonical Rewards & Recognition section of the Blinto Benefits hub so recognition rules are not duplicated across policies.
Responsibilities
Team members are responsible for punctual attendance and timely communication.
Team/Department Leads are responsible for monitoring delivery/coverage impact, reinforcing punctual meeting behavior, and escalating recurring attendance issues consistently.
People Operations owns attendance administration, records, approved exceptions, and consistent application of this policy.
Leaders and managers are expected to model the same punctuality and preparation standards they ask of their teams.
Exceptions & Escalation
Escalate to People Operations when:
- a recurring schedule accommodation is needed;
- an attendance record is disputed;
- lateness/absence becomes recurring;
- an emergency or exceptional circumstance requires special handling;
- attendance treatment is unclear; or
- corrective treatment may need formal documentation.