Before modifying a protection relay, engineers should create a verified protection relay settings backup containing the approved settings, active settings group, configuration files, relay identification, firmware information, logic where supported, communication and I/O data, event records, relevant drawings, previous test evidence, and enough documentation to restore the last approved state. The package depends on the relay model, software, scheme, and platform.
Quick Answer: What Should You Back Up Before Changing a Protection Relay?
Do not rely on a screenshot or one settings export. Before an approved change, preserve the following where supported by the relay model and engineering software:
- Approved protection settings and the currently active settings group.
- The relay settings file and broader configuration file, if the software distinguishes them.
- Logic equations, programmable functions, interlocks, trip logic, alarm logic, blocking, and permissive logic where applicable.
- Manufacturer, relay family, model, hardware variant, serial number, installed modules, and communication modules.
- Firmware version and relevant engineering-software version.
- Communication parameters, I/O mapping, binary inputs and outputs, analog signals, and SCADA mapping.
- Event logs, fault records, trip records, diagnostics, and oscillography or disturbance records where available.
- Time-synchronization configuration and the relay’s time reference.
- Existing test results, commissioning records, protection drawings, single-line diagrams, and coordination documentation.
- Previous approved backup, revision history, change request, approval record, and a protected rollback copy.
Record date, time, substation, panel, relay identifier, responsible person, integrity result, and storage location. The purpose is to prove what was approved.

Why Protection Relay Settings Backup Is a Critical Engineering Control
Protection settings determine how a relay responds to electrical conditions such as overcurrent, earth fault, voltage, frequency, differential, distance, directional, or other scheme-specific inputs. Without a baseline, engineers may not know which values, logic, active group, firmware, or communications were present when an event occurred.
A preserved baseline supports recovery if a change fails, exposes unintended differences, and gives commissioning teams evidence of what was installed. Event and disturbance records may be overwritten or cleared during maintenance, so saving relevant evidence helps separate a pre-existing issue from a problem introduced by the change.
Verification and testing should reflect the change, scheme, affected interfaces, and risk.
What Is a Protection Relay Settings Backup?
A settings backup is an export of protection parameters such as pickup values, time delays, curves, directional settings, thresholds, and protection groups where supported. A relay settings file backup may support comparison or restoration, but may omit logic, firmware, communications, I/O, event data, or the complete device state.
A configuration backup captures broader device and application information. A complete relay baseline combines available exports with identity, active-group, event and disturbance data, drawings, tests, approvals, and change history. Event-data backup preserves operational evidence, while a documentation package explains how the relay fits into the approved circuit and scheme.
A settings file alone is not automatically a complete baseline. Define the package by relay model, engineering tool, scheme, and document-control system, consistent with the need to develop, check, apply, and maintain quality relay settings [1].
What Should Be Included in a Relay Configuration Backup?
Protection Settings
Preserve protection-element settings, pickup values, time delays, curves, directional settings, voltage and current thresholds, frequency settings, and protection-group information where supported. Record which group is active and whether alternate groups exist for different operating conditions. The actual parameters depend on the protection scheme; no generic list represents every numerical protection relay.
Logic and Programmable Functions
Where supported, capture logic equations, programmable logic, interlocks, trip logic, alarm logic, blocking logic, permissive logic, timers, latches, and related mappings. A relay may store settings in one file and programmable logic or graphical configuration in another. Confirm that the export is readable by the applicable software and that the logic corresponds to the approved protection drawings.
Communication and I/O Configuration
Record communication addresses, protocol configuration, I/O mapping, binary inputs, binary outputs, analog signals, SCADA mapping, protection communication interfaces, and time-synchronization settings where relevant. Do not distribute unnecessary operational or cybersecurity-sensitive details in general documentation. Store the controlled technical record in accordance with the organization’s OT security and access rules.
Relay Settings File Backup vs Complete Relay Configuration Backup
| Backup type | What it captures | Main purpose | Limitation |
|---|---|---|---|
| Settings-only backup | Protection parameters and groups supported by the software | Compare or restore selected settings | May omit logic, firmware, I/O, communications, records, and drawings |
| Configuration backup | Settings plus broader device, logic, or interface configuration | Preserve a wider relay state | Scope varies by relay family and engineering tool |
| Event-data backup | Events, trips, faults, oscillography, and diagnostics where available | Preserve evidence of relay and system behavior | Does not necessarily restore configuration |
| Complete baseline package | Available settings, configuration, identity, records, drawings, tests, approvals, and rollback evidence | Establish a controlled engineering baseline | Requires document control and model-specific verification |
A relay configuration backup should therefore be defined by what the relay and engineering software actually export, then supplemented with the records needed to understand and recover the approved state.
What Relay Identification Information Should Be Saved?
Record manufacturer, relay family and model, hardware variant, serial number where applicable, firmware, engineering-tool version, installed options and modules, backup date, responsible person, and substation, panel, feeder, or circuit identification.
Identity data helps prevent restoring a file to the wrong hardware variant; confirm software compatibility in OEM documentation.
Why Firmware Version Matters Before a Relay Modification
Firmware can affect settings compatibility, engineering-software behavior, available functions, configuration migration, communications, event handling, and restoration. Not every firmware change affects every setting, but record the installed version and compare it with the configuration file and engineering tool before modification.
If firmware changes, treat it as a separate controlled activity with approval, backup, compatibility review, and testing. The OEM procedure takes precedence; a previous file may not be sufficient if hardware, software, options, or the protection application differs.
Event Records and Disturbance Records: Why Save Them Before Modification?
Preserve event logs, fault records, oscillography, trip records, sequence-of-events information, and diagnostics where available. They can show what happened before the modification, whether a pre-existing issue existed, and whether a later event may relate to the change.
When comparing relay records with breaker, SCADA, disturbance-recorder, or neighboring-relay evidence, save the time-synchronization configuration and note the time reference. Do not assume timestamps are comparable without checking the time source and quality.
Protection Setting Change Control — What Should the Process Look Like?
Step 1 — Define the Reason for the Change
Document the reason, such as a coordination revision, equipment replacement, network change, transformer change, CT/VT modification, fault-level change, corrective action, or approved protection study. Identify the affected feeder, scheme, interfaces, and operating constraints. This establishes the scope of protection setting change control.
Step 2 — Preserve the Existing Approved Baseline
Save the current settings, configuration, logic, active group, records, identification, firmware, drawings, test reports, and rollback copy where supported. Record date, time, responsible person, revision, and storage location. Verify file integrity through the approved comparison or validation method.
Step 3 — Review the Proposed Change
Review the protection study, coordination, scheme impact, adjacent protection, trip logic, interlocks, communication dependencies, CT/VT data, operating modes, and affected equipment. Confirm that the proposed change is approved for the actual relay model and firmware.
Step 4 — Apply Only the Controlled Modification
Apply only the approved change using the applicable OEM procedure and site electrical-safety controls. Avoid undocumented edits, uncontrolled copies, and field changes without an approved revision. If the modification expands beyond the original request, stop and re-evaluate the scope.
Step 5 — Verify the Result
Perform settings comparison, configuration verification, logic review, communication and I/O checks, and functional or protection testing where required by the change and scheme. Confirm the intended settings group is active and that no unintended differences were introduced.
Step 6 — Preserve the New Approved Baseline
Save the final configuration, settings, active group, records where appropriate, test evidence, revision, approval, and updated drawings. Retain the previous approved baseline according to rollback and document-control requirements.
A relay modification should be treated as a controlled engineering change, not simply as a parameter edit. Verification should be proportionate to technical and operational risk.
Relay Settings Verification After a Modification
Relay settings verification should compare the old and new approved revisions and confirm the intended changes. Review unintended differences, active settings group, protection logic, CT/VT data, time delays, communication parameters, protection status, I/O behavior, and relevant alarms. Do not rely only on a visual review of selected values; compare the complete available configuration where the software supports it.
Verification should also confirm that the file opens in the intended software, the relay identity matches the target device, and the installed state corresponds to the approved revision. Where testing is required, retain the test report with the final baseline rather than storing it as an unrelated maintenance document.
Numerical Relay Backup Checklist
A practical numerical relay backup should include the following where supported:
| Category | Items to capture |
|---|---|
| Relay identity | Model, serial number, firmware, hardware configuration, installed modules, and engineering-tool version |
| Settings | Protection settings, active group, control settings, groups, and logic |
| Records | Events, fault records, oscillography, trip records, and diagnostics |
| Interfaces | I/O, communication parameters, SCADA mapping, and time synchronization |
| Documentation | Single-line diagram, protection schematic, coordination study, previous test report, and change request |
The checklist is not a claim that every relay stores every item in one file.
How to Build a Controlled Relay Backup File Structure
A practical folder structure can follow the organization’s document-control system:
Substation / Panel / Relay ID
01_Approved_Settings02_Relay_Configuration03_Events04_Disturbance_Records05_Test_Reports06_Drawings07_Change_Control08_Approval09_Rollback_Baseline
Use revision identifiers, controlled permissions, clear ownership, and a record of each file’s contents. Keep sensitive credentials and uncontrolled operational details out of general-purpose folders. Match the structure to the organization’s information-security and document-control requirements.
What Is a Good Relay Rollback Baseline?
Rollback evidence should allow qualified personnel to identify the previously approved configuration, active settings group, installed firmware, logic, communication configuration, completed testing, and associated drawings. It should also identify the hardware and software context in which the baseline was created.
Do not assume that every relay can be restored simply by loading one file. Restoration may require a compatible firmware version, engineering software, hardware option, settings group, logic file, communication configuration, and approved procedure. Follow the applicable OEM restoration method and project safety controls. A rollback baseline makes recovery controlled rather than reconstructed from memory.
Common Mistakes in Protection Relay Configuration Management
The most damaging mistakes include editing settings without saving the original, keeping only a screenshot instead of the actual export, failing to record firmware, not identifying the active group, ignoring programmable logic, losing event records, overwriting the previous approved file, keeping multiple uncontrolled copies, failing to document who made the change, not comparing the final state with the approved revision, and failing to preserve test evidence.
Another common error is assuming that a settings file represents the complete relay configuration. Label each relay settings file backup by scope and supplement it with configuration, records, drawings, approvals, and rollback evidence where required.
Protection Relay Backup and Cybersecurity Considerations
Relay configuration files can be operationally sensitive. Use controlled access, file permissions, revision control, secure storage, backup redundancy, change authorization, audit trails, and controlled transfer procedures. Protect the approved baseline from accidental overwrite and keep it separate from working copies.
Cybersecurity controls should support availability and accountability under the organization’s OT security requirements. This is defensive governance for protection records.
What Should Be Verified Before and After a Relay Settings Change?
| Control | Before change | After change |
|---|---|---|
| Relay identity | ✓ | ✓ |
| Firmware | ✓ | ✓ |
| Settings | ✓ | ✓ |
| Active group | ✓ | ✓ |
| Logic | ✓ | ✓ |
| I/O | ✓ | ✓ |
| Communication | ✓ | ✓ |
| Event records | ✓ | ✓ |
| Test evidence | ✓ | ✓ |
| Approval | ✓ | ✓ |
| Rollback baseline | ✓ | ✓ |
Adapt the table to the relay, scheme, and change scope. A minor administrative correction may not require the same test depth as a protection-element, trip-logic, CT/VT, or communication change.
When Should You Request a Protection Relay Settings Audit?
An engineering review may be appropriate when documentation is incomplete, multiple setting versions exist, firmware has changed, a relay has been replaced, settings were modified without clear records, a substation has expanded, coordination studies have changed, commissioning records are missing, the original backup cannot be verified, or there is uncertainty about the active configuration.
Not every relay requires an audit. The need depends on the protection scheme, document quality, change history, equipment criticality, and consequences of uncertainty. A review should identify missing evidence and prioritize corrective actions rather than promise a result that has not been tested.
A configuration review may examine the relationship between protection relays, breakers, and LV and MV switchgear systems, especially when drawings or trip logic have changed.
How a Controlled Relay Configuration Review Supports Maintenance Teams
A controlled review can identify missing baselines, configuration inconsistencies, documentation gaps, uncontrolled revisions, missing test evidence, unclear rollback states, and mismatches between equipment and records. It gives maintenance and commissioning teams a common reference for future work.
Where relay communications and monitoring are involved, SCADA and HMI systems should be considered alongside communication parameters, alarm mapping, time synchronization, and event interpretation. The review does not guarantee protection performance; it improves the quality and traceability of the evidence used to make decisions.

Practical Protection Relay Change-Control Checklist
Before Modification
- Identify relay, panel, feeder, and protected circuit.
- Record firmware, hardware, modules, and engineering-tool version.
- Save approved settings, active group, and complete available configuration.
- Preserve logic, I/O, communications, and time synchronization where supported.
- Export available event, fault, diagnostic, and disturbance records.
- Preserve drawings, coordination documents, and previous test evidence.
- Verify file integrity, revision, date, responsible person, and storage location.
- Obtain required change approval and protect the rollback copy.
During Modification
- Apply only approved changes under the applicable OEM procedure.
- Record the revision and maintain the previous approved baseline.
- Maintain appropriate electrical safety controls and controlled access.
- Stop and re-evaluate if the actual scope differs from the approved change.
After Modification
- Compare settings and verify intended and unintended differences.
- Verify active group, logic, I/O, communications, and protection status.
- Perform required functional, secondary-injection, or protection testing.
- Save the final configuration and update revision history.
- Store test evidence, updated drawings, approval, and rollback information.
- Confirm the final relay state is recoverable by qualified personnel.
Request a Relay Settings Audit or Controlled Configuration Review
If a substation or industrial facility has incomplete settings records, multiple configuration versions, undocumented changes, missing test reports, or uncertain rollback capability, a controlled review can establish a clearer protection-settings baseline. The scope may include a relay settings audit, configuration backup review, baseline verification, settings comparison, change-control review, and documentation review.
Use request a relay settings review to discuss the relay model, active settings group, firmware, available files, protection drawings, previous test evidence, and intended modification. Related protection relay solutions can be evaluated in the context of the complete protection scheme rather than as an isolated parameter file.
Before changing a protection relay, save enough information to prove what was installed, understand what changed, verify what is active, and recover the previously approved configuration if required. That is the purpose of disciplined protection relay settings backup and controlled change management.


