KordBlog
Engineering document review, in practice
Real workflows, failure modes, and checklists for teams managing P&IDs, spec packages, and submittals.
Forty-seven comments and one Excel file
A customer review round comes back as dozens of comments spread across marked-up PDFs and an Excel log. It's easy to check a comment off in the log and never update the actual file, or to let a markup slip through. The hard part isn't fixing the comments. It's proving every fix made it into the revision you shipped.
Read articleThe calc sheet changed. Nobody diffed it.
Spreadsheets hold the numbers that drawings cite. When only PDFs go to review, formula changes and cell edits stay invisible until someone on site asks why the valve size does not match the calc.
Read articleYour P&ID still says 150 psig
When one pressure spec changes, the rest of the document set often doesn't. A realistic walkthrough of how cross-document drift causes rework, resubmittals, and expensive surprises, plus what to do about it.
Read articleYou forked the folder. The tags didn't follow.
Copying a base design for a new site is fast. Renaming four hundred equipment tags across P&IDs, datasheets, line lists, and calcs is where base-design programs quietly bleed margin.
Read articleRev C is approved. Which Rev C?
Approval stamps look definitive. On a live project they often cover different file revisions, partial discipline sign-offs, and a PDF export that happened Tuesday while the source file changed Wednesday.
Read article