CP survey records and review
Cathodic protection inspection form checklist
A reading arrives without its reference electrode. A photograph cannot be tied to a test station. The reviewer asks for a repeat visit, but the request never reaches the field team. Build the form around the evidence each handoff needs.
Use this checklist to design a CP survey record and its review process. It is a workflow template to adapt with your qualified CP personnel, not a measurement procedure or a compliance certificate.
Download the editable checklistPlain text. No sign-in required. Copy it into your existing form or field workflow.
Choose the collection tool and review record together
This guide is for CP supervisors preparing a form, integrity teams reviewing exceptions, and operations teams connecting a survey to corrective work. Start with the field tool and procedure already used by the crew, then agree how the record reaches the reviewer.
LatchWorkflow's cathodic protection survey software workflow holds configurable survey fields, attachments, decisions, and plugin action results on a ticket. Specialist offline collection, instrument capture, and GIS remain with the field tools. Mapping their output into Latch requires configuration or an integration.
Six parts of a reviewable CP inspection form
Treat these as record-design prompts. Your procedure determines which measurements, units, evidence, and review steps apply to each survey type.
01
Identify the survey and test point
Survey ID, asset or pipeline reference, test station or rectifier ID, survey type, CP system, operator procedure and revision.
Review check: Can a reviewer identify the location and measurement procedure without opening a separate spreadsheet?
02
Keep each reading with its context
Applicable on and instant-off potentials with units, rectifier voltage and current where relevant, reference electrode type and serial, instrument reference, and measurement notes.
Review check: Keep unavailable values distinct from zero. Use the fields required by the survey procedure; a test-station check and a close interval survey need different records.
03
Record where and when collection happened
Technician identity, measurement timestamp with time zone, latitude, longitude, reported accuracy when available, and location source.
Review check: Distinguish device coordinates from manual entry. Keep the field measurement time separate from the later upload time.
04
Preserve the evidence received
Original survey export, relevant CSV or KML files, photographs, field notes, source application, source record ID, and submission reference.
Review check: Tie each attachment to the correct survey or test point. Keep the original when adding a corrected file and explain the revision.
05
Make the review decision reconstructable
Assigned reviewer, review outcome, decision time, rationale, missing evidence, and any request for a repeat visit or further engineering review.
Review check: An accepted record, an incomplete record, and an engineering exception should lead to different next steps. A workflow label is not a compliance determination.
06
Close the loop on the action
Proposed work request, approval request and decision, execution outcome, returned work-order reference, and follow-up evidence.
Review check: Record a failed handoff as a failure. An approval alone does not establish that a work order was created or that field work was completed.
Test the offline handoff before relying on it
For a mobile inspection form, ask the field-tool supplier to demonstrate a complete disconnected visit: open the assigned test point, collect the required data and photos, close and reopen the app, reconnect, and confirm which records reached the receiving system. Include an interrupted upload and a corrected submission in that evaluation.
Agree how source IDs, timestamps, attachment associations, and corrections will be preserved. Check how duplicate submissions and upload failures are surfaced. These are acceptance checks for your chosen collection and integration path; this checklist does not establish that a particular tool passes them.
Latch is not an offline-first CP survey app. The current CP survey walkthrough shows stored coordinates from a field-device import. Automatic browser-device GPS capture is a planned feature, not a released capability demonstrated by that replay.
Follow TS-14 from evidence to a work request
In the synthetic walkthrough, survey ticket CP-2041 identifies test station TS-14 and keeps the readings, reference electrode, coordinates, source export, and cabinet photograph together. Its operator review state is "Engineering review required." The example makes no engineering or compliance determination.
The proposed integrity work order carries the survey context into a stored approval request. A separate reviewer can inspect that request before execution. The record then shows the plugin outcome and returned reference, so the team can distinguish a requested action from a successful handoff.
Use maker-checker approval where a separate decision is required. Review the audit trail alongside the original evidence. An exported form remains a document; the operating record needs the decisions and results that followed it.
Keep engineering criteria in the approved procedure
A generic form should not assign a universal pass/fail threshold. PHMSA describes several close interval survey types with different measurement contexts in its close interval survey fact sheet. Qualified personnel must choose and interpret the applicable procedure for the asset and jurisdiction.
Record the procedure reference, the review decision, and the reason for any follow-up. Retention, access, backup, and legal-hold requirements also need to be established for your deployment.
For wider inspection workflows, use the inspection audit trail guide. For a standalone findings document, the inspection report builder creates an editable report; it does not create an immutable audit trail.
See the survey record through the reviewer's eyes
Follow a fixed synthetic CP survey through evidence, review, and the work-order handoff. Then map one of your existing forms to the same steps.