Edit in Excel

Edit in Excel (/edit-in-excel) lets you round-trip a subset of a weld’s fields through Excel instead of editing them one at a time in the weld matrix. It’s a batch return, not offline sync — every change still goes through the same audited rules as the app.

Before you start

You need Weld Associate access or higher, plus write access to the project — a lower role can open the screen but is refused when it tries to check out or return a workbook.

Check out

Open Edit in Excel from the navigation.
Select Check out for editing. This downloads an Excel workbook of the project’s active welds that you can see — the same welds your weld list shows you — with a hidden, per-row identity token you never see or edit. If your access is limited to certain contractors, weld types, or facilities, or you’re working as a contractor company that sees only its own welds, welds outside it are left out of the workbook.

Only a whole-project check-out is available today; there’s no per-ISO scope picker yet.

Edit the workbook

These columns are editable: Weld Date, Schedule, Spool, Joint Location, Description, and the Welder slots (below). Everything else on the sheet — ISO drawing, weld number, weld type, latest RT, and status — is shown for context only and is ignored on return, even if you change it.

Write Weld Date as yyyy-mm-dd — for example 2026-05-07 — which is the form the check-out writes. A slash-separated date is read month-first, so 05/07/2026 means 7 May, not 5 July. A date MaxTrax can’t read at all doesn’t quietly disappear: the whole row is rejected on return, with the offending text shown in the reason, so you can fix it and return the file again.

Welders

The sheet carries the weld’s welders in numbered columns — Welder1, Welder2, and so on. Each cell holds a welder’s stencil, and each has a dropdown listing the welders you can assign on this project, so you can pick rather than type. The check-out always emits at least four slots, and more when some weld in the scope has more welders, so a weld can never run out of columns.

A row that names a welder must also carry a Weld Date — attributing a weld to someone means saying when they welded it — otherwise that row is rejected and nothing on it is applied.

If a stencil can’t be used, the row is rejected with the reason naming the stencil, and the rest of the file still applies. That happens when the stencil matches no active welder, when it belongs to a welder at a different facility from this project, or when it’s a welder you’re not allowed to assign. Picking from the dropdown avoids all three.

Some welds show blank Welder slots even though they do have welders — the welder is inactive, has no stencil, or belongs to a contractor outside your access. Those welds keep their welders untouched, and to protect the attribution you can’t see, MaxTrax refuses any Welder-slot edit on them (everything else on the row is unaffected; edit those welds in the app instead).

To remove a weld, type TRUE in its Archive column. A row with no hidden identity token (a row you added yourself) can’t be archived — remove the flag, or archive the row that actually owns that weld.

You can also append new rows: a row with no identity token, but with a drawing number, weld label, and weld-type code that match something already in the project, creates a new weld — as a skeleton only. Give it its full descriptive detail on your next check-out and return, or use Import for full new-weld authoring in one pass.

Return the workbook

Select Return workbook and choose the file you checked out — it must be the same file; a plain grid or report export has no round-trip marker and is refused outright, with nothing applied.
Review the counts under Review what will change — updates, creates, archives, and any conflicts or rejections — before anything is written. If the file matches the server exactly, the page says No changes found and offers nothing to apply; edit the workbook and return it again.
If any rows show a version conflict (someone changed that weld on the server since you checked it out), choose Keep mine or Keep theirs for each one. Nothing is overwritten automatically.
Select Confirm and apply.

What happens next

Each row applies as its own audited update, create, or archive, exactly as if you’d made the change in the app — the same guards apply (a signed ISO still blocks a change, for example). A summary shows how many rows were updated, created, archived, held for an unresolved conflict, or rejected, with the reason for each rejected or held row.

A row whose hidden identity token names a weld outside the workbook’s scope — a weld you can’t see, or one moved out of scope since you checked out — is rejected with a reason saying so, and nothing on it is written. That’s also what happens if you return a workbook someone with wider access checked out: its rows for welds you can’t see are rejected the same way. A new row you add is checked too: if it names an ISO or weld type outside your access, it’s rejected just as if that ISO didn’t exist.

If a weld was completed on the server after you checked the workbook out, that row comes back as a version conflict, and choosing Keep mine for it is refused: your workbook still carries the “not welded yet” date the weld had at check-out, and applying it would un-complete a weld that now records who welded it. The row is held with that reason and nothing is written. Choose Keep theirs to accept the completion, or put the real weld date in that cell, return the workbook again and choose Keep mine for the row — the row stays a conflict until you resolve it, so returning the file on its own changes nothing.

Import weld data from Excel — full new-weld, ISO, and inspection authoring; the place to go when Edit in Excel’s fixed field set isn’t enough.
The weld matrix — editing one weld at a time, including welders MaxTrax won’t let you change from a workbook.
Weld status lifecycle — what a signed ISO locks.