About the IT Ops Playbook
Built by COGNITO IT PTY LTD, the IT Ops Playbook was created to solve a simple but universal problem: IT teams are expected to run like mature organisations, but most don’t have the time to design mature processes, document them, and then map them to audit expectations.
The problem we saw
- Lack of structure — everyone works differently and nothing is standardised.
- Lack of time — teams are busy keeping systems running, not writing documentation.
- Compliance pressure — ISO 27001, SOC 2, Essential Eight and other frameworks demand clear evidence, consistent controls, and repeatable operating discipline.
The idea behind the Playbook
Create one complete operational blueprint that an IT team can adopt, customise, and deploy quickly—without compromising quality. The outcome is board-ready, auditor-acceptable operational documentation that supports real delivery, not shelfware.
Our approach
The Playbook is designed to be clear, comprehensive, actionable, and evidence-driven—aligned to recognised standards and structured to import cleanly into common documentation platforms.
What this means in practice: you get a repeatable operating model, high-quality policies and procedures, and audit-aligned evidence mapping—so you can improve service delivery while increasing compliance confidence.
What’s included today
The current release focuses on the highest-value deliverables that decision-makers care about: clarity, governance, and audit-grade evidence—delivered in formats that import cleanly.
Playbook Core
SOPs, checklists, runbooks, policies and knowledge-base articles for real-world IT operations—structured for easy navigation and adoption.
Compliance Tools
A compliance mapping matrix, Statement of Applicability (ISO 27001 Annex A), and executive-ready coverage artefacts designed to support audit conversations.
Guides & Insights
Platform import guides, executive insights and usage guidance to help teams deploy confidently and maintain quality over time.
Import Packs
HTML and Markdown packs are included for broad compatibility across common documentation stacks.
Roadmap note: Additional bulk import formats and evidence automation packs will be introduced in future releases.
Supported platforms
“Support” here means: can you import the Playbook with predictable results using the included packs, without needing a custom migration project.
| Platform | Support level | How we import (today) |
|---|---|---|
| IT Glue (Kaseya) | Full | HTML Import Pack (ZIP). Imports HTML documents (and folder structure) at scale. |
| Confluence (Atlassian) | Partial | HTML pack is usable via copy/paste or per-page import workflows (results vary by editor/settings). For enterprise deployments, API / marketplace migration tooling may be preferred. |
| Notion | Partial | Markdown pack is recommended. HTML can be used selectively but formatting and hierarchy may not map 1:1. |
| Microsoft SharePoint (Microsoft 365) | Partial | Best results via HTML pages or document libraries with curated navigation. Bulk structure may require SharePoint site design decisions. |
| GitBook | Full | Markdown Import Pack (ZIP). Ideal for modern documentation sites with fast publishing workflows. |
| MkDocs | Full | Markdown pack (static-site). Works well for internal portals and Git-based change control. |
| Docusaurus | Full | Markdown pack (static-site). Strong for engineering-led documentation and versioned releases. |
| GitHub Pages | Full | Markdown pack with a generator (MkDocs/Docusaurus/Docsify/Jekyll). Best for controlled, auditable change history. |
| Docsify | Full | Markdown pack (runtime-rendered). Simple setup for fast internal publishing. |
| HackMD / HedgeDoc | Partial | Markdown content can be imported/pasted and organised; large-scale hierarchy may require scripting or manual curation. |
| Hudu | Partial | Best via curated import/migration approach. (Note: CSV-based imports exist for certain data types; dedicated bulk import packs are planned.) |
| BookStack | Partial | Recommended via its native import formats and/or API workflows. Markdown pack can be adapted, but hierarchy limits apply. |
| Wiki.js | Partial | Suitable via API-based import scripts (HTML or Markdown). Best for teams comfortable with a scripted migration workflow. |
| Document360 | Not supported (HTML import) | HTML import is not the primary path. If you use Document360, we recommend an alternate conversion workflow. |
| DokuWiki / MediaWiki | Not supported (direct) | These typically rely on wiki-specific markup and plugins. Use Markdown packs only with a planned conversion/migration. |
CSV support: CSV bulk import will be supported in later versions for platforms that provide stable, validated CSV schemas and predictable field mappings.
Our role as your guide
COGNITO IT PTY LTD exists to provide clarity, structure, and a ready-made operating system—so you can run mature, secure IT operations without starting from a blank page. Customers come first: the deliverables are built to be usable by operators, defensible to auditors, and legible to boards.
Our mission
To bring operational maturity within reach for every IT team.
Our vision
A world where IT operations are predictable, processes are standardised, evidence is ready, and compliance is achievable.