MRB Software
for Oil & Gas.

MRB software is purpose-built tooling for assembling, sharing and approving the Manufacturing Record Book — the quality deliverable that proves a piece of fabricated oil & gas equipment was built to specification. It exists because spreadsheets, shared folders and PDF mergers are the wrong tools for the job, and because the cost of getting it wrong runs into hundreds of thousands of dollars in delayed hand-overs.

In an EPC context, the MRB is rarely produced by one party. A typical subsea tree might involve a primary fabricator, a forging supplier, a coatings sub-contractor, an NDT house, two third-party inspection bodies, and a logistics provider — each of whom owns a slice of the documentation. MRB software's primary job is to coordinate these parties.

The MRB process in oil & gas has a distinct shape: it is a chase. The Document Controller spends most of the project chasing certificates that should have been delivered weeks ago — usually by email, usually with WeTransfer links that expire before they are downloaded.

Where the time actually goes

Industry benchmarks suggest that on a medium-sized subsea or offshore module, the MRB lifecycle absorbs 40 to 80 hours of Document Controller time, plus another 20 to 40 hours of Quality Manager review. Of those hours, perhaps 30% is productive work — assembling, indexing, reviewing — and the remainder is overhead: chasing, re-merging when a supplier sends an updated revision, hunting for the latest version of a procedure, manually renumbering pages after a late insertion.

The handover gate

The contractual exposure makes this overhead expensive in a way that a manufacturing line never sees. The MRB typically gates the final 5% to 15% of the project value at handover — and on offshore projects worth tens of millions, a delayed MRB can hold up payments equal to a year of operating cost in a fabrication shop.

Oil & gas MRBs sit at the intersection of three code families. Most projects reference all three, plus a client-specific layer of additional requirements.

NORSOK — the Norwegian sector standard

The NORSOK suite was developed by the Norwegian petroleum industry to consolidate operator requirements across the North Sea. Three NORSOK standards are routinely referenced in MRBs: NORSOK M-101 (structural steel fabrication), M-630 (material data sheets for piping), and M-650 (qualification of manufacturers of special materials). Each comes with its own documentation expectations.

API — North Sea, Gulf of Mexico, global subsea

The American Petroleum Institute's standards are the global reference for upstream and subsea equipment: API 6A for wellhead and christmas tree equipment, API 17D for subsea wellhead systems, and API 1104 for pipeline welding. EPC contractors typically expect API certification or full conformance demonstrated through the MRB.

ASME — the construction code

ASME Section VIII Div. 1 and Div. 2 govern pressure vessels, while ASME B31.3 governs process piping. For most oil & gas MRBs in U.S.-led projects, ASME is the dominant construction code, with NORSOK or client-specific documents added on top.

Client specifications

Above the code minimums, each operator and EPC contractor publishes a Vendor Document Requirements list (VDR) that defines what must be in the MRB and in what format. TechnipFMC, Saipem, Subsea7, Aker Solutions, McDermott and Wood each have their own VDR templates, and most are non-negotiable in the contract.

Not every quality-document tool that calls itself "MRB software" is built for the EPC supply chain. The four differentiators that matter most:

Stripped to its essentials, a modern MRB workflow looks like this:

1. Day 1 — Index generated. The QC-Manager selects the project type and applicable codes. The platform produces a complete MRB index with the right categories, sections, and document slots — ready for client approval.
2. Day 2 — Index approved by client. The client (or EPC contractor) reviews the index online, comments inline, and approves it. From that moment the index is locked as IFA, and any change creates a controlled revision.
3. Day 3 onwards — Suppliers invited. The Document Controller assigns chapters to each supplier and sends invitation links. Suppliers upload directly. The Controller sees in real time who has delivered, who is late, and what is still missing.
4. Throughout fabrication — Continuous compilation.As welding, NDT and testing happen, certificates and reports flow into the MRB. The Quality Manager reviews per chapter, marking sections complete or rejecting with comments that go straight back to the supplier.
5. Project end — Final assembly. One click generates the final PDF: cover page, table of contents, bookmarks, transmittal — server-side, in seconds, from the data already in the platform.
6. Handover — Client review online. The client reviews the final MRB in the browser, annotates, approves, or rejects with revision requests. Once approved, the package is locked as Approved and archived.

The most under-appreciated benefit of a modern MRB platform only appears once it has been used across more than one project: suppliers learn the workflow. The forging supplier you used on Project A becomes faster and more accurate on Project B because they already know how to upload, where to upload, and what acceptance criteria look like.

Over time, this creates a network effect across the EPC supply chain. When a supplier you invite is already using the platform on someone else's project, your invitation arrives in a workspace they already understand. The project appears in their dashboard, clearly labelled as yours, and they are productive in minutes. It is the closest the fabrication world has to a shared operating system for quality documentation.

For an EPC contractor managing fifty suppliers across three continents, the cumulative effect on documentation lead time is substantial — and structural.