Guide

How to Write a Control Narrative

A control narrative is a plain-language description of how a control system should operate. It covers the process, the equipment and instruments, the operating modes, the normal start and stop sequences, interlocks, alarms, what operators see and change on the HMI, and what happens on power or signal loss. It becomes the reference for the drawings, the PLC program and the test procedures.

The Sections

What a Good Narrative Covers

Most narratives follow the same eight sections. Interlocks and fail-safe states are the two most often missed.

  • Written for operators and engineers alike
  • One section per process area
  • Every tag matches the I/O list
  • Reviewed before programming starts
Vertical list of the eight sections of a control narrative: process overview, equipment and instruments, operating modes, normal sequences, interlocks and permissives, alarms and trips, HMI screens and setpoints, and fail-safe states on power or signal loss.
Electrical schematics and panel layout drawings used to build to print
Control narrative and drawings for a new panel
Why It Matters

One Document Everyone Works From

The narrative is the agreement between the people who know the process and the people who build the controls. When it is clear, the programmer writes what the plant needs, and the FAT tests against what was agreed, not against memory.

When it is missing, those decisions are made at the keyboard or on site during startup, which is the most expensive place to make them.

Example Wording

Weak vs Clear Narrative Wording

Good narratives use numbers, tags and conditions instead of general phrases. A few examples from a duplex pump station:

WeakClear
Start the pump when the level is highStart lead pump P-101 when LIT-100 rises above 6.0 ft
Stop the pumps when the tank is emptyStop all pumps when LIT-100 falls below 1.5 ft
Alternate the pumpsSwap lead and lag after each pump-down cycle
Alarm on high levelAlarm when LIT-100 is above 8.0 ft for 10 s, or LSHH-100 trips
Protect the pumpStop the pump and alarm if no run feedback within 5 s of start

Tags and values are examples only.

Checklist

Before You Call the Narrative Finished

Content

  • Every motor and valve has a start and stop condition
  • Every analog input has a range and alarm limits
  • Every mode is defined: auto, manual, off

Safety

  • Interlocks and permissives are listed
  • Fail-safe states on power loss are stated
  • Emergency stop actions are described

Review

  • Operations has read and agreed it
  • Tags match the I/O list and drawings
  • Open questions are listed, not hidden
FAQ

Common Questions

Who should write the control narrative?

Whoever knows the process best, working with the controls engineer. At WETS AI our engineering team can write it with you as part of the project.

How long should a control narrative be?

Long enough to describe every sequence, interlock and alarm clearly. A small pump panel may need a few pages; a full treatment plant can need many.

Is a control narrative the same as a functional specification?

They are close. A functional specification is often more formal and may include the narrative alongside I/O lists, screen layouts and test plans.

Can you write the narrative for us?

Yes. Our engineers prepare control narratives, HAZOP and SIL input, process flow diagrams and panel drawings, led by a Texas-licensed Professional Engineer.

Related

Related Guides & Services

Design & Engineering

Control narratives, HAZOP and SIL identification, process flow diagrams and panel drawings.

PLC & HMI Programming

Programs written in-house for Allen-Bradley, Siemens and Schneider Electric, tested at FAT.

FAT Checklist

What to check, and what to ask for, at a factory acceptance test.

Request a Quote

Ready for a Quote?

Send what you have: drawings, an I/O list or a short description of the process. We will reply with questions, a quotation and a schedule.

Call Request a Quote