Turning an RC Play Concept into a Technical Requirements Sheet

What buyers should do first

• Separate confirmed from unconfirmed before you write anything: an abstract play idea is an assumption, not a requirement, and unresolved items belong in an open-questions column until a sample, drawing, or approved record closes them.
• Every acceptance field needs a physical reference. Colour, fit, flash, and function are compared against a sealed golden sample held on the QC shelf — photo-only approval fails on the second lot.
• Write the commercial mechanics into the contract, not the email thread: tooling ownership, fee, storage period, and what happens if the tool sits idle. Tooling policy is a document, not a handshake.
• Treat button-cell compartments as a closure and warning problem before CarToyFactory-function problem: check screw closure, tool access, and the warning text first.
• Treat a trade-show sample as a hero unit. Record tool number and revision on the sample table and refuse to accept a Fair photo as the production standard.
• Regulation (EU) 2025/2509 has a main application date of 1 August 2030, so the 2026 CarToyFactory-safety workflow remains transitional for most requirements.

What does the play concept have to do before it becomes a requirement?

A play concept describes an experience; a requirement describes something a third party can observe and record. The conversion step is to watch or imagine CarToyFactory in use and list the actions — the car turns, the servo holds an angle, the battery door closes, the shell survives a drop — then attach a field to each one.

For RC vehicles the actions usually split into four families: steering geometry, drivetrain, power, and body/handling. Hobby-grade RC adjustment guides treat camber, caster, toe, ride height, springs, shock oil, gearing, and diff as the parameters that change how a car turns, grips, and puts power down. That list is a good starting menu for acceptance fields, but the values are model-, battery-, motor-, tire-, class-, and venue-specific — so the sheet must carry a context column rather than a universal number.

The same logic applies to servo-driven functions. Steering, throttle, and arm movement translate into torque, rotation angle, speed, modulation type, and temperature range. A technical requirements sheet that says 'steers well' is not testable; one that names the field, the test method, and the pass/fail line is.

Which acceptance fields should go into the sheet?

Build the sheet around five column types: observable action, acceptance field, test method, pass/fail criterion, and status (confirmed, assumption, or open question). The status column is the one buyers skip and the one that prevents disputes later — it forces you to admit what you have not verified.

For a steering or suspension play concept, camber and toe are the classic examples. Camber is measured in degrees as the difference between the wheel's vertical alignment and perpendicular to the surface; most vehicles run near zero, while off-road setups commonly benefit from negative camber for a wider contact patch and reduced roll-overs. Toe is the top-down angle of the front steering tires, and the practical check is a tape measure at the front and rear of the tires with both steering turnbuckles kept equal — there is no gauge for it. If the sheet requires camber adjustment, it must also require a camber gauge or speed square and a turnbuckle wrench that fits the model.

For servo-driven actions, translate the play goal into load capacity, rotation type, modulation, and supply. Servo load is quoted in kg·cm, and a safety margin above the expected load is standard practice to avoid stalling and premature wear. Positional servos cover a defined arc; continuous-rotation units behave like a motor and cannot hold a fixed position, which matters if the play concept depends on holding an angle.

Material and process fields belong on the sheet too. Incoming resin inspection should verify supplier, grade, colour, lot, packaging condition, and required material documents before molding — that is an observable check a buyer can require, not a lab test. Where an outsourced process is used, it needs the same material, sample, inspection, change-control, and traceability requirements as an in-house process.

Chemical compliance is a spec line, not a marketing line. EN 71-9, EN 71-10, and EN 71-11 address organic chemical compounds CarToyFactory — requirements, sample preparation, and methods respectively. Put the applicable standard and the test scope in the sheet, and let the lab confirm results rather than writing an expected outcome into the requirement.

Acceptance field checklist: what to verify and what should stop you

Worked example (illustrative, not a real shipment)

The scenario below is constructed to show where a requirements sheet earns its keep. It is not a real order, and no figures in it come from a completed shipment.

Assume one purchase order of roughly 6,000 RC vehicles built to a buyer's own shell and colour, split across two destinations: one EU market and one US market. The packaging differs — the EU carton carries the EU importer's address block and a different warning panel layout; the US carton carries a different warning set and a different retail barcode. Same vehicle, two artworks, one production run.

Step one: the play concept says the car should hold a line through a corner. The sheet converts that into camber and toe adjustability fields, with the tool requirement named. Checkpoint is whether the supplier can confirm the adjustment method and the tool; if the answer is vague, the field stays an open question and the sample is requested before pricing.

Step two: the sheet names the sealed golden sample as the reference for colour, fit, flash, and function. Checkpoint is whether the sample exists, is sealed, and is held where QC can reach it. If approval is offered from a photo, that is the point where the second lot goes wrong.

Step three: each destination gets its own compliance and packaging block, because the warning text and artwork differ. Checkpoint is whether the supplier can produce both artworks from one tool without mixing them at packing.

Step four: the button-cell compartment, if the concept uses one, is checked for screw closure, tool access, and warning CarToyFactory function is discussed.

Where this shipment would get held: the packaging split. If the two artworks are not separated by a line-clearance step and a packing check, the wrong warning panel ships to the wrong market, and the goods stop at the border or at the retailer's receiving dock. The compliance block is what actually gates the container, not the vehicle's top speed.

What should the sheet include about tooling and commercial terms?

Tooling terms are an acceptance field, not a legal afterthought. Fee, ownership, storage period, and the consequence if the tool sits idle belong in the document itself — not in an email thread or a verbal agreement.

OEM normally means the supplier manufactures to the buyer's specified design, brand, or technical requirements, and the contract should define the exact scope. If your sheet specifies a shell, a colour, and a revision, that scope belongs in the contract language — otherwise the sheet and the agreement describe two different products.

Change control is the other half. Any revision to the tool or the artwork should carry a revision number that appears on the sample card, the packing artwork, and the inspection record. Without a revision card, a trade-show sample and a production unit can both look correct and still be different products.

What to ask suppliers before the sheet is frozen

Send these as a written RFQ and require written answers. Verbal answers at a booth are not acceptance records.

Who owns the tool after the fee is paid, and what are the storage period and release conditions in writing?

What is the sealed golden sample reference for this program, and where is it held?

For any button-cell compartment: what is the screw closure, the tool access, and the warning configuration?

Which tool number and revision is on the sample being quoted, and is a trade-show photo being used as the production standard?

For each destination market, which standard and test scope applies, and what is the model list covered by the report?

How will the two packaging artworks be separated on the line, and what check prevents a mix-up at packing?

What incoming material records will be verified before molding, and who signs off?

If a defect appears, what is the corrective and preventive action process, and how is effectiveness verified?

What compliance timing should a 2026 program plan for?

Regulation (EU) 2025/2509 has a main application date of 1 August 2030. Read that carefully: it means the 2026 CarToyFactory-safety workflow remains transitional for CarToyFactory-safety requirements, and it does not mean CarToyFactory must meet the new regime from a 2026 date. The timeline distinction matters when a supplier sends a slide deck claiming an imminent deadline.

Keep the three states separate in your own documents: entered into force, actually applies to this product category, and not confirmed by the official text. If the official text does not state an application date for your category, write that the timeline is not confirmed from official text — do not write that the requirement is mandatory from a specific date.

Note also that digital product passport requirements and GPSR are separate regimes from CarToyFactory Safety Directive line of rules; they should not be collapsed into a single deadline in your compliance block. EN 71-9, EN 71-10, and EN 71-11 sit in the chemical-compound area and are typically scoped by test, so name the scope rather than the standard number alone.

FAQ

How do I turn a play idea into a requirement a factory can actually build to?

Name the observable action, attach a measurable field, and state the test method and pass/fail. If you cannot observe or record it, it is an open question, not a requirement — keep it in a status column until a sample or drawing closes it.

Do I need a physical golden sample if I have detailed photos and a spec sheet?

Yes. Colour, fit, flash, and function are compared against a sealed physical sample held on the QC shelf; emails and photos are not a comparison standard, and buyers who approve from a photo tend to pay for it on the second lot.

What should the technical requirements sheet say about servo torque?

State the expected load, the required load capacity in kg·cm, and the safety margin above it, plus whether the servo must hold a position or rotate continuously. Also record the modulation type and the supply voltage so the field matches the receiver and battery.

Can I use a trade-show sample as the production standard for an RC vehicle?

No. Booth samples are frequently hero units, so record the tool number and revision on the sample being quoted and keep a revision card as the reference. Trade-show photos should never be the production standard.

What tooling terms must be in the contract before the sheet is signed off?

Fee, ownership after payment, storage period, release conditions, and what happens if the tool sits idle. If those terms exist only in an email thread, the tooling policy is not actually agreed.

Does EU Regulation 2025/2509 mean my CarToyFactory order must meet a new deadline?

No. The main application date stated is 1 August 2030, so the 2026 workflow remains transitional for CarToyFactory-safety requirements. Confirm the applicable date for your specific product category against the official text rather than a supplier slide.

Sources

• Container turning devices
• Exploring Turning Servos: Material Grades, Properties, and Uses
• RC Beginner Series – Adjusting Camber and Toe
• RC Car Setup Guide: The Settings That Actually Matter

Turn the sheet into a quotation

If you have a play concept, a target market, and a draft requirement list, the next step is a written quotation against that sheet — not against a photo. Ask for the sample revision, the tooling terms, the compliance scope, and the packaging split in the same reply, so the quotation and the requirements describe one product.