How to Track Vendor Documents and Drawings After a Purchase Order

After a purchase order is issued, the vendor owes you drawings, datasheets and certificates by agreed dates. How to list them, track every revision, count what is late and chase vendors without a master spreadsheet.

An engineer at a desk checking printed equipment drawings with a caliper and a pen, one sheet stamped For Overview.

To track vendor documents after a purchase order, turn each document the vendor owes you into its own record, with the date the vendor committed to, every revision they send and your decision on each one. Then review the late and due items every morning and chase the vendor on each one, not once per purchase order.

This guide is for buyers, expediters and document controllers at contractors and EPC companies, where one project can mean dozens of long-lead purchase orders and thousands of vendor drawings. It covers what to record, how to count what is late, how to handle revisions and where spreadsheets stop working.

The List of What the Vendor Owes You

When a purchase order is issued for engineered equipment, such as a heat exchanger, a pump package or a switchboard, the vendor owes more than the equipment. They owe the documents your engineers and your client need to approve it: general arrangement drawings, datasheets, calculations, inspection and test plans, procedures, certificates and, at the end, the manuals and the final data book.

These are listed in a document the vendor sends soon after accepting the order, with a date for each line. Companies call it different names:

  • VDRL: Vendor Document Requirement List, the name used on many oil and gas projects
  • SDRL: Supplier Document Requirement List
  • VDDR or SDDR: Vendor (or Supplier) Drawing and Data Requirements
  • Vendor document register or vendor document schedule

They all hold the same thing: the document number, title, discipline, the review it needs and the date the vendor commits to.

What to Record for Each Document

Each line of the list becomes one document you track until it is approved. For each one, record:

  • The purchase order, the vendor and the project
  • The document number and title, as the vendor gave them
  • The discipline, such as mechanical, electrical or quality
  • The date the vendor committed to
  • A forecast date, if the vendor has said they will miss it
  • Every revision received: the date, the file, the vendor's remarks
  • Your decision on each revision, with the comments and the marked-up copy
  • Who has to act next: the vendor, or your team

Keep every revision on the same record. A file name in an email thread is not a revision history.

The Statuses That Matter

A small, fixed set of statuses is enough, and they should follow from the revisions rather than be typed in by hand:

  • Awaiting submission: nothing has come in yet
  • Due soon: the committed date is within the next few days
  • Late: the committed date has passed and nothing acceptable has come in
  • Under review: a revision is with your team or your client
  • Resubmission required: the last revision was rejected with comments
  • Approved: the current revision is accepted

How to Count What Is Late

Count lateness from the date the vendor committed to, not from a forecast. A vendor who writes to say a drawing will be two weeks late has given you a useful planning date, but the drawing is still late, and the record should say so.

Count your own review time separately. If a drawing sits with your engineers or your client for three weeks, that is not the vendor's delay, and a fair tracker shows it as waiting with you.

The figure to watch for each purchase order is how many of its documents are approved against how many were due by today under its own list. The order with the biggest gap and the nearest delivery date is the one at risk.

A Daily Chasing Routine

  • Ask for the vendor's list within a set number of days of the purchase order, and flag the order once that date passes.
  • Remind the vendor a few days before each committed date, and every day once a document is late.
  • Send one email per vendor listing all their open items, not one per document.
  • Give your own team one morning summary: late, to be resubmitted, due today, due this week and waiting for review.
  • Escalate when a late document holds up something else, such as fabrication, inspection or shipment.

Revisions and Rejections

A document usually goes through more than one revision. Revision 0 comes in, your engineers or your client review it, and it comes back approved, or rejected with comments and a marked-up copy. The vendor then sends revision 1.

Two rules keep the history clean. The next revision cannot be added until the one before it has a decision. And a decided revision should not be edited afterwards, so the record shows what was sent, when and what was decided.

Where Spreadsheets Stop Working

A master spreadsheet works for a handful of orders. It stops working when:

  • Each vendor sends their list in their own layout, and someone copies it by hand
  • Revisions arrive by email, and the spreadsheet is only as current as whoever updated it last
  • Nobody can say which documents are late this week without an afternoon of checking
  • A rejected drawing is never sent back, and nobody notices until the delivery date moves

Which Software Tracks Vendor Documents

Three kinds of software come up, and they do different jobs.

  • The client's document system. On many projects the owner sets the system, such as Aconex, Asite or their own EDMS, and your approved documents must go into it. It holds the documents once they reach the client. It doesn't chase your vendors for their drawings before they reach you.
  • General document management systems. These store files, control versions and route approvals. Most don't know what each vendor owes you or by when, so the tracking stays in a spreadsheet.
  • Vendor document tracking. This starts from the vendor's list: one record per document owed, with its date, its revisions and who has to act. Some tools add a vendor portal, so vendors upload their own revisions.

Questions to ask before choosing:

  • Can a vendor's list come in from their own Excel file, in their own layout?
  • Is lateness counted from the vendor's committed date?
  • Are vendors reminded automatically, and does your team get one daily summary?
  • Is every revision kept, and locked once decided?
  • Does it work alongside your client's document system, instead of replacing it?

How Fieldmaster Approaches It

Fieldmaster builds vendor document tracking around your own procedure. The buyer uploads the purchase order copy and AI fills in the order number, vendor, scope and delivery date for the buyer to check. The vendor's list is read from their own Excel file into a table, and each line becomes a tracked document with its committed date.

Vendors sign in to their own portal with a one-time code, see only their own orders and upload each revision. Revisions are numbered automatically and locked once decided. Vendors are reminded three days before a committed date and every day once it is late, and your team gets one summary. A dashboard shows planned against actual for the project, and the purchase orders at risk, nearest delivery first. Before a vendor resubmits, AI checks the new revision against the rejection comments and flags any left open.

See the details on our VDRL tracking page, the purchasing side on purchase management, or talk to us about your vendor documents.

Frequently Asked Questions

What is a VDRL in procurement?

A VDRL, or Vendor Document Requirement List, is the list of drawings and documents a vendor must submit under a purchase order, with a date for each. It is common on oil and gas, petrochemical and power projects, where engineered equipment needs drawings and data approved before it is made.

Who tracks vendor documents on a project?

Usually a document controller or an expediter in the procurement team, with the buyer who placed the order. The engineers review the documents; the procurement side makes sure they arrive on time.

What is the difference between a VDRL and an MDR?

The VDRL lists what one vendor owes under one purchase order. The master document register (MDR) lists every document on the project, from every source, including your own engineering.