The calc sheet changed. Nobody diffed it.

The relief valve sizing workbook lives in Excel. Always has. Process updates a flow case without realizing that relief size on a separate tab changed as well. Saves. Exports a PDF snapshot for the submittal. The P&ID still shows the old valve size because the piping lead has not picked up the change yet. Both files go out on the same transmittal.

Reviewers compare PDF to PDF in Bluebeam. The calc PDF looks fine: neat tables, familiar layout. Nobody sees that cell D14 went from 12,400 to 8,900 lb/hr. The diff is a number in a grid, not a cloud on a drawing.

Why spreadsheets slip through

Engineering review culture is built around drawings. A change on a P&ID gets a revision cloud, and reviewers are trained to look for it. A changed cell in a spreadsheet announces nothing: same font, same layout, same total at the bottom. The number is different and the page looks identical.

• Formula cells change value without changing font color, so nothing "looks" different on print.
• Multiple tabs; reviewers open the summary sheet, not the inputs tab where the error lives.
• Linked workbooks break silently when someone moves a file in SharePoint.
• Version suffix in the filename says Rev B; the author forgot to bump it after a Friday edit.

Where it hurts

That valve size on the datasheet was not chosen by hand. It came straight from the calc: size the valve for the flow on sheet 3. So when process drops that flow from 12,400 to 8,900 lb/hr, the calc recomputes a smaller valve. But the edit was upstream, so the final number changes and the datasheet still lists the valve sized for the old flow. The calc moved; the design that depends on it did not. Nobody catches the gap until procurement, fabrication, or field fit-up, when changing a valve is expensive and explaining why is worse.

Diff the calc like you would a drawing, don't bury it in a static PDF.

How Kord fixes this

• Kord diffs the native workbook cell by cell, so a changed input or formula lights up instead of hiding behind a total that prints the same.
• It diffs every tab, including the inputs sheet reviewers never open, not just the summary at the front.
• It reviews the calc in the same session as the P&ID and the datasheet, so a change shows up next to the documents that cite it.
• Its consistency check reads across the package and flags the mismatch for you: the calc now sizes a smaller valve, the datasheet still specs the old one.
• It pins every approval to a specific workbook version, so Rev B can never quietly mean two different files.

On most projects, the spreadsheet is where the mistake starts. Treat the calc as a deliverable that gets diffed and versioned like every drawing, and the drift gets caught in review instead of at fabrication.