A county has draft policies that never left SharePoint. What does effective implementation still require?
Select an answer to reveal the explanation.
Short Explanation
A policy that lives forever as a SharePoint draft is a diary entry, not a control. People need to hear it, learn it, and face consequences when they ignore it. Publishing plus training plus enforcement turns paper into practice.
Full Explanation
Effective policy implementation requires communication, training, and enforcement so staff adopt and follow the rules; documentation alone is insufficient. Draft policies that never leave SharePoint are not operational controls—they are unfinished work. Counties must publish approved versions, teach expected behaviors, and apply consequences or corrective action when requirements are ignored, or the documents never change outcomes.
Only increasing draft version numbers monthly without distribution creates an illusion of progress while staff remain unaware of requirements. Deleting all drafts so auditors see an empty library destroys evidence of intent and guarantees an audit finding for absence of policy. Translating policies into Latin to demonstrate formality prioritizes appearance over comprehension and adoption.
Exam caveat: 'Policy on the shelf' stems want the implementation triad—communicate, train, enforce—not more drafting hygiene theater.
Operational check: Move drafts through formal approval, publish in the official repository, assign awareness training with completion tracking, test comprehension with scenarios, and tie repeated violations to progressive discipline documented with HR.