IT change management is the process that controls how you add, modify, or remove anything that could affect your technology services, so updates help the business instead of knocking it offline. For a small business, it comes down to four habits: write every change down, assess its risk, get the right person to approve it, and review the result afterward. This guide walks through each habit, the three change types, the change advisory board, and what a policy needs to say.
TL;DR
- A change is anything you add, modify, or remove that could directly or indirectly affect an IT service. Change management exists to make those changes safe and beneficial.
- Sort changes into three types: standard (pre-approved, low risk), normal (approved by risk level), and emergency (fast action to restore service or stop a threat).
- A sound process runs from request and risk review through approval, testing, implementation, verification, and closure, with a back-out plan at every step.
- A change advisory board can be two or three people at a small company. What matters is that someone with authority approves risky changes.
- Keep your policy short and scale the rigor to the system. Then track success rates and unplanned changes to improve.
Table of Contents
- What IT change management means
- Why small businesses need it
- The three types of IT changes
- The change control process, step by step
- The change advisory board
- What an IT change management policy should include
- Records, roles, and metrics
- Common mistakes to avoid
- Our perspective
- Put change control to work with Mavericks
- A simple starting plan for the next 30 days
- FAQ
- Sources
What IT change management means
The working definition most IT teams use is simple. A change is adding, modifying, or removing anything that could have a direct or indirect effect on services. That covers the obvious items, such as a firewall rule, a server patch, or a new phone system. It also covers quieter ones, like switching a cloud vendor, changing who has admin rights, or updating printer firmware.
The goal is stated plainly in Washington Technology Solutions’ process guide: enable beneficial change with minimal disruption while keeping service quality and availability intact. Change management is not meant to slow your business down. It is meant to stop the avoidable outage that follows a rushed, undocumented tweak.
For US financial institutions, the FFIEC IT Examination Handbook frames it as maintaining the integrity of hardware, software, firmware, and documentation while controlling and approving additions, modifications, or eliminations to technology assets. You may not be a bank, but the logic carries over to any business that depends on its systems.
A university framework puts the same idea in operational terms: approved production changes implemented with acceptable risk, including scheduling, documentation, approval, communication, implementation, testing, and monitoring. Notice how much of that list is communication and record keeping rather than technical work.
How it differs from organizational change management and release management
The phrase “change management” gets used for three different things, and mixing them up causes confusion.
- IT change management governs technology changes. ServiceNow notes that organizational change management generally addresses changes to employee roles and business processes instead.
- Release management is narrower. It focuses on planning and rolling out changes, including resources, sequencing, and deployment details, while change management requests, evaluates, authorizes, implements, and reviews them, according to the same ServiceNow explanation.
- Organizational change management is about helping people adopt a new way of working, such as a new CRM or a reorganized team.
If you roll out a new phone system, all three apply. IT change management decides whether and when the cutover is safe. Release management sequences the work. Organizational change management gets your staff comfortable using it.
Why small businesses need it
The usual failure in a small company is not malice or incompetence. It is a well-meaning fix made on a Friday afternoon, by one person, with nothing written down. Monday brings a broken integration and nobody who remembers what changed.
Change management addresses that directly. According to FFIEC, its purpose is to preserve confidentiality, integrity, and availability while implementing changes that support organizational goals. The Institute of Internal Auditors adds that effective change management relies on preventive, detective, and corrective controls and helps surface operational risks, control weaknesses, rework, unintended consequences, and system failure.
In plain terms:
- Preventive controls stop bad changes before they happen (approval, testing).
- Detective controls notice when something went wrong (monitoring, post-change checks).
- Corrective controls put things right (back-out plans, restores).
There is a security angle too. Unreviewed changes are how a stray open port, a forgotten admin account, or an unpatched device ends up on your network. If you are building a security program, change control is one of its quiet foundations. Our guide on five steps to a NIST CSF profile for small businesses shows where it fits.
The three types of IT changes
Not every change deserves a meeting. ITIL-style practice sorts changes into three types, as Atlassian’s change types overview explains.
| Change type | What it is | How it is approved | Small business example |
|---|---|---|---|
| Standard | Recurring, low-risk, documented | Pre-approved, so no full risk review each time | Creating a new user account from a checklist |
| Normal | Not an emergency, no pre-approved process | Approved according to risk | Moving file storage to a cloud platform |
| Emergency | Addresses an unexpected error or threat immediately | Expedited, usually to restore service or secure systems | Isolating a device after a ransomware alert |
Standard changes
Standard changes are low-risk, frequently performed, and documented, so each instance does not repeat the full risk assessment and approval. This is where small businesses gain the most. Write a short procedure once, get it approved once, and then let staff perform it without waiting.
Good candidates: onboarding and offboarding accounts, adding a printer to the network from a standard image, installing approved software from a catalog, and routine monthly patching within a defined window.

Normal changes
Normal changes are the everyday project work. Because there is no pre-approved path, each one gets approval according to its risk. A low-risk normal change might need only the IT lead’s sign-off. A change to your email system or firewall might need the owner as well.
Emergency changes
An emergency change responds to an unexpected error or threat and is usually aimed at restoring service or securing systems. Speed matters, but record keeping still does. Document what was done as soon as the situation is stable, and review it afterward. Emergency changes that happen often are a signal that something upstream is wrong.
The change control process, step by step
The FFIEC handbook lays out a sequence you can scale down to any size: request, review, approval, design and build, testing, implementation, verification, and closure. Here is how that looks in a ten-person office.
- Request. Someone describes the change. A good request records the justification, affected systems, impact and risk, timing, and a back-out plan. A shared form or ticket is enough.
- Review. Someone checks the request for viability and business practicality, and prioritizes it or asks for more information where needed, as FFIEC describes.
- Approval. Approval is proportionate to risk. A routine change needs a quick yes. A change touching customer data or core systems needs someone with real authority.
- Design and build. Prepare the change, ideally in a test environment or on a pilot device.
- Testing. Confirm the change works as intended and integrates with the systems around it.
- Implementation. Schedule it for a low-impact window and tell the people it affects before it happens, not after.
- Verification. Check that services behave normally.
- Closure and review. A post-implementation review checks whether the change succeeded and met its performance objectives. Close the record.
The back-out plan
The most skipped item on the request is the back-out plan, and it is the one that saves your Monday. Before any normal change, answer three questions: how will we know it failed, who decides to reverse it, and how long does reversal take? If the honest answer to the last one is “we don’t know,” test further before proceeding.
Changes that involve outside providers
Many small business changes depend on a vendor: a payment processor, a hosting provider, a booking platform. Swapping one is a change with real risk to customers. The principles are the same whatever the industry, and a walkthrough of planning a system migration shows how cutover timing, member communication, and fallback options map to the steps above.
The change advisory board
A change advisory board (CAB), sometimes called a change control board, is the group that reviews and decides on changes above the pre-approved level. CMS policy says such a board may operate at project or system level under a charter and procedures. It approves or rejects baseline change requests after evaluating scope, stakeholders, cost, schedule, compliance, risk, objectives, and budget.
Large organizations meet weekly with a dozen people. You do not need that. A workable small business CAB looks like this:
- Chair: the IT lead or the managed IT provider’s account lead.
- Business voice: an owner or department manager who knows what downtime costs.
- Technical reviewer: whoever will implement the change, or a second pair of eyes.
- Security reviewer: someone who checks how the change affects access and data.
Meet briefly on a set schedule, say weekly or every other week, and handle urgent items by message. Keep a one-page charter: who sits on it, what it can approve, and how emergencies are handled. The CMS description of a charter and procedures is a good model for that page.
What an IT change management policy should include
A policy turns good habits into expectations. CMS says policy should establish expectations for planning and performing change management across IT assets, and that the process should identify, prioritize, document, coordinate, review, approve, reject or defer, communicate, and implement changes while managing risk.
For a small business, a one- to two-page policy can cover:
- Purpose and scope: which systems and which people it applies to.
- Change types: your definitions of standard, normal, and emergency, with a list of pre-approved standard changes.
- Roles: who requests, who approves, who implements, who verifies.
- Required record: justification, affected systems, impact, timing, back-out plan, test results, and closure notes.
- Approval rules: who signs off at each risk level.
- Communication: who is told, and when.
- Emergency procedure: who may act immediately and how it is documented afterward.
- Review: how often you look at results and update the policy.
Scale it to your size
CMS says the rigor of policy should be scaled for large and small projects or systems, so that the level of control matches the need to protect assets. Practically, that means a password reset needs no paperwork, a new server needs a plan, and anything touching customer or financial data gets a second approver. Related policies work the same way, for example a risk-tiered remote access policy that tightens controls as privileges rise.
Records, roles, and metrics
Three things keep a process alive after the first enthusiasm fades.
Roles. FFIEC points to responsible staff, reviewers, stakeholders, and approval committees. Even if one person holds two roles, name them. Separating the person who requests a change from the person who approves it is worth doing wherever you can.
Records. Keep the request’s justification, affected system, impact analysis, timing, and back-out plan, plus documented testing and closure. A ticketing system is ideal, but a shared spreadsheet beats memory. Your records also feed your asset inventory, which is why IT asset lifecycle management and change control work best together.
Metrics. FFIEC’s examples include implementation time, success rates, and planned versus unplanned changes. Review three numbers monthly:
- What share of changes succeeded without a back-out?
- How many changes were emergencies, and why?
- How long did changes take from request to closure?
A rising share of unplanned changes tells you that planning, patching, or monitoring needs attention.
Common mistakes to avoid
- Treating every change the same. Heavy approval for trivial tasks teaches staff to bypass the process. Use standard changes.
- No back-out plan. If reversal is unclear, the change is not ready.
- Skipping communication. Staff who are told in advance report problems faster and blame IT less.
- Letting emergencies become the norm. Review each one and fix the cause.
- Forgetting devices at the edge. Printers, phones, cameras, and USB devices all change too. See our practical guides on print security controls and USB device control.
- Never closing the loop. Without post-implementation review, you repeat mistakes.
Our perspective
We see the same pattern across small and mid-sized businesses in Ohio and Michigan. The business has a handful of systems that matter a great deal, nobody whose full-time job is to look after them, and a history of changes that live in one person’s head.
That is the gap an outsourced IT department is built to close. Our approach to managed IT is proactive support with 24/7 monitoring, so many changes get planned, scheduled, and verified instead of improvised in the middle of a workday. When something does go wrong, you reach a local, USA-based help desk with no offshore call center, and our average help desk response is under 12 minutes.
We also think change management works best when one provider sees the whole stack. A phone system change, a firewall rule, a cloud migration, and a printer fleet update all touch each other. When IT, security, voice, print, and cloud sit with a single partner, the impact review is more complete because the people reviewing know the environment.
If you do not have the budget for a full-time IT director, fractional IT leadership can own the policy, chair the change review, and keep the roadmap honest. You get the discipline without the headcount.
Jeffrey
Put change control to work with Mavericks
If you would rather not build this alone, we can run it with you. Mavericks Office Solutions operates as an outsourced IT department for small and medium businesses, covering managed IT services, cybersecurity, cloud hosting, voice, and managed print, with a local Ohio help desk behind all of it.

For executive-level planning without a full-time hire, our fractional IT leadership can help you write the policy, set up the review board, and manage the roadmap. If you are weighing providers, our scorecard for choosing a managed IT provider and these five questions to ask your IT provider are good places to start. Ready to talk? Reach us through mavericksofficesolutions.com.
A simple starting plan for the next 30 days
You can put the basics in place in a month without new software.
- Week 1: List your critical systems and who owns each. Draft the one-page policy using the outline above.
- Week 2: Pick five to ten recurring tasks and write them up as pre-approved standard changes, each with a short checklist.
- Week 3: Set up a request form or ticket template that captures justification, affected systems, impact and risk, timing, and back-out plan. Name your review group and set its meeting time.
- Week 4: Run your first review meeting. Close every completed change with a short note on what worked and what did not.
After the first month, start tracking your three metrics and adjust. If you are mapping this to a broader security framework or budget, our guide to NIST controls and small business IT budgets can help you decide what to keep in-house and what to outsource.
FAQ
What is the difference between change management and change control?
Change management is the whole discipline: policy, roles, process, and review. Change control usually means the approval and tracking steps within it, where a request is evaluated, authorized, and recorded. In practice, most IT teams use the terms close to interchangeably.
Does a small business really need a change advisory board?
You need the function, not a large committee. Two or three people who review higher-risk changes, meet briefly on a schedule, and keep a short charter are enough. Pre-approved standard changes keep routine work out of the meeting entirely.
What is an emergency change?
An emergency change responds to an unexpected error or threat and is usually meant to restore service or secure systems right away. Act first with the right person’s authority, then document it and review it afterward so the cause gets fixed.
What should I measure to know the process is working?
Track implementation time, success rates, and the balance of planned versus unplanned changes, the kinds of measures the FFIEC handbook lists. A steady rise in successful, planned changes means the process is paying off.
Sources
- FFIEC IT Examination Handbook: Change Management
- Washington Technology Solutions: Change Management Process Guide
- University of Chicago: IT Services Change Management Framework 3.0
- Atlassian: Change management types
- The IIA: IT Change Management Audit Guide
- ServiceNow: What is IT Change Management?
- CMS Policy for Change Management