FiveM Security Guard Job Scripts: Building Bouncer, Escort and VIP Protection Into a Paid Loop

A security guard job dies the moment it becomes a payout button players click between AFK sessions. Stand at a door, press E every ten minutes, collect a wage from thin air — that isn’t roleplay, it’s a slot machine with worse odds. The scripts that actually keep a city busy treat protection as the other half of crime: guards only earn when something is worth guarding, and something is only worth guarding when a player on the other side might take it.

That two-sided design is where most servers get it wrong. This guide walks through the five tiers of a FiveM security guard job — door work, static site guarding, cash-in-transit, armored transport, and VIP close protection — and how to wire each one into your framework so the pay is honest, the risk is real, and the police loop gets pulled in instead of bypassed.

What makes a security guard job create real roleplay?

A FiveM security guard job creates roleplay when its pay sits below what a robber can net, so crime still makes sense, and when every high-value contract needs a second player to threaten it. Fixed hourly wages produce AFK farming. Contract-based pay tied to escort routes, club incidents, or a VIP’s session turns protection into a job players choose to show up for.

Keep that principle in your head for every tier below. If a guard earns more sitting still than a criminal earns taking a risk, you’ve built passive income with a uniform, and your economy will bleed.

The five tiers of security work

Stack these as an escalating career. Each rung raises pay, raises risk, and raises the whitelist bar — so a new hire starts on the door and a supervisor runs armored routes. Gate the higher tiers behind society grades and the whole thing reads as a real company.

• Door security (bouncer): ID checks, weapon frisks, capacity control, and kick/ban power inside a club or venue instance. Low pay, high interaction — this is where new players learn the job.
• Static site guarding: patrolling a business, warehouse, or event. Pays a modest shift rate plus incident bonuses when a real player triggers an alarm.
• Cash-in-transit escort: guarding a courier or business owner moving marked bills between a shop and the bank. Mid pay, and only worth running when robbers are online.
• Armored transport: the Gruppe Sechs loop — a crewed truck running scripted routes between banks and corporations, carrying a physical cash bag a criminal crew can intercept.
• VIP close protection: a player-hired bodyguard detail. Highest pay, ideally funded by the client’s own wallet, not the server economy.

Notice the pattern: pay scales with how likely a human is to attack you. Door work is constant but cheap; armored transport is rare but lucrative because the whole point is that someone might blow the doors off your truck.

Paying guards without printing money

The fastest way to wreck an economy is paying protection wages out of nowhere. Route every payout through a society account instead, so guarding a business drains that business’s funds and armored contracts pay from a company treasury the boss has to keep topped up. When money moves between player-owned accounts, protection becomes a service with a price, not a faucet.

Here’s a payout frame that holds up on a mid-population server. Adjust to your own money curve, but keep the ratios:

• Door shift: $120–250/hour flat, capped and tied to an active venue. Cheap on purpose.
• Cash-in-transit run: $2,000–4,000, paid only on delivery, split among the escort.
• Armored transport: $5,000–9,000 per completed route, split across the crew.
• VIP detail: $3,000–6,000 per session, client-funded where your framework allows a direct transfer.

Now balance the crime side against it. If your armored truck carries a $12,000–18,000 cash bag that launders at 60–70%, a successful heist crew nets roughly $8,000–12,000 for an armed robbery with a live police response. That has to stay above the guard payout, or nobody ever pulls the trigger and your transport job quietly becomes AFK income again. Set the numbers so crime pays a little better than protection — the guards are trading excitement for reliability, and that’s exactly the trade a real security contractor makes.

Wiring it into ESX or QBCore

Build the security company as a whitelisted society job with grades, not a standalone resource bolted on the side. On ESX that means an esx_society job with a shared account; on QBCore it’s a qb-management society plus job grades. Either way you want a boss menu to hire, fire, promote, and withdraw from the treasury.

A grade ladder that maps cleanly to the five tiers:

0  recruit    -> door + static guard only
1  guard      -> cash-in-transit escort
2  senior     -> armored transport crew
3  supervisor -> VIP details + route assignment
4  boss       -> hire/fire, treasury, contracts

Gate the armory and the high-tier contract board behind grade checks so a recruit physically can’t pull an armored route. On QBCore you can wire the boss menu, stash, and duty toggle straight into the framework’s management stack — there are drop-in QBCore job and management scripts at qb-tebex.io that already handle society funds and grade gating, which saves you rebuilding society plumbing from scratch. Pay contracts with addAccountMoney pulled from the society account on the server side only — never trust a client event to hand out cash, or someone will replay it.

The bouncer job is its own animal

Door work looks simple and is the hardest tier to make fun, because nothing happens 90% of the time. The trick is giving the bouncer real authority over a venue instance: scan IDs against a wanted or banlist, frisk for weapons with a target-based interaction, enforce a headcount, and kick or soft-ban a troublemaker from the club for the night. When those actions have teeth, players roleplay around them — they bribe the door, forge IDs, or start something in the smoking area to pull the bouncer off the entrance.

Tie the bouncer to club ownership so it feeds an existing loop rather than standing alone. If a player owns the nightclub, they hire the door, set the guest list, and eat the loss when a fight scares off customers. A full club-management resource with a bouncer module — the kind you’ll find among the nightlife and venue server builds — bundles bartending, society funds, and door security so the whole venue runs as one economy instead of three disconnected scripts.

Pull the police loop in, don’t replace it

Security that resolves every incident by itself makes cops redundant, and redundant cops log off. Wire your escort alarms and armored-transport robberies into the same dispatch or MDT your law enforcement already uses, so a truck heist pings PD with a location and the guards’ job is to survive and stall until units arrive. A good dispatch and MDT script from shop-tebex.io gives you the shared alert layer that ties private security, the transport crew, and the police response into one scene instead of three isolated jobs.

The best sessions come from that overlap: a Gruppe Sechs truck gets rammed on the freeway, the escort calls it in, PD rolls, and the robbery crew has a ninety-second window to crack the bag before the city descends. None of that happens if security is a self-contained payout loop.

Keep it performant and abuse-proof

Patrol peds and NPC contracts are the usual resmon killers. A script that spawns thirty guard peds and runs a per-frame loop checking every one of them will sit at 3–5ms idle and tank a full server. The scripts worth buying spawn peds on an event, cull them by distance, and idle near 0.00–0.01 when no contract is active. Check the resmon claim before you buy, and load-test with bodies on the server, not an empty map.

On the exploit side, three defenses matter most:

• Cash as a serialized item: make the transported bag a physical inventory item with a unique identifier so it can’t be duped or spawned. Validate the serial on delivery.
• Server-side payouts only: calculate and grant contract money on the server, gated by the player’s job and grade, never on a client trigger.
• Contract cooldowns and live-threat gating: put a per-player cooldown on runs, and scale the top payouts so they require a real robber attempt or a minimum police count — not an empty-server solo farm.

Get those three right and your security job resists the two things that break every job script: duplication and AFK farming. Get the economy ratios right on top of them, and you’ve built a protection career players actually clock in for.

FAQ

Is a FiveM security guard job better on ESX or QBCore? Both handle it well; the deciding factor is your society backbone. QBCore’s qb-management makes society treasuries and grade gating almost turnkey, so fresh servers tend to wire security faster there. ESX works equally well with esx_society once it’s configured, so build on whichever framework your server already runs rather than switching for one job.

How do I stop the security job from becoming AFK money? Kill fixed hourly wages, or cap them hard. Pay the real money through contracts that need a delivery, an incident, or a live threat to complete, and route it from a society account so a business actually funds it. When high-tier payouts require a robber attempt or a minimum police count, solo AFK farming stops paying.

What’s the difference between a bouncer job and a bodyguard job? A bouncer works a fixed venue — door control, ID checks, and kick/ban power inside a club instance — and earns a low, steady rate. A bodyguard runs mobile VIP close protection for a specific player or contract, earns far more per session, and ideally gets paid from the client’s own wallet rather than the server economy.