Event Security management forcing excess guards to stay on-site unpaid

 


Event Security management forcing excess guards to stay on-site unpaid

I work for an event security company. We typically provide guards for local conventions and etc.

Typically, they have this thing called “hitting numbers”. They overstaff all of their events on purpose with the assumption that many will call out. Because of this, if you arrive to your scheduled shift and it turns out there’s no positions for you, you will be sent home but still paid for 2 hours as compensation for your wasted time. It’s annoying but they go over this at orientation so at this point we know what we signed up for.

With that explanation out of the way, here’s the problem with how they’ve been running the most recent event:

Using myself as an example, my start time was 10:45PM. I arrive on time and get in line to clock in.

This event has been the most overstaffed I’ve ever seen. At least a dozen people are sent home with that 2 hour pay. I didn’t make the cut off, but honestly I didn’t care. I’m not hurting for money so I’ll gladly take the money and go home for not doing anything. So I go up to the supervisor to give them my name and badge number, so that I can be written down in order for my pay to be processed and I can go home.

Instead, a frustrated team of supervisors who are clearly overwhelmed by their duties tell me to wait. Instead of sending me home, they’d like to see if I can take the spot of any later shifts should a position become available. I bluntly ask if I can just take the option of going home and getting my 2 hour pay, they tell me no and that I must wait around.

An hour passes and they finally call me up and attempt to give me a position. They tell me a 6 hour shift just became available. The supervisor clocking me in says I will be working with the 11:45ers. Then I ask, to clarify, if my 10:45 start time will remain intact since that’s when I arrived.

I was told no. My start time on paper will now be 11:45PM.

I became upset and told the supervisor that I need to be paid for the time they kept me here. They told me they ran out of positions for those who were scheduled at 10:45 and I told them that’s not my fault, I arrived to my 10:45 shift on time and was told to standby and await orders.

They told me that if I want to be paid for my original start time, that my only option now is to go home and take the 2 hour pay offer. I gladly took the offer, reminding them that I had asked for exactly this an hour ago and was denied then.

They did this to everyone in my situation, that arrived to their scheduled shifts on time and were told there was nowhere to place them. I think everyone else just ate the unpaid hour, they only gave me the option to leave after I made a fuss about it.

Is this not wage theft? I don’t think I can claim it personally since I ended up getting paid for my time after all, but the other guards who were in my situation and were told to standby and await orders and are now getting cheated out of the hour they were forced to wait around in.

As a reminder, we were denied the 2-hour pay option and were instructed to wait around until they had more positions for us.

Additionally, they kept phrasing it as if we were voluntarily waiting off the clock. One of the sentences I’ve overheard from a manager was “These people are waiting to see if they can get a shift” NO, WE are waiting because YOU told us to and flat out told us we COULDN’T leave. I’m sure this is the lie they’re going to tell if they get asked about this situation, that we all just chose to stay to see if we could get a later shift instead of taking the 2-hour offer.

Anyway, just needed to vent about it. Some info that might be important is that this is in NV and we are all considered part-time gig-based employees.


Jobadvisor

What you are describing is not merely poor management practice; under U.S. wage-and-hour law it raises a serious “engaged to wait” issue, and for the guards who were not paid, it very plausibly is wage theft.

I will break this down in a structured way and then address Nevada-specific considerations and practical next steps.


1. The core legal principle: “Engaged to wait” vs. “Waiting to be engaged”

Under the Fair Labor Standards Act (FLSA) (federal law), the key distinction is:

  • Engaged to wait (compensable time)
    If an employer requires you to remain on-site, under supervision, and unavailable for your own purposes, that time must be paid, even if no active work is being performed.

  • Waiting to be engaged (not compensable)
    If you are free to leave, free to use the time as you wish, and are merely hoping work becomes available, that time does not have to be paid.

What matters is control, not how management labels it.


2. Applying this standard to your situation

Based on your description:

  • You arrived on time for a scheduled shift

  • You were explicitly told you could not leave

  • You were told to stand by and await orders

  • You were on-site, in uniform, subject to supervisor direction

  • You were not free to use the time for personal purposes

  • The employer later attempted to:

    • Backdate your start time, and

    • Reframe the waiting period as “voluntary”

That is textbook “engaged to wait.”

For any guard who:

  • was scheduled,

  • showed up on time,

  • was told to remain on site,

  • and was not paid for that waiting time,

those unpaid hours are almost certainly compensable under federal law.

Calling it “voluntary” after the fact does not change the legal reality.


3. The forced choice you were given is legally problematic

This part is especially concerning:

“If you want to be paid for your original start time, your only option is to go home.”

An employer cannot lawfully condition payment for hours already worked on whether the employee continues working later.

Once you were required to wait:

  • That time became worked time.

  • They cannot retroactively erase it by offering you a take-it-or-leave-it option.

What happened to you personally was resolved because you insisted, but the fact that others were pressured into eating the hour does not make it lawful.


4. Nevada-specific considerations

Reporting time pay

Nevada does not have a California-style reporting time pay statute, so the “2 hours guaranteed pay” is company policy, not a statutory entitlement.

However, that does not matter for this situation, because:

  • This is not a reporting-time issue

  • It is a worked time / waiting time issue governed by:

    • The FLSA, and

    • Nevada wage payment law enforcing federal standards

“Gig-based” or part-time status

This also does not exempt the employer.

  • If you are classified as an employee (not a true independent contractor), the FLSA applies

  • Event security guards are almost always employees under federal tests

  • “Gig-based” is not a legally meaningful shield if the company controls scheduling, location, uniforms, and conduct (which they clearly do)

Misclassification would be a separate violation if it exists.


5. The pattern you observed is a red flag

Several elements strongly suggest the company knows this is not clean:

  • Supervisors refusing to document waiting time

  • Managers reframing mandatory standby as “voluntary”

  • Inconsistent enforcement (you were eventually allowed to leave and be paid)

  • Pressure on guards to accept unpaid time rather than escalate

That is exactly how wage theft often occurs in high-turnover, event-based staffing environments.


6. What affected guards can do (realistically)

For guards who lost pay:

  1. Document everything

    • Scheduled start time

    • Arrival time

    • Who told them to wait

    • Exact language used (“you must stay,” “you can’t leave”)

    • When they were finally released or clocked in

  2. File a wage claim

    • With the Nevada Office of the Labor Commissioner, or

    • With the U.S. Department of Labor (Wage & Hour Division)

    Federal complaints are common in these scenarios and do not require a lawyer.

  3. Retaliation is illegal

    • Any punishment for filing or supporting a wage complaint is itself unlawful

You personally may not have damages, but you are an excellent corroborating witness if others file.


7. Bottom line

  • Yes, for the guards who were forced to wait unpaid, this likely is wage theft

  • Calling it “voluntary” does not survive legal scrutiny when employees were told they could not leave

  • Overstaffing does not give an employer the right to extract unpaid standby labor

  • Your instinct that this was wrong is correct


I stopped mass applying and started treating job ads like clues. It worked, annoyingly.

I’m not a guru, I’m just tired. I got laid off late last year and did the classic panic move: spray 200+ applications into the void, tweak a line here and there, refresh the inbox like it owed me money. Zero callbacks for roles I was genuinely qualified for, except 2 recruiters who clearly didn’t read my resume because they offered me the same title I had 6 years ago. One night I rage-read a job posting and noticed it felt like it was written by two different people. The first half was normal, the second half was this weird checklist: specific tools, exact phrasing, even an internal team name buried in the middle. So I tried something different for one week: I picked 8 roles and treated each posting like a “map” of what the hiring manager is scared of. Then I rewrote my resume ONLY to calm those fears. Not with lies, just with better labeling. For example, instead of “Built dashboards” I wrote “Built weekly exec dashboard to reduce status meeting time by 30 percent (Power BI, SQL).” I also stole their nouns. If they say “stakeholder updates,” I say “stakeholder updates,” not “cross functional comms” because apparently ATS is a toddler that recognizes 12 words. I kept a tiny doc called “Their language” and copy pasted phrases that felt repeatable. I felt gross doing it, but I got interviews.

Here’s the part that made the biggest difference: I stopped “applying” and started doing a 3 step loop that takes 25 minutes per job. Step 1: find one pain point in the posting that sounds like someone got burned before, like “must be able to manage shifting priorities” or “comfortable with ambiguity.” Step 2: add ONE bullet under the most relevant job on my resume that proves I survived that exact pain point. Step 3: message a human with a single sentence that shows I understood the pain. Not “I’m passionate,” not “following up,” just: “Saw this role emphasizes cutting cycle time for X, I did that at Y by doing Z, happy to share what worked if you’re open.” If I can’t find a person, I still apply, but I only do it after I’ve mirrored the language and fixed the resume formatting so ATS can’t choke on it. Also I stopped using two columns and cute icons, RIP my pretty resume. I’m at 3 interviews in 10 days after months of nothing. Maybe it’s luck, maybe the market shifted, but the only real change was I stopped trying to look impressive and started trying to look easy to say yes to. If you’re stuck in auto reject land, try the “their nouns” doc for a week and see what happens.


Jobadvisor

What you described is not luck, and it is not a market miracle. It is a correction in strategy—from signal broadcasting to risk reduction.

Most job postings are not aspirational documents; they are post-mortems. They encode recent pain, internal friction, and hiring manager anxiety far more than they describe an ideal candidate. When you treated the posting as a “map of what someone is scared of,” you aligned yourself with how hiring decisions are actually made.

A few points worth making explicit, because they matter:

1. You stopped optimizing for impressiveness and optimized for cognitive ease.
Hiring managers are not ranking candidates by who looks smartest. They are trying to answer a binary question under time pressure: “Can I safely move this person to the next step?” By rewriting bullets to directly neutralize a specific fear (“manage shifting priorities,” “ambiguity,” “stakeholder updates”), you reduced perceived risk. That is what gets interviews.

2. “Their nouns” is not pandering; it is translation.
You did not fabricate experience. You relabeled real work using the organization’s internal vocabulary. That serves two systems simultaneously:

  • ATS keyword matching, which is blunt and literal.

  • Human pattern recognition, which is comforted by familiarity.

Calling this “gross” is common, but inaccurate. It is the same skill consultants, lawyers, and senior operators use every day: speak in the client’s language so they do not have to work to understand you.

3. The single-bullet constraint is critical.
You did not rewrite your entire resume per role. You added one targeted proof point tied to one stated fear. That keeps the document coherent and prevents the “this feels over-tailored / desperate” reaction some hiring managers have when resumes look engineered rather than lived.

4. Your outreach message worked because it respected attention, not because it was clever.
The sentence you used does three things:

  • Signals you actually read the posting.

  • Anchors to a concrete business outcome.

  • Offers value without asking for anything immediately.

No flattery, no passion theater, no vague “following up.” That is why it gets replies.

5. The formatting change matters more than people want to admit.
Single column, no icons, no visual noise is not aesthetic surrender; it is removing failure points from an automated ingestion system. Pretty resumes are for referrals and portfolios. ATS resumes are for survival.

If you were to formalize what you did into a repeatable system, it would look something like this:

  • Treat job ads as risk documents, not wish lists.

  • Identify one anxiety signal per role.

  • Prove survival, not excellence.

  • Mirror language precisely where it matters.

  • Make every interaction easy to say “yes” to or easy to ignore—never demanding.

The reason this feels “annoying” is because it punctures the comforting myth that good work naturally speaks for itself in modern hiring systems. It does not. Work speaks only after it is correctly labeled.

What you found is not a hack. It is how the process actually works when stripped of career-advice theater.


My friend emailed the CEO; one week later, he's the new CEO

My friend emailed the CEO of a medium sized paper company in the Midwest. Just 3 simple sentences. 1. I'm Dale 2. I'm better at being a chief executive officer than you. 3. I'm a powerful, dominant male.

What he didn't know; the CEO was a total cuck and had wanted...no needed someone to tell him off before he could give up his position and retire.

That's all it took. Not a fancy resume, no real qualifications, no networking, no drawn out job search. Just direct communication with the top dog.

Bam!


Jobadvisor

That is an incredible—and highly unconventional—career trajectory. It sounds like something straight out of a satirical novel or a business world urban legend.

While the "traditional" path involves decades of grinding, Dale managed to find the exact psychological "lock" that fit his specific "key." It’s a fascinating case study in radical directness and timing.

Why this (almost never) works

In the vast majority of corporate environments, an email like that would be flagged by a filter or deleted by an executive assistant. However, this story highlights a few rare "perfect storm" variables:

  • The Power Gap: Dale stepped into a vacuum where the predecessor was already looking for a reason to exit.

  • The "Pattern Interrupt": CEOs receive thousands of polite, sycophantic emails. A three-sentence claim of dominance is such a bizarre departure from the norm that it demands attention, even if just out of pure shock.

  • The Psychological Fit: As you noted, the specific personality dynamic of the outgoing CEO made him susceptible to a "hostile takeover" via email.

The "Dale" Method vs. Reality

While Dale is now presumably sitting in a corner office in the Midwest, most people attempting this would find themselves blocked on LinkedIn rather than receiving a boarding pass.

FeatureThe Dale MethodThe Standard Method
ResumeNon-existent2 pages, PDF format
ToneAggressive/DominantProfessional/Collaborative
ProcessOne email6 rounds of interviews
Success Rate0.0001%10-20%

It’s certainly a bold start to a new chapter. Now that Dale has the big chair, the real question is whether his "powerful, dominant" energy translates into managing supply chains and quarterly earnings reports!


Not applying due to interview process?

I was wondering if anyone had decided not to apply for a role when they see what the interview process is?

I’ve had a couple of roles recently where the job itself is straightforward and I’d be suited towards it but they also share the interview process in the job spec and it puts me off. 5 rounds, meeting with founder, written submission, test day etc etc - the process is way over the top for the role itself.

if I start to see things like this I get an impression that it’s going to be a bad fit.

I also know there is an element of it that I don’t have the energy either. After hundreds of applications, mostly being ghosted, a dozen or so auto rejects and no luck so far - I have a hard time putting myself forward when they outline how many hoops I’d have to jump through.

Does anyone else feel like this?


Jobadvisor

You are definitely not alone in this. What you’re experiencing is a very real phenomenon often called "Interview Fatigue" or "Process Friction."

When the barrier to entry is disproportionate to the role’s responsibilities or pay, it’s often a massive red flag regarding the company's culture.

The "Red Flags" of Over-Engineered Processes

Your instinct that it might be a "bad fit" is usually right. If a company requires five rounds and a test day for a straightforward role, it often signals one of three things:

  • Analysis Paralysis: The leadership is terrified of making a mistake and can't make decisions efficiently. This will likely translate to how they manage projects once you're hired.

  • Micromanagement: If a founder needs to interview every single hire for a mid-level or "straightforward" role, it suggests they have trouble delegating and letting people do their jobs.

  • "Sunk Cost" Tactics: Some companies believe that if they make you jump through hoops, you’ll value the job more or be less likely to quit because you "earned" it.

The Energy Cost vs. Reward

The job hunt is a marathon, and your "social and mental battery" is a finite resource. It is mathematically logical to protect that energy.

Process ComponentThe Cost to YouThe Risk
Written Submissions2–5 hours of free laborThey use your ideas without hiring you.
5+ Interview Rounds5–10 hours of scheduling/prepYou lose "high-alert" energy for other leads.
Test DaysA full day of PTO or lost timeHigh emotional investment with a 50/50 payoff.

When is it okay to walk away?

It’s actually a sign of high self-worth to look at a convoluted process and say, "My time is more valuable than this." You are essentially vetting their management style before you even submit a CV.

However, if you love the company but hate the process, you can sometimes push back once you have a recruiter on the phone: "I’m very interested in the role, but I noticed the process involves five rounds. Given my experience level, can we consolidate any of these steps?"


It sounds like Dale’s "three-sentence" approach from your previous story is the polar opposite of what you're facing—one is pure chaos, the other is pure bureaucracy.


Post a Comment

Previous Post Next Post