EV Specs as Ranges
Most EV spec sites create a separate page for every trim, drivetrain, and battery combo. ElectronsX takes a different approach: one canonical model page per body variant, with specs shown as min–max ranges.
What "Collapsed Into Ranges" Means
What is used:
- Canonical model page: one page representing a model family + a body variant (example: “EQS Sedan” vs “EQS SUV”).
- Range values: show min–max for specs that vary across trims/configs (range, battery kWh, power, charging kW, price).
- Named trims: shown only when they are stable and meaningful.
Why Traditional "One Page per Trim" Breaks
It seems precise, but it creates structural problems for both users and data integrity.
Explosion of permutations. One model can have dozens of buildable configs: seat layouts, software packs, battery tiers, AWD packages, regional homologations.
Specs change frequently. Prices, charge curves, software features, and even battery suppliers can change mid-year with little public visibility.
Many thin, near duplicate pages. Pages differ by one number and are hard to compare against, leading to page flipping and ultra-wide "compare models" UX.
False precision. “Peak DC charging” is not a promise of average speed. Range depends on wheels, temperature, and duty cycle.
Why Ranges Are Better for Real Decisions
Buyers and fleets usually start at the family level, then narrow down.
- Families first: “Is the Mach-E family viable for fleet?” precedes “Which trim?”
- Boundaries matter: fleets care about worst-case and best-case boundaries for cost, range, and turnaround time.
- Engineering drivers: platform, voltage, thermal system, and charging behavior often explain performance more than a single brochure value.
What Gets Ranged vs What Stays Singular
Attributes only get ranged when they are inherently variable across trims/configurations.
| Attribute Type | How ElectronsX Displays It | Example | Why |
|---|---|---|---|
| Trim-variable numeric specs | Min–max range | EPA range, usable kWh, peak kW, MSRP | Varies by battery, motors, wheels, region |
| Platform / architecture | Single value (or small set) | Platform name, voltage class | Usually stable across the family |
| Feature presence | Yes / No / Optional | Heat pump, preconditioning, Plug&Charge | More important than a “number” |
| Behavioral performance | Explained (not just listed) | Charge curve shape, cold-weather impact | Depends on thermal + software strategy |
Preventing Ranges From Becoming “Vague”
Ranges are only useful if they are constrained and annotated.
- Include the anchor assumptions: test cycle (EPA/WLTP/CLTC), region, and whether capacity is gross vs usable.
- Separate peak from typical: peak values are labeled as such; average behavior is discussed qualitatively when known.
- Reference trims in special sections: for Fleet Core and Autonomy Core reference sets, the scoring section names the specific reference variant.
When Separate Pages are Used
Separate pages are justified by reality, not marketing.
- Different body shell: Sedan vs SUV vs Wagon/Avant/Sport Turismo.
- Different purpose-built vehicle: Track variants, off-road variants, convertible variants, robotaxi-only platforms versus host vehicles.
- Different market vehicle: if the “same name” is materially different across regions (hardware + homologation + packaging).