Glossary term
Supplier Document Requirements List (SDRL)
The customer's list of every document a supplier must submit for an order, each with a code, a due date and a review requirement, and the list a package builder issues in turn to each sub-vendor.
Last reviewed by the OdysseyGPT team
What it is
A supplier document requirements list (SDRL) is the schedule of documents a supplier must submit for an order. Each line has a code, a due date and a review requirement. It does the same job as a vendor data requirements list. A package builder also issues its own list to each sub-vendor, with earlier dates.
Key Takeaways
- SDRL and VDRL are two names for the same kind of list.
- A package builder works with two lists: the customer's, and one for each sub-vendor.
- Sub-vendor dates need a margin for checking, renumbering and submission.
- Requirements in the order text that the list omits still apply.
Why it matters
A supplier document requirements list, or SDRL, is the schedule of documentation attached to a purchase order. Each line names a kind of document, gives it a code, says when it is due and says whether the customer wants it for information or for review and acceptance. It serves the same purpose as a vendor data requirements list (VDRL). Which name a project uses depends on the customer. SDRL is the usual name on projects that follow Norwegian practice, where NORSOK Z-018 is the standard for supplier's documentation of equipment. The IOGP JIP33 procurement specifications carry a similar schedule in a document called the information requirements specification. This page is about what the list means for a supplier who buys in most of its content. For a package builder there are two lists. The first is the customer's list to the builder. Its lines are written by type: one line for instrument datasheets, one for material certificates, one for certificates of equipment in hazardous areas. The second is the list the builder writes for each sub-vendor. It has to turn each customer line into the actual documents that supplier will produce, in the format the customer wants, with a date early enough for the builder to check the document, renumber it and submit it on time. Most late submissions on a package trace back to that second list. Either it was never issued, or it copied the customer's dates with no margin, or it left out a line because nobody matched the customer's codes to the sub-vendor's scope. Three checks are worth making at bid stage. Read every line and mark the ones a sub-vendor will have to supply. Look for requirements in the purchase order text that the list does not carry, because the order usually takes precedence. And note the lines due before manufacture may start, since those are holds on the programme. An agreed exception to the list belongs in the deviation list, not in an email.
How OdysseyGPT uses it
OdysseyGPT is not a document control system. It does not number, transmit or store controlled documents. VDRL/MDR Tracker (beta) reads the SDRL spreadsheet with the order's documentation clauses and your schedule, and reports overdue lines, lines with no clear due date and documents the order requires that the list leaves out. MRB Readiness Check (beta) later checks the documentation folder against the customer's index. Each finding quotes its source. Your document controller still prepares and sends every submission.
Evaluation questions
How do you pass an SDRL down to sub-vendors?
Mark each customer line that a sub-vendor must fill. Write a list for that sub-vendor naming the actual documents, the format and the date, and attach it to the purchase order. Set the date ahead of the customer's.
What if the SDRL and the purchase order text disagree?
Check the order of precedence in the contract and raise a clarification. Do not assume the list is complete. A document required by a clause is still required if the list has no line for it.
Does OdysseyGPT manage the SDRL?
No. It checks the list you have against the order's documentation clauses and your schedule, and reports gaps and late lines. Numbering, transmittals and the customer's portal stay with your document control system.
Frequently asked questions
What is an SDRL?
A supplier document requirements list. It is the customer's schedule of the documents a supplier must submit for an order, with a code, a due date and a review requirement for each.
What is the difference between an SDRL and a VDRL?
Mostly the name. Both list the documents a supplier owes. SDRL is common on projects that follow Norwegian practice. VDRL and similar names are used elsewhere. Always work to the list and the codes your contract gives.
Who writes the SDRL?
The customer writes the list for its supplier. A package builder then writes its own list for each sub-vendor, based on the customer's lines that apply to that sub-vendor's scope.
Is the SDRL part of the contract?
Usually yes, as an attachment to the purchase order or requisition. A document you cannot supply, or cannot supply by the date given, should be declared as a deviation before award.
References
NORSOK Z-018: Supplier's documentation of equipment
Standards Norway, listed by GlobalSpec
Public listing of the standard's title and subject. Paid standard.
JIP33 frequently asked questions
IOGP
The information requirements specification and how purchasers mark each deliverable.
NORSOK standards
Standards Norway
