Your Vendor Didn't Read the Spec: A 15-Minute Datasheet Check Before You Submit

The datasheet your vendor sent describes the product they quoted, and they quoted from a line on your request, not from the spec. So before it goes in the package, put the spec section's Part 2 next to it and answer every requirement for that product one way: meets, with the page; doesn't meet; depends on the option ordered; or not stated. The last two are where the kickbacks hide. It takes about fifteen minutes a product, and it's the fifteen minutes the engineer is going to spend anyway.

The package comes back Revise and Resubmit. Two comments, both on the flowmeters. "Accuracy does not meet 2.02.B." "Provide NSF/ANSI 61 certification for the liner." You open the datasheet. Standard accuracy is ±0.5% of rate, and the spec wants ±0.25%. There's a high-accuracy calibration on page 4, but the order code on the quote doesn't include it. NSF 61 isn't mentioned anywhere in the twelve pages.

The rep sent exactly what you asked for: a 6-inch mag meter, remote transmitter, 4-20 mA. That was the line you sent. Section 40 71 13 asked for more, and nobody held the two side by side until the engineer did.

Why the vendor's datasheet misses

It's rarely carelessness. It's how quoting works.

• They quoted your line, not the section. Your RFQ said "6 in. mag meter, remote mount." The rep priced the standard build that fits that line. Part 2 was never in the email, or it was one attachment among forty and nobody opened it.
• The datasheet covers the whole family. One sheet shows every size, liner, electrode and output the product line offers. The thing you're actually supplying is one path through the ordering table, and nothing on the cover tells the reviewer which path you took.
• Standard options are the cheapest ones. IP67 instead of IP68. Standard accuracy instead of the calibrated option. A liner that's fine for wastewater and has no potable water certification. The quote wins on price because it left those out.
• The spec changed after they quoted. If they did see the section, it may have been the bid set. Addendum 2 tightened the accuracy, and the rep never got Addendum 2.

None of that is the vendor's problem once the package goes out. It has your name on the transmittal.

The 15-minute check

Do this for each product type in the package. Repeated tags of the same part only need it once.

1. Pull the requirements about this product out of Part 2. One line each, in the spec's words, with the article number: "2.02.B Accuracy ±0.25% of rate." "2.03.A Liner certified to NSF/ANSI 61." Skip the installer instructions and the warranty language. You want the ratings and features a product passes or fails on. If you haven't read the section yet, how to read a spec section for submittals covers where these hide.
2. Put the order code next to the datasheet. Use the catalog number on the quote, not the family name on the cover. If the sheet has an ordering table, decode the code position by position so you know exactly which options you're getting.
3. Answer every line one of four ways. Write the page number beside each answer.
4. Write down what you checked against. The section number and the last addendum that touched it: "Checked against 40 71 13, through Addendum 2." When someone asks later why the package says what it says, that line is the answer.

Fifteen minutes is for a normal instrument with a two-page spec article. A drive or a PLC with three pages of Part 2 takes longer, and those are exactly the ones worth it.

What to do with each answer

Meets. Highlight the value on the page you wrote down. The reviewer is going to look for it, so make it one glance instead of a search. Catalog number highlighting covers how to mark it so they trust it.

Doesn't meet. You found it first, which is the whole point. Either swap the product or option before the package leaves, or call it out as a deviation on the transmittal with the article, what the spec asks, what you're providing and why. A deviation you list gets a decision. One the engineer finds gets a stamp.

Depends on the option ordered. The datasheet offers what the spec wants, but nothing proves you ordered it. This is the flowmeter accuracy above. Get the rep to correct the order code in writing, update your catalog number, and highlight the option on the ordering table so the reviewer can see it's part of what's being supplied.

Not stated. The datasheet is silent. Silence isn't compliance, and the reviewer won't treat it as compliance either. Ask the rep for the certificate, a test report, a more specific datasheet, or a signed letter stating the product meets that paragraph, and put it in the package behind the datasheet. If they can't give you one, you probably have a "doesn't meet" you haven't found yet.

Flag every "or equal" up front

If the section names a manufacturer "or equal" and you're supplying a different one, the datasheet can meet every number and still bounce. Whether it's equal is the engineer's call, and they'll make it faster with the comparison in front of them. Say on the transmittal which named product yours replaces, and line up the requirements that matter side by side. If the section names manufacturers and allows no equal, an unnamed one is usually a substitution with its own process and timing: see substitution requests and the or-equal clause.

Stop it at the quote next time

The cheapest place to catch a miss is before the purchase order. When you send an RFQ, attach the section, or at least the Part 2 articles for that product, and the latest addendum. Ask the rep to quote to the spec and list every exception. A quote with "no exceptions taken to 40 71 13" in writing is a quote you can hold them to when the datasheet shows up short.

You'll still run the check. You'll just find fewer surprises in it.

How Submittal Kit handles this

Fifteen minutes a product adds up on a package with forty of them, and it's the kind of reading that gets skipped when the submittal is due Friday. In Submittal Kit, tie a submittal to its spec section and the Spec Check on the Checks tab reads every datasheet on it against that section, one row per requirement for each part. Each row comes back Meets with the value, the line it was found on and the page, Does not meet, Look at this when it depends on the configuration ordered or the product is an "or equal" that only the engineer can rule on, or Not stated. Not stated is counted on its own and never counted as Meets. The panel opens on Does not meet, so the rows that need you come first.

Mark any row yourself with a note, such as the compliance letter the rep sent, and your mark survives re-runs and revisions of the same part. Add a Spec Check Results section in Configure sections and the compiled package prints the results with your marks in place. Load an addendum on the Specifications page and, when it changes the section's text, the last check is marked out of date so you know to re-run it against the current wording. See Upload specifications. Calling the rep is still yours.

Disclosure: I build Submittal Kit, and every step above works with the spec section, the datasheet and a highlighter.