The Job Book That Answered Nothing

A midstream operator had an opportunity to take on more gas from a new well connect. One condition: the line would have to carry it at a higher operating pressure, which meant uprating its maximum allowable operating pressure — the MAOP. Uprating is fundamentally a records question: you demonstrate, from traceable, verifiable, complete records, what every component in the system is rated for — pipe, fittings, valves, flanges — because the weakest one sets the ceiling.

The records couldn't answer it. The system's job books existed — volumes of them — but they could not establish something as basic as the flange class at the future connection point. So the construction manager did the only verification left available: he spent a full day driving the line, in person, reading flange markings off the steel itself.

When our specialist reviewed the job books, the verdict was blunt: this was risk-wise worse than having no book at all. The operator clearly knew they needed records — they had built books. But nothing in them was of value or confidence for the question that mattered.

And there was a coda. Visiting their operations group, our specialist learned the same line had recently been repaired for internal corrosion after a failure at low pressure. The physical asset was in worse condition than anyone's records suggested — the very line they were evaluating for a pressure increase.

Records that exist but answer nothing — false confidence, filed in volumes.

Federal pipeline safety regulation is explicit about what records must do: for an operator to establish or increase MAOP, it needs records that are traceable, verifiable, and complete — or it must fall back to testing and conservative assumptions. A book that fails that standard isn't a partial-credit record set. Regulatorily, it's the same as no records at all, plus one additional liability: internally, it stops people from acting. That's why a book with nothing of value in it is worse than no book. No records prompts a project. False records postpone one.

The MAOP question is also the purest test of what a record system is for. Records exist so that a question like 'can this line carry more gas?' is answered at a desk, in minutes, from documents. When the answer requires a day in a truck reading steel, the record system has already failed — the truck day is just the visible cost. The invisible cost was the opportunity sitting in a queue behind an unanswerable question.

The root is a record set that exists but cannot answer the question it exists for. The public record shows what that root produces:

And the doctrine that binds them: under federal regulation, an operator whose records cannot establish its maximum allowable operating pressure must fall back to conservative assumptions and testing. The regulator's own codification of this finding is that a book which answers nothing is treated exactly like no book — with one difference. No book prompts a project. A hollow one postpones it.

The stranded party in this story is not only the operator. Upstream, there is a well behind the connect — a producer waiting on new revenue while the line's records couldn't answer the question standing between them and it. Closer in: a construction manager spent a full day doing physically what a single mill certificate should have done in minutes; engineering stalled mid-evaluation; and whoever wins the eventual remediation project inherits the chaos the original records were supposed to prevent. The original record producers fared worst of all — volumes of deliverables, multiple years of work, worth nothing when tested against the one question that mattered.

By asking the record system the exact question it existed to answer. A review that evaluates records against a real engineering decision — not for presence, completeness of tabs, or volume — exposes the difference immediately. And by walking the gap between paper and reality: operations knew things about that line the books didn't.

A construction manager's full day of physical verification — the cheapest line item. The evaluation itself stalled: an uprate on a line with unproven component ratings and a recent corrosion failure isn't a records problem anymore, it's a capital project. And behind all of it, a well connect — new revenue — waited on documentation that had never actually been built.

A record system is measured by the questions it can answer, not the paper it contains. 'We knew we needed a book' is the beginning of compliance, not the end of it. The book that gets built for show is the most dangerous artifact in the records room: it looks like an answer, and it isn't one.