A consistent Management of Change (MOC) form is the backbone of a reliable change process. A good template makes sure every proposed change is described, assessed, and approved the same way — no matter who submits it. This page outlines what a strong MOC form, checklist, and procedure template should contain, and gives you a starting point to adapt to your own operations.
New — AI-assisted MOC forms: Ecesis now includes an AI MOC Question Generator that suggests review questions tailored to your industry, operations, and known hazards, so your committee starts from a strong draft instead of a blank form. Suggestions are presented for review and never added automatically — your team chooses what to keep.
What a Management of Change Form Should Include
Core MOC Form Fields
At minimum, a Management of Change form should capture the following so reviewers have the context they need to make a sound decision:
- Change request title, requestor, date, and affected location or area
- Description of the change and the reason for it
- Change type — permanent, temporary, or emergency
- Systems, equipment, chemicals, procedures, or personnel affected
- Risk assessment: potential hazards, severity, and likelihood
- Required reviews and approvals (engineering, EHS, operations, management)
- Action items with owners and due dates
- Pre-startup and post-startup verification
- Documentation and training updates needed
- Final approval, implementation date, and closure sign-off
The MOC Review Checklist
MOC Procedure Template Structure
A Written Procedure Behind the Form
A form works best alongside a short written MOC procedure that defines: the purpose and scope, what qualifies as a change requiring MOC, roles and responsibilities, how change types are handled, approval authority levels, recordkeeping requirements, and how the program is audited. Regulations such as OSHA PSM (29 CFR 1910.119(l)) expect a documented, systematic procedure — not just a form.
Tailoring the Template to the Change Type
One Template Is Rarely Enough
Different changes need different rigor. A minor, low-risk change should not require the same review path as a major process change, and a temporary or emergency change needs special handling such as expiration dates or retroactive documentation. The most effective programs use conditional logic so the form expands or contracts based on the risk and scope of each change.
Ecesis Management of Change Software
MOC Software
Streamline change reviews and approvals
Compliance Obligations
Track regulatory requirements and deadlines
Audits & Inspections
Schedule and conduct compliance audits
Incident Management
Report, investigate, and track incidents
Training Management
Track employee training and competency
Document Management
Centralized document storage and control
Frequently Asked Questions
What should an MOC form include?
An MOC form should capture the change description and reason, the change type (permanent, temporary, or emergency), affected systems and personnel, a risk assessment, required reviews and approvals, action items with owners and due dates, pre-startup and post-startup verification, documentation and training updates, and final closure sign-off.
Is the MOC template free?
Yes. Ecesis offers a free downloadable MOC form template you can adapt to your own operations. It is a starting point you can use on paper or build into MOC software.
Can I customize the MOC template?
Yes. Every organization manages change differently. The template is meant to be tailored, and Ecesis MOC software lets you customize fields, workflows, and conditional questions without costly vendor programming.
What is the difference between an MOC form and an MOC checklist?
The MOC form captures the details of a specific change request. The MOC checklist is the sequence of steps a change moves through, from initiation and risk assessment to approval, implementation, and closure. A good program uses both together.
Do I need a different template for temporary or emergency changes?
Often, yes. Temporary changes need an expiration date and extension process, and emergency changes need an expedited path with retroactive documentation. Many teams use conditional logic so a single smart form adapts to each change type.
