Policy & Documentation
WVP Standard Operating Procedures vs. the Written Plan
Your WVP plan states what your facility will do; standard operating procedures state exactly how staff do it. Here is the procedure layer surveyors trace and how to write it defensibly.
Your workplace violence prevention plan states what your facility will do. Standard operating procedures (SOPs) state exactly how staff do it — which form, which channel, which role, within what timeframe. A surveyor reads the plan to learn your commitments and then traces a procedure to test whether those commitments actually run on the floor. Facilities that write the plan but skip the procedure layer fail that trace, even when the plan itself is excellent.
#Three layers, not two
Most facilities know the policy and the plan are different documents. Fewer recognize the third layer beneath them. The full stack reads top to bottom:
| Layer | What it answers | Who it speaks to |
|---|---|---|
| Policy | Why we have a program and what we commit to | Leadership, governing body, surveyor |
| Plan | What the program contains and how it is governed | Committee, program leader, surveyor |
| Procedure (SOP) | How a specific task gets done, step by step | The nurse, tech, or clerk on the unit |
The policy and plan are the governance and architecture; the procedure is the operating instruction. A surveyor's tracer almost always lands at the bottom layer: "If a patient struck you right now, show me what you would do." The answer the staff member gives is the procedure — and it must match what the document says.
#Why the procedure layer is where tracers break
The policy-to-practice gap — a facility with strong documents that still gets cited — almost always lives in a missing or contradicted procedure. The plan promises confidential reporting; the surveyor asks a float nurse how to report, and she names a channel that no longer exists. The plan promises post-incident support; the procedure that would have triggered it was never written, so the charge nurse improvised. In each case the failure is not the plan. It is the absence of a procedure that turns the plan's promise into a repeatable action.
Texas HSC Chapter 331 requires a written, facility-specific plan, a confidential reporting mechanism, and post-incident response that includes acute treatment and work-assignment adjustment. The statute does not use the term "SOP," but none of those obligations is provable on the floor without a procedure that staff can execute the same way every time. The Joint Commission's reporting, post-incident, and training requirements (effective January 1, 2022 for hospitals) have the same dependency: leadership defines the program, but the unit executes the procedure.
#What a defensible WVP procedure contains
A procedure is not prose — it is an instruction. Every WVP SOP should answer five questions explicitly:
- Trigger. What event starts this procedure? ("Any physical assault, verbal threat, or aggressive act by a patient, visitor, or staff member.")
- Steps, in order. Numbered actions a person follows without interpretation.
- Roles. Who does each step — by role, never by name.
- Channel or form. The exact reporting form, hotline, or system used.
- Timeframe. Within what window each step happens.
A line that reads "notify the appropriate person and document as needed" fails every one of these. A line that reads "the involved staff member completes the WVP incident report in [system] within 24 hours and notifies the charge nurse immediately" passes. The test is simple: could a brand-new float nurse follow it without asking a question?
#The procedures every WVP program needs
You do not need a procedure for everything, but a survey-ready program has SOPs for the moments that recur and the moments that hurt. At minimum:
- Incident reporting — how any staff member reports a workplace violence event confidentially, with the form, channel, and timeframe.
- Immediate response / call for help — how staff summon assistance during an active event (rapid-response activation, overhead code, or equivalent), framed in compliance terms, not as a security-guard deployment.
- Post-incident response — the checklist that runs every time: acute treatment offered, work-assignment adjustment considered, debrief and employee-assistance referral logged. This is where Chapter 331's post-incident requirement becomes provable.
- Behavioral-risk flagging — how a known risk is recorded and communicated across shifts.
- Escalation and notification — who is told what, in what order, after a serious event.
Each SOP should cross-reference the plan section it executes, so a surveyor following the thread from plan to floor never loses it.
#Keep the plan and the procedure consistent — or both fail
The most common self-inflicted finding is a contradiction between layers. The plan routes reports to the program leader; the procedure routes them to HR. The plan promises a 24-hour reporting window; the SOP says "as soon as possible." When the two disagree, a surveyor reads it as an unmanaged program, and the better-written document does not save you. Before you finalize, reconcile every shared detail — reporting path, timeframes, roles, post-incident steps — so the policy, the plan, and the procedure read as one voice.
This consistency is also why generic, purchased procedures are dangerous. A downloaded SOP references units, systems, and channels you do not have, guaranteeing a contradiction. Write the procedure to your actual workflow: your real reporting system, your real rapid-response process, your real units.
#Make the procedure usable where the work happens
A procedure filed in a binder no one opens during an event is not operational. Put the action-level SOPs where staff act — a laminated quick-reference at the nurses' station, a one-screen job aid in the system, an item in unit onboarding. The filed master governs; the floor copy executes. Keep both under the same version control and sign-off discipline so the posted copy never drifts from the approved master, and confirm in training that staff can find and follow the procedure, not just attest that it exists.
#Where SOPs fit in the binder
In your survey-readiness binder, the procedures sit immediately behind the plan section they execute, so the surveyor's thread from policy to plan to procedure to record is unbroken. Assembled this way, the procedure layer is what lets you answer the hardest tracer question — "show me how this actually works on the unit" — with a document instead of an improvisation.
#How VIGILO helps
VIGILO writes the policy, the facility-specific plan, and the operating procedures as one consistent set — drafted to your actual workflow and mapped to Chapter 331 and The Joint Commission — through the WVP Foundation Package and our policy and documentation development service. The Annual Compliance Subscription keeps the procedure layer aligned with the plan as both change, and a Survey-Readiness Audit tests whether your procedures would survive a floor-level tracer before a surveyor runs one.
VIGILO provides compliance, training, and consulting assistance and supports survey-readiness; it does not guarantee safety outcomes. Sources: Texas HSC Chapter 331 (SB 240, 88th Leg., 2023); 26 TAC §133.55; HHSC PL 2024-10; The Joint Commission workplace violence prevention requirements (effective Jan. 1, 2022 for hospitals); OSHA General Duty Clause §5(a)(1) and Publication 3148.