isolvedHCM Attendance Points, Missed Punches, and Occurrence Help

An employee opens isolvedHCM and notices an attendance exception for arriving seven minutes late.

Another worker receives two attendance points for an absence that had already been approved as paid sick leave. Someone else clocked in correctly, but a failed network connection left the timecard showing a missing punch.

A manager later refers to the employee’s “occurrence count,” although the employee cannot find any explanation of how the total was calculated.

These situations can involve several separate records:

• Published schedule.
• Clock punches.
• Timecard.
• Attendance exception.
• Absence code.
• Paid-time-off request.
• Manager approval.
• Attendance occurrence.
• Disciplinary point.
• Written warning.
• Payroll calculation.

isolved’s current workforce-management materials describe Time and Labor Management as supporting timecard collection, absence management, scheduling, attendance tracking, labor allocation, and payroll-ready time data. Employers configure the policies, permissions, exception rules, and corrective processes used by their workforce.

This is an independent informational guide. It is not operated by isolved or an employer. It cannot remove attendance points, approve an absence, change a timecard, reverse discipline, or access private employee records.

What is isolvedHCM attendance tracking?

The keyword isolvedhcm generally refers to isolved People Cloud, an employer-configured human capital management platform.

Depending on the employer’s setup, People Cloud or a connected workforce system may be used to:

• Record clock-in and clock-out times.
• Collect timesheets.
• Display work schedules.
• Identify missing punches.
• Track late arrivals.
• Record early departures.
• Manage absences.
• Review time-off requests.
• Route timecards for approval.
• Send payroll-ready hours.
• Produce attendance reports.

Official isolved materials describe Workforce Management as covering time and attendance, scheduling, leave management, and labor forecasting. Its time-clock products can support physical clocks, mobile punches, web punches, badges, PINs, and biometric methods.

Not every employer uses the same clock, attendance policy, or employee interface.

Time record versus attendance record

These records are related but not identical.

Time record

Shows the employee’s work-related entries, such as:

• Clock-in.
• Meal start.
• Meal end.
• Clock-out.
• Paid leave.
• Unpaid leave.
• Job transfer.
• Total hours.

Attendance record

Can categorize events such as:

• Late arrival.
• Early departure.
• Absence.
• Missed punch.
• Unscheduled leave.
• No-call/no-show.
• Approved exception.
• Policy occurrence.

Disciplinary record

Can include:

• Coaching.
• Verbal warning.
• Written warning.
• Attendance points.
• Final warning.
• Other employer action.

A missing punch can create an attendance exception without proving that the employee was absent.

Likewise, an employee can be paid correctly after a timecard correction but still need an inaccurate attendance occurrence removed separately.

What are attendance points?

Some employers use a point-based attendance policy.

A policy might assign points for events such as:

• Late arrival.
• Early departure.
• Unscheduled absence.
• Failure to report an absence correctly.
• Missed shift.
• No-call/no-show.
• Repeated missed punches.

Example policy:

Late by less than 15 minutes: 0.5 point
Late by 15 minutes or more: 1 point
Unscheduled absence: 1 point
No-call/no-show: 3 points

This is only an example.

isolved does not establish one universal point schedule for all employers. The employer defines:

• Which events receive points.
• How many points apply.
• Whether approved leave is excluded.
• Whether points expire.
• Whether consecutive absences count separately.
• Which thresholds trigger discipline.
• Who can remove or adjust an occurrence.

Ask HR for the current written attendance policy rather than relying on a coworker’s explanation.

Attendance exception does not always mean discipline

A system exception can simply identify a record that needs review.

Examples include:

• Missing punch.
• Punch outside the scheduled window.
• Early clock-in.
• Late clock-out.
• Long meal.
• Short meal.
• Unscheduled work.
• Overtime.
• Clock at another location.

The employer can review the exception and determine that:

• No violation occurred.
• Manager authorization existed.
• Schedule was wrong.
• Clock malfunctioned.
• Leave was protected or approved.
• Timecard correction is required.
• Attendance point should not be assessed.

Do not treat every red icon or warning symbol as a final disciplinary decision.

Schedule versus actual hours

The published schedule shows when the employee was expected to work.

The time record should reflect the time actually worked.

The U.S. Department of Labor states that when an employee works longer or shorter than the scheduled period, the employer must record the actual hours worked. Employers may choose their timekeeping method, but records must be complete and accurate.

Example:

Scheduled shift: 8:00 a.m.–4:30 p.m.
Actual authorized work: 7:50 a.m.–4:45 p.m.

The timecard should not be reduced automatically to the scheduled hours merely to eliminate an attendance exception.

Attendance policy and wage payment are separate questions.

How to review an attendance issue

A practical review should compare:

1. Published schedule.
2. Schedule-change notifications.
3. Raw clock punches.
4. Timecard calculations.
5. Leave request.
6. Manager approval.
7. Attendance exception.
8. Occurrence or point entry.
9. Final pay stub.
10. Written attendance policy.

Identify whether the problem is primarily:

• A missing time entry.
• An incorrect schedule.
• A leave-coding error.
• A point-calculation dispute.
• A payroll error.
• A notification problem.
• A disciplinary dispute.

Using the correct category helps the employer route the issue to the right person.

Missed punch

A missed punch occurs when a required time entry is absent.

Examples include:

• Employee forgot to clock in.
• Employee forgot to clock out.
• Meal punch is missing.
• Clock rejected the punch.
• Mobile application lost connection.
• Badge was not recognized.
• Supervisor asked the employee to begin work immediately.
• Employee used the wrong clock location.
• System failed to save the entry.

Official isolved payroll materials say its payroll-preview tools can flag missing punches before a payroll run is approved.

A flagged punch should be corrected using accurate information—not guessed or changed merely to avoid an attendance consequence.

How to report a missed punch

Provide:

• Date.
• Scheduled shift.
• Actual start time.
• Actual end time.
• Meal period.
• Work location.
• Job or department.
• Reason the punch is missing.
• Supervisor who can verify the time.

Example:

“My isolved timecard for August 4 is missing my 5:12 p.m. clock-out. I worked from 8:03 a.m. to 5:12 p.m. with a meal from 12:18 p.m. to 12:48 p.m. Please correct the timecard before payroll closes.”

Do not enter a standard scheduled time when the actual time was different.

Missed punch request remains pending

Possible reasons include:

• Manager has not reviewed it.
• Request went to the wrong approver.
• Payroll period is locked.
• Required note is missing.
• Employee submitted the wrong date.
• Manager needs supporting information.
• Another timekeeping system controls the record.
• Correction was saved but not submitted.

Check whether the status says:

• Draft.
• Submitted.
• Pending.
• Approved.
• Rejected.
• Returned.
• Processed.

Notify the manager before the payroll cutoff.

Clock malfunction

When a physical or mobile clock fails:

1. Notify the supervisor immediately.
2. Record the actual time independently.
3. Save the displayed error when possible.
4. Follow the employer’s manual procedure.
5. Review the corrected timecard.
6. Confirm payroll includes the hours.
7. Confirm no incorrect attendance point remains.

Official isolved time-clock materials state that its systems can provide notifications involving missed punches and late arrivals and can export approved timecards to payroll.

A technology failure should be documented so it is not mistaken for employee misconduct.

Mobile punch failed

Possible causes include:

• Poor connection.
• Application session expired.
• Location permission disabled.
• Geofence mismatch.
• Device time incorrect.
• Employer profile changed.
• Application outdated.
• Punch remained queued.
• Wrong job selected.

Take a screenshot of the error without displaying sensitive payroll information.

Tell the manager:

• Time of attempted punch.
• Location.
• Error message.
• Time work actually began or ended.

Do not repeatedly tap the punch button if it may create duplicate entries.

Duplicate punches

Duplicate entries can occur when:

• Employee taps twice.
• Clock responds slowly.
• Mobile punch is retried.
• Physical and mobile clocks are both used.
• Manager enters a manual punch after the original synchronizes.

The timecard may show:

• Two clock-ins.
• Two clock-outs.
• Zero-length shift.
• Overlapping segments.
• Excessive hours.

Request correction.

Do not approve an obviously duplicated timecard merely because the weekly total looks acceptable.

Late arrival

An employee can be marked late when the recorded arrival is after the scheduled start.

Before accepting the occurrence, verify:

• Correct scheduled start.
• Schedule-change notice.
• Raw punch time.
• Employer grace period.
• Approved adjusted schedule.
• Manager authorization.
• Clock malfunction.
• Work performed before the punch.
• Applicable accommodation or protected leave.

A system can calculate the difference between schedule and punch, but the employer determines how the policy applies.

Grace periods

An employer may define a grace period, such as:

• No attendance point until five minutes late.
• Point assessed after seven minutes.
• Separate rule for payroll rounding.
• No grace period.
• Manager discretion.

A grace period for attendance is not necessarily the same as a payroll-rounding rule.

Example:

Employee clocks in at 8:04 a.m.
Attendance policy: no occurrence within five minutes
Timekeeping rule: actual or rounded time recorded according to lawful policy

The employee might avoid a disciplinary point while still having the timecard reflect the applicable timekeeping calculation.

Rounding and attendance points

Time-clock rounding and attendance discipline should not be confused.

Federal guidance recognizes that time records may sometimes be rounded to common increments when the practice is neutral over time, but the employer must still keep accurate records of compensable work.

An employer might:

• Round payroll time to the nearest increment.
• Assess attendance based on the raw punch.
• Use the scheduled start for policy purposes.
• Apply a grace period.

Ask which record controls the occurrence.

Do not assume a rounded pay entry proves the employee arrived exactly at the rounded time.

Early arrival

An employee can receive an exception for clocking in too early.

Possible reasons include:

• Overtime control.
• Schedule lockout.
• Unapproved preparation.
• Wrong shift.
• Employee arrived for another location.
• Manager requested an early start.
• Clock window is configured incorrectly.

When the manager required early work, the employee should ensure the time is recorded.

A policy violation for unauthorized early work does not generally permit the employer to erase compensable time that was actually worked.

Early departure

An early-departure occurrence may result from:

• Employee left before scheduled end.
• Manager released the employee.
• Business closed early.
• Approved appointment.
• Illness.
• Schedule was changed.
• Clock malfunction.
• Shift coverage occurred.
• Employee forgot to clock back in after a meal.

Ask whether the departure was:

• Authorized.
• Paid.
• Unpaid.
• Covered by PTO.
• Protected by applicable leave.
• Coded correctly.

An authorized early release should not automatically be recorded as an unapproved attendance event.

Unscheduled absence

An unscheduled absence generally means the employee did not work an assigned shift and did not have the absence approved in advance.

Possible circumstances include:

• Sudden illness.
• Family emergency.
• Transportation failure.
• Weather.
• Childcare issue.
• Workplace injury.
• Protected sick leave.
• Approved intermittent leave.
• Shift removed without synchronization.

The attendance result depends on:

• Employer policy.
• Notice procedure.
• Available leave.
• Applicable state or local law.
• Protected-leave status.
• Manager documentation.

Do not assume every unscheduled absence lawfully receives the same number of points.

No-call/no-show

A no-call/no-show generally means the employee did not report to work and did not follow the employer’s required callout procedure.

Before accepting that classification, verify:

• Schedule was published.
• Employee received the schedule.
• Correct contact procedure was available.
• Employee attempted to call or message.
• Manager acknowledged the notice.
• Emergency prevented communication.
• Shift had been swapped.
• Approved leave existed.
• Wrong telephone number was listed.
• Technical outage affected the callout system.

Preserve:

• Call log.
• Text message.
• Voicemail.
• Email.
• App submission.
• Manager response.
• Schedule screenshot.

Callout procedure

An employer can require employees to report absences through a specific process.

Examples include:

• Telephone line.
• Manager call.
• Scheduling application.
• Leave administrator.
• Attendance hotline.
• HR email.
• Callout form.

Telling a coworker may not satisfy the policy.

Likewise, submitting PTO may not replace the required callout for an unexpected same-day absence.

Ask HR for the written procedure, including:

• Who must be contacted.
• How early notice must be given.
• Whether text messages are accepted.
• What information is required.
• Whether daily calls are required for multi-day absences.

Manager says no call was received

Provide objective evidence.

Example:

“I called the attendance line at 6:14 a.m. for my 8:00 a.m. shift and left a 42-second voicemail. My phone log and voicemail confirmation are attached. Please remove the no-call/no-show classification and apply the correct absence code.”

Do not edit call logs or fabricate a message.

Approved PTO coded as an occurrence

This can happen when:

• Time-off approval did not synchronize.
• Manager approved the request after the attendance record was generated.
• Wrong leave category was selected.
• Schedule was not updated.
• Employee did not follow a separate callout procedure.
• PTO covered pay but not attendance under the employer policy.
• Approval was later canceled.
• Wrong employee profile was used.

Review both:

• Leave approval.
• Attendance policy.

A paid leave balance does not always guarantee that an absence is protected from every attendance consequence. However, an employer should apply its written policy accurately and consistently.

Sick leave and attendance points

State or local paid-sick-leave laws can restrict employers from assessing attendance penalties for protected use of qualifying sick leave.

Rules differ by jurisdiction.

When an employee believes protected sick leave was counted improperly, preserve:

• Work location.
• Sick-leave balance.
• Request.
• Callout record.
• Approval.
• Occurrence notice.
• Employer policy.

Contact HR and, where necessary, the appropriate state or local labor agency.

Do not assume the isolved attendance code itself determines whether the absence was legally protected.

FMLA-related occurrence

Approved Family and Medical Leave Act leave should not be treated as an ordinary unexcused absence when the employee and employer have completed the applicable process.

Potential problems include:

• Intermittent leave not coded.
• Leave administrator has not transmitted approval.
• Certification pending.
• Employee failed to follow ordinary callout rules where required.
• Manager cannot see the leave status.
• Incorrect employee profile.
• Absence date outside the approved parameters.

Contact:

• HR.
• Leave administrator.
• Attendance manager.

Avoid sending medical details to coworkers or public support sites.

Disability accommodation and attendance

An employee can have an approved adjustment involving:

• Start time.
• Additional breaks.
• Intermittent absence.
• Modified schedule.
• Remote work.
• Medical appointments.

The attendance system may still flag the event automatically.

A system-generated exception should be reviewed against the approved accommodation.

The employee should not be required to place detailed medical information in an ordinary timecard note.

Contact HR or the designated accommodations team.

Bereavement, jury duty, and military leave

These absence types can require specific documentation or codes.

Examples include:

• Bereavement leave.
• Jury service.
• Witness duty.
• Military leave.
• Voting leave where applicable.
• School-related leave.
• Other statutory leave.

An ordinary “unpaid absence” code might create an attendance point even though another category should apply.

Ask HR which leave code and documentation are required.

Consecutive-day absences

Policies differ on whether consecutive days count as:

• One occurrence.
• One point per day.
• Increasing points.
• Separate event after return to work.
• Medical-leave event.
• No occurrence when protected.

Example:

Employee is absent Monday through Wednesday because of the same illness.

Possible policies:

• One occurrence for the continuous event.
• Three separate absence points.
• No points when qualifying sick leave applies.

Only the employer’s current policy and applicable law can answer the question.

Attendance points expiration

Some policies remove or reduce points after:

• 90 days.
• Six months.
• Twelve months.
• Rolling period without another occurrence.
• Calendar-year reset.
• Anniversary date.
• Successful attendance period.

Ask whether the policy uses:

• Rolling 12 months.
• Fixed calendar year.
• Date of each occurrence.
• Disciplinary step date.
• Last incident date.

Example:

Occurrence date: October 10, 2025
Rolling 12-month expiration: October 10, 2026

A January 1 reset would produce a different result.

Point total appears wrong

Request an itemized attendance history containing:

• Event date.
• Scheduled shift.
• Event type.
• Points assigned.
• Policy provision.
• Approval status.
• Expiration date.
• Correction history.
• Current total.

A useful request is:

“My attendance summary shows 5.5 points, but the individual events visible to me total 3.5. Please provide the complete occurrence history, including expired, pending, reversed, and manager-entered events.”

Do not rely only on the dashboard total.

Points remained after correction

Correcting the timecard may not automatically remove the associated attendance occurrence.

Example:

1. Missing clock-out creates an exception.
2. Manager corrects the timecard.
3. Payroll pays the proper hours.
4. Attendance point remains.

Ask separately for:

• Timecard correction.
• Attendance-record correction.
• Disciplinary-record correction.

Different administrators may control each record.

Occurrence appears twice

Duplicate points can result from:

• Missing punch and late arrival recorded for the same event.
• Absence imported twice.
• Schedule changed after occurrence creation.
• Manager entered a manual point in addition to an automatic exception.
• Duplicate employee profile.
• Leave request processed after attendance.
• Payroll period reopened.

Ask whether the policy allows multiple points for the same incident.

Request removal of any duplicate created in error.

Attendance warning based on incorrect total

Do not ignore the warning.

Respond in writing with:

• Warning date.
• Point total shown.
• Events disputed.
• Evidence.
• Correct total requested.
• Policy language.
• Request to attach the response to the record.

Example:

“I acknowledge receipt of the attendance warning but dispute the stated six-point total. The August 1 absence was approved sick leave, and the July 22 missed punch was corrected as a clock failure. Please review those events and revise the warning if the total changes.”

Acknowledgment of receipt does not always mean agreement, but read the employer’s exact language.

Written warning does not disappear automatically

Even when an occurrence is corrected, the employer may need to update:

• Attendance report.
• Written warning.
• Performance record.
• Manager notes.
• Payroll exception.
• Termination recommendation.

Ask HR to confirm each affected record.

Do not assume deleting the dashboard point removes every disciplinary reference.

Attendance point added after payroll closes

Attendance administration and payroll can operate on different timelines.

An occurrence can be reviewed days after the paycheck is finalized.

Likewise:

• Employee can be paid correctly.
• Attendance point can still be assessed.
• Employee can dispute the point separately.

Payroll accuracy does not prove disciplinary accuracy.

Missing hours and attendance discipline

An employee should not choose between:

• Being paid correctly.
• Avoiding an attendance point.

When work was performed, the employer’s records should reflect the actual hours.

The Department of Labor requires covered employers to maintain accurate records of hours worked and wages earned. Required records include daily and weekly hours, regular and overtime earnings, deductions, total wages, pay date, and pay period.

A manager should not change actual work time solely to make the employee appear punctual.

Manager edits a punch

A manager may need to correct:

• Missing punch.
• Wrong job.
• Duplicate punch.
• Incorrect meal.
• Clock malfunction.
• Approved schedule change.

Ask whether the timecard displays:

• Original punch.
• Edited punch.
• Edit reason.
• Approver.
• Audit history.

When the edit is wrong, report it before approving the timecard.

Example:

“My original clock-out was 6:18 p.m., but the timecard was edited to 6:00 p.m. I continued performing assigned closing duties until 6:18. Please restore the actual time and preserve the edit history.”

Employee timecard approval

Some employers ask employees to review or approve their own timecards.

Before approving:

• Check every workday.
• Review raw punches.
• Check meals.
• Verify PTO.
• Review overtime.
• Review job transfers.
• Check manager edits.
• Check total hours.

Do not approve a card known to be inaccurate merely because a deadline is approaching.

Notify the manager and preserve the correction request.

Timecard already approved with an error

Contact payroll and the manager immediately.

Ask whether the employer can:

• Reopen the timecard.
• Process a correction.
• Issue off-cycle wages.
• Update the attendance exception.
• Preserve the audit history.

Employee approval does not necessarily permit the employer to withhold pay for work that can be verified.

Attendance system and payroll integration

Official isolved sources state that approved timecards can be integrated or exported to payroll, helping reduce manual entry and payroll errors.

Errors can still occur when:

• Timecard was unapproved.
• Exception was unresolved.
• Wrong pay period was exported.
• Manager changed time after export.
• External system failed to synchronize.
• Employee profile was duplicated.
• Job code was wrong.

Compare the final timecard with the pay stub.

Attendance information in another platform

An employer may use isolved for payroll while using another system for:

• Scheduling.
• Attendance points.
• Mobile timecards.
• Callouts.
• Leave administration.

Official isolved customer and Marketplace materials show that outside scheduling and timekeeping systems can exchange employee or timecard information with People Cloud.

Ask which system is the official source for:

• Schedule.
• Punches.
• Point balance.
• Disciplinary notices.
• Payroll hours.

Do not assume every attendance record must be visible inside the main People Cloud dashboard.

Wrong employer account

An employee with multiple isolved employers can accidentally review:

• Former employer’s timecard.
• Second job’s schedule.
• Old attendance policy.
• Inactive employee profile.

Before disputing an event, verify:

• Employer name.
• Work location.
• Employee ID.
• Pay period.
• Manager.
• Schedule.

Attendance points generally do not transfer from one unrelated employer to another.

Rehire attendance record

A rehired employee might see:

• Old occurrences.
• New attendance period.
• Duplicate profile.
• Previous warning.
• Reset balance.
• Combined service history.

The employer’s rehire policy determines whether previous disciplinary history remains active.

Ask HR:

• Which occurrences are active?
• Did the point period reset?
• Which policy version applies?
• Are old events visible only as historical records?
• Is the employee connected with the correct rehire profile?

Notification arrived after the event

An employee might learn about an occurrence only after:

• Manager review.
• Attendance report generation.
• Payroll approval.
• Written warning.
• Dashboard refresh.

Request the employer’s process for:

• Employee notification.
• Dispute deadline.
• Manager review.
• Appeal.
• Documentation.

A short dispute deadline should be addressed promptly.

How to dispute an attendance point

Use a factual written request.

Include:

• Event date.
• Scheduled shift.
• Recorded punch.
• Actual event.
• Leave or manager approval.
• Supporting evidence.
• Policy provision.
• Correction requested.

Example:

“My attendance record assigns one point for arriving late on August 2. The published schedule was changed from 8:00 a.m. to 9:00 a.m. by my manager on August 1, and I clocked in at 8:56 a.m. Please review the schedule-change record and remove the occurrence.”

Avoid emotional accusations when a specific records comparison can resolve the issue.

Useful missed-punch request

“My August 3 timecard shows a missing clock-in. I began assigned work at 7:58 a.m., and my supervisor was present. Please add the actual punch, correct payroll, and confirm whether the related attendance exception will be removed.”

Useful approved-leave request

“My August 4 absence was approved as paid sick leave, but the attendance record shows an unexcused absence and one point. Please review the approved leave and apply the correct attendance code.”

Useful no-call/no-show dispute

“My record shows a no-call/no-show for August 1. I called the attendance line at 5:42 a.m. and left a voicemail before my 7:00 a.m. shift. Please review the call record and correct the classification.”

Useful duplicate-point request

“My attendance history shows both a late-arrival point and a missed-punch point for the same August 5 clock issue. Please confirm whether the policy permits both or remove the duplicate occurrence.”

Useful expired-point request

“My attendance total includes an occurrence dated July 10, 2025. The policy states that points expire after 12 months. Please verify the expiration calculation and update the current total.”

Useful warning-response request

“I acknowledge receiving the written attendance warning but dispute two of the listed events. Please attach this response to the record and pause further action until the supporting schedule and leave approvals are reviewed.”

Useful edited-time request

“My clock-out was changed from 5:22 p.m. to 5:00 p.m., although I performed assigned closing work until 5:22. Please restore the actual work time, review the edit audit trail, and correct any payroll or attendance consequences.”

These messages provide enough information for investigation without exposing account passwords or unrelated personal details.

Who should handle each issue?

Contact the direct manager about:

• Missing punch.
• Immediate schedule issue.
• Late-arrival explanation.
• Early release.
• Timecard correction.
• Shift coverage.
• Current absence notification.

Contact HR or the attendance administrator about:

• Point calculation.
• Policy interpretation.
• Duplicate occurrence.
• Expired points.
• Written warning.
• Protected leave.
• Disciplinary dispute.
• Wrong manager or employee profile.
• Rehire history.

Contact payroll about:

• Missing paid hours.
• Overtime.
• Timecard export.
• Off-cycle correction.
• Pay-stub error.
• Incorrect unpaid deduction.

Contact the leave administrator about:

• FMLA.
• Disability leave.
• Intermittent leave.
• Medical certification.
• Protected absence coding.

The employer controls attendance policy, discipline, approvals, and employee records. isolved provides the timekeeping and workforce tools configured by that employer.

Attendance phishing and fake warnings

Be suspicious when a message says:

• Attendance points can be removed after paying a fee.
• Employee must share the isolved password.
• A manager needs a one-time login code.
• A warning must be acknowledged through an unrelated domain.
• Gift cards are required to restore employment status.
• Remote-access software must be installed.
• Payroll banking information is needed to correct a punch.
• Cryptocurrency can erase a no-call/no-show.

Open the official employee account independently or contact HR through a known channel.

Never share:

• Password.
• Time-clock PIN.
• Authentication code.
• Bank password.
• Debit-card PIN.
• Coworker credentials.

Protect attendance records

Attendance documents can contain:

• Work schedule.
• Location.
• Leave information.
• Manager comments.
• Disciplinary history.
• Medical-leave references.
• Pay-period details.
• Coworker names.

Do not post a full attendance warning or team schedule publicly.

When seeking advice, redact:

• Employee ID.
• Coworker information.
• Medical details.
• Employer-confidential data.

Preserve the unredacted original securely.

Frequently asked questions

Does isolvedHCM track employee attendance?

It can. Official isolved workforce materials describe tools for collecting timecards, tracking attendance, managing absences, scheduling employees, and sending approved time data into payroll.

Does isolved decide how many attendance points I receive?

No. The employer creates and applies its attendance policy.

Is a missed punch the same as an absence?

No. A missed punch can mean the employee worked but failed to record one required entry.

Why did my point remain after my timecard was corrected?

The timecard and attendance occurrence may be separate records requiring separate corrections.

Can approved PTO still create an attendance point?

It depends on the policy, the type of leave, the callout procedure, and applicable law. Review the approval and written attendance rules.

What should I do if a clock malfunction made me late?

Notify the supervisor immediately, record the actual time, preserve the error, and confirm both the timecard and occurrence are corrected.

Can a manager change my clock punches?

Managers may correct records according to employer procedures, but time records should reflect actual compensable work. Federal rules require accurate hour and wage records.

Does a schedule prove how many hours I worked?

No. When actual hours differ from a fixed schedule, the employer must record the actual work time.

What is a rolling 12-month attendance period?

Each occurrence generally remains active until 12 months after its own event date, rather than all points resetting on January 1. The employer’s policy controls the actual method.

Can isolved remove a written warning?

No. The employer controls attendance and disciplinary records. Contact HR or the designated administrator.

Final point

An isolvedHCM attendance issue should be reviewed across all connected records.

The employee should compare:

1. Published schedule.
2. Schedule changes.
3. Actual work time.
4. Raw clock punches.
5. Corrected timecard.
6. Leave request.
7. Approval.
8. Attendance exception.
9. Point history.
10. Written warning.
11. Final paycheck.

The safest process is:

1. Record actual work time accurately.
2. Report failed punches immediately.
3. Review timecards before approval.
4. Preserve schedule and callout confirmations.
5. Distinguish system exceptions from final discipline.
6. Request the written attendance policy.
7. Ask for an itemized occurrence history.
8. Verify point expiration dates.
9. Dispute inaccurate events with evidence.
10. Request separate correction of payroll and attendance records.
11. Follow protected-leave procedures.
12. Keep written responses to warnings.
13. Contact payroll when wages are missing.
14. Contact HR for policy or disciplinary disputes.
15. Never share an isolved password, PIN, or authentication code.

Official isolved materials confirm that its workforce tools can collect time, detect missed punches and late arrivals, track attendance, manage schedules, and prepare approved timecards for payroll. Federal recordkeeping guidance separately requires covered employers to maintain accurate records of actual hours worked and wages earned.

This independent website does not operate an isolved attendance portal, modify timecards, erase points, reverse warnings, or collect employee credentials.

Sources Consulted

This article was researched using current official isolved Time and Labor Management, Workforce Management, time-clock, payroll-preview, employee-timekeeping, customer-story, and Marketplace integration materials. Current U.S. Department of Labor guidance concerning hours worked, timekeeping methods, actual-time records, payroll recordkeeping, overtime, and employer record-retention requirements was also reviewed.