Monday - Friday 9AM – 6PM EST
Passing guarding, patrol, or systems work to another firm means your standards have to travel with it. Work through the guided form and your agreement is ready to sign.
Choose the state or form type you need to start.
Answer a few simple questions to customize your form.
Download or print your custom document in PDF or Word.
A security subcontractor agreement covers a security provider and another firm brought in to deliver part of the service. It fixes the coverage, the standards, and who answers when something goes wrong.
Providers subcontract for ordinary reasons. Overflow shifts, a site outside their usual area, a specialist skill, or a short event contract all push work outward.
Your client rarely sees that arrangement. Because your name stays on the client contract, a subcontracted officer’s conduct reflects on you rather than on them.
That exposure shapes the whole document. Screening, reporting, and insurance all need to match what you promised your client, not what your subcontractor normally does.
The document has limits worth knowing. It allocates risk between two providers. However, it does not reduce what you owe your client, so your obligations stay exactly where they were.
Security covers several distinct services, and the agreement shifts with each one.
Static guarding places officers at a fixed post, such as a lobby, gate, or construction site. Coverage hours and post orders drive everything else.
Mobile patrol runs scheduled or random checks across several sites. Route records and check-in evidence matter more here than headcount.
Event security staffs a crowd for a defined window. Volume, briefing, and command structure carry most of the risk.
Systems work covers alarm, access control, and camera installation or monitoring. That sits closer to a trade contract, so scope, commissioning, and service levels take over.
Name which service you are buying before anything else. A patrol agreement will not carry an event, and a systems scope will not cover a guard.
Mixed scopes turn up too. One event may need static posts, a roving patrol, and camera coverage at once. So break pricing and standards out by service line.
Officers perform to the instructions in front of them. So make post orders part of the security subcontractor agreement rather than a separate email.
Attach the written post orders and require the subcontractor to brief every officer on them. Say who updates them and how changes reach the field.
State the hours, the number of officers, and the response expected for a no-show. Uncovered shifts are the most common failure, so agree the remedy in advance.
Name who supervises the officers and how attendance gets verified. Electronic check-ins, patrol tours, or scheduled calls all work once written down.
Say whose uniform an officer wears and who supplies radios, vehicles, and devices. Client sites often expect a particular appearance.
Say whether your subcontractor may pass the work to a third firm. Silence here can put an unknown officer on your client’s site.
Record every credential issued, who holds it, and how it comes back. Also require immediate notice when an officer leaves the assignment.
Your client hired you on the strength of your standards. Pass those standards down in writing.
Require the subcontractor to:
Set out what happens when a check comes back adverse. A clear removal process protects the client and gives the subcontractor a route to follow.
Licensing rules for security personnel differ from state to state, and some cities add their own. So confirm current requirements with your state’s licensing authority instead of assuming another provider’s credentials transfer.
Tip: Ask for the officer roster and credential expiry dates, not a blanket assurance. Expired licenses tend to surface during an incident, which is the worst possible moment.
An incident is where a security subcontractor agreement gets tested. Write the process before you need it.
Set how fast the subcontractor tells you about an incident, injury, or arrest, and in what form. Same-shift notice stops you hearing it from your client first.
Define when officers contact police, fire, or medical services, and who they inform internally. Also confirm that officers follow the client’s own site protocols.
Require incident reports, patrol logs, and footage retention for a set period. Then say who owns those records and who may release them.
Require the subcontractor to refer press and social media questions to you. Incidents attract attention, and one stray comment becomes your problem.
State plainly that the subcontractor does not approach your client directly. All reporting routes through you, since your contract carries the obligation.
Security work attracts claims that other services rarely see. So cover the money side properly.
The agreement should record:
Handle the exit as well. Set the notice each side owes, how officers transition, and what happens to credentials and records on the final day.
Disputes need a route as well. Name who talks first, then the step after that, so a billing disagreement never reaches your client.
Non-solicitation deserves a line too. Trained officers are the asset, so agree whether either side may hire the other’s people, and keep any restriction narrow.
Both parties execute the same version before the first shift, and a copy goes with the site file. You can customize and sign a security subcontractor agreement template the same day. Nothing needs to start on a handshake.
One place to build, sign, and manage documents.
