Maintain an authoritative organizational policy record with owner, scope, approval, effective date, version, requirements, exceptions, related procedures, evidence, review cycle, and supersession history.
Scanned 9/11/2026
Install to Claude Code
npx -y skills add Dadmin88/hermes-profile-packs --skill policy-record --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Policy Record?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/dadmin88-policy-record)More formats (shields.io, HTML) on the badges page.
---
name: policy-record
description: Maintain an authoritative organizational policy record with owner, scope, approval, effective date, version, requirements, exceptions, related procedures, evidence, review cycle, and supersession history.
---
# Policy Record
Use when an approved policy must become a durable source of truth for the organization.
## Procedure
1. Identify the policy owner, approving authority, title, scope, affected audiences, effective date, and authoritative source document.
2. Record version and approval history and preserve superseded versions according to organizational retention requirements.
3. Separate policy requirements from explanatory guidance, procedures, templates, and implementation examples so authority remains clear.
4. Link related legal or regulatory basis only when supplied or verified by qualified owners and distinguish it from internal business policy.
5. Record permitted exceptions, waiver authority, request process, and evidence requirements where the approved policy provides them.
6. Link procedures, training, controls, forms, systems, and owners responsible for operational implementation.
7. Set review triggers based on scheduled review, legal or regulatory change, incident, organizational change, or evidence the policy no longer matches practice.
8. Publish or restrict access according to audience and confidentiality, and ensure downstream references point to the current authoritative version.
## Decision rules
- The policy record preserves approved policy; Legal Ops should not create obligations absent authorized approval.
- Procedures can change without silently changing policy authority.
- Superseded versions need unmistakable status.
- Review date is not a substitute for substantive revalidation.
## Quality gate
The record is reliable when scope, authority, version, effective date, requirements, exceptions, related procedures, and ownership are explicit; the current version is easy to identify; superseded history is preserved appropriately; and changes cannot occur without traceable approval.Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!