— A Practical Guide for Engineers, EPCs, and Project Teams
In any EPC project, the engineering work does not stop when the purchase order is issued. In fact, a significant portion of the instrument engineer's workload shifts to vendor document review (VDR) —the systematic process of reviewing, commenting on, and approving the technical documents that equipment suppliers submit throughout the project lifecycle.
A poorly managed VDR process is one of the leading causes of project delays. Documents sit in review queues for weeks. Comments are vague or contradictory. Vendors resubmit the same errors multiple times. By the time the final approval is given, the construction schedule has slipped, and the project is playing catch-up.
This guide provides a practical framework for reviewing instrument vendor documents during EPC project execution, covering the VDR process, key document types, review priorities, common pitfalls, and best practices.
1. What Is Vendor Document Review (VDR)?
Vendor Document Review is the process by which the EPC contractor's engineering team reviews, comments on, and approves the technical documents submitted by equipment vendors. These documents include datasheets, drawings, calculations, procedures, and quality records that together define the equipment being supplied.
1.1 Why VDR Matters
| Purpose | Why It Matters |
|---|---|
| Ensures compliance | Verifies that the vendor's offering meets project specifications, standards, and contractual requirements |
| Captures design intent | Documents the "as-designed" configuration before manufacturing begins |
| Enables interface coordination | Confirms that the equipment interfaces correctly with other systems (piping, electrical, civil, control system) |
| Reduces field changes | Catching issues during document review prevents costly rework during construction and commissioning |
| Provides audit trail | Creates a documented record of technical decisions and approvals |
| Supports quality assurance | Vendor documentation is evidence that materials and equipment comply with project specifications- |
EPC insight: Vendor documentation is not administrative overhead—it is the evidence that materials comply with project specifications-. A well-executed VDR process is the difference between a project that stays on schedule and one that suffers from preventable field surprises.
2. The VDR Process: A Step-by-Step Framework
2.1 Establish the Vendor Document Register (VDR)
Before any documents are submitted, the EPC contractor must establish a Vendor Document Register (VDR) —a tracking tool that records the status of every document listed in the Material Requisition or purchase order-.
What the VDR should contain:
| Field | Purpose |
|---|---|
| Document Number | Unique identifier for each required document |
| Document Title / Description | What the document covers |
| Required Submission Date | Contractual deadline for first submission |
| Actual Submission Date | When the vendor actually submitted |
| Review Status | Draft, Under Review, Comments Issued, Resubmitted, Approved |
| Review Due Date | Contractual deadline for EPC review |
| Reviewer | Assigned engineer or discipline lead |
| Revision History | Track changes across submissions |
| Comments / Remarks | Summary of outstanding issues |
Best practice: The VDR must be agreed with the vendor in writing at project kick-off-. Both buyer and vendor maintain the VDR throughout the order lifecycle-.
2.2 Define Review Cycles and Turnaround Times
Contractual review cycles must be clearly defined in the purchase order. A typical VDR process includes:
| Stage | Activity | Typical Duration |
|---|---|---|
| Vendor Submission | Vendor submits documents for review | — |
| EPC Internal Review | Discipline engineers review and consolidate comments | 5–10 working days |
| Inter-Discipline Check (IDC) | Cross-check with piping, electrical, civil, and process | 2–5 working days |
| Client Review (if required) | Submit to client for approval | 5–15 working days |
| Comments Issued | EPC returns commented documents to vendor | — |
| Vendor Resubmission | Vendor addresses comments and resubmits | 5–10 working days |
Typical contractual requirement: The purchaser shall complete the supplier's document review within 15 working days from the date of receipt-. If the document is reviewed with Code 'B' or 'C' (requiring resubmission), the supplier shall respond to the comments and re-submit the document within 10 working days-.
2.3 Review Status Codes
Standard review status codes help both parties understand the outcome of each review:
| Code | Meaning | Action Required |
|---|---|---|
| A (Approved) | Document is approved as submitted | No further action |
| B (Approved with Comments) | Document is approved subject to minor corrections | Vendor to correct and resubmit for record |
| C (Revise and Resubmit) | Document requires significant revisions | Vendor to revise and resubmit for full review |
| D (Reject) | Document is fundamentally non-compliant | Vendor to rework and resubmit |
2.4 The Review Workflow
1. Vendor submits document → enters VDR as "Submitted" 2. Document Control distributes to assigned reviewers 3. Discipline engineers perform technical review 4. Comments are consolidated and reviewed internally 5. Inter-Discipline Check (IDC) is performed[reference:7] 6. Document is returned to vendor with status code 7. Vendor addresses comments and resubmits 8. Repeat until document achieves "Approved" status
Inter-Discipline Check (IDC) is performed to ensure that the design and engineering output, including supplier documentation, meets the project design requirements across all related internal disciplines-.
3. Key Instrument Vendor Documents and Review Priorities
Different document types require different review approaches. The following table outlines the key instrument vendor documents and what to check for each:
3.1 Instrument Datasheets
| What to Check | Why It Matters |
|---|---|
| Process data alignment | Cross-check with process data, P&ID, and control philosophy- |
| Range and units | Confirm measurement range matches the process requirements |
| Accuracy class | Verify meets project specification minimum |
| Wetted materials | Confirm compatibility with process media and temperature/pressure |
| Process connection | Verify thread type, flange rating, and facing match the piping specification |
| Electrical requirements | Confirm power supply, output signal, and communication protocol |
| Ex certification | Verify zone, gas group, and temperature class are correct |
| All fields complete | Ensure no blank fields—incomplete datasheets are a common issue- |
3.2 Dimensional Drawings / Outline Drawings
| What to Check | Why It Matters |
|---|---|
| Overall dimensions | Confirm the instrument fits in the allocated space |
| Process connection location | Verify alignment with piping and hook-up drawings |
| Cable entry location | Confirm cable entry orientation and gland size |
| Mounting details | Verify bracket type, bolt pattern, and mounting orientation |
| Weight | Confirm support structures are adequately sized |
| Clearance requirements | Verify sufficient space for maintenance access |
3.3 Wiring Diagrams / Connection Diagrams
| What to Check | Why It Matters |
|---|---|
| Terminal identification | Verify terminal numbering matches loop diagrams |
| Wire colours and numbering | Confirm consistency with project colour coding |
| Shield and drain wire termination | Verify grounding arrangement (single-point vs multi-point) |
| Power supply connections | Confirm voltage and polarity |
| Communication wiring | Verify HART, Modbus, or fieldbus wiring details |
3.4 Hook-Up Drawings (Vendor-Specific)
| What to Check | Why It Matters |
|---|---|
| Impulse line details | Verify slope, length, and connection details |
| Manifold details | Confirm valve type, configuration, and orientation |
| Mounting arrangement | Verify bracket and support details |
| Thermowell details | Confirm insertion length, material, and connection type |
| Material Take-Off (MTO) | Verify all required bulk materials are listed |
3.5 Quality Documents
| Document Type | What to Check |
|---|---|
| Quality Assurance Plan (QAP) | Verify inspection and test plan (ITP) aligns with project requirements |
| Material Certificates (EN 10204 3.1) | Confirm material traceability and compliance with specifications |
| Calibration Certificates | Verify traceability to national standards and accuracy |
| Ex Certificates | Confirm validity and coverage of the specific model |
| SIL Certificates | Verify SIL rating and any limitations on use |
3.6 Calculations and Sizing
| Document Type | What to Check |
|---|---|
| Thermowell Wake Frequency Calculation | Per ASME PTC 19.3 TW—confirm frequency ratio < 0.8 |
| Control Valve Sizing | Verify Cv, noise, and cavitation calculations |
| Flow Element Sizing | Verify orifice plate, flow nozzle, or Venturi calculations |
| Pressure Drop Calculations | Confirm pressure drop is within acceptable limits |
4. Common Vendor Document Review Issues
4.1 Incomplete or Missing Fields
Vendors often submit datasheets with blank fields. This is one of the most common and frustrating issues in VDR.
What to do: Return the document with a clear comment specifying which fields must be completed. Do not approve incomplete datasheets.
4.2 Deviations from Specifications
Vendors may propose alternative materials, connection types, or performance characteristics that deviate from the project specification.
What to do:
Evaluate whether the deviation is acceptable
If acceptable, document the deviation and obtain client approval if required
If not acceptable, require the vendor to comply with the specification
4.3 Inconsistent Information Across Documents
Different documents from the same vendor may contain conflicting information—for example, the datasheet may specify one material while the dimensional drawing specifies another.
What to do: Cross-check all documents from the same vendor. Flag inconsistencies and request clarification.
4.4 Poor Quality Drawings
Drawings may be illegible, missing dimensions, or incorrectly scaled.
What to do: Reject the document and require a readable, properly formatted version.
4.5 Late Submissions
Vendors may submit documents after the contractual deadline, compressing the review schedule.
What to do:
Track submission dates against the VDR
Escalate late submissions to procurement and project management
Require the vendor to compress their resubmission cycle to recover schedule
4.6 Failure to Address Previous Comments
Vendors sometimes resubmit documents without addressing all previous comments.
What to do: Compare the resubmission against the previous comment list. If comments are not addressed, return the document with a clear note.
5. Best Practices for Effective Vendor Document Review
5.1 Start with Clear Requirements
The VDR must be defined before the purchase order is issued. Include a detailed list of required documents, submission deadlines, and review cycle expectations in the Material Requisition-.
Key actions:
Define the VDR in the purchase order
Agree the final VDR with the vendor in writing at project kick-off-
Include document submission as a payment milestone
5.2 Use a Structured Review Process
| Practice | Why It Matters |
|---|---|
| Assign clear ownership | Each document should have a designated reviewer |
| Use standardised comment formats | Consistent comments reduce confusion |
| Track comments | Use a comment log to track each issue through resolution |
| Set review deadlines | Contractual review periods keep the process moving |
| Perform IDC | Ensure cross-discipline consistency- |
5.3 Review with the End in Mind
Every document review should answer three questions:
Does this document meet the specification?
Does this document interface correctly with other systems?
Can this document be used for construction, commissioning, and maintenance?
5.4 Be Specific in Comments
Poor comment: "Incorrect."
Good comment: "The process connection specified is 1/2" NPT. The piping specification requires 3/4" NPT. Please revise and update the dimensional drawing accordingly."
5.5 Prioritise Critical Documents
Not all documents have the same level of importance. Prioritise reviews based on:
| Priority | Document Types |
|---|---|
| High | Datasheets, dimensional drawings, wiring diagrams, thermowell calculations |
| Medium | Quality documents, material certificates, hook-up drawings |
| Low | Operation and maintenance manuals, as-built drawings (can be reviewed later) |
5.6 Maintain a Comment Log
Track every comment and its resolution:
| Comment ID | Document | Comment | Vendor Response | Status |
|---|---|---|---|---|
| 001 | Datasheet | Process connection incorrect | Revised to 3/4" NPT | Closed |
| 002 | Wiring Diagram | Terminal 3 labelling incorrect | Corrected | Closed |
| 003 | Dimensional Drawing | Weight not specified | Added | Open |
5.7 Use the "Approve with Comments" Status Effectively
Not every issue requires a full resubmission. Use status codes appropriately:
| Status | When to Use |
|---|---|
| Approved (A) | Document is complete and correct |
| Approved with Comments (B) | Minor corrections needed; vendor to correct and submit for record |
| Revise and Resubmit (C) | Significant changes needed; full re-review required |
| Reject (D) | Document is fundamentally non-compliant |
6. The Role of the Instrument Engineer in VDR
The instrument engineer's role in VDR includes:
| Responsibility | Description |
|---|---|
| Technical review | Verify that the vendor's offering meets all technical requirements |
| Comment consolidation | Consolidate comments from all disciplines into a single response |
| Interface coordination | Ensure the equipment interfaces correctly with piping, electrical, and civil systems |
| Compliance verification | Confirm Ex certification, SIL rating, and material compliance |
| Schedule management | Track submission and review dates against the project schedule |
| Document control | Ensure all approved documents are properly filed and available for construction |
7. Common Mistakes to Avoid
| Mistake | Consequence | Prevention |
|---|---|---|
| Starting the review too late | Compressed schedule, rushed reviews | Begin review immediately upon document receipt |
| Vague comments | Vendor confusion, repeated resubmissions | Be specific; reference clauses and standards |
| Not performing IDC | Interface issues discovered during construction | Perform IDC before issuing comments- |
| Approving incomplete documents | Field changes, rework | Only approve documents that are complete |
| No comment tracking | Comments lost or not addressed | Maintain a comment log |
| Ignoring vendor deviations | Non-compliant equipment delivered | Evaluate and document all deviations |
| No schedule tracking | Delays go unnoticed | Track VDR against the project schedule |
| Reviewing without the end in mind | Documents approved but not usable for construction | Consider constructability, operability, and maintainability |
8. Why This Matters for EPC Contractors
For EPC contractors, effective vendor document review is not just a technical activity—it is a project risk management tool:
| Factor | Impact |
|---|---|
| Schedule | Delays in document approval delay manufacturing and construction |
| Cost | Late changes discovered during construction are expensive |
| Quality | Poorly reviewed documents lead to non-compliant equipment |
| Safety | Incorrect Ex certification or SIL rating compromises plant safety |
| Turnover | Incomplete documentation creates punch list items and delays final acceptance |
9. Conclusion
Reviewing instrument vendor documents is one of the most important—and most frequently underestimated—activities in EPC project execution. A well-managed VDR process ensures that equipment is designed, manufactured, and delivered in compliance with project requirements, reducing field changes, schedule delays, and cost overruns.
Key takeaways:
| Phase | Key Action |
|---|---|
| Pre-order | Define the VDR in the purchase order; agree with vendor at kick-off- |
| During review | Use a structured process; assign clear ownership; be specific in comments |
| Post-review | Track comments; ensure all issues are resolved; file approved documents |
| Throughout | Maintain the VDR as a living document; track status and schedule |
Remember: Vendor documentation is not administrative overhead—it is the evidence that materials comply with project specifications-. The time spent on thorough vendor document review is an investment in project success.
Contact Us
For instrumentation engineering support, technical documentation, or project quotations, please contact:
Yin Shuangjie
International Sales Manager
📧 Email: [email protected]
📱 WhatsApp / Zalo: +86 17856068126
🌐 Website: http://www.tiankang-global.com/
Anhui Tiankang – Supporting EPC projects with reliable instrumentation solutions.
