write-a-policy-summary

# write-a-policy-summary The summary explains the policy but does not replace it. ## When to use - Use for employee, customer, public, vendor, academic, or operational policies. - Do not add rights, obligations, promises, or exceptions absent from the authoritative document. ## Procedure 1. Confirm approved policy version, owner, audience, purpose, effective date, and authoritative link. 2. Extract scope, covered people, required actions, prohibited actions, rights, exceptions, deadlines, evidence, and consequences. 3. Organize around reader questions and actions using plain, direct language. 4. Define unavoidable terms and preserve important thresholds, conditions, and jurisdiction differences. 5. Add contacts, accessibility support, appeal or exception routes, and where to read the full policy. 6. Compare every claim and omission to the source; flag unresolved ambiguity to the policy owner. 7. Obtain owner approval and label version plus update date. ## Done - A policy summary document records audience, scope, duties, rights, exceptions, dates, contacts, source link, and version - Claim, threshold, omission, plain-language, accessibility, authority, link, and approval checks verify accuracy