The MDR is created by the buyer’s engineering team and included in the MRQ/RFQ package. It specifies every document the vendor must provide, including the required format, number of copies, and submission deadline.
MDR Field
Description
Example
Document code
Standardized classification
A (for approval), B (for information), C (as-built)
The VDR is the tracking tool that records the status of every document listed in the MDR. Both buyer and vendor maintain the VDR throughout the order lifecycle.
VDR Field
Content
PO number
Purchase order reference
Document title
Per MDR
Revision
Current document revision
Vendor submission date
Date vendor submitted the document
Buyer review status
Under review / Approved / Approved with comments / Rejected
Buyer response date
Date buyer returned comments
Resubmission date
If rejected, date of revised submission
Final status
Approved / Outstanding
Document Submission Process
Step
Activity
Timeline
1
Vendor submits documents per MDR schedule
Per PO milestones
2
Document control logs receipt and distributes for review
1-2 days
3
Engineering reviews against specification
10-14 working days
4
Comments returned to vendor (or approval issued)
Same day as review completion
5
Vendor resubmits revised documents (if required)
5-10 days
6
Final approval issued
5-7 days
Vendor documentation is not administrative overhead—it is the evidence that materials comply with project specifications. Incomplete or non-compliant documentation delays inspection release, shipment, and ultimately construction. For hydrostatic test documentation and shipping document requirements, see the detailed guides.
Leave a Comment
Have a question or feedback? Send us a message.