Owner engineering teams occupy a structurally different position in the document review process than EPC contractor teams. The contractor produces documents as part of its design work. The owner engineer reviews those documents against a set of requirements that were defined before the contractor was engaged. This distinction creates specific review dynamics that are worth understanding on their own terms, separate from how the contractor manages its internal document control.
This article describes the typical owner engineering review workflow, the specific types of inconsistency that owner engineers are best positioned to catch, and where the workflow breaks down under document volume and schedule pressure.
The Owner Engineer's Reference Baseline
Before a contractor begins work, the owner defines the project requirements in a set of basis documents: the project specifications (process, civil, mechanical, instrument, electrical), the design basis memorandum, and often a set of owner-specific engineering standards that supplement or supersede general industry standards. These basis documents are the reference against which contractor deliverables are reviewed.
The owner engineer's primary review question is: does this contractor document conform to the requirements stated in the basis documents and project specifications? This is distinct from the contractor's internal question, which is: does this document conform to the current P&ID and the other documents in our own deliverable set?
In practice, owner review covers both questions. An owner engineer reviewing an instrument datasheet will check both that the datasheet meets the project's instrument specification requirements and that the process conditions stated on the datasheet agree with the process data sheet that was issued as part of the project basis. These are different checks, and failing either one generates a comment.
The Transmittal-Review Cycle
Contractor documents are issued to the owner through a formal transmittal process. The transmittal package typically includes a cover sheet listing the documents being issued, their revision status, and the reason for issue (for review, for approval, for information, etc.). The owner engineer receives the transmittal and has a contractually defined review period, typically ranging from 10 to 21 calendar days depending on the document type and the project contract terms.
Within the review period, each document receives a review code: Approved, Approved as Noted (comments to be incorporated in next revision), Returned for Revision (significant comments, resubmittal required), or similar project-specific codes. The review comments are compiled into a comment sheet attached to the returned document transmittal.
The volume of documents in a single transmittal batch varies widely. BASIC engineering milestone submissions may contain 50 to 200 documents covering multiple disciplines. Vendor document submittals can add another 30 to 80 documents per major equipment package. Over the course of a detailed design project, a large capital project may generate several thousand transmittal transactions, each requiring owner review of some portion of the document set.
What Owner Engineers Actually Check
The depth of review varies by document type and by the criticality of the system being designed. For P&IDs, owner engineering typically performs a detailed technical review: are all control philosophy elements correctly implemented? Are safety instrumented functions shown consistently with the safety requirement specification? Are owner-specified equipment types correctly represented?
For instrument datasheets, the review focuses on specification compliance: does the instrument type meet the project specification requirements for that service? Are the materials of construction appropriate for the process fluid? Do the process conditions fall within the instrument's rated range? Are the set points (where shown) consistent with the project's alarm and trip philosophy?
For line lists, the review typically checks that line classes and specifications match the project's piping material specification, and that design pressure and temperature values are consistent with what was stated in the project basis documents for each process area. A line list entry with a design pressure that does not match the relevant process system's maximum allowable working pressure is a category error that owner review should catch.
Where Inconsistencies Surface During Owner Review
Owner engineering review has a different view of the contractor's document set than the contractor's internal review processes. Because the owner engineer is checking against external basis documents rather than against internal project documents, they often catch a specific category of inconsistency that contractor self-review misses: the drift between the contractor's current documents and the project basis that was defined before contractor engagement.
A common example: the project basis documents specify that all high-integrity pressure protection systems on a particular process unit shall be designed to a specific overpressure protection philosophy. The contractor's P&ID for that unit, revised several times since FEED, may have drifted away from that philosophy in a minor but real way. The contractor's internal review does not catch this because the reviewer is comparing the current P&ID to the previous P&ID revision, not to the owner's project specification. The owner engineer, working from the specification, catches it.
A second category is numeric consistency between contractor documents and the process data sheets issued by the owner as part of the project basis. If the owner's process data sheet for a pump states a maximum suction temperature of 85 degrees C, and the contractor's pump datasheet shows a design temperature of 75 degrees C, the discrepancy is a review finding. The root cause may be a P&ID revision that the owner issued after the process data sheet was frozen, or a transcription error in the contractor's datasheet preparation. Either way, the owner engineer catches it by cross-checking the two documents.
The Volume Problem and What Gets Missed
The structural weakness of owner engineering review is that it is performed at limited depth at high volume and under schedule pressure. A single owner engineer reviewing 80 instrument datasheets in a 15-day review period has roughly 2.5 hours per document. For a complex instrument, that is manageable. For a batch of straightforward instruments that share similar characteristics, it creates pressure to batch-review rather than individually check each one against all relevant basis documents.
Batch reviewing means applying a pattern check: if the first 20 datasheets in a batch look consistent with the specification, assumptions are made about the rest. This is rational behavior under time pressure. It also means that a systematic error, a recurring wrong value, a consistently missing specification requirement, may be checked in the first five documents and then passed through without further checking in the remaining 75.
Owner engineers are generally aware of this limitation and compensate by prioritizing their review effort on high-risk or high-complexity documents and spot-checking lower-risk documents. This prioritization is informal and depends on the reviewer's knowledge of which systems carry the highest engineering risk. Formalizing that prioritization, and ensuring that spot-checks are directed toward the documents most likely to contain inconsistencies, is a natural application for a cross-check tool that can flag which specific documents in a batch contain attribute values that do not align with the project basis.
Owner engineering review will remain a judgment-intensive process regardless of what tools are available. The engineering decisions, the system safety implications, and the contractual interpretation of specification compliance require human expertise. What a cross-check tool can do is reduce the search cost for finding the documents that most warrant careful review, and provide a structured record of which attribute values were checked against which reference documents and what the outcome was. That record is also valuable during construction and commissioning, when questions arise about the basis for a particular design decision.