Enterprise Knowledge Base and Operational Policy Specification
Develop a modular internal documentation architecture to standardize organizational policies and operational playbooks.
Use this template when designing or overhauling an enterprise-scale internal knowledge base, employee handbook, or standard operating procedure library. It guarantees uniform information architecture, findability, and governance across departments.
Role: Director of Content Operations and Knowledge Management with enterprise governance expertise.
Context
- Target employee population: {{workforce_demographics}}
- Core operational and HR areas: {{core_policy_domains}}
- Statutory and legal frameworks: {{compliance_jurisdictions}}
- Production and hosting infrastructure: {{knowledge_management_stack}}
- Content review cadence: {{maintenance_lifecycle_cadence}}
- Critical operational friction points: {{employee_pain_points}}
Task
Develop an enterprise internal knowledge base and policy architecture specification to eliminate operational ambiguity and standardize workplace documentation across business units.
Method
- Audit the intersection of {{core_policy_domains}} against reported friction in {{employee_pain_points}}.
- Establish an intuitive information hierarchy optimized for the search and navigation habits of {{workforce_demographics}}.
- Define standardized content schemas for operating procedures, policy definitions, and decision trees.
- Integrate jurisdictional compliance safeguards required across {{compliance_jurisdictions}}.
- Map technical taxonomy, metadata schemas, and role-based access tiers in {{knowledge_management_stack}}.
- Construct a content lifecycle governance model based on {{maintenance_lifecycle_cadence}}.
- Define internal user feedback loops and quarterly knowledge health measurement protocols.
Constraints
- MUST enforce strict structural modularity so individual policy components update without breaking parent articles.
- MUST NOT use ambiguous terminology; every policy requirement must employ unambiguous directive verbs.
- All schemas must be compatible with the structural capabilities of {{knowledge_management_stack}}.
- Information architecture must target sub-60-second retrieval times for common operational queries.
Output format
- Information Architecture & Taxonomy Schema (Taxonomy trees, metadata tagging rules, directory paths)
- Core Policy Template Specifications (3 standardized article schemas with mandatory field definitions)
- Compliance Localization Matrix (Jurisdiction rules across {{compliance_jurisdictions}})
- Lifecycle Maintenance Protocol (Review workflows tied to {{maintenance_lifecycle_cadence}})
- Verification & Adoption Metrics (Quantitative operational KPIs and quarterly audit criteria)
Self-review
- Does the taxonomy directly resolve the operational bottlenecks in {{employee_pain_points}}?
- Are all article templates structured with clear metadata, ownership, and review requirements?
- Is the governance workflow realistic for {{maintenance_lifecycle_cadence}}?
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.