# Chemical Plant Management of Change (MOC) Request Template

> Source: https://netray.co/tools/chemical-plant-management-of-change-request-template
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

A management of change request form covering the change, hazard review, approvals, training, documentation updates and pre-startup sign-off.

## Category

ehs-workforce

## Industry

Chemicals & Process Manufacturing

## Audience

- Process safety engineer
- Plant manager
- Operations manager

## Tool

**Kind:** template

**Output:** document

**Fields:**

#### Company / site

**Key:** company

**Type:** text

**Default:** Riverbend Specialty Chemicals, Plant 2

#### MOC number

**Key:** moc_no

**Type:** text

**Default:** MOC-2026-031

#### Date raised

**Key:** date

**Type:** date

**Default:** 2026-10-20

#### Requested by

**Key:** requester

**Type:** text

**Default:** S. Okafor, Process Engineer

#### Type of change

**Key:** change_type

**Type:** select

**Options:**

- Equipment
- Process chemistry
- Operating limits
- Procedure
- Raw material or supplier
- Control system or interlock
- Temporary change

**Default:** Equipment

#### Duration

**Key:** permanence

**Type:** select

**Options:**

- Permanent
- Temporary
- Trial

**Default:** Permanent

#### Unit / area

**Key:** area

**Type:** text

**Default:** Reactor R-210, Unit 2

#### Description of change

**Key:** description

**Type:** textarea

**Default:** Replace the existing carbon steel transfer line from R-210 to T-215 with 316L stainless steel of the same diameter, and add a manual isolation valve at the tank inlet.

#### Reason for change

**Key:** reason

**Type:** textarea

**Default:** Repeated corrosion leaks at the weld joints due to a change in feed acidity.

#### Expiry date (temporary changes)

**Key:** expiry

**Type:** date

**Default:** 2026-12-31

**Blocks:**

#### Management of Change Request

**Body:** Site: {{company}}
MOC number: {{moc_no}}
Date raised: {{date}}
Requested by: {{requester}}
Unit / area: {{area}}
Type of change: {{change_type}}
Duration: {{permanence}}
Expiry (if temporary): {{expiry}}

#### Description of Change

**Body:** {{description}}

#### Reason and Benefit

**Body:** {{reason}}

#### Technical Basis and Hazard Review

**Table:**

**Columns:**

- Question
- Yes / No / NA
- Comment or action

**Rows:**

**0:** Is it a replacement in kind?

**0:** Are materials compatible with all process fluids?

**0:** Do operating limits (pressure, temperature, flow) change?

**0:** Are relief devices still adequately sized?

**0:** Are interlocks or alarms affected?

**0:** Is a PHA or HAZOP revalidation needed?

**0:** Environmental or permit impact?

**0:** Impact on adjacent units or utilities?

#### Documents to Update

**Table:**

**Columns:**

- Document
- Owner
- Updated (date)

**Rows:**

**0:** P&ID

**0:** Operating procedure / SOP

**0:** Process safety information

**0:** Inspection and maintenance plan

**0:** Emergency response plan

**0:** ERP bill of materials / routing / equipment master

#### Training and Communication

**Body:** Affected personnel to be informed or trained before startup: ____________
Training completed (date): ____________
Contractors informed: ____________

#### Approvals

**Signatures:**

- Requester
- Process safety / EHS reviewer
- Engineering reviewer
- Operations manager
- Plant manager

#### Pre-Startup Safety Review and Close-Out

**Signatures:**

- Pre-startup review completed by
- Operations accepts change
- MOC closed by

**Notes:** Starting point only, not legal advice. The questions are generic prompts. Align the form with your site's MOC procedure and with the regulations that apply to you, such as OSHA PSM or your national equivalent.

## Content

**Intro:** Plant incidents often trace back to a change that was never reviewed: a different valve, a new supplier, a raised setpoint. A management of change request forces the question 'what could this affect?' before the change goes in. This template gives you a clean, exportable form.

**Sections:**

#### How to use it

**Body:** Complete the header and description, export the document and route it for review. The hazard review table is a prompt list, so write an action next to every 'Yes' or 'Not sure'. The change is not complete until documents are updated, people are trained and a pre-startup review has been signed. For temporary changes, always set an expiry date and a named person who will remove or formalise it.

#### What counts as a change

**Body:** Anything that is not a replacement in kind is a change. Replacement in kind means the same specification and the same function. Everything else needs review.

**Bullets:**

- New or modified equipment, piping, instruments or software logic
- Changed chemistry, concentration, catalyst or raw material source
- Altered operating limits or alarm and trip setpoints
- New or revised procedures and staffing changes affecting safety tasks
- Temporary bypasses and workarounds

#### Linking MOC to the ERP and maintenance system

**Body:** A change that alters a recipe, routing, work centre or equipment record must also change the ERP master data, or the plant will keep running the old specification on paper. List those records in the documents table and assign an owner. In many ERPs a bill of materials or recipe revision can be tied to the MOC number so the audit trail is complete.

#### Common mistakes

**Body:** Frequent failures are treating a large change as replacement in kind, skipping the pre-startup review under schedule pressure, letting temporary changes become permanent without review, and closing the MOC before drawings are updated. Track open MOCs on a register with ageing, and review that list at the safety meeting.

**Cta:** Netray can help link your MOC records to ERP master data changes so affected recipes, routings and equipment records are not missed.

**Faq:**

#### Is a replacement in kind exempt from MOC?

**Answer:** Under common PSM practice, a true replacement in kind with the same specification and function does not need the full MOC process, though it should still follow normal maintenance controls. If there is any doubt, treat it as a change.

#### Who should approve an MOC?

**Answer:** At minimum the requester's supervisor, an engineering or process safety reviewer and the operations owner. Higher risk changes need plant management and often a formal hazard study. Your site procedure defines the matrix.

#### How long can a temporary change run?

**Answer:** Set a short, specific limit, often days or weeks, with an expiry date and owner. Extensions should require a new review. Temporary changes with no expiry are a known cause of incidents.

#### Does MOC apply outside the United States?

**Answer:** OSHA PSM is a US rule, but the practice is widely used, and equivalents exist, such as Seveso requirements in the EU. Check your local legislation and company standards.

## Search terms

management of change template, MOC form chemical plant, MOC request form pdf, process safety management MOC, PSM management of change checklist, MOC procedure template, plant change request form, moc form word

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json