An officer posted to a client site during a labor dispute has a camera in a phone, a notepad, and hours of standing there watching people who are, for the most part, doing exactly what they’re legally allowed to do. The instinct is to document everything — every face, every sign, every chant, every license plate in the lot — because “capture it all and let someone else sort it out later” feels like the safe, thorough version of the job. It’s also the version most likely to create legal exposure for the client and the security company, because a chunk of what gets swept up in “document everything” is protected activity that isn’t the company’s business to record in the first place. What security guards can and cannot document during a labor dispute is the question that actually matters here, and it’s rarely covered in general training.
This is a genuinely confusing assignment for officers who’ve never worked one before, and the confusion runs both directions — under-documenting a real safety or property threat is a failure, but over-documenting protected picketing is a different kind of failure with its own consequences. Below are the questions officers and supervisors actually ask when this assignment comes up.
Is a picket line itself something officers should be documenting?
Not by default. Employees exercising their rights under the National Labor Relations Act to picket, carry signs, and engage in other protected concerted activity are doing something the law protects, and routine surveillance of that activity — photographing or logging who’s present, what signs they carry, who they talk to — is the kind of documentation that tends to create problems rather than solve them. The presence of a picket line is not, by itself, a security event.
So what actually justifies documenting something?
The dividing line professionals use is conduct, not presence. An officer’s job on a picket-line assignment is to watch for things that threaten safety or property — blocking a driveway so vehicles can’t safely enter or exit, physical confrontation, damage to a vehicle or the building, or anything that crosses from protest into something the post’s safety plan would need to escalate regardless of who was involved. Those are events. Document them the way you’d document any other incident: what happened, when, who was involved to the extent it’s relevant to the safety or property issue, and what action was taken.
The people carrying signs and walking a line, on their own, are not an event. The habit worth building in officers is to ask, before raising a phone or opening a notebook, “am I recording a threat to safety or property, or am I just recording that picketing is happening” — because those are different actions with different consequences.
What about names, faces, and license plates?
This is where the instinct to be thorough does the most damage. Compiling identifying information about picketers — names, license plate numbers, employer affiliations — reads, from the outside, like building a list of who participated, and that’s precisely the kind of activity that has drawn legal challenge in past labor disputes. An officer isn’t in a position to know, in the moment, whether a given piece of identifying information is relevant to a genuine safety incident or whether it’s just being collected because it’s available. The safer discipline is to document identifying details only when they’re directly tied to a specific safety or property incident that’s being logged anyway — a license plate because a vehicle struck something, not a license plate because it belongs to someone on the line.
How should officers communicate what they’re seeing, in real time?
The same discipline that applies to writing it down applies to what goes out over the radio. A call describing a blocked loading dock or an aggressive confrontation gives dispatch something concrete and actionable. A running narration of who’s out there and what they’re carrying does not — it just puts more of the same information onto a channel that other people can hear, without adding anything to how the safety issue gets handled. Keep radio traffic tied to the safety event, the same way the written log should be.
What if the client asks the officer to photograph or record picketers directly?
That request should go back to the client’s own counsel before the officer does anything, not get treated as a routine instruction the officer simply follows. An officer isn’t in a position to evaluate whether a specific request crosses into unlawful surveillance of protected activity, and following an instruction that turns out to be improper doesn’t shield the officer or the security company from the consequences. The right response to that kind of request in the moment is to note it and route it up the chain — to a supervisor and, from there, to the client — rather than to comply on the spot because the client asked directly.
Deciding what security guards can and cannot document during a labor dispute has to happen before the assignment starts
Because an officer standing on a picket line, watching something tense unfold, is not in a good position to work out where the legal line sits in real time. This has to be part of the pre-assignment briefing: what counts as a safety or property event worth documenting on this specific site, what doesn’t, and who the officer calls if something ambiguous happens that they’re not sure how to categorize. Clear post orders for this kind of assignment should spell out the documentation standard explicitly rather than leaving officers to infer it from general training, because a labor dispute assignment is different enough from routine patrol that generic guidance doesn’t transfer cleanly.
The routine, every-shift log for a picket-line post should look like the daily activity report for any other post — arrival, post checks, notable observations — without becoming a running account of the protected activity itself. Keep the incident-worthy events in the incident reporting channel where severity and escalation are tracked, and keep the routine log routine.
The part that isn’t optional: get this reviewed before the assignment, not after
This article names the National Labor Relations Act because it’s the relevant federal framework for picket-line activity, not because it’s a complete statement of what applies to any specific assignment. Labor law in this area is fact-specific — what’s protected, what a company can lawfully monitor, and what documentation is appropriate can turn on details particular to the dispute, the site, and the parties involved. Before a security company takes on a picket-line assignment, get case-specific guidance from counsel on what officers should and shouldn’t document for that assignment, and build the briefing and post orders around that guidance rather than around general practice. Nothing in this post is legal advice.
Get this wrong and the exposure lands on the client and the security company both, well after the picket line is gone. If you want to see how CGuardPro keeps routine logs and incident documentation cleanly separated for assignments like this, get in touch.