A valve register is a structured list of every valve on a site or network, with fields for identity, service, fittings and maintenance history. Build it from nameplates, drawings, OEM documents and walkdown surveys, and update it after every job. A register with no owner goes stale quickly, so assign responsibility and set a review cadence.
Building a valve register: fields, sources and upkeep
A valve register turns scattered nameplate and maintenance data into decisions you can defend.
1. What the register is for
A valve register is the backbone of valve integrity management. It answers basic questions fast. Which valve is this, what service does it carry, and when was it last touched? Without a register, every decision starts with a search.
Keep the first version modest. A short, accurate list beats a long, half-empty one. Start with valves that matter for safety and throughput, then expand outward.
The register also shows what is possible. Online treatment needs injection fittings in good condition, a valve design that suits injection, and site rules that allow the work. Recording fittings and their condition answers this before you plan a job.
2. Core fields for every valve
Each row describes one valve. The core fields fall into two groups: what the valve is, and what has happened to it.
- Identity: tag number, manufacturer, model, serial number, size and body material.
- Location: site, line, drawing reference and access notes, such as buried or overhead.
- Service: fluid, pressure class, temperature rating and normal position.
- Maintenance fit: injection fittings present, fitting condition, and the OEM document reference.
- History: last clean, lubricate or seal action, products used and the result observed.
- Condition: current symptoms, how each was checked, and the date.
Condition fields earn their place. A risk-based valve integrity study of upstream and midstream sites, published by Valve World, recorded 61 per cent of valve failures as passing and 28 per cent as seized. Distributions vary by population, so track seat tightness and ease of movement first.
3. Capturing nameplate data in the field
The nameplate is the primary source on the valve itself. Photograph it before you transcribe anything. A photo keeps details the register has no field for yet.
Work to a routine each time. Clean the plate, light it from a low angle, and capture the whole plate plus body stamping. Record worn characters as unreadable rather than guessing them.
Interpretation matters as much as capture. Manufacturers use their own codes for body material, trim and seat options. Our guide to reading valve nameplates explains the common markings. Where a code stays unclear, record the raw characters and query the manufacturer.
Nameplate data also anchors the OEM document reference. That document, not memory, sets torque limits, lubricant compatibility and warranty terms.
4. Sources beyond the nameplate
No single source holds every field. A register is assembled from several, and each one has gaps.
- Drawings: P&IDs and isometrics give location, line service and valve count, but rarely model numbers.
- Procurement records: orders and datasheets give manufacturer, model and trim, but plants change after commissioning.
- OEM documents: manuals set limits and recommended care, where they exist and match the installed valve.
- Walkdowns: a physical survey verifies what stands in the field today and captures nameplate photos.
Expect conflicts between sources. What is installed beats what was ordered. Where records have drifted badly, rebuild from a walkdown instead of reconciling paper. A condition survey is one way to close the gap with verified field data.
5. Spreadsheet or maintenance system
Teams usually ask whether a spreadsheet is enough. It often is, at the start. A spreadsheet is quick to build, easy to share, and readable by anyone you hand it to.
The trade-off is control. Copies multiply, versions drift, and nobody knows which file is current. A maintenance system enforces one record and prompts updates, but it needs setup time and training.
Choose by behaviour, not by features. The right format is the one your team will actually update after every job. A well-kept spreadsheet with one owner can serve a large network for a long time.
6. Keeping the register current
A register decays without a routine. Every clean, lubricate, seal or repair job ends with a row update the same day. Symptoms noticed on rounds go in with a date and an observer.
Record how each symptom was verified. A pressure decay check across the closed valve, or double block and bleed monitoring, is confirming evidence. Sound, smell or bubbles are screening signs that indicate, not prove.
Give the register one named owner per site. Review it against a calendar that fits your climate and loading. Our notes on seasonal planning for the valve calendar and on starting a valve maintenance programme help set that rhythm.
Let the register force honest endpoints. A valve that still passes after recorded treatment needs a proper assessment, or replacement, not another entry.
Valve register template questions, answered directly
What fields should a valve register template include?
Include tag number, location, manufacturer, model, serial number, size, body material, service conditions, injection fittings and their condition, OEM document reference, maintenance history and current symptoms. Add a field showing how each symptom was verified, because screening signs and confirmed tests should not sit at the same level.
How do I collect valve data for a register?
Photograph each nameplate during a walkdown, then transcribe it. Cross-check against P&IDs, isometrics, procurement records and OEM documents. Where sources conflict, trust what is physically installed over what was ordered, and flag gaps rather than guessing entries.
Can I maintain a valve register in a spreadsheet?
Yes, and many sites do. A spreadsheet is quick to build and easy to share, but copies drift apart and versions multiply. Give the file one named owner, update it the same day as each job, and move to a maintenance system only when discipline fails.
How often should a valve register be reviewed?
Update rows the same day any valve is worked on or a symptom is logged. Beyond that, review the whole register on a fixed cadence that matches your maintenance calendar and climate. A register nobody reviews goes stale and stops supporting decisions.
Send the valve list and nameplate photos. An engineer replies within 24 hours.
Share your site details, valve count, existing records and any nameplate photos. We will suggest a register structure and a survey plan.