# ISO 20000 Service Management Plan > Create and validate the service management plan for ISO/IEC 20000-1:2011 per Clause 4.5.2. Covers SMS objectives, governance structure, PDCA approach for each process area, resource planning, documentation framework, risk management, and implementation timeline. SMS plan validator checks all required elements are present. Tags: ISO 20000, SMS, Service Management Plan, IT Service Management, Governance ## Example Prompts - Create a service management plan for our ISO 20000 certification - Define SMS objectives and governance structure for our organization - Build an implementation timeline for ISO 20000 certification - Validate our service management plan covers all Clause 4.5.2 requirements URL: https://rakenne.app/skills/iso20000-service-management-plan/index.md Try this skill: https://rakenne.app/a/?skill=iso20000-service-management-plan ## Overview The service management plan is the master planning document for your SMS, required by Clause 4.5.2. It defines how the organization will achieve its service management objectives — covering governance, the PDCA (Plan-Do-Check-Act) approach for each process area, resource planning, documentation framework, risk management, and a phased implementation timeline. This is the document that ties together everything from the organization profile, scope, service catalog, and gap assessment into a single actionable plan. The skill reads all four prerequisite artifacts to produce a plan that is grounded in your real organizational context rather than generic template content. Gap assessment findings become remediation tasks with owners and timelines. Service catalog entries inform process-specific PDCA cycles. The organization profile's governance structure and resource commitments flow directly into the plan's governance and resource sections. For a step-by-step walkthrough, see the [**ISO 20000 SMS workspace tutorial**](/learn/tutorials/iso20000-sms-workspace-guide/). ### What It Covers - **SMS objectives** — measurable, time-bound targets aligned with business goals and gap assessment findings - **Governance structure** — roles, responsibilities, authorities, decision-making bodies, and communication plan - **PDCA approach** — Plan-Do-Check-Act cycle defined for each SMS process area (Clauses 5-9) - **Resource plan** — personnel, ITSM tools, training needs, and budget - **Documentation framework** — document types, naming conventions, review and approval process, retention, and version control (Clause 4.3) - **Risk management** — risks to SMS implementation, assessment methodology, and mitigation strategies - **Implementation timeline** — phased roadmap from foundation through certification audit preparation ## Example Conversation > **You:** We need to create the service management plan for our ISO 20000 certification. All prerequisites are in place — organization profile, scope, catalog, and gap assessment. > > **Agent:** I've loaded all four prerequisites. Your gap assessment shows an average maturity of 1.8 with 8 critical gaps, primarily in Clause 4 (governance), Clause 8.2 (problem management), and Clause 9.1 (configuration management). Your target is Stage 1 audit in 6 months. Let me build the plan around that. > > First, let me define the SMS objectives. Based on your gap assessment and business drivers, I'd propose: > > 1. **Achieve ISO 20000 certification within 9 months** (Stage 1 at month 6, Stage 2 at month 9) > 2. **Reach maturity level 3 or above for all 15 clause areas** (currently 1.8 average) > 3. **Achieve 99.5% SLA compliance** across all in-scope services within 12 months > 4. **Reduce mean incident resolution time by 25%** within 6 months > > Do these align with your business objectives? > > **You:** Yes, but add one more — we want to eliminate the spreadsheet-based CMDB and move to a proper tool within the first 3 months. > > **Agent:** Added: **Implement a tool-based CMDB within 3 months, replacing spreadsheet-based configuration tracking.** Now let me define the governance structure. Based on your organization profile: > > - **SMS Manager**: Sarah Chen — day-to-day management of the SMS > - **Management Review Board**: Managing Director (chair), SMS Manager, and process owners — meets monthly > - **Change Advisory Board (CAB)**: Infrastructure Lead (chair), Network Lead, Service Desk Manager — meets weekly > - **Service Review**: SMS Manager with each client — quarterly > > Does that match your intended structure? > > **You:** Yes, that's right. The MD wants to chair the management review personally. > > **Agent:** Good — that demonstrates top management commitment, which auditors look for. Now let me define the PDCA approach for each process area. For example, for **Incident and Service Request Management (Clause 8.1)**: > > - **Plan**: Document the incident process with categorization, prioritization matrix, and escalation paths > - **Do**: Operate the process through Jira Service Management, route alerts from Nagios > - **Check**: Weekly incident metrics review, monthly SLA compliance reporting > - **Act**: Post-major-incident reviews, quarterly process improvement cycle > > I'll define similar PDCA cycles for all 13 process areas. Now for the implementation timeline — I recommend 5 phases based on your gap assessment roadmap... > > *[The agent continues through resources, documentation framework, and risk management...]* > > Let me run the `sms_plan_validator`... > > **Result:** PASS. All required elements present: 5 measurable objectives, governance structure with key roles, PDCA approach for all process areas, resource plan covering personnel/tools/training, documentation framework per Clause 4.3, and 5-phase implementation timeline with milestones. ## Sample Output Excerpt The skill produces a comprehensive markdown plan document. Here is a representative excerpt showing the objectives, governance, and timeline sections. --- ```markdown # Service Management Plan — Apex IT Services Ltd ## 1. SMS Objectives | # | Objective | Metric | Target Date | |---|-----------|--------|-------------| | 1 | Achieve ISO 20000 certification | Stage 2 audit pass | Month 9 | | 2 | Reach maturity level 3+ for all clause areas | Maturity score per clause | Month 6 | | 3 | Achieve 99.5% SLA compliance | Monthly SLA compliance % | Month 12 | | 4 | Reduce mean incident resolution time by 25% | MTTR from Jira | Month 6 | | 5 | Implement tool-based CMDB | Migration complete, spreadsheets retired | Month 3 | ## 2. Governance Structure ### Roles and Responsibilities | Role | Person | Responsibilities | |------|--------|-----------------| | SMS Manager | Sarah Chen | Day-to-day SMS management, process coordination, audit liaison | | Top Management Sponsor | James Wright, MD | Budget approval, management review chair, escalation authority | | Incident Process Owner | Mike Torres | Incident and service request process design, monitoring, improvement | | Change Process Owner | Priya Patel | Change and release process design, CAB chair | ### Decision-Making Bodies | Body | Chair | Frequency | Purpose | |------|-------|-----------|---------| | Management Review Board | Managing Director | Monthly | SMS performance review, resource decisions, strategic direction | | Change Advisory Board | Infrastructure Lead | Weekly | Change assessment, approval, scheduling | | Service Review | SMS Manager | Quarterly | Per-client service performance and satisfaction review | ## 5. Implementation Timeline | Phase | Timeline | Focus | Key Milestones | |-------|----------|-------|---------------| | 1 — Foundation | Months 1-2 | Governance, policy, documentation framework | SMS policy approved, roles formally assigned | | 2 — Process Design | Months 2-3 | Process documentation for all 13 areas | All process documents drafted and reviewed | | 3 — Implementation | Months 3-5 | Process rollout, CMDB migration, training | CMDB live, staff trained, processes operational | | 4 — Monitoring | Months 4-6 | KPI measurement, internal audit | Internal audit complete, management review held | | 5 — Certification | Months 6-9 | Stage 1 and Stage 2 audit preparation | Stage 1 pass (month 6), Stage 2 pass (month 9) | ``` ## Extension Tools ### `sms_plan_validator` Validates the service management plan document for all required elements per Clause 4.5.2: | Check | What It Does | |-------|-------------| | **Objectives** | Plan must contain measurable objectives (looks for numeric targets, percentages, KPI references) | | **Governance structure** | Roles and responsibilities section must define key SMS roles | | **PDCA approach** | Plan-Do-Check-Act or continual improvement approach must be documented | | **Resource plan** | Personnel, tools, and training sections must be present | | **Documentation framework** | Document control, naming conventions, or record retention must be defined (Clause 4.3) | | **Implementation timeline** | At least two phases or milestones must be documented | The validator scans the markdown content for required section headings and keywords, ensuring the plan addresses every element that Clause 4.5.2 requires. It flags missing sections as errors and provides specific guidance on what needs to be added. ## Getting Started Run all four prerequisite skills first: *Organization Profile*, *SMS Scope*, *Service Catalog*, and *Gap Assessment*. The service management plan reads all of these to build a plan grounded in your real organizational context, scope, services, and identified gaps. Have this information ready: - Business objectives that the SMS should support - Budget and staffing available for the SMS implementation - Target dates for Stage 1 and Stage 2 certification audits - Preferred governance structure (who chairs management reviews, how often the CAB meets) - Training needs and any planned tooling changes The service management plan is the capstone document of the ISO 20000 SMS workspace — it ties together everything produced by the earlier skills into a single, auditor-ready implementation roadmap. --- Back to [Skill Library](https://rakenne.app/skills/index.md)