Custom Life Jacket RFQ Controls for a Legacy 160.064 Approval

Suppose a sourcing team signs off on a custom colorway and a lighter shell fabric for a life jacket the factory already builds, places the MOQ, and waits out the lead time. The cartons arrive, the goods look right, and then someone reads the label against the paperwork and finds the two no longer describe the same product. The loss is not a sample. It is the whole run, plus every week that went into production instead of into review, plus the standing question of what the label can now legitimately say.

That is the failure a custom life jacket RFQ exists to prevent, which is why the document's first job is not to describe the customization well. It is to push every design, material or construction change in front of a recognized laboratory before a purchase order exists. A jacket built on a legacy 46 CFR 160.064 approval is a specific object backed by a specific approved configuration, and procurement's job is to keep those two from drifting apart between the inquiry and the shipment.

The Cost of a Change Nobody Re-Approved

An approval attaches to a defined design, a defined material set and a defined construction. Swap the shell fabric or a buckle, and the configuration leaving the factory is no longer the configuration that was approved. Which means the damage is not measured in a correction but in a rerun: the run has to be rebuilt to the approved configuration and slotted back into a schedule that has already moved on. Approvals cannot be added at the loading dock, because nothing an inspector does at the carton converts an unapproved jacket into an approved one.

Cost concentrates in three places. Laboratory turnaround lands directly on the delivery date, and it lands late, after tooling and materials are already committed. Rework is counted per run rather than per sample, so exposure scales with the order rather than with the unit. And the approval basis the label rests on stopped holding at the moment the change was made, which turns a commercial disagreement into a compliance one that no discount settles. No dollar figure or day count belongs here, because those depend on the lab queue, the run size and the supplier's rebooking position.

First Confirm the Model Is a Legacy 160.064 Approval

The change-submission procedure sits in 46 CFR 160.064-23, and its reach is bounded: it serves PFDs approved under 160.064 before January 6, 2025. Before anything is quoted, the RFQ asks the supplier to state in writing which subpart the approval sits under, the model identifier, and the approval date. A photograph of a label is not that statement. Because the procedure's scope is limited, an RFQ that never names the subpart will drift onto whichever rule set the supplier habitually works with, and a wrong procedure is harder to catch than a missing one, since it produces confident answers that do not apply to this product.

This section does not settle whether any particular model is approved, and it does not describe a route for a newly designed life jacket. If the subpart and approval date are not on paper, the line stays an open question addressed to the supplier, and pricing waits. That single discipline closes a common way a custom program starts badly: a quotation built on an assumption about approval that nobody wrote down and nobody tested.

Sort Each RFQ Line as Design, Material, or Construction

The same provision separates changes into design, material and construction, which makes it a sorting tool rather than a paragraph to skim. Panel shape, pattern geometry and fit block belong to design. Buoyancy foam, shell fabric, webbing and thread belong to material. Stitching method and assembly sequence belong to construction. The reason to sort at all is that the rule names all three categories in the same breath, so a lighter shell fabric is not a lighter case in the eyes of the provision. A request that straddles two categories is treated as the stricter of the two until the laboratory says otherwise.

Logos and label placement are the awkward line. Nothing in the material at hand answers whether a relocated label counts as a change requiring submission, so it becomes a written question to the recognized laboratory, and nobody on the buying side gets to answer it yes. I will take a position here, once: anything touching buoyancy material, shell fabric or labeling comes out of this version of the RFQ before price talks begin, even when that costs the design some of its appeal. The trade-off is clean, because a customer who will drop the item and keep the approved configuration still has a project that moves.

Who Is Allowed to Call a Substitute Equivalent

Determinations of equivalence of design, construction, and materials must be made only by the Commandant or a designated representative. That is a narrow set of decision-makers, and it does not include the factory, the trading company, the laboratory contact who answers email, or the buyer. When a supplier writes that its foam meets the same specification, the sentence is a claim, and pasting it into a purchase order appendix does not upgrade it into a determination. The gap between the two is where unapproved product ends up on a boat.

The practical move is to put the equivalence question in writing to the recognized laboratory, naming the approved item and the proposed substitute, and to file the reply alongside the model record. Keep it out of phone calls. A verbal answer cannot be attached to a shipment, cannot be compared against a cutting ticket, and cannot be produced when a customer, an auditor or a retailer asks how this configuration came to exist.

Run the RFQ in This Order, Not in Quote Order

Start by requiring the approval subpart, model identifier and approval date on the quotation page itself, and do not move to the next step until they are there; you know it worked when the statement exists on a document you can file, not in a message thread. Next, list the customization requests line by line and label each one as design, material or construction, treating any line that spans two categories as the stricter one.

Then send that list to the laboratory and ask about the path before asking about price. The order cannot be reversed, because a quotation obtained first anchors the negotiation to a configuration that may not survive review, and buyers defend anchors. Only after the answer returns do you request MOQ, tooling cost, lead time and unit price, and you request them for the configuration the answer describes, quoting its wording rather than paraphrasing it. Sampling follows the same rule: the sample is built to the post-answer configuration, never to the version that was priced first.

Each step confirms itself the same way, through a written receipt that can be filed and compared later; a verbal confirmation closes nothing, because it leaves no object to check against the next document in the chain. The sequence costs a supplier conversation or two up front and saves the entire run later. It also keeps the commercial questions where they belong, downstream of the answer instead of standing in for it.

What a Correct Answer Looks Like on Paper

What you want on file is not a sentence saying the change is approved. It is a written answer that lines up in three places at once: the model it names, the change it describes, and the RFQ line it responds to. Confirming it means comparing the change wording in the answer against the wording of the RFQ line word by word, then checking which configuration version the sample will actually be built to.

Answer formats vary by laboratory and by case, so this is the correspondence to look for, not a template to demand. What is not in hand here is any factory-specific record: no approval evidence, quotation or capability statement for a named supplier exists in this file, so those stay written questions rather than assumptions added to make the file look complete.

Fit, Activity, and Condition Still Gate the Order

Lifejackets and buoyancy aids must be the appropriate size for the intended user, appropriate for the intended activity, in good and serviceable condition, and U.S. Coast Guard approved to meet carriage requirements. Those conditions run in parallel rather than in sequence, which means a jacket with an intact approval path can still fail the order by sitting in the wrong size range or being built for the wrong activity. Hand a supplier nothing but a model number, and the quote comes back for whatever approved style sits closest, carrying a certificate while fitting nobody on the boat.

So the RFQ carries the target user size range and the intended activity next to the model, plus the condition expectation for delivered goods. That regulatory page states conditions of use; it certifies no supplier's product and substitutes for no approval document. Use it to write a sharper requirement, not to close one.

One Check Before the PO Goes Out

If only one thing gets confirmed before the purchase order leaves, make it this: the approving laboratory's written answer to this specific change is on file, and the change wording inside it, the RFQ line and the configuration about to be sampled all match. It outranks the rest of the checklist because price, tooling and delivery dates can be renegotiated after signature, while goods already built to an unapproved change cannot be brought back into compliance by any clause added later.

One scope note keeps that check honest. It applies to wearable PFDs approved under 160.064 before January 6, 2025, and this file holds nothing about how a jacket designed from scratch would be approved, so a buyer who needs that answer is asking a different question and should not let a legacy quotation stand in for it.