You’re already at your Allied Universal site.
Uniform on.
Relief has left.
You’ve started working.
Then your phone buzzes.
LISA is asking about your work status because the system doesn’t appear to have a clock-in for your scheduled shift.
It’s tempting to dismiss the message.
After all, you’re physically at work.
But those are two different facts:
You arrived at the site.
The timekeeping system successfully recorded your arrival.
Don’t assume one automatically proves the other.
Check the Clock-In Before Answering Anything
Start with the simplest question:
Did the clock-in actually register?
Maybe you forgot.
Maybe you attempted it and thought it went through.
Maybe the site device was slow.
Maybe the method normally used at your assignment wasn’t functioning correctly.
Don’t answer an automated question from memory if you can first verify what happened.
Being on Site Doesn’t Create the Punch
You can arrive five minutes early, speak with the outgoing officer, receive the pass-down, and begin your duties exactly on time.
If the required clock-in never registers, the timekeeping record can still look incomplete.
From your perspective:
“I was obviously here.”
From the record:
No successful clock-in appears.
That’s the discrepancy you need to address.
Don’t Claim an Earlier Time Just Because It Was Your Scheduled Start
Suppose your schedule says:
Start: 7:00 AM
You actually arrived:
7:08 AM
If LISA asks about the missing clock-in, don’t simply select or report 7:00 because that’s what the schedule says.
Scheduled time and actual arrival time aren’t automatically identical.
Use the truthful time worked and follow the applicable site procedure for correcting a missing or incorrect punch.
The Opposite Problem Can Happen
Maybe you really were there at 7:00.
You attempted to clock in at 7:00.
But the system doesn’t appear to have recorded it.
Now you have a legitimate discrepancy.
Don’t “fix” it by inventing a different story.
Instead, preserve the facts:
Scheduled start: 7:00 AM
Arrived: 6:55 AM
Clock-in attempted: Approximately 7:00 AM
LISA message received: 7:15 AM
Site device: Wasn’t responding normally
That’s something a manager can actually investigate.
A Site Phone Problem Doesn’t Mean Timekeeping Stops Matter
Some Allied assignments use site equipment as part of their normal clock-in process.
If that equipment isn’t working, don’t conclude:
“Well, nobody can clock in, so it doesn’t matter.”
Determine what alternate procedure your site expects.
Allied Universal’s technology setup can vary by assignment, so the method another officer uses at a completely different account isn’t automatically the method you’re supposed to use.
Don’t Use LISA as a Shortcut Unless Your Site Allows It
This is particularly important because Allied sites don’t all operate identically.
If LISA presents a way to respond to a missing clock-in, don’t automatically assume that means your local management wants employees routinely using that method instead of the site’s normal timekeeping procedure.
Know your assignment’s rules.
A fallback option and the standard clock-in method aren’t necessarily the same thing.
Check the Schedule Too
Sometimes the strange part isn’t the punch.
It’s the schedule.
Imagine you’re normally off on Tuesdays.
LISA suddenly contacts you about a Tuesday shift you didn’t know existed.
Before answering the clock-in question, check whether the system actually shows you scheduled.
Now the issue may be:
Unexpected scheduled shift
rather than:
Forgotten clock-in
Those require very different conversations with management.
Don’t Clock In for a Shift You Aren’t Working
A LISA message isn’t proof that you’re supposed to start recording time.
If you’re at home and receive a message asking about a shift you weren’t expecting, don’t clock in simply because the automated system contacted you.
First verify the schedule and assignment.
A scheduling mistake shouldn’t become an inaccurate time record.
Don’t Ignore the Message Either
The opposite reaction is also risky:
“LISA is wrong, so I’ll just ignore it.”
If the system genuinely missed your clock-in, ignoring the discrepancy leaves the incorrect record unresolved.
Even when you’re certain you arrived on time, respond according to the applicable process or contact the appropriate supervisor.
The goal is for the record to match what actually happened.
Record the Time the Problem Happened
If the system isn’t behaving normally, write down the relevant times while they’re fresh.
For example:
6:52 AM — arrived at property
6:58 AM — completed pass-down
7:00 AM — attempted clock-in
7:14 AM — LISA missing-clock-in message
7:17 AM — notified supervisor
That timeline is much stronger than remembering three days later:
“I think I was there around seven.”
Your Relief Can Be Useful Context
If another officer was physically present when you arrived, that can help establish what happened operationally.
For example, the outgoing officer may know exactly when you took over the post.
But don’t treat a coworker’s memory as a replacement for correcting the actual timekeeping record.
The objective is still to make the official record accurate.
Don’t Create a Second Problem While Fixing the First
You notice the missing clock-in.
You panic.
You clock in again.
Then you submit another correction.
Then you message your manager with a third time.
Now there are several different versions of what happened.
Before taking multiple actions, determine what the system currently shows and follow the applicable correction procedure.
One accurate correction is better than several guesses.
A Late Clock-In and a Missed Clock-In Aren’t Identical
Suppose you were physically at the site at 7:00 but didn’t realize until 7:20 that you forgot to clock in.
That’s not the same situation as arriving at 7:20.
When explaining the discrepancy, separate:
Arrival time
from
Recorded clock-in time
and
Scheduled start time
Those three timestamps can tell very different stories.
Don’t Let the Schedule Rewrite Reality
The schedule says 3:00 PM.
That doesn’t automatically mean you worked beginning at 3:00 PM.
Likewise, a recorded clock-in of 3:08 PM doesn’t necessarily prove you physically arrived at 3:08 PM if there was a documented technical problem.
The purpose of resolving the discrepancy is to determine what actually occurred—not simply to choose whichever timestamp is most convenient.
Site-Specific Procedures Matter
Allied Universal supports a huge variety of client locations.
A high-rise account, warehouse, hospital, residential property, and corporate campus may not all handle operational technology exactly the same way.
Follow the clock-in procedure assigned to your site.
If you’ve recently transferred, don’t assume the process from your old site still applies.
Ask before your first shift rather than discovering the difference after LISA flags you.
Keep Technical Problems Specific
Avoid reporting:
“LISA is broken.”
Instead:
“I attempted to clock in at 6:59 AM. The site device remained on the validation screen, and at 7:14 AM LISA contacted me as though no clock-in had been recorded.”
That’s useful.
It identifies the time, action, device behavior, and resulting discrepancy.
Repeated Problems Need More Than Repeated Corrections
If the same site equipment fails every week, correcting individual punches addresses the immediate record but not the recurring problem.
Keep track of the pattern and report it through the appropriate channel.
For example:
Monday — delayed clock-in registration
Wednesday — missing clock-in
Friday — device unavailable
Now there’s evidence of a recurring operational issue rather than three unrelated employee mistakes.
Don’t Wait Until Much Later
If LISA flags a missing clock-in while you’re currently working, that’s the best time to investigate.
You’re at the site.
You remember exactly when you arrived.
The outgoing officer may still remember the handoff.
The equipment condition can still be checked.
Trying to reconstruct everything two weeks later is much harder.
Build the Timeline, Not an Excuse
If LISA says you haven’t clocked in, work through the situation in order:
Am I actually scheduled for this shift?
Am I at the correct site?
Did I attempt the required clock-in?
Did it successfully register?
What time did I actually arrive?
Is the site equipment functioning normally?
Does my manager need to know about a discrepancy?
Then make sure the record reflects what actually happened.
LISA’s message doesn’t automatically mean you were late.
But physically standing at the site doesn’t automatically mean the timekeeping record is correct either