Case Study

Fixing the requirements before the records exist.

Specification Development

Situation

A privately held midstream operator backed by private capital needed to redevelop its construction specification. The old version no longer reflected the work actually being performed — or the evidence required to prove it. The gap is one the whole industry recognizes: requirements live scattered across codes, procedures, drawings, qualification records, and contractor practices, with no clear assignment of who must verify their combined applicability in the field. A qualified welding procedure and a qualified welder do not by themselves prove a particular weld was properly authorized. Someone has to verify that the procedure and the qualification ranges cover the actual material grade, diameter, thickness, joint, and field condition — and document that verification so the owner can demonstrate why the work was accepted.

The Work

MPS led the redevelopment in three stages. First, requirement identification: the construction, welding, inspection, material, and documentation requirements the specification had to address. Second, drafting: converting those requirements into specification language organized for both management and field use. Third — the step that separates a living specification from a desk exercise — MPS reviewed the draft line by line with the operator's construction management, testing every provision against actual operating conditions and management expectations until the language survived contact with the field.

The specification converted general compliance expectations into project-execution requirements. It clarified responsibility among construction management, contractors, welders, and inspectors. And it established the principle that inspection responsibility must be stated and documented — not assumed.

Outcome

The operator received a construction specification its own management had reviewed and accepted line by line — requirements written by people who had stood in the field they govern. The work also proved a larger point about where records quality begins: no records process can rescue a project whose requirements never clearly assigned verification responsibility in the first place.

The specification's principles — approved and qualified procedures verified for applicability, welder qualifications evaluated against actual ranges, acceptance tied to actual material and field condition, inspection responsibility documented — became the foundation of MPS's later specification work and were carried directly into the requirements-and-relationships model at the core of MPS-JobBook, where the platform captures the evidence that proves the requirements were met.

Why It Matters

Records review finds failures after the weld is in the ground. Specification work prevents them before the first weld is struck. Operators who fix the requirements get a downstream dividend: better records during construction, less reconstruction at closeout, and a stronger basis for audit, turnover, operations, and any future ownership change.

Request a briefing to review what your specification requires — and what it lets slip through.

Request a briefing through our implementation partner →