A loop check verifies the installed signal path and its documented behavior from the field device through wiring, marshalling, I/O and control-system indication or output. It requires clear boundaries, safe preparation, calibrated equipment and one controlled record per loop.
The short answer
Release construction and point-to-point prerequisites, identify the loop and current drawings, verify isolation and work authorization, then inspect installation, tag, range, wiring and I/O assignment. Stimulate the field input or command the output with an approved method and calibrated reference. Confirm direction, scaling, units, indication, status, alarms and fail behavior at each defined endpoint. Record actual values and test equipment, remove every temporary force, correct defects through controlled revisions and sign the loop complete only after reconciliation.
- One loop record identifies one scope and current document set.
- Test methods respect process, electrical and functional-safety boundaries.
- Actual values and equipment identify evidence, not checkmarks alone.
- Temporary simulation, forces and jumpers are removed and verified.
Decision guide
| Loop stage | Check | Evidence |
|---|---|---|
| Readiness | Construction, drawings, permits and access complete | Released loop package and test authorization |
| Field path | Tag, installation, range, wiring and polarity correct | Inspection and measured values |
| System path | Channel, scaling, units, alarm and indication correct | Endpoint observations and screenshots |
| Restoration | Forces removed and normal configuration restored | Independent reconciliation and sign-off |
A practical workflow
- 01
Prepare the loop package, roles, method, risk controls and calibrated tools.
- 02
Verify field installation and trace the complete physical and logical path.
- 03
Apply approved stimuli or commands across defined test points.
- 04
Capture actual response, deviations and evidence at each endpoint.
- 05
Correct and retest, remove temporaries, reconcile the loop and approve completion.
Evidence and acceptance
Keep loop identifier, service and location, P&ID, loop and wiring drawing revisions, instrument data, I/O channel and range, work authorization, test equipment ID and calibration, as-found condition, injected and observed values, alarm and fail-state results, screenshots, defects, corrected documents/software, retest, temporary-force register, restoration confirmation and signatures.
Common mistakes
- Checking only PLC input without the field path.
- Using obsolete loop or wiring drawings.
- Writing a pass without actual injected and observed values.
- Leaving a force, jumper or simulation active.
- Combining unrelated defects under one loop sign-off.
Responsibility boundary
Primary sources
Technical claims and product boundaries were checked against these primary sources. Fact-checked
Frequently asked questions
Is a point-to-point check a loop check?
No. Point-to-point continuity is a prerequisite; the loop check verifies the defined installed functional path and behavior.
Must every alarm be tested?
Test scope follows the approved procedure, requirements and risk classification; omitted functions must be explicit.
Can one sheet cover several loops?
Only if individual identity, results, defects and sign-off remain unambiguous.
Does AutoNexit perform loop checks?
No. It preserves the controlled package and evidence produced by authorized technicians and engineers.