Document control built for the fabrication shop. Heat numbers, welders, procedures, examinations and tests recorded against the item they belong to — and compiled into a Manufacturer’s Data Report that survives review, for the life of the vessel.
Most software would file a vessel under the purchase order it was built on. That works until the order closes — and then a nameplate goes out the door carrying a National Board number that will be looked up in fifteen years by an inspector who has never heard of your job number. A code shop’s permanent unit is the item. It gets built, stamped, sold, installed, inspected, repaired and re-rated, long after the paperwork that authorised it is archived. CodeShop QC is built that way from the database up: records hang off the item, so the traceability chain does not break the moment the item ships — which is precisely when it starts to matter.
Mill test reports checked against the specification, heat numbers recorded, and — the part auditors actually look at — the traceability marking carried across every cut. A heat number on a plate is worthless once it becomes six pieces.
Every joint on a weld map, tied to the procedure it was run to and the welder who ran it. Qualification is checked as at the date of the weld, not today — a lapse last month does not invalidate a weld made in March.
NDE by method, extent and acceptance, with the technician’s certification. Heat treatment charts. Pressure test with the inspector’s witness and the gauge calibration standing behind the reading.
One chain, reconstructable on demand for any item you have ever built. The nameplate — not an internal record number — is what the customer, the jurisdiction and the next inspector will search by.
Once an item is stamped and its data report signed, the package is a legal document, and CodeShop QC treats it as one — the records become read-only. Nobody quietly edits the weld log on a vessel that has already shipped. Changes after that point are a repair or alteration under the R stamp, recorded as a new layer with the original left intact.
The certification that lets you build and sell in the first place. It belongs to the shop, not to any one item, and it is what a joint review examines.
What travels with the vessel. Owned by the item, handed to the customer, and looked at again every time the vessel is inspected for the rest of its life.
An inspector seat is free and read-only. They can see the package, and the one thing they can write is their own observations — a walk-down note is their record of what they saw, not a change to yours. Charging for that account would put a price on exactly the person you most want looking at your work.
A joint review runs in three stages. Most shops fail the first one on paperwork they already had, filed somewhere nobody could find it under questioning. CodeShop QC keeps the evidence in the shape the review asks for.
$599 per review cycle — and that includes the thirty-day follow-up and any re-review, through to closure. If deficiencies are found you are not invoiced again for the privilege. That is the moment you most need the tool and least want another bill.
Sold per review cycle, on top of your seats. Covers the review, the thirty-day follow-up and any re-review, through to certificate issuance. Attaches to your shop’s authorization, not to any single item.
CodeShop QC launches for new construction. Repairs and alterations to already-stamped vessels — the R stamp item workflow — are not in the first version, so a vessel you stamp today has no repair history in the app until that ships. Joint review preparation for an R stamp is unaffected: that covers your shop’s authorization to perform repairs, which is a separate thing. Said here rather than discovered later.
Document control for your code shop.
You followed a reset link. Set a password and you’ll be signed in.
This is the organization every item, job and certificate will belong to. You can rename it later.