You know you can’t work your scheduled Allied Universal shift, so you follow the applicable call-off process through LISA.
Later, you check your schedule.
The shift is still there.
Did the call-off fail?
Not necessarily.
Reporting that you can’t work a shift and changing the underlying schedule are related actions, but they don’t always represent the same thing. Your original assignment may remain visible even after your absence has been reported.
The important question is whether the call-off was properly recorded—not simply whether the shift disappeared from your calendar.
A Call-Off Doesn’t Rewrite History
Suppose you’re scheduled:
Friday — 3:00 PM to 11:00 PM
On Friday morning, you properly report that you’re unable to work.
The original schedule can still matter.
It establishes that you were expected to work from 3:00 PM to 11:00 PM before the call-off occurred.
Removing the shift entirely could make it harder to understand what the original assignment was.
So seeing the scheduled shift afterward doesn’t automatically prove that nobody received your call-off.
Look for Confirmation of the Action You Actually Took
Don’t use the schedule as your only confirmation.
If the applicable LISA workflow provides confirmation or a status associated with the call-off, pay attention to that information.
You’re trying to establish:
Was the call-off submitted?
Was the correct shift involved?
When was it submitted?
Those details are much more useful than assuming success or failure based solely on whether the calendar changed.
Make Sure You Reported the Correct Shift
This becomes important when you have several shifts close together.
Suppose you’re scheduled:
Friday — 11:00 PM to 7:00 AM
Saturday — 11:00 PM to 7:00 AM
It’s easy to think of both as “night shift.”
But they’re separate assignments.
If you’re unable to work Friday night’s shift, make sure the call-off corresponds to the correct date.
Don’t assume one report automatically covers another scheduled shift unless that’s actually what the process indicates.
Overnight Shifts Need Extra Attention
An overnight assignment crosses two calendar dates.
For example:
Starts: October 16 at 11:00 PM
Ends: October 17 at 7:00 AM
If you’re reporting that you can’t work it, identify the shift by its scheduled start and full time range rather than casually referring to it as “Friday morning” or “the October 17 shift.”
That makes the assignment much easier to distinguish.
Coverage and Call-Off Are Different Problems
Once an employee reports an absence, the shift may still need to be covered.
That can involve another employee being offered the open work.
Your responsibility is to follow the applicable absence-reporting process.
Don’t assume the call-off isn’t valid simply because the original shift remains visible while coverage is being handled.
Likewise, don’t assume another employee claiming the shift automatically erases every record of your original assignment.
Don’t Claim Your Own Open Shift
If a shift becomes available through LISA after your call-off, don’t start experimenting with the shift-offer functionality to see whether it’s connected to your absence.
If you’ve already reported that you can’t work, follow the applicable process for that situation.
Claim a Shift is for accepting work you’re able and intending to perform.
It isn’t a troubleshooting tool for checking whether your call-off reached the scheduling process.
A Schedule Can Show What Was Originally Expected
Think of the schedule as one piece of the record.
Before the call-off:
Scheduled — 3:00 PM to 11:00 PM
After the call-off, the organization may still need to know that this was the assignment you were originally expected to work.
That’s different from saying you never had a shift at all.
This distinction can matter when reviewing attendance or understanding why coverage was needed.
Don’t Assume “Still Scheduled” Means “Just Show Up Anyway”
If you properly reported that you couldn’t work because of the situation that caused the call-off, don’t reverse course solely because the shift remains visible.
Instead, determine whether your call-off was successfully recorded.
The schedule display by itself doesn’t tell the entire story.
If you’re uncertain whether the report went through, verify through the appropriate Allied Universal process rather than guessing.
Timing Matters
When you report an absence can matter under the applicable attendance and call-off procedures.
Don’t treat LISA as a way to retroactively turn a missed shift into a timely call-off after the fact.
If you’re unable to work, follow the required reporting procedure within the applicable timeframe.
A timestamp can become important if there is later confusion about when the absence was reported.
Save Useful Confirmation
If the workflow provides confirmation that your call-off was submitted, keep the useful information until the situation is resolved.
You don’t need a folder containing dozens of screenshots.
The useful facts are straightforward:
Shift date
Scheduled time
Date and time you reported the absence
Confirmation or status available through the process
Those details are enough to explain what happened if the schedule continues to create confusion.
Don’t Submit the Same Call-Off Repeatedly
If the shift doesn’t disappear, don’t automatically report the same absence five more times.
Duplicate submissions don’t necessarily make the original report more valid.
First determine whether the first submission was recorded.
If it was, the unchanged schedule may simply reflect the original assignment rather than a failed call-off.
If there is no evidence the submission succeeded, then use the appropriate procedure to address that specific problem.
Check the Shift Afterward
Once the scheduled time has passed, review the resulting information if necessary.
If the system or attendance record later treats the shift differently from what you expected despite a properly submitted call-off, you now have a specific discrepancy to raise.
For example:
Scheduled shift: October 18, 7:00 AM–3:00 PM
Call-off submitted: October 18, 4:45 AM
Confirmation received: Yes
Later record: Appears to indicate no call-off was reported
That’s a meaningful issue.
Compare it with:
“The shift never disappeared.”
The second statement doesn’t actually establish that anything went wrong.
Being Covered Doesn’t Erase Your Call-Off
Suppose another officer ultimately works the shift.
That solves the staffing need.
It doesn’t change the fact that you were originally scheduled and reported that you couldn’t work.
Coverage and attendance records answer different questions.
Don’t use another employee’s schedule to determine whether your own call-off was properly recorded.
Report the Exact Mismatch
If you need assistance, describe what you can actually verify:
“I was scheduled October 21 from 3:00 PM to 11:00 PM. I submitted my call-off at 9:15 AM and received confirmation, but the shift still appears on my schedule.”
Now it’s possible to determine whether the remaining schedule entry is expected or whether something actually needs correction.
That’s much clearer than:
“LISA didn’t remove my shift.”
Call-Off and Schedule Status Shouldn’t Be Treated as the Same Field
LISA can help Allied Universal manage employee communications and call-off-related workflows, but reporting an absence doesn’t necessarily mean your original scheduled assignment must vanish from every view.
Keep the distinction clear:
Schedule: When you were expected to work.
Call-off: Your report that you can’t work that assignment.
Coverage: How the organization handles the staffing need afterward.
Those three pieces are connected, but they aren’t interchangeable.
So if you’ve properly called off and still see the shift, don’t immediately submit another report or assume the process failed.
Verify the call-off itself first. The fact that the original shift remains visible may simply preserve the assignment that existed before you reported the absence.