Your P&ID still says 150 psig

The process engineer updates the P&ID. Inlet pressure drops from 150 psig to 120 psig. The change is correct. The customer revised the operating case. The P&ID gets saved, exported to PDF, and uploaded to the submittal folder. Reviewers mark it approved. So far, so good.

Three weeks later, the customer opens the Concept of Operations, the document they read first, and it still describes a 150 psig inlet. Everything technical had moved: the P&ID, the datasheets, and the heat and mass balance all show 120. But the narrative spec was updated last, by someone else, and it kept the old number. The engineer did almost everything right and still shipped one document that said 150. Nobody lied. Nobody skipped a step. One file just drifted.

Why this happens on almost every project

Engineering deliverables are a set, not a file. A pressure change ripples through P&IDs, vessel datasheets, line lists, relief studies, heat and mass balances, procurement lists, and narrative specs. Teams know this intellectually. In practice, updates happen under deadline pressure: one discipline moves first, others catch up in the next transmittal, and tribal knowledge fills the gaps between.

• Files live in SharePoint or Drive with version numbers, but no one sees semantic drift across the set.
• Bluebeam sessions compare PDFs one at a time, great for markups but weak for package-level consistency.
• PLM tracks parts and CAD files; it was never built for spec packages and submittal PDFs.
• Document control records status and approvals, not whether the Concept of Ops matches the vessel MAWP.

Where the old number usually hides

In a typical package after a single pressure revision, these are the usual suspects:

• Concept of Operations: narrative text still cites 150 psig inlet pressure.
• Vessel spec V-301: MAWP still shows 150 psig while operating pressure moved to 120 psig.
• Heat and mass balance: valve CV sized for 150 psig upstream; flow rates no longer match the revised case.
• Procurement list: material grade may be over-spec for the reduced pressure (SA-516 Gr.70 when a lower grade would suffice).

Each item is fixable in an afternoon. Catching them after customer review costs weeks. And credibility.

What good looks like before release

High-performing teams treat the document set like a system under test. When a driving parameter changes (pressure, temperature, material, equipment tag), they ask one question: what else still references the old value? That check used to mean senior engineers scanning folders from memory. It does not scale across site forks, customer variants, and fast-turn submittals.

The workflow we built Kord for: sync the changed files, run cross-document consistency checks (including AI-assisted reads across specs and calculations), group everything into a structured review session with visual diffs per format, and release with an audit trail that ties approvals to a specific revision set, not a scattered email thread.

How Kord catches the drift

• Kord's consistency check reads across the whole set (Concept of Operations, vessel datasheet, heat and mass balance, procurement list) and flags any document still carrying 150 psig after you drop the inlet to 120.
• It diffs each format natively, so the change surfaces as a marked cell in the heat and mass balance, a clouded region on the P&ID, and a redline in the narrative spec, not just "this file changed."
• Every changed file lands in one review session, so a second discipline signs off on the downstream docs before release, not three transmittals later.
• It pins each approval to a specific file revision, so "approved" means a named snapshot of the set rather than a PDF that kept drifting after export.
• It syncs on top of SharePoint or Drive, so the change layer plugs in without moving a single file.

If your team runs base designs across multiple sites, scanning folders from memory does not scale. That is the gap between file storage and PLM: document-set change management with visual diffs and consistency checks before the customer sees 150 psig in a document you thought was dead.