To fill out a MOP form — a Method of Procedure document for high-risk maintenance work — you work top to bottom through a fixed set of fields, populating each one with site-specific facts drawn from your asset records, vendor documentation, and applicable safety standards before any technician signs it or touches the equipment. The sections below walk through each field in the order it typically appears on the template.
What a MOP Form Captures
A MOP is a step-by-step document that walks technicians through high-risk maintenance on infrastructure like electrical systems, network equipment, or industrial controls. The form captures what you plan to do, how you plan to undo it if something goes wrong, who authorized the work, and what safety gear the job requires. Every person involved signs off before work begins.
Before you start filling anything in, confirm your template contains all of the standard sections: document control, scope of work, site logistics, contact list, prerequisites, step-by-step procedure, back-out plan, safety and PPE requirements, tools and materials list, stakeholder notification plan, authorization signatures, and supporting documents. If any of those sections is missing, add it. A gap in the template becomes a gap in the plan.
Document Control, Scope, and Site Logistics
The top of the form establishes what document this is and what it covers. Fill in a version number, the author’s name, the creation date, and a unique identifier so the MOP can be tracked and retrieved later.
Keep the scope of work field tight. Instead of writing “upgrade server infrastructure,” write “replace two 10GbE SFP+ transceivers in switches A3-R12 and A3-R14, then verify link aggregation.” Narrow scope prevents scope creep during the maintenance window and gives reviewers a clear picture of what is and isn’t authorized.
For site logistics, pull the equipment identification numbers and exact rack or room coordinates from your facility’s asset management system. Getting these wrong is one of the fastest ways to cause an incident. A technician who powers down the wrong circuit because a rack number was transposed can take out a production system that was never supposed to be touched.
The contact list comes next. At minimum, include the project manager, the lead technician performing the work, the facility owner or operator, the safety officer, and whoever handles emergency response on site. Use direct phone numbers, not office lines. During a 2 a.m. maintenance window, you need someone who answers on the first ring.
Use the prerequisites field to list conditions that must be true before work starts: completed permits, a confirmed outage window, pre-staged replacement parts, or a validated change ticket. If a prerequisite isn’t met on the day of the window, the MOP isn’t ready to execute.
Writing the Step-by-Step Procedure
The procedure section is the heart of the form. Each step should be specific enough that a qualified technician who has never seen this particular site could follow it. Vague instructions like “configure the device” are worthless under pressure. Spell out every command, every setting, every physical action.
Number every step sequentially and leave no gaps in the logic. If step 6 depends on the outcome of step 4, say so explicitly. Mark conditional steps clearly: “if the link comes up, proceed to step 8; if not, go to the back-out plan.” The technician shouldn’t have to interpret ambiguity while standing in front of a live panel.
Assign a time estimate to each step. The estimates let the team track whether the job is running behind schedule, and they let the project manager confirm the full procedure fits inside the maintenance window. If your steps add up to five hours and the window is four, you know before anyone picks up a tool that the plan needs revising.
Pull technical specifications directly from equipment manuals or vendor documentation when describing settings, torque values, firmware versions, or configuration parameters. Don’t work from memory. If a firmware upgrade requires version 4.2.1 and you write 4.2, the technician may install the wrong package and spend an hour troubleshooting a problem the MOP created.
Fill in the tools and materials list in parallel with the procedure. Every hand tool, test instrument, and consumable the steps call for should appear on the list so nothing is discovered missing at the site.
Filling In the Back-Out Plan
The back-out plan is the field most people rush, and it’s almost always the one they wish they had written more carefully. It documents exactly how to reverse every change and return the system to its pre-maintenance state if a step fails.
A complete back-out plan has three parts. First, define the trigger criteria: the specific conditions that tell the team to stop moving forward and start rolling back. Examples include a failed link verification, a service that does not come back online within a defined window, or an error code from a diagnostic test. Without explicit triggers, technicians tend to keep pushing forward hoping the next step will fix the problem, and that impulse makes things worse.
Second, write the rollback steps with the same level of detail as the forward procedure. If step 3 of the forward plan was “remove the existing transceiver from port Gi1/0/24,” the corresponding back-out step is “reinstall the original transceiver (SN: XXXX) into port Gi1/0/24 and verify link status.” Restoration steps that say “reverse the above” are not back-out plans. They are wishes.
Third, include verification tests that confirm the system is actually back to its original state. A rollback is complete when the system passes the same health checks it passed before the maintenance window opened, not when the old hardware is physically reinstalled.
Completing the Safety and PPE Section
Any MOP involving electrical equipment, pressurized systems, or other stored energy sources needs the safety section filled in with job-specific detail, not generic boilerplate. Start with hazard identification: what energy sources are present, what their voltage and current levels are, and whether arc flash is a risk.
Lockout/Tagout Fields
OSHA’s lockout/tagout standard requires employers to establish written procedures that protect workers from unexpected energization or release of stored energy during maintenance. The written energy control procedure must include a statement of its intended use, the specific steps for shutting down and isolating the equipment, the steps for placing and removing lockout or tagout devices, and the requirements for testing the equipment to verify that the energy isolation is effective.1Occupational Safety and Health Administration. 29 CFR 1910.147 – The Control of Hazardous Energy (Lockout/Tagout)
In the MOP’s lockout section, name the specific energy-isolating devices (circuit breakers, disconnects, valves), identify who places and removes the locks, and describe how the team will verify the equipment is de-energized before work begins. A technician should be able to read the section and know exactly which breaker to open, which lock to hang, and which meter reading confirms zero energy, without consulting any other document.
Arc Flash Assessment and PPE Category
When the work involves energized electrical equipment, NFPA 70E requires an arc flash risk assessment before the job begins. The assessment identifies arc flash hazards, estimates the likelihood and potential severity of an incident, and determines whether additional protective measures are needed. It must also account for equipment condition, including whether the gear was properly installed, maintained per manufacturer recommendations, and shows no evidence of impending failure such as arcing, overheating, or visible damage.
NFPA 70E organizes PPE into four categories based on incident energy at the working distance:
- Category 1 (minimum 4 cal/cm²): arc-rated long-sleeve shirt and pants, arc-rated face shield, hard hat, safety glasses, hearing protection, and leather or arc-rated gloves.
- Category 2 (minimum 8 cal/cm²): the same base clothing at a higher arc rating, plus an arc-rated balaclava if a face shield is used instead of a full hood.
- Category 3 (minimum 25 cal/cm²): a full arc flash suit (jacket, pants, and hood), arc-rated or rubber insulating gloves with protectors, and all standard protective equipment.
- Category 4 (minimum 40 cal/cm²): the same arc flash suit configuration at the highest arc rating, representing the maximum protection level the standard addresses.
In the PPE field, specify the category required for each step that involves exposure to an arc flash hazard, and note the arc flash boundary, which is the distance from the equipment at which incident energy drops below 1.2 cal/cm². Anyone crossing that boundary needs the listed PPE, whether they’re performing the work or just observing.
Compliance Fields for Regulated Work
Most MOPs don’t need to satisfy anything beyond general workplace safety and your internal change-management policy. Two sectors are the common exceptions: electric utility work subject to NERC CIP, and federal information systems subject to NIST SP 800-128. If your work falls outside those frameworks, you can skip this section of the form.
NERC CIP-010 Fields
If the MOP covers configuration changes to cyber systems supporting the Bulk Electric System, NERC CIP-010 requires that each change be authorized before implementation and that the required cyber security controls be verified after the change is complete.2North American Electric Reliability Corporation (NERC). CIP-010-4 Build fields into the template for the change authorization record and for documenting post-change security verification results.
CIP-010 also requires that intended changes be tested in an environment that minimizes differences with production, or, if tested in production, that the test is performed in a way that minimizes adverse effects. The MOP needs to document test results and, when a test environment was used, describe the differences between that environment and production.3North American Electric Reliability Corporation (NERC). CIP-010-5 – Cyber Security – Configuration Change Management and Vulnerability Assessments For software or firmware changes, the standard further requires verifying the identity of the software source and the integrity of the software before installation.
NIST SP 800-128 Fields
For federal agencies and contractors working on government information systems, NIST SP 800-128 requires that configuration changes be formally identified, proposed, reviewed, analyzed for security impact, tested, and approved before implementation.4National Institute of Standards and Technology (NIST). Guide for Security-Focused Configuration Management of Information Systems After implementation and testing, a security impact analysis must confirm that the change was made as approved and that no unintended effects on existing security controls occurred.
If your MOP touches a system subject to the Federal Information Security Modernization Act, add fields for the pre-change security impact analysis, the approval record, and the post-implementation verification. Auditors will expect to see these records tied directly to the MOP that authorized the work.5National Institute of Standards and Technology (NIST) Computer Security Resource Center. Guide for Security-Focused Configuration Management of Information Systems
Stakeholder Notification Plan
A technically perfect MOP can still create chaos if the people affected by the outage don’t know it’s coming. In the notification plan field, document who gets told, when, and through what channel.
At minimum, each notification should include the type of maintenance (scheduled or emergency), the systems or services affected, the exact start time and estimated end time with time zone, a brief description of the work, any actions users need to take beforehand such as saving work or logging out, and contact information for questions. For critical systems, plan on notifications at least a week in advance, with reminders a few days before and again the day of the window.
Include a sub-field to record when each notification was sent and to whom. That creates an audit trail if a stakeholder later claims they weren’t informed, and it surfaces scheduling conflicts early. If a business unit has a critical deadline inside your proposed window, you want to discover that a week out, not an hour before cutover.
Signatures, Attachments, and Final Review
Once every section is populated, the MOP moves into review. The signature block should include lines for the facility owner or operator, the lead engineer, and the designated safety officer at minimum. Each reviewer checks the document against their area of responsibility: the facility owner confirms no scheduling conflicts with other site activities, the engineer validates the technical accuracy of the procedure and back-out plan, and the safety officer verifies that hazard controls and PPE are adequate.
For work involving structural changes or modifications to building systems, a licensed professional engineer may need to review the plan to verify compliance with applicable building codes. Build that review into the project schedule rather than treating it as a last-minute formality.
Fill in the attachments checklist too. One-line electrical diagrams, network topology maps, manufacturer technical bulletins, and any other supporting documents the reviewers need should be listed and confirmed present. A MOP without its supporting documents is incomplete no matter how many signatures it carries. The form is ready for execution only once every required signature is in place and every attachment is confirmed.
Executing and Archiving the Completed Form
During execution, the lead technician works through the numbered steps in order, physically marking or initialing each one as it’s completed. This real-time annotation serves as both a progress report and a safeguard against skipping a step, and it lets a supervisor glance at the form at any point and know exactly where the job stands.
If a step produces an unexpected result, the technician refers to the back-out plan’s trigger criteria to decide whether to continue or roll back. The quality of the back-out plan you wrote earlier pays off here, because explicit go/no-go criteria remove ambiguity from a high-pressure moment.
When the work finishes, the completed MOP becomes the official record of the maintenance window. The technician submits the annotated document, with every step initialed, every deviation noted, and the final system health check results attached, to the facility manager for final review. The facility manager then archives the signed document in the maintenance log or a digital repository. Industry practice and many regulatory frameworks, including NERC, expect these records to be retained for several years for audit purposes.