trio.so
Templates

IT Governance Policy Template (Free Word + PDF)

Free IT governance policy template in Word and PDF, with an Excel tracker: 17 sections, a RACI, decision rights, KPIs and a framework example.

Mountain landscape representing leadership perspective and vision
Written by
Atena Ladchartabi

Content writer, trio.so

Published on
Modified on

An IT governance policy says who decides what about technology in your company: who sets IT priorities, who approves an IT investment and up to what amount, how much IT risk you accept, and how the board and management check that IT delivers. This free IT governance policy template gives you that policy as an editable Word document with 17 sections, written for companies of 50 to 1,000 people.

Every decision sits in [brackets] with a default you can keep or change. The download also includes a PDF guide with a one-page IT governance framework example and a worked example of a 200-person company, and an Excel tracker for your RACI, decisions, investments, policies, risks, KPIs and steering committee meetings. The policy maps to COBIT 2019, ISO/IEC 38500:2024, NIST CSF 2.0 and ISO/IEC 27001:2022 by ID.

Preview of the IT governance policy template: Word policy, PDF guide and Excel tracker
Preview of the IT governance policy template: Word policy, PDF guide and Excel tracker

In short

  • IT governance is the board and senior management setting direction for IT, deciding within clear limits and checking results. IT management runs IT inside that direction.
  • The core of the policy is decision rights: who decides on strategy, investments, architecture, risk, vendors and exceptions, up to which amount.
  • Set approval thresholds by the total cost over three years, so a SaaS subscription can't slip under a limit that a purchase would hit.
  • Give each governance activity exactly one accountable person in a RACI.
  • Track a short list of KPIs with targets, and have the steering committee discuss only the reds and ambers.

What Is an IT Governance Policy?

An IT governance policy is a document the board or owners approve that sets how the company directs and oversees its use of IT. It names the governance bodies and roles, gives each one its decision rights, sets the approval thresholds for IT spending, states the risk appetite, and says which measures the board and management review and how often. The day-to-day records, such as decisions, investments, risks and KPIs, live in a tracker.

It is also the IT governance document people search for: the single place that explains your IT governance framework. The other IT documents sit under it. The information security policy, the acceptable use policy and the access control policy say what the rules are; the governance policy says who sets those rules and who approves them.

An ICT governance policy is the same document under another name.

Why IT Governance Is Essential

Without governance, IT decisions get made wherever the budget sits. A business unit buys a SaaS tool nobody reviewed, two projects compete for the same engineers, a risk is accepted by whoever happened to be in the room, and nobody can tell the board whether last year's IT spend delivered what it promised. A written policy fixes six things:

  • Alignment with business goals: IT priorities come from the business plan, and every investment has a business owner who answers for its benefits.
  • Clear decision rights: people know what they can decide alone, what needs the CIO, and what goes to the steering committee or the board.
  • Risk taken knowingly: IT risks are rated the same way across the company, and only the right person can accept a high one.
  • Cost control: approval thresholds and a portfolio view stop duplicate tools and projects that drift over budget without anyone deciding to continue.
  • Accountability and transparency: decisions are logged with who made them and why, which an auditor, an investor or a new manager can follow. It also brings shadow IT into the open, because buying outside the process breaks the policy.
  • Regulatory and audit readiness: laws and frameworks that apply to you, such as data protection law, sector rules, SOC 2 or ISO/IEC 27001, expect leadership oversight, documented roles and reviewed policies. The governance policy is where you show it.

A policy does not make IT governance happen on its own. It works when a steering committee holds its meetings on schedule, looks at the same dashboard each time, and records what it decided. The tracker in this download is built around that rhythm.

IT Governance vs IT Management

The two are easy to mix up, and the policy works better when you keep them apart.

IT governanceIT management
WhoThe board, owners and the IT steering committeeThe CIO or IT lead and the IT team
QuestionAre we doing the right things with IT, and is it working?Are we doing things right?
ActivitiesEngage stakeholders, evaluate, direct, monitorPlan, build, run, monitor
OutputsStrategy, budget, risk appetite, decision rights, policiesProjects, services, standards, procedures, reports
RhythmQuarterly committee, yearly board reviewDaily, weekly and monthly operations

ISO/IEC 38500:2024 frames governance as the governing body engaging stakeholders, evaluating, directing and monitoring, while management runs IT within the framework the governing body sets. COBIT 2019 makes the same split: its Evaluate, Direct and Monitor domain holds the governance objectives, and four other domains hold the management objectives.

Key Components of an IT Governance Policy

A policy that only says "IT will be aligned with the business" gives nobody anything to follow. The template has 17 sections in four parts: setting direction, deciding, controlling risk and overseeing results.

The 17 sections of the IT governance policy template, grouped into four parts
The 17 sections of the IT governance policy template, grouped into four parts
  1. Purpose and principles: what the policy is for, and five governance principles based on the ISO/IEC 38500:2024 model, in plain words.
  2. Scope: all IT the company owns, rents or uses, including SaaS bought by business units.
  3. Governance structure: board, IT steering committee, CIO or IT lead, security lead, business and system owners.
  4. Decision rights: who decides on strategy, investment, architecture, risk, vendors, policies, changes and exceptions.
  5. IT strategy alignment and planning: a yearly planning cycle tied to the business plan, with a two-page IT strategy.
  6. Portfolio and investment approval: four approval thresholds by three-year cost, business cases and benefits reviews.
  7. Policy hierarchy: policy, standard and procedure: who approves each, how often each is reviewed, and staff training.
  8. Risk management and risk appetite: a 5 x 5 rating, who may accept each rating, and a risk appetite statement to complete.
  9. Information security governance: where the security lead and the security policy fit, and admin access reviews.
  10. Asset and device management: inventory of hardware, devices and installed software, owners and lifecycle.
  11. Vendor and cloud service governance: approval of new vendors and SaaS, criticality and yearly reviews.
  12. Change and architecture governance: who approves which changes, architecture standards and exceptions to them.
  13. Performance measurement: KPIs with targets, amber limits and owners, reviewed by the committee.
  14. Compliance and audit: the list of obligations, the audit plan, findings and evidence.
  15. Exceptions: who approves one, for how long, with which compensating control.
  16. Review: a yearly review, the events that trigger an early one, and breaches.
  17. Definitions: governance vs management, decision rights, RACI, risk appetite and more.

Appendices add a RACI matrix with 16 activities, a decision rights and approval threshold table, a KPI starter set with 16 measures, a steering committee charter with a standing agenda, and a framework mapping. Training and awareness sit in section 7: owners tell staff about new and changed rules, new hires cover them during onboarding, and all staff repeat the training every [12] months.

Governance Structure and RACI

Most companies of 50 to 1,000 people need four levels. The board or owners approve strategy, budget and risk appetite. An IT steering committee, chaired by the CEO or COO with the CFO, the CIO or IT lead, the security lead and the heads of the main business units, decides within limits every quarter. The CIO or IT lead runs IT. Business and system owners sponsor projects and own their systems and data.

Four governance levels: direction goes down, reports go up, and the tracker holds the records
Four governance levels: direction goes down, reports go up, and the tracker holds the records

A RACI matrix says who is responsible (R), accountable (A), consulted (C) and informed (I) for each activity. The one rule that matters: exactly one A per row. Here are nine of the 16 rows in Appendix A:

ActivityBoard or ownersIT steering committeeCIO or IT leadSecurity leadFinanceBusiness and system owners
Approve the IT governance policyARCCII
Set IT strategy and prioritiesARRCCC
Approve the annual IT budgetARCIRC
Approve investments of [250,000] or moreARCCCC
Approve investments of [50,000] up to [250,000]IARCCC
Set risk appetiteARCCCI
Accept a high riskIARCIC
Approve architecture and technology standardsARCC
Approve the information security policyIACRC

In a small company one person can hold several roles; the CEO may chair the committee and act for the board. Write the names down anyway. The tracker's RACI tab flags any row without exactly one A.

Decision Rights and Approval Thresholds

Decision rights are the part of the policy people use most. For each area, the template names who proposes, who decides and when a decision goes up a level:

AreaDecidesGoes up a level when
IT strategy and prioritiesBoardThe committee recommends; the board approves
IT investmentPer the threshold tableCost above the approver's limit, or a business case is missing
Architecture and standardsSteering committeeA project wants a technology outside the standards
Security risk acceptancePer the risk ratingHigh risks go to the committee; critical risks to the board
Vendors and cloud servicesCIOCritical vendors go to the committee
Policies and standardsPer the policy hierarchyPolicies to the committee; standards to the CIO; procedures to the process owner
ChangesCIO (major); IT lead (standard)Changes with high business impact go to the committee
ExceptionsCIO (standards, procedures); steering committee (policies)It is an exception to a policy, or it raises a high risk

For investments, the threshold is the total cost over three years: the purchase plus three years of running costs. That way a SaaS subscription is judged the same way as a purchase.

Four approval levels by three-year cost, from the IT lead to the board
Four approval levels by three-year cost, from the IT lead to the board
Total cost (3 years)Approved byWhat is needed
Under [10,000]IT leadWithin the approved IT budget; no business case needed
[10,000] up to [50,000]CIOShort business case; finance consulted
[50,000] up to [250,000]Steering committeeFull business case with benefits, risks and running costs
[250,000] or moreBoardFull business case; committee recommendation first

The amounts are placeholders; set them with your CFO so they match your finance approval limits. Two rules go with them: nobody splits a purchase to stay under a limit, and a project more than [10%] over budget or [two months] late goes back to whoever approved it. Our IT budget template helps with the numbers behind the business case.

Risk Appetite, Security and Assets

Section 8 rates each IT risk by likelihood and impact from 1 to 5. The score sets who may accept the risk instead of treating it: low (1 to 4) the IT lead, medium (5 to 9) the CIO, high (10 to 16) the steering committee, and critical (20 to 25) the board. You write your own risk appetite statement in the brackets, for example that you don't accept high risks to customer data or payments without board approval. Our guide to IT risk management covers the risk process in more depth.

Sections 9 to 12 connect governance to the controls underneath it: the security lead owns the information security policy and reports to the committee; IT keeps an inventory of hardware, devices and installed software with an owner for each; new vendors and SaaS are approved before purchase; and changes follow a change process with the CIO approving major ones. Each of these has its own detailed policy. The IT security policy template, IT asset management policy template, vendor management policy template and IT change management template cover them.

IT Governance KPIs

The committee can't oversee what it doesn't measure. Appendix C has 16 starter KPIs across strategy and value, risk and security, operations, compliance and governance itself. Pick eight to twelve, give each a target, an amber limit, a data source and an owner, and look at the reds and ambers at every meeting.

AreaKPITargetData source
Strategy and valueApproved projects within 10% of budgetat least 85%Investment register
Strategy and valueApproved projects on scheduleat least 80%Investment register
Strategy and valueIT spend against the approved budgetat most 100%Finance
Strategy and valueProjects with a benefits review doneat least 90%Investment register
Risk and securityHigh and critical risks past their treatment dateat most 0Risk register
Risk and securityLaptops and phones with disk encryption onat least 98%Device management tool
Risk and securityDevices with a screen lock policy appliedat least 98%Device management tool
Risk and securityDevices on a supported OS versionat least 95%Device management tool
Risk and securityKnown exploited vulnerabilities (CISA KEV) open past [14] daysat most 0Vulnerability findings
OperationsAvailability of critical servicesat least 99.5%Monitoring tool
OperationsMajor changes with an approved change recordat least 100%Change log
CompliancePolicies past their review dateat most 0Policy register
ComplianceExceptions past their expiry dateat most 0Exception register
ComplianceAudit findings closed by their due dateat least 90%Audit tracker
ComplianceCritical vendors reviewed in the last 12 monthsat least 100%Vendor register
GovernanceSteering committee meetings held as plannedat least 100%Committee log

Targets are starting points; set your own. Pull device measures, such as encryption, screen lock and OS versions, from your device management tool's reports rather than counting by hand.

IT Governance Frameworks: COBIT, ISO/IEC 38500, ITIL and NIST CSF 2.0

An IT governance framework is a published reference for how to structure governance. You don't have to adopt one in full; a policy can borrow the parts it needs. The main options:

  • COBIT 2019 (ISACA): 40 governance and management objectives in five domains. The five governance objectives sit in the Evaluate, Direct and Monitor domain: EDM01 Ensured Governance Framework Setting and Maintenance, EDM02 Ensured Benefits Delivery, EDM03 Ensured Risk Optimization, EDM04 Ensured Resource Optimization and EDM05 Ensured Stakeholder Engagement (ISACA, 2025).
  • ISO/IEC 38500:2024: guiding principles for governing bodies on the effective, efficient and acceptable use of IT. The third edition, published in February 2024, aligns its principles with ISO 37000, adds "engage stakeholders" to the evaluate, direct and monitor model, and describes a governance framework with six elements: direction, capability, policy, delegation, performance and accountability.
  • NIST CSF 2.0: the Cybersecurity Framework 2.0 (February 2024) added a Govern function with six categories: GV.OC Organizational Context, GV.RM Risk Management Strategy, GV.RR Roles, Responsibilities, and Authorities, GV.PO Policy, GV.OV Oversight and GV.SC Cybersecurity Supply Chain Risk Management.
  • ITIL (PeopleCert): IT service management. ITIL 4 describes a service value system with governance, guiding principles and 34 management practices. PeopleCert has released ITIL (Version 5), which keeps the value system and guiding principles, and plans to retire the ITIL 4 modules at the end of 2027. ITIL is about running IT well, so it complements a governance framework rather than replacing one.
  • ISO/IEC 27001:2022: for security governance, clause 5 covers leadership and commitment (5.1), the policy (5.2) and roles, responsibilities and authorities (5.3), and Annex A 5.1 to 5.4 cover policies, roles, segregation of duties and management responsibilities.
Four IT governance frameworks and what each is for
Four IT governance frameworks and what each is for
FrameworkPublisherUse it for
COBIT 2019ISACAA detailed reference for IT governance and IT audit; a good fit when your auditors already work with it.
ISO/IEC 38500:2024ISO and IECA short, board-level statement of how IT is governed; a good base for the policy's principles.
NIST CSF 2.0NISTGovernance of cybersecurity risk in particular; free to use.
ITILPeopleCert (AXELOS)Running IT services well (management), not governance by itself. Pair it with COBIT or ISO/IEC 38500.
ISO/IEC 27001:2022ISO and IECSecurity governance, when customers ask about ISO/IEC 27001 or you plan an audit against it.

Which framework should you choose? For most companies of 50 to 1,000 people, a mix works: ISO/IEC 38500 for the principles in section 1, the COBIT EDM objectives as a checklist for structure and audit, and NIST CSF 2.0 Govern for security risk. Add ISO/IEC 27001 clause 5 if you run an ISMS, and ITIL practices for IT operations. Choose COBIT in more depth if your auditors or lenders already use it.

IT Governance Framework Example: A 200-Person Company

Here is the whole framework on one page, the way the PDF shows it: the policy on top, three bodies with their own rhythm, five registers, and the data that feeds them.

IT governance framework example: policy, three bodies, five registers and their data feeds
IT governance framework example: policy, three bodies, five registers and their data feeds

The company in the worked example is a 200-person software and services company with offices in two countries, a CEO, a CFO, an IT lead with a team of four and a part-time security lead. The board of five approves the IT strategy, the budget and the risk appetite once a year. The COO chairs a steering committee with the CFO, the IT lead, the security lead and the heads of engineering and customer success, with a 90-minute meeting every quarter. The IT lead acts as CIO and approves spend up to [50,000]. Four decisions from its first two quarters:

DecisionDecided byWhat happened
A new CRM, 3-year cost 180,000Steering committeeBusiness case from the head of sales; security review of the vendor; approved with a benefits review after 12 months.
A laptop refresh of 60 devices, 90,000Steering committeeInside the approved budget, but above the IT lead's limit, so it goes to the committee as a single decision, not three smaller orders.
A design team wants a new file-sharing SaaSIT lead (non-critical vendor)Allowed after the security lead confirms it holds no customer data; added to the inventory and vendor register.
No MFA on a legacy finance app until it is replacedSteering committee (exception)High risk; compensating control: access only from managed devices on the office network; expires in [6 months].

On the first KPI dashboard, disk encryption on laptops and phones came in at 97% against a 98% target (amber), and only 62% of approved projects were within 10% of budget (red). The budget KPI went on the agenda, and the CRM project's scope was cut back to its approved budget. These numbers are an illustration, not a benchmark.

Sample clauses from the template, each saying who does what:

  • "A person may decide only within their decision rights. A decision outside them is referred up, not split into smaller decisions to stay under a limit."
  • "Every IT investment, including SaaS subscriptions and renewals, is approved at the level its total cost requires."
  • "Accepted risks have an end date and are reviewed by then."
  • "The committee discusses reds and ambers only. Each red gets an owner, an action and a date in the Decision log."

Free IT Governance Policy Template

IT governance is not a one-time project. The template is built so the policy keeps working after it is approved: a yearly review, a quarterly committee rhythm, and registers that show what was decided and why. The download has three files:

  • Word policy: 17 sections with document control and version history, and five appendices: RACI matrix, decision rights and approval thresholds, KPI starter set, steering committee charter and agenda, and the framework mapping.
  • PDF guide: the same policy, plus the structure, thresholds, framework choice, the one-page framework example and the 200-person worked example.
  • Excel tracker: RACI matrix, decision log, investment register, policy register, risk register, KPI dashboard, committee log, exception register, review calendar and a dashboard. It works out who must approve each investment and accept each risk, checks it against who did, and sets each KPI to red, amber or green. Formulas only, no macros.

How to roll it out in 90 days:

  1. Weeks 1 to 2: name the people in each role and fill in the RACI. Agree thresholds and risk bands with the CFO.
  2. Weeks 3 to 4: fill in the brackets in the policy, and load current projects, policies and top risks into the tracker.
  3. Weeks 5 to 6: choose eight to twelve KPIs and find a data source for each.
  4. Weeks 7 to 8: hold the first steering committee meeting with the standing agenda; recommend the policy and charter to the board.
  5. Weeks 9 to 12: board approval, then the decision log and review calendar go into daily use.

Framework Mapping and Audit Evidence

Each section of the template maps by ID to COBIT 2019, ISO/IEC 38500:2024, NIST CSF 2.0 and ISO/IEC 27001:2022. The mapping is our judgement; check the current official text before you rely on it.

SectionCOBIT38500CSF 2.027001
1. Purpose and principlesEDM01Clauses 5, 6GV.PO5.1, 5.2; A.5.1
2. ScopeEDM017.1GV.OC4.3
3. Governance structureEDM016.2, 7.2.7GV.RR5.3; A.5.2, A.5.4
4. Decision rightsEDM017.2.5GV.RR5.3; A.5.3
5. IT strategy alignment and planningEDM025.4GV.OC5.1
6. Portfolio and investment approvalEDM02, EDM045.3GV.RRNot mapped
7. Policy hierarchyEDM017.2.4GV.PO5.2; A.5.1
8. Risk management and risk appetiteEDM035.10GV.RM6.1
9. Information security governanceEDM035.10GV.RR, GV.PO5.1 to 5.3; A.5.1, A.5.2
10. Asset and device managementEDM047.2.3GV.OCNot mapped
11. Vendor and cloud service governanceEDM035.10GV.SCNot mapped
12. Change and architecture governanceEDM017.2.2GV.PONot mapped
13. Performance measurementEDM057.2.6GV.OV9.1
14. Compliance and auditEDM055.5GV.OC, GV.OV9.2
15. ExceptionsEDM035.10GV.RM6.1.3
16. ReviewEDM016.2.4GV.OV, GV.PO9.3; A.5.1

When an auditor, an investor or the board asks how IT is governed, expect to show the approved policy with its review date, the RACI and committee charter with names, committee minutes and board summaries, the decision log, investment approvals at the right level with business cases, the risk register with accepted risks signed off, the KPI history, the policy register, the exception register, and device reports for inventory, encryption and OS versions. For a broader review, see our IT audit checklist, ISO 27001 checklist and IT health check template.

Where trio.so Fits

trio.so does not do IT governance: decision rights, committees and oversight are people and process, and the templates in this download cover them. trio.so is device management, and it supplies the device data that governance decisions and KPIs need.

  • A device inventory for Windows, macOS, iOS and Android that lists hardware and installed apps, as asset data for the inventory and for spotting software nobody approved (section 10).
  • OS update policies for Windows, macOS, iOS and Android, and vulnerability findings matched to CVEs with CVSS, EPSS and CISA KEV data, for the risk register and the security KPIs (sections 8, 13).
  • Disk encryption (BitLocker, FileVault and encryption on phones) and screen lock status per device, as inputs for the device KPIs (section 13).
  • Built-in and custom console roles, so each admin gets only the device access their job needs (section 9).
  • A compliance engine with templates for frameworks such as ISO 27001, SOC 2 and NIST SP 800-53. You choose the frameworks you need and export the device evidence for your auditor (section 14).

Plans start at $5 per device.

Start free trial Book a demo

14-day free trial. No credit card required.

Sources. Last reviewed November 2026. Framework names and IDs identify their publishers' documents; descriptions are our own summaries. trio.so is not affiliated with or endorsed by ISACA, ISO, IEC, NIST or PeopleCert. COBIT is a trademark of ISACA; ITIL is a trademark of PeopleCert. Bracketed defaults, thresholds and targets are our suggestion, not a framework requirement. Size them to your company, and check your regulators', auditors' and investors' expectations before you adopt the policy.

Ready-to-use Templates

Must-have Template Toolkit for IT Admins

Explore All
Template Toolkit

Start your free trial

No credit card required
Full access to all features

Manage Every Device From One Console

trio.so brings device management, patching and security policies for Windows, macOS, Linux, iOS/iPadOS and Android into one console. Enroll a device and see it in the console within minutes.

14-day free trial. No credit card required.

trio.so brings device management, patching and security policies for Windows, macOS, Linux, iOS/iPadOS and Android into one console. Enroll a device and see it in the console within minutes.

Smiling womanAbstract geometric patternAbstract geometric patternSmiling womanSmiling woman

Frequently Asked Questions (FAQ)

Have questions? We've got answers. This section covers some of the most commonly asked questions related to this topic.

An IT governance policy is a document approved by the board or owners that sets how a company directs and oversees its use of IT: the governance bodies and roles, who decides what and up to which amount, the risk appetite, and which measures are reviewed and how often.

Purpose and principles, scope, governance structure, decision rights, IT strategy and planning, investment approval thresholds, the policy hierarchy, risk management and risk appetite, information security governance, asset and device management, vendor and cloud governance, change and architecture governance, KPIs, compliance and audit, exceptions, review and definitions. This template has all 17, plus a RACI matrix, a threshold table, a KPI starter set and a steering committee charter.

The best known are COBIT 2019 from ISACA, ISO/IEC 38500:2024 from ISO and IEC, the Govern function of NIST CSF 2.0, and ITIL from PeopleCert for IT service management. ISO/IEC 27001:2022 clause 5 covers leadership, policy and roles for information security. The PDF in this download includes a one-page IT governance framework example for a 200-person company.

IT governance is the board and senior management engaging stakeholders, evaluating options, setting direction and monitoring results. IT management is the CIO and IT team planning, building, running and monitoring IT within that direction. Governance asks whether IT is doing the right things; management asks whether things are done right.

For most companies of 50 to 1,000 people, a mix works: ISO/IEC 38500 principles in the policy, the COBIT 2019 EDM objectives for structure and audit, and NIST CSF 2.0 Govern for cybersecurity risk. Use COBIT in more depth if your auditors already work with it, and ITIL for running IT services.

It is the document that describes how IT is governed, usually the IT governance policy itself, supported by a RACI, a decision rights table, a steering committee charter and the registers that record decisions, investments, risks and KPIs. This template gives you all of them in Word, PDF and Excel.

At least once a year, and earlier after a major change in the business, a merger or acquisition, a serious incident, a new regulation or an audit finding about governance. The steering committee reviews it and recommends changes to the board.

Yes. The Word policy, the PDF guide and the Excel tracker are free to download and edit. Bracketed defaults, thresholds and targets are suggestions to size to your company.

Related

From the blog

The related industry news, interviews, technologies, and resources.