We e-mail the editable toolkit files to the address you gave, usually within 2 to 3 business days.
Risk & Governance

What Documents You Need for COBIT 2019 Implementation

What Documents You Need for COBIT 2019 Implementation
In short

Find out which documents a COBIT 2019 implementation needs, from governance scope and policies to RACI charts, procedures, and capability assessments.

In this article
  1. Start with what COBIT actually asks you to do
  2. The core documents, in a sensible order
  3. A quick reference table
  4. Common mistakes to avoid
  5. Build or start from templates?
  6. Frequently asked questions

COBIT 2019 is a framework, not a certifiable standard. There is no clause that says "you shall maintain these 20 documents". That leaves many teams unsure what to write, how much detail to include and what an auditor, board member or regulator will expect to see.

The practical answer is that you need documents that show how IT governance is designed, who is accountable, how each relevant objective is carried out, and how you measure and improve it. This article lists those documents and suggests an order for creating them.

Start with what COBIT actually asks you to do#

COBIT 2019, published by ISACA, defines 40 governance and management objectives. Five are governance objectives (the Evaluate, Direct and Monitor domain, EDM). The rest are management objectives grouped into four domains: Align, Plan and Organize (APO); Build, Acquire and Implement (BAI); Deliver, Service and Support (DSS); and Monitor, Evaluate and Assess (MEA).

It also uses design factors to tailor the governance system to your organisation, and capability levels to measure how well each process performs. Your documents should therefore answer four questions:

  • What does our governance system need to achieve, and for whom?
  • Which objectives are in scope, and why?
  • How is each in-scope objective carried out, and by whom?
  • How do we know it works, and how do we improve it?

You do not have to document all 40 objectives in full on day one. Scope first, then write in depth where it matters most.

The core documents, in a sensible order#

1. Scope, context and design documents#

  • Governance scope and objectives statement: which parts of the enterprise and its technology are covered, and the business drivers behind the programme.
  • Design factor assessment: a record of how you considered your enterprise strategy, risk profile, compliance requirements, IT sourcing model and similar factors when tailoring the system.
  • Prioritised objectives list: which governance and management objectives are in scope, with a short rationale for each.

These are the most commonly skipped documents, and the ones that most often cause trouble later. Without them, the rest looks like a generic copy of the framework.

2. Governance framework documents#

  • IT governance charter or policy: management's intent, principles and authority for IT governance.
  • Roles, responsibilities and RACI matrix: who is responsible, accountable, consulted and informed for each in-scope objective.
  • Governance bodies and terms of reference: steering committee, risk committee or equivalent, with membership, meeting frequency and decision rights.
  • Reporting and escalation model: what goes to the board and executives, how often, and in what format.

3. Policies#

Policies turn objectives into rules people can follow. The set you need depends on your scope, but a typical IT governance programme includes policies for:

  • Information security and access control
  • Risk management
  • Change and release management
  • Incident and problem management
  • Third-party and supplier management
  • Data and asset management
  • Business continuity

If you already run an ISO 27001 ISMS or ITIL-based service management, reuse what exists and map it to COBIT instead of rewriting it. Our guides on ISO 27001 documentation and ITIL documentation show what those programmes typically produce.

4. Procedures and process documents#

For each in-scope objective, document how the work is done: inputs, activities, outputs, owners and the records produced. Examples include:

  • Managed strategy and enterprise architecture (APO)
  • Managed risk and managed security (APO)
  • Managed changes and managed projects (BAI)
  • Managed operations, service requests and incidents (DSS)
  • Managed performance and conformance monitoring (MEA)

Keep these short. A one- to three-page procedure that people actually use is worth more than a long document nobody opens.

5. Checklists, registers and records#

These are the day-to-day evidence that the system operates:

  • IT risk register with owners and treatment status
  • Change, incident and problem records
  • Supplier and service-level review records
  • Asset and configuration inventories
  • Meeting minutes and decision logs from governance bodies
  • Internal review or audit checklists

6. Performance and capability documents#

  • Gap assessment: current state against target state for each in-scope objective.
  • Capability level assessment: current and target capability levels, with the evidence behind each rating.
  • Metrics and KPI definitions: what you measure, the data source, the owner and the reporting frequency.
  • Improvement roadmap: prioritised actions, owners and target dates.

A quick reference table#

Document groupPurposeTypical owner
Scope and designTailor COBIT to your enterpriseCIO / governance lead
Governance frameworkAuthority, roles, decision rightsExecutive sponsor
PoliciesSet rules and expectationsFunction heads
ProceduresDefine how work is doneProcess owners
Checklists and recordsProve the system operatesProcess operators
Performance and capabilityMeasure and improveGovernance lead / internal review

Common mistakes to avoid#

  • Documenting everything at once. Prioritise objectives using your design factors and start with the highest-value ones.
  • Copying the framework text. COBIT describes good practice. Your documents must describe what your organisation actually does.
  • No named owners. A procedure without an accountable person tends to go stale quickly.
  • Ignoring existing documents. Map current ISO, ITIL or internal controls instead of duplicating them.
  • Skipping the gap assessment. Without a baseline, you cannot show improvement.

Build or start from templates?#

Writing a full set from scratch takes time and requires someone who knows the framework well. Many teams start from a structured set of templates and adapt it to their context. Whichever route you take, review every document against your actual practices, because a template that does not match how you work will not stand up to scrutiny.

The COBIT Toolkit from AdWiser is built for this approach. It provides editable policies, procedures, controls, checklists and worked examples based on COBIT 2019, along with a gap assessment checklist, so you start from a complete structure instead of a blank page.

Frequently asked questions#

Is COBIT 2019 certifiable?#

No. COBIT is a framework for governance and management of enterprise information and technology, not a certification standard. Organisations use it to design and improve their governance system, and may be assessed against it internally or by a third party, but the documents you keep are your own choice based on scope and risk.

Do I need to document all 40 objectives?#

Not necessarily. Use your design factor assessment to decide which objectives matter for your organisation, and document those first. You can extend coverage over time as the programme matures.

How is COBIT documentation different from ISO 27001 documentation?#

ISO 27001 focuses on an information security management system and has defined mandatory documented information. COBIT covers wider IT governance and management, and leaves the form of documentation more flexible. Many organisations use both, with COBIT providing the governance layer and ISO 27001 the security detail.

If you are planning a COBIT 2019 programme and want a documented starting point, the COBIT Toolkit is worth a look, or you can contact the AdWiser team to discuss your scope.

Share this guide

Ready to put this into practice?

Start with the COBIT Toolkit and adapt it to your organisation, or talk to us about implementation support.

Chat on WhatsApp