Policy & Documentation
Version Control & Sign-Offs: Proving WVP Docs Are Current
Surveyors cite undated, unsigned, and outdated workplace violence documents constantly. Here is the version-control and sign-off discipline that proves your WVP program is current.
Surveyors cite workplace violence programs for being undated, unsigned, or out of date at least as often as they cite them for missing content. A facility can have an excellent, facility-specific plan and still fail a tracer because no one can prove which version is current, when it was last reviewed, or who approved it. Version control and sign-offs are the unglamorous discipline that converts a good document into provable evidence — and they are entirely within your control.
#Why "looks current" is not "is current"
A surveyor's question is rarely "is this a good policy?" It is "show me the current one, and show me when you last reviewed it." Texas HSC Chapter 331 builds in a recurring annual plan evaluation reported to the governing body, and The Joint Commission expects an annual worksite analysis and periodic program review. Each of those obligations is a date the surveyor will check. A plan with no review date, or a review date outside the required window, signals a program that was built once and shelved — the exact opposite of the program of record you are trying to demonstrate.
Worse than an undated document is a superseded one still in circulation: an old policy taped to a break-room wall, or last year's plan on the shared drive next to this year's. When two versions exist and staff cannot tell which governs, the policy-to-practice gap is visible in the artifact itself.
#The minimum version-control header
Every controlled WVP document — policy, plan, incident form, training materials, charter — should carry a small, consistent control block. It costs nothing and resolves most date-and-currency findings before they happen:
| Control element | What it states | What it proves |
|---|---|---|
| Document title & ID | Unique name/number | One canonical reference, no ambiguity |
| Version number | e.g., v3.0 | Which iteration this is |
| Effective date | When this version took effect | Currency within the required window |
| Last reviewed date | When it was last evaluated (even if unchanged) | The annual review actually happened |
| Next review due | The forward date | The program is on a cadence, not adrift |
| Approved by | Role/committee that approved it | The right authority signed off |
| Supersedes | The version this replaces | No orphaned old copy governs |
"Reviewed, no change" is a legitimate and valuable entry. Surveyors want to see that you looked on schedule; an unchanged document with a fresh review date is fully compliant, while a document untouched for three years is not — even if nothing needed changing.
#Sign-offs: who approves what
A sign-off is the evidence that the right authority adopted the document. Match the approval to the obligation:
- The written plan and policy should show approval by the WVP committee and, where the program reports up, acknowledgment at the leadership or governing-body level — Chapter 331 ties the annual evaluation to the governing body, so that approval trail matters.
- The annual plan evaluation should show the committee reviewed it and that results went to the governing body, with a date.
- Committee minutes should show attendance, decisions, and approval of the prior minutes — the chain that proves the committee is a living body, not a name on a charter.
- Training materials should show the version staff were actually trained on, so the training documentation and the curriculum line up.
Electronic approvals are fine if your system captures who approved, what version, and when, in a way you can reproduce on demand.
#One source of truth
Version control fails when copies multiply. Establish a single authoritative location for the current version of each document and treat everything else as a reference copy that must be replaced when the master changes. Practical controls:
- Retire superseded versions deliberately — pull old copies from walls, drives, and binders when a new version takes effect, and record the supersession.
- Date the binder index. The survey-readiness binder should list each document with its current version and review date, so the index itself proves currency.
- Reconcile what is posted to what is filed. If the unit-level quick reference says one thing and the filed plan says another, the surveyor believes the unit.
- Keep the version history even as you retire active copies; showing v1 → v2 → v3 with dates is the cleanest proof of a continuous program.
#The payoff: currency you can demonstrate in seconds
The whole point of version control is speed and confidence on survey day. When a surveyor asks for the current plan and its last review date, the answer is a single document with a control block that answers both questions before you say a word — and a binder index that confirms it. That is what separates a program that is current from one that merely hopes it looks current.
#How VIGILO helps
VIGILO applies a consistent document-control standard across your entire WVP document set — control blocks, sign-off routing, and a dated binder index — through our policy and documentation development service and the WVP Foundation Package. The Annual Compliance Subscription keeps every review date inside its window year over year, and a Survey-Readiness Audit will flag every undated, unsigned, or superseded document before a surveyor does.
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.