OperationsTemplate / formDocumentation style guideWhat writing, structure, terminology, procedure, and review standards should documentation follow?IntermediateOperationalTemplate
OperationsTemplate / formTechnical documentation QA checklistIs technical documentation accurate, usable, safe, consistent, and maintainable?IntermediateOperationalTemplate
OperationsTemplate / formContent review checklistIs a business document concise, complete, audience-appropriate, evidence-backed, and actionable?IntermediateOperationalTemplate
OperationsTemplate / formProcedure-writing templateHow should a procedure explain prerequisites, ordered actions, branches, verification, and recovery?IntermediateOperationalTemplate
OperationsProcess / methodGlossary governanceHow should specialized terms be introduced, defined, reused, and retired?IntermediateOperational
OperationsKPI / metricDocumentation health metricsIs active documentation current, and can intended users complete the documented task without additional help?IntermediateOperational
OperationsFramework / modelCallout decision guideWhen should documentation use a note, tip, warning, prerequisite, or no callout?Use the callout decision guide when people working on documentation and naming are using different mental models for callout types, user consequence, and severity, and that difference is changing choices or coordination.AccessibleOperational