A lessons-learned register records what each valve job found, what was done, and what the result was under stated test conditions. The team reviews entries on a fixed cadence, separates screening evidence from confirmed results, and turns repeated findings into work instructions and training. Over time it shows which failure modes dominate your own valve population, and which practices actually hold.
Knowledge ยท Programme playbooks
A lessons-learned register for valve work
A simple register turns each valve job into evidence your next job can use.
1. Why valve work needs a register
Valve maintenance work repeats itself across any pipeline network. The same designs, the same services and the same neglect appear again and again. Lessons certainly exist, but most of them live in a single operator's memory.
A register moves each lesson onto paper that the programme owns. It records what a job found, what was done, and what the measured outcome was. The next crew then starts from evidence rather than from memory.
We see the same effect in our own field work across the Middle East, Asia and Africa. The same findings recur in different countries and different plants. A register captures them once, with dates attached.
Over time it becomes the shared memory behind a wider valve integrity management programme. It supports decisions with dated evidence instead of recollection.
2. Capture the job while it is fresh
Write each entry before the crew leaves site, while the detail is still clear. Memory fades quickly, and second-hand entries lose the facts that matter. Keep the form short so people actually complete it.
- Valve identity: tag number, type, size, class and service.
- Symptom as found: passing, seized or leaking, and who noticed it first.
- Condition on arrival: state of the injection fittings and any site constraints.
- Action taken: compound used, controlled amount injected, and the pressure response observed.
- Outcome and evidence: what improved, and how that was checked.
The evidence line matters most. Sound, bubbles and pressure behaviour are screening evidence; they suggest a result without proving it. The confirming test is a seat-leak test under agreed conditions, for example pressure decay across the closed valve. Record which one the entry rests on.
Note that API 598 and ISO 5208 are factory acceptance references. A field entry should not claim them as its result. For a typical clean, lubricate and seal job, these fields take minutes on site.
3. Review entries on a fixed cadence
Capture without review is just paperwork. Choose a review cadence that suits the programme, write it down, and keep to it. Review sooner after any surprise, near miss or repeat failure.
Review with the crew that did the work, not just a supervisor. The people on the valve remember why a step was changed or skipped. A desk review alone loses that context.
Sort the entries by failure mode: passing seat, seized, external leakage, or other. Common causes include dried sealant, debris, missing lubricant, corrosion and seat damage. The register should show which causes dominate your own population.
An outside comparison helps here. A risk-based valve integrity study of upstream and midstream sites, published by Valve World, reported 61 per cent passing and 28 per cent seized. External leakage accounted for 6 per cent and other causes 5 per cent. Distributions vary by population, so treat the figures as a comparison, never a target.
The review meeting also shows where technique or judgement needs support, which feeds operator competency assessment.
4. Turn lessons into working practice
A lesson that changes nothing is only an anecdote. Each review should end with at least one change, or a recorded decision to change nothing.
- Update the work instruction: amounts, dwell expectations and stop-work conditions for similar valves.
- Adjust the plan: bring forward valves that keep failing the same way, and feed the change into maintenance window planning.
- Correct the training: repeat the points where technique slipped, through operator training.
One caution before a lesson becomes a rule. Injection of cleaner, lubricant or sealant assumes certain gates held. The valve needs fittings in good condition. Its design and service must suit injection, and site rules and permits must allow the job. Where OEM documents exist, consult them for limits and warranty terms. Record which gates were satisfied, so each lesson transfers only to genuinely similar jobs.
Keep the numbers bounded as well. Dwell times, top-up amounts and cadences vary by fitting, valve and site, so log them as practice reported for that job, not as a universal standard.
5. Keep the register honest
Most registers fail in predictable ways. Vague entries that say only that all went well carry no lesson. An entry with no amounts and no stop condition teaches nothing and hides risk. Screening results presented as proof will mislead the next crew.
Avoid blame as well. A register that names and shames will soon contain nothing worth reading. Describe the conditions, not the person.
Some lessons end in a larger conclusion. A valve that still passes after sound treatment and a confirmed test may need formal assessment or replacement. The register should record that honestly, and not chase another treatment.
Small teams can keep this simple. A short form, a brief review and one named owner beat a complex system nobody maintains. See valve maintenance for small operators for a lighter pattern.
A condition survey can give a young register its first baseline across the whole population.
Common questions
Lessons learned register questions, answered directly
What should a valve lessons-learned entry record?
Record the valve identity, the symptom as found, the condition of the fittings, the controlled amounts injected and the pressure response, and the outcome with its evidence. State whether the result was screening evidence or a confirmed seat-leak test.
How often should a lessons-learned register be reviewed?
Set a cadence that suits the programme and keep to it. Review sooner after any surprise, near miss or repeat failure. The cadence matters less than holding it consistently.
Who should own the lessons-learned register?
Give it one named owner who maintains the form and chairs the review. The crew that did each job must attend, because they hold the context behind the entry. Ownership can sit with maintenance, integrity or operations.
Can lessons from one site be applied to another?
Yes, with care. A lesson transfers when valve type, service and fitting condition are similar, and the same gates were satisfied. Where these differ, treat the entry as a hint and verify under your own test conditions.
Starting a register for valve work?
Send the valve problem and job history. An engineer replies within 24 hours.
Include valve type and size, service, symptoms, fitting condition, what has been tried, and how each result was checked.