A control narrative explains how operators and automation should move a process through normal, transitional, abnormal and recovery states. It provides shared intent before logic diagrams and code, while remaining specific enough to derive requirements and tests.
The short answer
Define process purpose, boundary, equipment, roles and operating modes first. For each mode and sequence, state entry conditions, operator actions, automatic actions, transitions, permissives, interlocks, timing, alarms, failure response, fallback and exit criteria. Reference tag and document IDs rather than inventing aliases. Identify assumptions, unresolved decisions and safety-related functions that require their own approved lifecycle. Link each narrative section to functional requirements, detailed design and verification cases.
- Write from the operator and process perspective before software structure.
- Describe every state transition and its authority.
- Distinguish permissive, interlock, alarm and safety function.
- Use stable references and controlled terminology.
Decision guide
| Narrative element | Required content | Downstream use |
|---|---|---|
| Mode | Purpose, availability, entry and exit | State model and HMI indication |
| Sequence | Ordered steps, transitions and timing | PLC/DCS logic and tests |
| Protection | Permissives, interlocks, alarms and trips | Cause/effect and acceptance |
| Failure/recovery | Detection, fallback, reset and restart | Abnormal-operation and recovery tests |
A practical workflow
- 01
Agree scope, process references, glossary, modes and accountable reviewers.
- 02
Interview operations, process, control and maintenance roles using real scenarios.
- 03
Write normal sequences, transitions, protections, abnormal states and recovery.
- 04
Walk through edge cases and trace statements to requirements and test coverage.
- 05
Baseline the narrative and control changes with impact on design, HMI and tests.
Evidence and acceptance
Keep source P&IDs and operating philosophy, process and equipment boundary, mode/state definitions, sequence steps and timing, commands and ownership, permissives, interlocks, alarms and trips, failure detection, fallback, reset and restart, role and access assumptions, linked tags and requirements, open decisions, review record, approval and traceability to tests.
Common mistakes
- Writing directly from existing code and preserving its defects.
- Leaving transitions and reset authority implicit.
- Calling every protective action an interlock.
- Ignoring manual, maintenance and degraded modes.
- Using names that do not match drawings and registers.
Responsibility boundary
Primary sources
Technical claims and product boundaries were checked against these primary sources. Fact-checked
Frequently asked questions
Who writes the control narrative?
Usually a collaborative engineering effort with process, operations, control and safety input appropriate to the scope.
Is a sequence table enough?
A table can help, but roles, modes, abnormal behavior, assumptions and recovery still need context.
Should safety functions be described?
Their interfaces and intent may be referenced, but detailed safety requirements follow the approved functional-safety lifecycle.
Does AutoNexit create the logic?
No. It preserves the narrative and links to accountable design and testing.