How to brief a bespoke vehicle electronics supplier
A good brief saves weeks of back and forth. Here is what an engineering team needs from you, what to ask them in return and how the stages usually run.
Ian D., Head of R&D at Scorpion Automotive. Reviewed by James M., Technical Director at Scorpion Automotive.
What should a bespoke electronics brief contain?
Say what the product must do, which vehicles it fits, how many you expect to buy and which quality and approval documents you need. Add the environment, the interfaces and the target dates. The supplier can then price and plan without guessing, and you can compare bids like for like.
Start an OEM or bespoke project
Key facts
- Scorpion designs and builds vehicle electronics in Chorley, with R&D and firmware in-house
- The quality framework is IATF 16949 certification, with design following APQP
- Current OE programmes cover alarms, tracking, CAN bus products and lighting
- Lead times, minimum quantities and tooling terms are not published, so ask us
Ten items that make a brief usable
Not every item needs a final answer on day one. A marked gap is far better than a missing line.
| Item | What to tell the supplier | Why it matters |
|---|---|---|
| Function | What the product does, in one paragraph, and what it must never do | Sets the architecture and the safety boundaries |
| Vehicle platforms | Makes, models, years and whether line-fit or retrofit | Decides the connectors, networks and fitment method |
| Interfaces | CAN or other buses, signals needed, power supply range and outputs | Decides the hardware and the firmware workload |
| Environment | Temperature, vibration, water and dust exposure, fitting location | Drives the enclosure, coating and test plan |
| Volumes | Expected annual quantity, ramp-up and any variants | Drives the build method and the unit cost |
| Quality and documents | Certificates, process documents and sample approval you require | Sets the paperwork to plan from the start |
| Approvals | Any vehicle or component approval the product must carry | Approvals take time and test access |
| Software | Update method, data you need out, security and ownership of code | Avoids rework late in the programme |
| Commercial | Target cost, tooling expectations and the contract length | Allows a reliable feasibility answer |
| Timeline | Prototype date, validation window and start of production | Shows whether the plan is realistic |
Questions to put to the supplier
A bid answers your questions. These tell you how the supplier works.
-
Is design done in-house or subcontracted?
Ask who writes the firmware and designs the board. A single accountable team shortens fault resolution.
-
Where is it built, and what is tested?
Ask for the site, the inspection stages and what end-of-line testing proves on each unit.
-
Which quality system covers the work?
Ask for the certificate and the design framework the team follows, then match both against your own requirements.
-
Who owns the design and the code?
Agree intellectual property, licence terms and escrow in writing before design starts.
-
How is change handled?
Ask how a design change is requested, costed and recorded once production has started.
-
What happens at end of life?
Ask about spares, last-time-buy terms and support for units already on the road.
-
Will an NDA be signed before the brief is shared?
Confirm this early. Sharing a brief under a signed agreement protects both sides.
How a bespoke programme usually runs
The names vary, but the sequence is common to most suppliers.
| Stage | What happens | What you receive |
|---|---|---|
| Feasibility | The supplier reads the brief and tests the idea against the platform | A view on what is possible, and the open questions |
| Design | Hardware and firmware are specified and built | A specification both sides sign off |
| Prototype | Early units are built and fitted to the target vehicle | Samples to test on the real platform |
| Validation | Environmental, electrical and vehicle tests, then approvals | Test evidence and corrections |
| Production | Volume build under the agreed process | Units to the agreed standard, with documents |
Durations depend on the product and the approvals involved, so ask for a plan with dates instead of relying on a general rule.
Scorpion's engineering and manufacturing
Scorpion Automotive has built vehicle electronics in the UK since 1973.
- In-house engineering: PCB-level hardware design and Embedded C firmware, with satellite positioning, GSM, RF and Bluetooth skills.
- In-house manufacture: prototype and volume builds in Chorley, using SMT and THT assembly, automated conformal coating and automatic optical inspection.
- Quality: IATF 16949 certification, with hardware and software developed under an APQP framework.
- Programmes: alarms and immobilisers, tracking and telematics, CAN bus motor controllers and sensors, LED light clusters, and connected vehicle development.
- A sensor example: a programmable microwave intrusion detector, approved by Aston Martin Lagonda and DAF Trucks.
Minimum quantities, lead times and tooling arrangements are not published here, so ask us for them. See bespoke solutions for the programmes and the sensor case study, OEM and bespoke to start a project, and our interface modules manufacturer page for CAN products.
Frequently asked questions
How detailed does the first brief need to be?
Detailed enough for a feasibility answer. Function, vehicle platform, interfaces and rough volumes are the essentials. Mark everything else as unknown rather than leaving it out.
Should I send a specification or a problem statement?
Send the problem and any hard constraints. A supplier with its own engineers can often reach a better design than one copied from a fixed specification.
Can a supplier work to my quality documents?
Ask directly. Share the documents you require, and ask the supplier to confirm in writing which it already works to and which would be new for the project.
What does an OEM need to know before approaching a UK manufacturer?
The volume range, the vehicle platforms, the approvals you need and the dates. Those four allow a supplier to say yes, no or not yet.
How is intellectual property handled?
It should be written into the agreement before design starts, covering the hardware design, the firmware and any tools built for the project.
Sources
- IATF 16949: automotive quality management system standard (IATF) (opens in a new tab) (accessed 10 October 2026)
- Scorpion Automotive: OEM and bespoke electronics (opens in a new tab) (accessed 10 October 2026)
- Scorpion Automotive: bespoke solutions and OE programmes (opens in a new tab) (accessed 10 October 2026)
Ready to brief an engineering team?
Tell us the function, the platform and the volumes, and we will say what is feasible and what we need next.