Objective. Students will read and accurately extract, summarize, and apply key information from authentic security post orders, use-of-force policies, and legal notices using active reading strategies.
This lesson, its worked examples and its practice questions has not yet been verified by a licensed professional in the field or by a certification or approval body. It is a study draft and may contain errors. Do not use it as instructions for work on a job site or on live equipment. Always follow your instructor, your supervising professional, and current official references and regulations.
VoTechWorks program approval and accreditation are still in progress. Credentials are issued only by the certifying bodies named in each program, after their own exams.
As a security professional, you will spend a significant part of every shift acting on written documents — post orders, policy manuals, trespassing notices, and licensing statutes. Misreading a single directive can mean denying access to an authorized person, failing to notify the right supervisor during an emergency, or taking an action that is not legally authorized. Accuracy is not optional; it is the foundation of the job.
This lesson teaches you how to read technical documents actively, extract the information that governs your duties, and translate legal or formal language into plain, actionable understanding.
Post orders are written instructions issued by your employer or client that tell you exactly what to do at a specific post — a fixed location or assignment such as a hospital lobby, parking structure, or data center entrance. A well-written post order covers:
Post orders are legally significant documents. They define the scope of your authority at that location. Acting outside the post order — even with good intentions — can expose you and your employer to liability.
A use-of-force policy tells you when and how you are permitted to use physical or other force to protect yourself, others, or property. Clear policies use specific, observable language: "An officer may use the minimum force reasonably necessary to overcome active physical resistance." Vague policies use undefined terms or contradict themselves: "Officers should use appropriate force when the situation warrants it" — without defining appropriate or warrants.
When you read a use-of-force policy, ask:
1. Does this tell me exactly what conditions must be present before I act?
2. Does it tell me which specific options I may use and in what order?
3. Are there any statements that contradict each other?
Ambiguous policy language creates risk. If you cannot clearly answer all three questions, flag the section to your supervisor before an incident — not during one.
Safety note: No policy authorizes force that exceeds the legal standard in your state. Your state security license and any applicable statutes set the outer boundary. When in doubt, do less, not more, and summon law enforcement.
A trespassing notice is a legal document that formally informs a person they are not permitted on a specific property. It typically states the property address, the owner or authorized agent's name, and the legal consequence of remaining or returning. You may be asked to deliver or witness the delivery of such a notice. You must be able to read it accurately and explain its meaning to a visitor in plain language — without providing legal advice.
State security licensing statutes are the laws that require you to hold a valid security guard license before you work. They describe who must be licensed, the application process, conduct that can cause a license to be suspended or revoked, and the penalties for working without a license. Reading these statutes carefully protects your career. A violation of the statute — even an unintentional one — can end your ability to work in this field.
Passive reading — simply moving your eyes across the page — does not produce reliable recall or accurate application. Use the SQ3R method for any technical document:
| Step | What You Do |
|------|-------------|
| Survey | Skim headings, subheadings, bold text, and any numbered lists. Get the map before you read the territory. |
| Question | Turn each heading into a question. "Access Control" becomes "What are the access control rules at this post?" |
| Read | Read one section at a time with your question in mind. Annotate: underline key directives, circle defined terms, put a question mark next to anything unclear. |
| Recite | Without looking, say or write the answer to your question. If you cannot, re-read that section. |
| Review | After the whole document, review your annotations and answers. Note gaps and re-read only those sections. |
Annotation is an active safety behavior. A post order you have annotated is faster to reference during a real incident than one you only read once.
You will often need to explain a legal or policy document to a member of the public who did not read it and has no obligation to understand legal terms. Plain-language translation means:
Example: A trespassing notice may read, "You are hereby notified that your presence on the aforementioned premises is unauthorized and that any subsequent entry constitutes criminal trespass subject to arrest and prosecution under applicable state law." In plain language: "You are not allowed on this property. If you come back, you can be arrested."
After reading any policy or order, test yourself: Can you describe the key rules out loud without the document? Can you identify the reporting chain from memory? Can you explain what the trespassing notice means to a visitor? If yes, you are ready to work the post. If no, re-read the relevant section before your shift begins — not after a problem occurs.
Answer each question, then check it. Nothing is recorded; this is your own practice.
A free tech program — complimentary, as our commitment to get America working. Help us build VoTechWorks. Tell us what works, what doesn’t, and what you want to learn.