Write compliance requirements into the pack spec before the RFQ

Write the compliance requirements into the pack specification before the RFQ goes out, and write them as named documents with an owner and a delivery point rather than as adjectives. UL certified is not a requirement; it is a blank that each supplier fills with whatever is already in their file cabinet. Name the standard and its revision, name the configuration the certificate has to describe, name who performs the testing, and name the program milestone where the document is due. Do that and the bids come back comparable. Skip it and the missing test report surfaces two weeks after the purchase order, when the tooling is already cut.

I keep a binder on the shelf behind my desk that exists because I got this wrong once. Four responses to the same RFQ, spread across a conference table, and one narrow column in my comparison spreadsheet labeled Compliance. Bid one: cells are UL certified. Bid two: meets all applicable standards. Bid three attached a certificate issued to a different pack model — same cell, different protection board, different enclosure. Bid four wrote TBD at PPAP and left the tab empty.

Sit down at that table with me. The four quotes land within a few percent of each other on price, which is exactly the range where you stop trusting the number and start reading the fine print. And the fine print in three of the four is nothing at all. The question in the room is no longer who is cheapest. It is which of these four will hand me a report I can put in front of the customer's reliability engineer — and I cannot answer it, because I never told any of them what a report was.

None of that was the suppliers' fault. My specification had asked for compliance the way you ask for good weather.

The shortest phrases cost the most

Certified. Compliant. Meets applicable standards. Tested to UL. Every one of those phrases reads like a requirement and functions like an invitation. The supplier is not being evasive. They are answering the question I actually asked, which was broad enough to be answered with a sentence.

What replaces them is a clause with four parts, and the four parts barely change from document to document: the standard by designation and revision, the configuration the certificate has to describe, who performs the testing and who pays for it, and the milestone where a legible copy is due. Write those four parts for every deliverable on the list. It feels mechanical. Mechanical is what makes two bids comparable.

A cell certificate is not a pack certificate

This is the one that burns people quietly, because the paperwork looks complete.

A cell-level standard — UL 1642, IEC 62133-2 — tells you something about the cell. It tells you almost nothing about the pack. The pack is a different article with different failure modes: the protection board, the fuse, the thermal interface, the enclosure, the charging path. A pack standard such as UL 2054, UL 2271 for light electric vehicles, or UL 1973 for stationary applications covers the assembly as it was tested. Swap the protection board, swap the cell model, change the housing material, and you can be standing outside the tested configuration with a valid certificate in your hand that no longer describes what you are buying.

So the specification has to say what the certificate must describe. Not a certificate for a similar pack. The pack, the cell model inside it, the revision of the standard it was evaluated against, the date on the report. I ask for the certificate submitted as a PDF with the configuration page intact, because I have received the cover page alone more times than I can count.

The line that decides whether quotes are comparable

Who performs the certification testing.

Two suppliers read the same spec, and one builds the test cost into the unit price while the other assumes the buyer arranges it and quotes a number that is quietly missing the test work. Six months later, when the testing lands on your side of the table, the winning bid stops being the winning bid.

The specification does not need to be clever here. It needs one sentence per test. Performed by supplier, witnessed by a third party, at supplier's cost, report delivered with the pre-production sample. Or the exact opposite — buyer arranges, supplier provides samples and documentation support. Either answer works. Silence does not.

Cells: acceptable standards and a paper trail

If the specification does not name the cell standards you will accept, you get whatever the supplier's distributor had in stock that month, and you find out when you sit down to assemble the technical file.

I list the acceptable cell standards and their revisions, then add the part that generic templates leave out: traceability. Cell manufacturer and model on the shipping documents. Lot code or date code recorded and retained. A commitment that the cell inside the production pack is the cell named in the qualification file, with any substitution notified in writing before it ships rather than after. That last item is not a formality. It is the difference between a qualification file that holds together for the life of the program and one that quietly stops describing your product somewhere around month eight.

Say what the pack is for, and where it sells

A capacity figure and a voltage do not tell a supplier what to certify.

The pack in a floor-care robot sold to consumers in the United States, and the pack in an industrial floor scrubber sold to a very different customer, walk into different standards. If the specification says only 48 V, 10 Ah, the supplier guesses, and their guess becomes my problem. So the end product, the market, and the use environment go on the first page, above the electrical requirements. Consumer use, indoor charging, vibration, whatever the reality is. The supplier's engineering team reads that page and proposes a standard. I review a proposal instead of inventing an answer.

Marking and labeling belong in the specification

Model designation format. Language. Label location. Whether it is printed, laser-marked, or applied as a durable film. What the label has to say, and in what order.

Two people read that label against your documentation: the customs reviewer holding the invoice in one hand, and the end customer holding the user manual in the other. If the model designation on the pack does not line up with the model designation on the paperwork in a way a stranger can follow, you have bought yourself a delay measured in weeks and a search for someone to blame.

I put the required label content and an artwork approval step into the specification with a delivery point attached: draft artwork at the pre-production sample stage, approved before the first mass-production lot. Suppliers accept this without argument. It is four lines of text, and it saves a shipment.

Name the delivery points

Every deliverable gets a milestone. I use three:

1. With the quote — certificates and reports the supplier already holds today, so I can see what actually exists.
2. With the pre-production sample — new test reports, the full certificate including the configuration page, the artwork proof.
3. With the first mass-production lot — lot traceability records, a re-issued certificate if anything in the configuration changed, the final label revision.

Splitting it this way does something useful to bid evaluation. A supplier with nothing at the quote stage is telling you they will start from zero, and that risk belongs in your scoring rather than in a surprise later.

Scale the requirements to the build

Tight compliance language narrows the bidder pool. That part is real, and pretending otherwise does not help anyone. A capable small supplier with a certificate covering a slightly different configuration may decline rather than re-test, and for a two-hundred-unit engineering build the re-test may not be worth anybody's money.

So I scale it, and I scale it on purpose. High-volume, long-life, consumer-facing end product: full requirements, no exceptions, and I would rather lose a bidder than a launch date. A short engineering build where the pack gets redesigned in a year: I will accept an existing certificate if the configuration genuinely matches, and I write that acceptance into the specification so the decision is documented instead of remembered by whoever is still at the company.

What I do not do is leave the wording vague and hope the gap does not matter. A vague spec does not buy flexibility. It buys a phone call in month eight.

Read it backward before you send it

The last thing I do is hand the compliance section to someone who was not in any of the meetings and ask one question: could two different suppliers read this and return two different documents?

If the answer is yes, the spec is not finished. I would rather find that out at my own desk, with the document open in front of me, than at a conference table with four quotes and an empty column.