The item outlives the job
that built it, by decades.

So why are your records filed under the job?

The vessel ships. The folder stays behind.

A pressure vessel leaves your floor with a National Board nameplate on it. From that moment it has to stay traceable to its materials, its welds, its NDE and its inspection sign-offs — for its whole service life. Twenty, thirty, forty years.

But the records that prove all that are almost always hung off the job. The purchase order. The work order. A folder named after the customer. Which means traceability starts breaking the moment the item ships, which is exactly the moment it starts to matter.

You find it. You usually find it. But it takes a day and a half, and the finding is the whole job — a record you cannot produce is a record you do not have.

CodeShop is built around the item.

Every record hangs off the vessel, the spool, the skid — not off the job that happened to pay for it. The heat number, the WPS, the welder, the NDE report, the hydro, the AI's signature on each hold point. Attached to the thing itself.

Jobs still exist. A customer order groups several items under one PO with the client and PO number recorded for the office, and the package shows one rolled-up status. But the records belong to the item, so when the package is closed and the customer is gone, the vessel still knows what it is made of.

Two levels, because they have two different owners.

Qualification is checked as at the date of the weld.

Not as at today. A welder whose continuity lapsed last month did not invalidate a weld he made in March, and a system that says otherwise is one you will stop trusting by the second week. CodeShop checks the qualification against the date the work was actually done.

The Authorized Inspector has a seat, and it costs nothing.

The AI is an outside party with real authority over your work. Treating that relationship as a paid user account never made sense to us, so it is free — enforced in the system, not promised in a price list. The seat count excludes inspectors and auditors entirely.

An AI serving six shops appears on six accounts and generates a charge on none of them. They sign hold points; they do not edit your records.

A third-party inspector sees one client's work. Only that client's.

If you build for Company A and Company B, and both have inspection firms on your floor, A's rep sees A's packages, items, records and findings — and nothing of B's. That boundary is enforced by the database, not by a screen that hides a menu. They raise NCRs and Observation Reports against their own client's work, and once a report is issued the finding is frozen.

Joint review preparation — $599 per cycle.

An R or U stamp runs about three years, and then the whole thing happens again. CodeShop tracks the cycle: application sent, acknowledged, review scheduled, certificate issued, expiry. It holds every document the team will ask for and tells you which ones are still outstanding.

What it will not do.

• It records a classification; it does not pick one.
• It holds a document; it does not approve one.
• It does not decide whether your work conforms. The code, your Authorized Inspector and your own quality program decide that.

Better to know that here than after a purchase order.

What it costs.

One tier. No setup fee, no per-item charge, no minimum term. Count the people who enter or change records — not the people who read them.

If you stop paying, your records stay readable and printable. What stops is adding new work. A code shop locked out of its own certification records over an invoice has a problem far larger than a subscription.

Start at codeshopqc.com

Fourteen days, no card. Build one vessel through the checklist and see whether the shape of it fits how your shop actually works. If it does not, tell me what is wrong with it — this is a small industry and I would rather hear it.

Jacob Horton · CodeShop QC