Every fabrication project starts the same way.

Someone opens a blank spreadsheet, sets up columns for weld number, spool, WPS, welder ID, inspection status, and NDT result — and calls it the weld register. It works fine on day one. By week three, it's a problem.

This post is for the QC managers, document control leads, and project engineers who have built that template, maintained it through a live project, and felt it start to crack under the weight of real work. We'll look at why the Excel weld register breaks, what it costs when it does, and what a more durable approach looks like.

If you're here looking for a free template to download, there's one linked at the end. But read this first — it'll save you time later.

What a Weld Register Is Supposed to Do

A weld register is the master record of every weld on a project. It tracks:

Identity — weld number, spool, line, drawing reference
Process — welder qualification, WPS assigned, date welded
Inspection — visual inspection status, NDT type required, result
Repair history — cut-outs, re-welds, retests

At project close, the register is part of the documentation package handed to the client or owner. It proves traceability: that every weld was done by a qualified welder, under an approved procedure, inspected to the required standard, and that any repairs were properly tracked.

That's the job. On paper, Excel handles it. In practice, it doesn't — not under the conditions of an active fabrication project.

Why the Excel Weld Register Fails in the Field

1. The data is always a day behind

Welding happens on the shop floor. The spreadsheet lives on someone's laptop or a shared drive. Those two things are not in the same place.

The practical result: a fitter or inspector makes notes on paper or in their head, and those notes get typed into the register later — if at all. By the time the spreadsheet is updated, the workday is over, the data is hours old, and anyone trying to check current status is looking at yesterday's reality.

This gap is where most weld register problems start. Not because people are sloppy, but because the tool was never designed for the shop floor.

2. NDT tracking lives in a side system

Most weld register templates have a column for NDT type and a column for result. That's not enough.

Real NDT tracking requires: what percentage of welds on this line require RT? Of those, how many have been completed? Are any overdue? Are there hold points blocking progression? Which welds are in repair loops that affect the inspection count?

A flat spreadsheet column can't answer those questions without someone doing manual math and cross-referencing another file. So it either doesn't get done, or it gets done by a QC manager who rebuilds a summary every time the client asks for a progress report.

3. The drawing and the register are disconnected

The isometric drawing is where the physical work happens. The register is where the data lives. In an Excel workflow, these two things are completely separate — you mark up a paper print, then you go type the data somewhere else.

That manual transcription step is the source of most traceability errors. Numbers get transposed. Welds get entered against the wrong spool. A repair gets noted on the drawing but never makes it into the register. By the time someone notices, the original markup has been lost.

4. Version control breaks under project pressure

On a real project, the weld register template gets emailed between people. It gets saved as "weld_register_v2_FINAL_REVISED_use_this_one.xlsx." Someone edits it offline during a site visit and their changes conflict with the copy on the server.

Nobody is trying to create chaos. It just happens, because a shared Excel file is not built for concurrent use under project pressure.

5. Reporting gets rebuilt from scratch every time

When the client wants a progress report, or the inspector needs a list of all welds pending RT, or project management wants to know completion percentage — someone has to filter, sort, and format the spreadsheet into a presentable output. Every time. That's not reporting; that's manual reconstruction.

What the Weld Register Actually Needs

The register isn't the problem. The capture method is.

A weld register that works reliably on a live project needs to be:

Tied to the drawing. Weld data should be captured at the source — on the isometric — not in a parallel spreadsheet that has to be synced manually. When the drawing is the capture surface, the register updates itself as work progresses.

Accessible in the field. If the tool doesn't work where the welds are, it won't get used where the welds are. That means it has to run on a tablet, work without reliable WiFi, and not require logging into a system that needs IT to set up.

Built around weld identity, not just columns. Each weld entry should know its spool, its line, its NDT requirements, and its repair history — not as adjacent columns in a flat table, but as linked data that can be queried and reported without rebuilding the structure each time.

Exportable on demand. When it's time to hand over documentation, structured data should come out cleanly — not after someone spends a Friday afternoon reformatting the register.

How MapWeld Approaches This

MapWeld is built around one specific idea: the PDF isometric is the working surface, not a reference document you consult separately.

You load the drawing directly into the app. You place markers on the isometric — one per weld — at the exact location where the weld sits on the drawing. Each marker carries the weld data: WPS, welder, inspection status, NDT requirements, repair history. The drawing and the register are the same thing.

Because it runs in the browser and works fully offline, it's usable on the shop floor without an IT setup. There's no account to create, no server to configure, no training budget required. You can hand it to any QC inspector and they're capturing weld data in ten minutes.

When the job needs reporting — progress summary, NDT coverage, handover package — the export comes directly from the captured data. No reconstruction. No reformatting.

It doesn't replace your ERP or your document management system. It's the capture layer between the physical work and whatever system you hand data into.

The Free Weld Register Template (Excel)

If you need to start right now and Excel is what you have, here is a clean weld register template structured for pipe fabrication work:

Download: Weld Register Template — Excel (.xlsx)

The template includes columns for:

Weld number, spool reference, isometric drawing number
Weld joint type, diameter, wall thickness
Welder ID, WPS number, date welded
Visual inspection status and date
NDT type required, percentage, result, date
Repair record (repair number, date, re-weld, retest)
Notes / hold points

It's a starting point. Use it on small scopes or short-duration jobs where the limitations won't hurt you. On anything larger, consider whether the capture method is going to hold up under real project conditions.

The Honest Bottom Line

The Excel weld register template is not broken because Excel is bad software. It's broken because fabrication work doesn't happen at a desk, NDT tracking isn't a column problem, and version control under project pressure requires more than a shared file.

The teams that track welds reliably aren't the ones with the best spreadsheet. They're the ones whose capture tool is closest to where the work actually happens.

If that's a gap you've been working around, it's worth trying a different approach.

Load a drawing in MapWeld — free, no account needed →

Have a question about weld register setup or NDT tracking? Email us at hello@mapweld.app.