Governance Writing Style Guide

Governance Writing Style Guide

Purpose

Provide a consistent writing standard for governance artifacts in analytics domains.

Scope

This skill covers structure, tone, and mandatory content for:

• governance charters
• policy statements
• controls documentation
• executive summaries

Before drafting governance documentation, check and apply: .github/skills/finance-documentation-lifecycle

Use it as the source of truth for ISO 9001-inspired terminology, process/procedure/SOP distinctions, documentation lifecycle, and evidence/record expectations.

Writing rules

• Use clear section headers and concise bullet lists.
• Distinguish processes from procedures, SOPs, work instructions, and evidence.
• Map every policy requirement to a process/control point.
• Maintain a neutral, professional tone.
• Avoid unnecessary jargon; use business-friendly language.

Required sections

1. Purpose
2. Scope
3. Policy / governance rules
4. Process map
5. Control points
6. Roles and responsibilities
7. Evidence and records

Output expectations

• Use consistent terminology across artifacts.
• Include explicit non-goals in every governance artifact.
• Make mappings visible: policy → control → SOP → evidence.
• Keep artifacts concise but complete.