Two design briefs land on the same sourcing desk on a Monday. Brief A opens with a motor rating, a battery brand, a frame colour and a row of supplier logos; the reviewer reads to the end and still cannot tell whether the thing being quoted is a two-wheeled low-speed electric bicycle, a throttle-only moped, or a scooter with decorative cranks. Brief B opens with six lines: wheel count, pedal operability, motor rating, the speed test condition, the shipped assembly state, and a compatibility block covering device, battery, cells and charger. Brief A comes back with three quotes that cannot be compared and one email asking which vehicle the buyer actually means. Brief B comes back with quotes that line up column to column, plus a note about a charger pairing nobody had thought to raise.
The difference is field order, not field count. In this category the first fields decide whether a build can be reviewed as a complete low-speed electric bicycle at all; styling and component wish lists sit downstream of that decision. What follows is the order a US buyer can run through the first weeks of a custom programme, built on the vehicle definition in 16 CFR 1512 as captured in the 2025 CFR edition and on the system-level electrical framing CPSC set out in its February 2023 letter to standards bodies. Neither document is a certificate for your build, and the annual CFR snapshot may not carry later amendments. Both tell you what the brief has to ask before anyone quotes.
Day One Lock the Vehicle Definition Fields
Day one is classification, and it fits on one page. The brief fixes four things: two or three wheels; fully operable pedals, meaning pedals that can actually drive the bike rather than folding pegs or cosmetic cranks; an electric motor rated under 750 W; and a maximum speed under 20 mph, measured on a paved level surface with a 170 lb operator aboard and with the motor as the only power source. Write the speed line as a test condition rather than a marketing claim — the operator weight, the surface and the motor-only qualifier are part of the number. A brief that writes a bare speed figure without the surface, the operator weight and the motor-only qualifier has thrown all three away and left the reviewer to guess which condition the supplier's number describes.
Two consequences follow from how the thresholds are worded. The wording is "less than" on both the motor rating and the speed, so a motor declared exactly at the ceiling and a speed quoted exactly at the limit are boundary cases to be flagged rather than rounded off; the brief should ask on what basis the rating is declared and how the speed figure was produced. The definition is also vehicle-level. A motor spec sheet says nothing about pedals, wheel count or a tested speed on a named surface, so it cannot classify a build on its own — it is one input to a judgement about the whole machine.
Imagine a brief whose first page reads "sporty geometry, fast, big motor". Three suppliers will quote three different vehicles, and the mismatch surfaces at sample time, after tooling conversations have started and after somebody has paid a deposit on a frame jig. That cost is predictable, which is why the classification block goes first.
Week One Write the Assembly-State Clause
Assembly state is where briefs go quiet and shipments go sideways. The rule to carry into the brief: a covered bicycle must meet the requirements in the condition in which it is offered for sale, and a bicycle offered disassembled or partially assembled must meet them after assembly according to the manufacturer's instructions. For a buyer that becomes a field rather than a line of boilerplate — shipped state (fully assembled, partially assembled, boxed), who performs final assembly, which instruction revision that assembly follows, and which checkpoint confirms the assembled condition.
Suppose a container of boxed bikes arrives with front wheels, bars and pedals loose. Incoming inspection checks what is in the box, because that is what the dock can see. The condition that actually matters — the assembled bike — has no owner in the brief, so nobody signs it off, and "we assemble per instructions" becomes the entire record. Naming the field changes the review: the instruction revision gets cited, the assembly step gets a responsible party, and the post-assembly check has a place to be written down.
Keep the clause at the right altitude. It points to the manufacturer's instructions and to your acceptance process; it is not a licence to invent torque values, cable routing or a test sequence inside the brief. Those belong to the model documentation and to what the RFQ agrees, and they differ by frame and drive layout. The brief's job is to name the checkpoint and the document that governs it, so that a partially assembled shipment cannot pass review before the assembled state has been addressed at all.
Before RFQ Release Build the Compatibility Matrix
Before the RFQ goes out, the electrical block becomes a matrix with one line per build. The framing comes from CPSC's 2023 letter to standards organisations, which describes a system approach in which the device, battery, cells and charger are compatible and function safely together. That sentence is the specification for the table: it names the four things that have to appear in a single row rather than in four attachments.
Charger output profile, cell chemistry, pack protection cutoffs, connector keying, the exact combination being asserted as compatible, the revision date of that assertion and the name of whoever signed it — one row, keyed to the configuration that will actually be quoted, with firmware and controller pairing recorded alongside. A folder of component certificates does not answer that question.
The matrix earns its place by changing what a reviewer can do in ten minutes: compare the four electrical elements side by side, spot a pack that does not match the asserted combination, and see who signed the assertion and when. That is the improvement — not a thicker attachment list, but one place where a mismatch becomes visible before a purchase order exists.
Two boundaries keep the matrix honest. The CPSC letter sets out safety expectations addressed to standards bodies; it is not a product approval and not a statement that any one standard covers every configuration on the market. The specific standards, versions and evidence for your build remain a documentation question for that build and that supplier, checked against whatever is current when you order. Fix the shape of the matrix now, and leave the standard-version column to be filled with documents rather than assumptions.
At First Supplier Review Ask Evidence Questions
At the first supplier review, the brief is only as good as the questions it produces. The set that does the most work: which exact device-battery-cell-charger combination was evaluated; whether the statement covers the configuration as shipped and assembled, or a bench setup on a different pack; which document revision and date the statement comes from; what changes void it — a cell substitution, a different charger model, a controller or firmware change, a new pack supplier; and which model-specific records will travel with the sample rather than arriving three weeks later.
Put those questions in writing and file the answers beside the brief. A verbal "yes, it is compatible" is the most common weak point in this category, because six weeks later, when the cell supplier changes, nobody can reconstruct which combination was blessed or by whom. A written answer that names a combination and a revision survives staff turnover; a friendly email does not.
None of this is a finding about any particular supplier. It is the question set that separates a reviewable file from a pleasant conversation. If the answers do not come, that silence is itself information the sourcing team can price into the schedule instead of discovering it at the sample stage.
Before Sample Approval Freeze the Configuration Record
Before the first sample is approved, freeze the configuration record: exact device, battery pack, cell, charger, pedal setup and shipped assembly state, each tied to the revision that was reviewed. Add a substitution clause so that any change to those fields comes back as a written flag rather than as a quietly different build. Without the freeze, the sample that arrives is not necessarily the configuration the brief described, and the approval covers whatever was in the box that day.
Everything commercial stays open at this point, and that is deliberate. MOQ, unit price, lead time, available tooling, tolerance stack-ups and the certificate package are RFQ items to be answered with documents and a quotation. List them as questions with owners and due dates; do not pre-fill them with plausible-looking numbers to make the page look finished. A frozen technical configuration and an open commercial term sheet coexist perfectly well on the same two pages.
The freeze also gives the sample review something to check against. A tester can compare the pack label, the charger model, the pedal hardware and the shipping configuration to the record line by line, and a mismatch becomes a specific question instead of a general unease about the build.
After Review Keep Only Auditable Brief Fields
After the first review, cut the brief down to fields a reviewer can trace. Classification inputs, assembly state, the compatibility matrix and the freeze record each point to a document, a model condition or a written supplier statement. Decorative claims and unqualified "certified" labels point to nothing checkable, and they cost review time while manufacturing confidence that nobody can audit. A label without a scope line — certified to what, for which configuration, under which revision — is noise in a sourcing file.
Three months later, the test is simple. Hand the brief to someone who sat in none of the meetings and ask whether the shipping configuration still matches what the file says was approved; if the answer needs a phone call to reconstruct, the field you kept was decoration and the field you cut was load-bearing. That is the trade this ordering asks you to accept: the front end slows down, and suppliers who cannot document system-level compatibility will fall away. What comes back is a review that can be reconstructed from the file, and fewer classification surprises arriving after tooling has started. Teams that would rather move fast than be able to audit the decision should say so out loud and price the added review risk into the schedule.
