For almost a year, Marcus worked from 8:00 AM to 4:30 PM.
Then his childcare situation changed.
He spoke with his supervisor and asked whether he could start an hour later. The supervisor agreed.
The conversation wasn’t vague, either.
“Starting Monday, come in at 9:00 and stay until 5:30. That’s fine.”
Marcus even had the conversation in writing.
So Monday he arrived at 8:54.
Tuesday at 8:57.
Wednesday at 8:52.
Two weeks later, he was called into the office and handed an attendance warning for repeated tardiness.
According to the company’s records, Marcus had been late nine times.
The problem was simple: his supervisor approved the new schedule but never got the official schedule changed.
That’s not an attendance problem. That’s an administrative screwup.
The Records Still Said 8:00 AM
From the system’s perspective, nothing had changed.
Marcus was still scheduled:
8:00 AM – 4:30 PM
So an 8:54 arrival looked like:
54 minutes late.
Nine days produced nine apparent attendance problems.
The software wasn’t inventing anything. It was comparing the recorded schedule with the recorded arrival time.
The bad information came from the company.
This distinction matters because it’s tempting to look at a report showing nine late arrivals and assume the report proves misconduct.
It doesn’t.
It proves that the recorded arrival times didn’t match the recorded schedule.
Now someone has to determine which record was wrong.
In this case, it was the schedule.
The Supervisor’s Message Changes the Situation
Marcus pulls out his phone.
There it is:
September 3, 2:14 PM
“9–5:30 starting Monday works for me.”
Sent by his supervisor.
At this point, issuing a warning based solely on the old 8:00 AM schedule makes little sense.
The company has evidence that the person responsible for supervising Marcus authorized the change.
HR shouldn’t try to save the warning by arguing that Marcus technically violated a schedule nobody expected him to follow anymore.
Fix the underlying record.
Then deal with whatever remains.
Don’t Make the Employee Eat the Manager’s Mistake
A particularly bad response would be:
“Your manager should have updated it, but technically the system still showed 8:00, so the occurrences stand.”
That may make the database tidy, but it’s lousy employee relations.
Marcus did exactly what his supervisor told him to do.
If the company has an internal rule requiring a formal schedule-change request, then the supervisor should have followed it.
That’s a management problem.
It shouldn’t magically become nine attendance violations for Marcus.
The manager may need coaching on how schedule changes are supposed to be processed. That’s separate from whether Marcus was actually late.
Now Check the Real Arrival Times
Once the correct schedule is established as 9:00 AM, the attendance history needs to be looked at again.
Suddenly:
8:54 — on time
8:57 — on time
8:52 — on time
9:06 — six minutes late
8:59 — on time
Maybe Marcus wasn’t nine times late.
Maybe he was late once.
That’s a completely different conversation.
This is why correcting the schedule first matters. Otherwise HR is investigating garbage data.
The Warning May Need to Be Corrected Too
Suppose the supervisor already issued a written warning stating:
“Employee has demonstrated an ongoing failure to report to work at the scheduled 8:00 AM start time.”
Once HR confirms the approved 9:00 AM schedule, that statement is factually wrong.
Leaving it in the file anyway is stupid.
Six months later, another manager may see the warning and assume Marcus had a serious attendance history.
A year later, it could be referenced during another disciplinary decision.
Bad documentation doesn’t become harmless just because everybody currently remembers what happened.
If a warning was based on incorrect facts, the company should handle the correction according to its documentation procedures instead of pretending the mistake never mattered.
The Same Problem Happens With Temporary Schedule Changes
This isn’t limited to permanent schedule changes.
A manager tells an employee:
“Come in at 10 tomorrow because you stayed late tonight.”
The normal schedule still says 8:00.
The next morning, the attendance report flags a two-hour late arrival.
Again, the report isn’t enough.
There was an approved exception.
If managers are allowed to make these changes, the company needs some reliable way to record them.
Otherwise HR gets stuck reconstructing conversations from texts, emails, Slack messages, and everyone’s memory.
That’s a terrible system.
Verbal Approval Is Where Things Get Messier
Now remove Marcus’s text message.
He says:
“My supervisor told me 9:00 was approved.”
The supervisor says:
“I told him I’d think about it.”
Great. Now HR has an actual factual dispute.
There may be calendar entries, emails, coworkers who were told about the schedule, previous 5:30 PM departures, or other evidence that helps establish what happened.
But this is exactly why managers shouldn’t casually change schedules and leave no record.
A ten-second message such as:
“Confirming your new schedule is 9:00–5:30 beginning September 7.”
can prevent weeks of bullshit later.
It Gets Worse If Someone Is Terminated Over It
Imagine nobody catches the mistake after nine occurrences.
Marcus receives a warning.
Then another.
The attendance policy eventually reaches its termination threshold.
Management fires him for repeated tardiness.
Afterward, someone finally finds the supervisor’s written approval for the 9:00 AM schedule.
Now the company doesn’t merely have a bad schedule entry.
It has made an employment decision using attendance violations that may never have existed.
That’s why the boring administrative detail matters.
The correct schedule needs to exist before attendance data is used for discipline.
Trion Solutions Doesn’t Make Bad Information True
A workforce system can organize schedules, employee records, attendance information, and HR administration.
It cannot know that a supervisor had a hallway conversation and forgot to process the change.
If Vfficient or another Trion-supported record says Marcus starts at 8:00, while management actually approved 9:00, somebody has to correct the discrepancy.
The answer isn’t:
“The computer says 8:00.”
Computers are very good at consistently applying the wrong information you gave them.
What Should Have Happened?
The supervisor approved the change.
That approval should have been documented and routed through whatever process the company uses to maintain schedule or employment information.
Marcus’s effective schedule should then have reflected:
Old schedule: 8:00 AM – 4:30 PM
New schedule: 9:00 AM – 5:30 PM
Effective date: September 7
From that date forward, attendance should have been evaluated against 9:00 AM.
No mystery.
No nine fake tardies.
No pointless disciplinary meeting.
No HR investigation two weeks later.
Just an accurate schedule.
Fix the Source, Not the Symptom
When an employee says:
“I’m not late. My manager changed my schedule.”
don’t immediately argue about the attendance report.
Check the schedule change.
If the employee is bullshitting, the facts will matter.
If the manager forgot to process an approved change, that matters too.
And if the company’s own mistake created nine bogus attendance occurrences, don’t bury the mistake under more paperwork.
Correct the schedule.
Correct the affected attendance record where appropriate.
Deal with any disciplinary document that relied on the wrong information.
Then make sure the manager knows how to process the next schedule change properly.
Because writing someone up for being “late” to a shift they weren’t supposed to start yet isn’t strict attendance management.
It’s just bad recordkeeping.