What an IT change management process does for a small business
An IT change management process is the agreed path every change takes: someone requests it, someone assesses the risk, someone approves it, and it is scheduled, carried out, tested and recorded, with the documentation updated at the end. Without one, a firewall rule added on a Friday afternoon or a Conditional Access policy switched off “for a minute” becomes next quarter’s mystery.
The process does not need to be heavy. For a 20-person dental office or CPA firm it can be a short form, a named approver and a shared calendar. What matters is that every change leaves a record, and that the record matches what is actually configured.
OC Security Audit designs and audits change processes for businesses in Irvine, across Orange County and Southern California, and remotely nationwide. We do not run your changes. Your IT team or MSP does, or our implementation partner IT Perfection can carry them out for you.

Standard, normal and emergency changes
Sorting changes into three types keeps routine work fast and puts the review effort where the risk is.
Standard
Low-risk, repeatable and pre-approved: adding a user to a group, replacing a laptop, renewing a certificate. Documented once as a template, then logged each time it is used.
Normal
Assessed and approved before work starts: a new firewall rule or VPN, a Conditional Access change, a server upgrade, a new SaaS integration. Most of the process below applies to these.
Emergency
Made to restore service or contain an active threat. Approved by a named person, even by phone, then recorded and reviewed afterward. We recommend completing the record within one business day.
The IT change management process, step by step
Six stages cover the full path from request to close.
What, why, which systems, who asks
Risk, impact and a written rollback plan
Named approver, agreed window
Do the work, confirm it works
Diagrams, registers, settings record
Before and after compared, record closed
The rollback plan is written before approval, not after a change fails. And a change is not closed until the documentation it affects is updated: the firewall rule-justification register, the network diagram, or the cloud settings record.
What each step records
These are the fields we build into a change record template.
| Step | What is recorded | Who |
|---|---|---|
| Request | Description, business reason, systems and sites affected, requested date | Requester |
| Risk and impact | Risk rating, users and services affected, downtime expected, dependencies | IT lead or MSP engineer |
| Rollback plan | How to undo the change, how long it takes, the point at which you roll back | Implementer |
| Approval | Approver name, date, any conditions | Business owner and technical approver |
| Schedule | Change window, people notified, freeze-window check | IT lead |
| Implement | What was actually done, by whom, start and end time, deviations from the plan | Implementer |
| Test | How success was confirmed, test results, who confirmed | Implementer and a user |
| Documentation | Which records were updated, before and after configuration or a link to the diff | Implementer |
| Close | Outcome (successful, rolled back, failed), lessons learned | IT lead |
A change advisory board for a 20-person firm
Large enterprises run weekly boards with a dozen members. A small firm needs the same discipline with far less ceremony.
Who approves
Two or three people: the owner or practice manager for business impact, the IT lead or MSP engineer for technical risk, and a second technical reviewer for high-risk changes.
How it meets
A short weekly review, or approval inside the ticket when there is no meeting. The record of the decision matters more than the meeting.
One change calendar
A single shared calendar of approved changes, so two vendors do not work on the same firewall on the same night.
Freeze windows
No normal changes during periods you cannot afford an outage: payroll runs, month-end close, tax deadlines for CPA firms, or the week before an audit.
Sample change record
- Change
- CHG-0142 · Normal
- Request
- Create Conditional Access policy CA05, Require compliant device for admin portals, in report-only mode. Requested by J. Ortega, 2026-09-18
- Reason
- Admin portals can currently be reached from unmanaged devices
- Risk and impact
- Medium. In report-only mode nothing is blocked. 3 admin accounts in scope; break-glass accounts excluded
- Rollback plan
- Delete CA05. No other policy depends on it. About 5 minutes
- Approval
- Practice manager (business) and IT lead (technical), 2026-09-22
- Window
- 2026-09-24, 6:00 to 6:30 p.m. Pacific, outside patient hours
- Test
- Sign-in logs reviewed for 7 days: 1 admin laptop would fail the device check
- Documentation
- Tenant settings record updated; confirmed in the 2026-10-01 snapshot comparison
- Close
- Successful, closed 2026-10-01. Follow-up CHG-0151: enroll the laptop, then switch CA05 on
The same change appears in the sample on our cloud documentation page, where the snapshot comparison shows CA05 appearing between two dates. The snapshot shows what changed; the change record shows that someone meant it to.
The evidence auditors ask for
Several frameworks address change management directly. Your change records are the evidence for each.
| Requirement | What it says | Evidence from your records |
|---|---|---|
| ISO/IEC 27001:2022 Annex A 8.32 | Changes to information processing facilities and information systems are subject to change management procedures | A written change procedure and change records that follow it |
| SOC 2 CC8.1 | The entity authorizes, designs, develops or acquires, configures, documents, tests, approves and implements changes to infrastructure, data, software and procedures | Change records showing approval and testing before implementation |
| PCI DSS v4.0.1 Req. 1.2.2 | Changes to network connections and network security control configurations are approved and managed under the change control process (Req. 6.5.1) | Firewall change requests linked to approvals and to the updated rule register |
An auditor may pick a handful of changes from the review period and trace each one from request to close. Complete records make that a short conversation. They support your compliance evidence; they do not make you compliant on their own. See IT documentation for compliance and our SOC 2 compliance services.
Use the ticketing tool you already have
Change management modules are built into common ITSM tools such as ServiceNow, Jira Service Management, Freshservice, ManageEngine ServiceDesk Plus, HaloITSM and SysAid, and most MSP PSA platforms include change tickets. A very small firm can run the same process with a form and a SharePoint list. The fields and the discipline matter more than the product.
Configuration backup and history tools add the before-and-after diff that turns a change ticket into proof. See configuration backup and change tools for how they fit together.
Audit your change process, or build one
The IT Documentation Audit reviews your change process and a sample of recent changes, and the deliverables include a change-process gap list alongside the domain scorecard and roadmap. The IT Documentation Build includes a change-log template set up in your own platform. Both are $3,500 fixed, one-time.
See the IT documentation audit or IT documentation pricing. A quarterly review of your change records can be part of our virtual CISO service.

Where to go next
Firewall and network settings documentation
A rule-justification register that every firewall change updates.
Runbooks and disaster-recovery documentation
Step-by-step procedures, restore order and a contact tree for the day something fails.
Page 12 of 22: IT change management
- 1. IT documentation services (hub)
- 2. Why IT documentation matters
- 3. What to include in IT documentation
- 4. Network documentation
- 5. IP address and VLAN documentation
- 6. WAN and ISP circuit documentation
- 7. Firewall and network settings documentation
- 8. Cloud documentation: Microsoft 365, Azure, AWS
- 9. Data-flow diagrams
- 10. IT asset inventory
- 11. IT password documentation
- 12. IT change management (this page)
- 13. Runbooks and disaster-recovery documentation
- 14. Securing your IT documentation
- 15. IT documentation for compliance
- 16. IT documentation software compared
- 17. Configuration backup and change tools
- 18. How to document a network
- 19. IT documentation checklist
- 20. Sample IT documentation package
- 21. IT documentation audit
- 22. IT documentation pricing

Guided by Ali Hassani, CISO
Certified CISO (C|CISO) and CISSP with 25+ years in IT, cybersecurity, compliance and infrastructure, and dozens of Microsoft and Cisco certifications, including MCSE, MCITP, MCSA Security, CCNP and CCNA. Ali designs change processes that a busy office will actually follow: few fields, named approvers and a record that matches the configuration.
Change management questions
We are a 15-person office. Do we really need a change process?
You need a small one. A short form, a named approver and a shared calendar give you the records auditors and insurers ask about, and they make troubleshooting faster when something breaks after a change.
Does OC Security Audit make the changes?
No. We design and audit the process and the records. Your IT team or MSP carries out changes, or our implementation partner IT Perfection can do that hands-on work.
What counts as an emergency change?
A change needed right away to restore service or contain an active threat. It still needs a named approver, and the full record is completed afterward.
How long should we keep change records?
Keep them at least as long as your longest applicable requirement. For example, HIPAA requires documentation required by the Security Rule to be retained for six years from creation or the date it was last in effect, whichever is later.
Which changes can be pre-approved as standard?
Low-risk, repeatable tasks with a known procedure and a known rollback, such as adding a user to a group. We help you write the list and the template for each.
Implementation partner
OC Security Audit documents and audits; it stays independent of the administration of your systems. If you want hands-on work, IT Perfection can fix what the documentation uncovers and keep the records current as part of managed IT.
Sources and references
- ISO 27001:2022 Annex A 8.32 Change management (ISMS.online)
- SOC 2 CC8.1 Change management procedures (Cyberday)
- PCI DSS v4.0 Requirement 1.2 (myctrl.tools)
- PCI DSS v4.0 guide (Wazuh)
- 45 CFR 164.316 Policies and procedures and documentation requirements (eCFR)
- ITSM ticketing tools (SupportBee)
ServiceNow, Jira Service Management, Freshservice, ManageEngine ServiceDesk Plus, HaloITSM, SysAid and Microsoft are trademarks of their respective owners. OC Security Audit is independent and not affiliated with or endorsed by any vendor named on this page.

Make every change leave a record
We will review how changes happen today and show you the smallest process that gives you clean records. Schedule a consultation.
Irvine, Orange County and Southern California on-site; remote nationwide. Fixed one-time price: $3,500.


