Policy & Documentation
Who Signs What: The WVP Document Approval Authority Matrix
A WVP document approval authority matrix defines which role signs each document — committee, program leader, or governing body. Here is how to build the sign-off matrix surveyors expect.
A workplace violence document signed by the wrong person is a governance gap, even when the content is flawless. If your written plan was approved only by a coordinator and never adopted by leadership or the governing body, a surveyor reads it as an unenforced program. A document approval authority matrix — a table that names which role signs each document — removes that ambiguity. It ensures the right authority approves every artifact, and it gives a surveyor a single reference for how your program is governed.
#Why "signed" is not the same as "properly approved"
Document version control establishes that a document is dated, signed, and current. The approval-authority matrix answers the next question: who had the authority to sign it? These are distinct concerns. A plan can carry a fresh date and a signature and still fail, because the signature belongs to someone without the authority to adopt it on the facility's behalf.
The distinction matters most for the documents with explicit governance ties. Texas HSC Chapter 331 requires the annual plan evaluation to be reported to the governing body, which means the governing body must actually see and act on it — a program leader's signature alone does not satisfy that step. The Joint Commission (effective January 1, 2022 for hospitals) frames the program as leadership-defined, which is a statement about who owns and adopts it. The matrix is how you make sure the right level signs each thing.
#Two roles per document: recommend and approve
A clean matrix usually distinguishes two functions:
- Review / recommend. The role that develops and vets the document and recommends it for adoption — typically the WVP committee or the program leader.
- Approve / adopt. The role with authority to make it binding — leadership or the governing body for the highest-governance documents; the committee or program leader for operating-level documents.
Separating the two prevents the most common error: the body that writes a document also being the only body that adopts it, so nothing is ever elevated to leadership. For the plan and the annual evaluation, the recommend-and-adopt split is what produces the governing-body trail Chapter 331 expects.
#A model approval-authority matrix
The table below is a starting structure. Adjust the approving role to your facility's actual governance, then make it the controlling reference for every sign-off.
| Document | Reviews / recommends | Approves / adopts |
|---|---|---|
| WVP policy (governance statement) | Program leader + committee | Leadership / governing body |
| Written, facility-specific plan | Committee | Leadership / governing body |
| Annual plan evaluation | Committee | Governing body (reported, per Ch. 331) |
| Committee charter | Program leader | Leadership |
| Operating procedures (SOPs) | Program leader | Program leader / committee |
| Incident report form | Program leader | Committee |
| Training curriculum | Program leader | Committee |
| Retention schedule | Program leader + risk/legal | Leadership |
| Committee minutes | Recording member | Committee (approved at next meeting) |
The pattern: governance documents — policy, plan, annual evaluation — rise to leadership or the governing body; operating documents — procedures, forms, curricula — are approved at the program-leader or committee level. The annual plan evaluation is the one that most often goes wrong, because facilities evaluate the plan but stop short of the governing-body adoption the statute requires.
#Name roles, not individuals
Build the matrix entirely in terms of roles and credentials, never named individuals. "Designated program leader," "WVP committee," "governing body" — these survive turnover, where a matrix keyed to a person's name breaks the moment they leave. This also keeps the program rails-clean: authority is defined by function, not by any individual's identity. When a person changes, the role is unchanged and the matrix still governs; you simply re-record who currently holds the role.
#Handle delegation explicitly
Real programs delegate. The program leader may approve a routine procedure revision; the committee chair may sign minutes; an interim leader may hold authority during a vacancy. Rather than let delegation happen informally — which produces documents signed by whoever was available — name it in the matrix. State which approvals can be delegated, to which role, and under what conditions. Documented delegation is defensible; undocumented delegation looks like a document approved by someone without authority. The goal is that for any signed document, the matrix explains why that role's signature was sufficient.
#Make the matrix part of the survey-readiness binder
The approval-authority matrix belongs in the governance section of the binder, near the committee charter and the version-control standard. Together they answer the surveyor's governance questions completely: the charter says who is on the committee, the matrix says who approves what, and the version control says the approved copy is current. A surveyor who sees those three documents working together extends trust to the program's documentation as a whole.
A practical test before survey: take any signed WVP document and check it against the matrix. Did the role that signed it have approval authority for that document class? Was any required second-level adoption recorded? If every document passes, your sign-offs are defensible. If some were approved below their required level, you have found a governance gap you can fix by routing them to the correct authority before a surveyor asks.
#Where it fits with version control
The matrix and version control are complementary halves of document governance. Version control proves when and that a document was approved and that the current copy is in use; the matrix proves the right role approved it. Keep them aligned: the version-control block should name the approving role, and that role should match what the matrix authorizes for that document. When the two agree on every artifact, your program demonstrates not just current documents but properly governed ones.
#How VIGILO helps
VIGILO builds the document approval-authority matrix for your facility's governance, routes each WVP document to the correct approving role, and ties it to the version-control standard — through the WVP Foundation Package and our policy and documentation development service. The Annual Compliance Subscription keeps approvals current as roles change and ensures the annual plan evaluation reaches the governing body, and a Survey-Readiness Audit checks whether every document was approved by the authority the matrix requires.
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.