Electric scooter testing log: what to record on every ride
A good electric scooter testing log records the same details on every ride (battery, ride mode, distance, conditions and errors) and backs every fault with a timestamped photo or clip. BetaSuite: Tester's Toolkit (betasuite.app) is an iPhone, iPad and Android app built for this: it burns the date and time into every photo and video, keeps each ride as a session and turns them into a report for the manufacturer. The template and range test below work with any notebook or spreadsheet, and there is a free 12-step ride protocol to import. Ride safely and within your local rules.
What to test in an electric scooter beta
Cover each area at least once, then repeat the ones that fail so you can say how often they fail. Do the riding tests on ground where riding is allowed, and read the safety note before you start.
| Area | What you are checking | Evidence worth capturing |
|---|---|---|
| Range vs claimed | Distance per charge at a set ride mode, rider weight and route, compared with the manufacturer's claimed range. Use the fair range test below. | Stamped photos of the display at the start and end of each ride. |
| Acceleration and throttle | A smooth pull-away from a standstill in each mode, with no surge or lag, and sensible behaviour when you change mode or let go of the throttle. | A note of what you felt, plus a clip if a helper can film from the side. |
| Braking | Stopping in a straight line with the brakes it has (electronic, drum or disc), with no pulling, grabbing, fade or noise, and the motor cutting as the manual says. Test at low speed in a quiet, traffic-free place. | A clip filmed by a helper from the side, and a note of the speed and the surface. |
| Hills | Your steepest hill within the rated gradient, and the way back down (speed limiting, regenerative braking if it has it). Does it hold speed, overheat or cut out? | A photo of the display at the top, with the time visible. |
| Speed limits and ride modes | Each mode caps speed as described, with no jolt at the limit, and any lower-speed mode for local rules works. | A note of the mode, the speed shown and what happened. |
| Lights, horn and indicators | Headlight, rear and brake light, indicators and the bell or horn, in daylight and after dark. Are they visible from the distance the manual claims? | A photo with the lights on, taken at dusk. |
| App, lock and firmware | Pairing, lock and unlock, live speed and battery, mode changes, any alarm, dropped connections and firmware updates. | A screen recording, or a dual recording of the app and the scooter together while stopped. |
| Folding and build | Folding and unfolding, latch security, play in the stem, rattles, deck grip, tyres (air-filled or solid) and loose bolts after a week of use. | A clip of the fold, and photos of any wear or play. |
| Wet weather and water | Only as far as the manual and the rated water protection allow: damp roads, splashes and rain exposure. Never hose it down or immerse it. | Stamped photos with the weather visible, and notes of any fault afterwards. |
| Charging | Time to charge from a known level, how warm the charger and the scooter get, whether it stops at full, and how much charge it loses while parked. | A photo of the battery level and the time at each end. |
| Noise and vibration | Motor whine, brake noise and rattles over rough ground. | A short clip with sound, taken while stopped, and notes on the surface. |
Safety first, and check the rules. Wear a helmet, and consider other protective gear. Test brakes, cut-offs and speed limiting at low speed in a quiet, traffic-free place, never at speed on a public road. Rules for electric scooters differ widely: in many places a privately owned scooter is restricted or not allowed on public roads, footpaths or cycle paths, and there can be rules on age, top speed, lights and insurance. Check your local rules before you ride anywhere, and if you can't ride legally where you live, test on private land with the owner's permission. Don't use your phone while riding: stop first, then record. If the battery swells, smells, hisses, gets unusually hot or is damaged, stop using it, don't charge it, keep it away from anything flammable and contact the manufacturer straight away. Charge with the supplied charger, on a hard, non-flammable surface.
Conditions to record every ride
Write the same fields down on every ride. A log with the same columns each time is what lets you say "range dropped after the update" instead of "it feels worse".
| Field | What to write | Why it matters |
|---|---|---|
| Date, start time, route | The date, the time you set off and the route or loop. | Lets you repeat the same ride and line the ride up with any logs the manufacturer keeps. |
| Odometer and distance | Odometer at the start and end, and the trip distance. | The basis for any range figure. |
| Battery | Percentage at the start and end (and the voltage or bars if the display shows them). | A gauge isn't always linear, so record both ends. |
| Ride mode | Which mode you used, and roughly how much of the ride in each. | Range, speed and feel change a lot with the mode. |
| Rider and load | Your weight plus anything you carry. | Range and hill performance depend on it. |
| Tyres | Pressure, front and rear, if they are air-filled. Say if they are solid. | Low pressure costs range and changes the feel. |
| Conditions | Temperature, wind, rain, surface and how much climbing. | Cold weather typically reduces range, and headwinds and hills use more battery. |
| Versions | Firmware for the scooter, display and app. | Engineers need to know exactly what you were running. |
| Errors and oddities | The code, the time and what you were doing. | This is where the findings come from. |
| Feel | A 1–5 rating and a line on smoothness, noise and vibration. | Subjective, but trends matter. |
Copy this into a notes app or a spreadsheet:
Date / start time: Route and distance: Odometer start / end: Battery start / end: Ride mode(s): Rider + load weight: Tyre pressure (front / rear, if air-filled): Weather, surface, climbing: Firmware (scooter / app): Errors or oddities (time, what happened): Feel (1–5) and notes:
And here is how two filled-in lines might look. The numbers are made up, to show the shape.
| Date | Route | Distance | Battery | Mode | Notes |
|---|---|---|---|---|---|
| 4 Oct, 7:50 am | Private-land loop | 12.4 km | 100% to 52% | Mode 2 | 11°C, light headwind, no errors. Slight rattle over the speed bumps. Feel 4/5. |
| 6 Oct, 5:30 pm | Private-land loop | 12.2 km | 100% to 55% | Mode 2 | 16°C, calm. The app dropped its connection once at the far end. Feel 4/5. |
BetaSuite adds the date and time to every photo and video for you, and can add GPS, live weather, the season and the time zone, each of which you can turn on or off in Settings.
How to run a fair range test
Range depends on everything, so the only fair comparison is one where you change a single thing at a time.
- Charge fully with the supplied charger. Note the date, time and battery reading.
- Pick a loop you can repeat, on ground where riding is allowed, with a known distance and amount of climbing.
- Fix the variables: ride mode, tyre pressure, rider and load, and as close as you can to the same temperature and wind. Note whether the ride was steady speed or stop-start.
- Ride until the battery reaches a set point (for example 20%) rather than riding it flat, because some scooters cut power sharply when the battery is low.
- Record the distance and the battery at the finish. If you can, take the distance from a second source (a phone GPS app or a bike computer) too, so you can see whether the scooter's own figure is believable.
- Work out the result. Kilometres per 10% of battery is simple. If you know the battery capacity in watt-hours, Wh per km = capacity × (% used ÷ 100) ÷ distance.
- Repeat in another ride mode, and again in different temperatures. Treat the numbers as comparisons, because battery percentages are estimates.
- Only then compare with the claimed range, and read the conditions behind that claim first. Manufacturers' range figures are often measured under set conditions (a lighter rider, steady speed, flat ground) that may not match your ride.
A pass/fail checklist for an electric scooter
Agree your thresholds with the manufacturer's brief first. If it doesn't give any, write your own before you start (for example, "at least 20 km in mode 2 on the test loop") so you aren't judging after the fact.
- Powers on, the display shows speed and battery, the lights work and no error code appears.
- Each ride mode pulls away smoothly from a standstill, with no surge, delay or cut-out.
- The brakes stop the scooter in a straight line, and the motor cuts as the manual says.
- Speed is capped as described in each mode, without a jolt at the limit.
- Climbs your test hill (within the rated gradient) with no overheating warning or big drop in power.
- Range meets the target in your brief in the agreed mode, with the conditions noted.
- The app connects, locks and unlocks every time, and stays connected for a full ride.
- Lights, horn and indicators work every time, including after dark.
- Folds and unfolds easily, the latch holds, and there is no new play or rattle in the stem.
- Charges fully and stops, with no unusual heat, smell or noise.
- Handles wet weather only as the manual says, with no fault afterwards.
- Installs a firmware update cleanly and keeps your settings.
A fail isn't a verdict on the scooter. It's a finding. Write it up with the conditions and the evidence.
How to capture evidence engineers can use
- Stop first, then record. Don't use your phone while riding. When something goes wrong, pull over somewhere safe, then photograph the display and make a note.
- Photograph the display at the start and end of every ride. A stamped photo of the odometer and battery beats a typed number.
- Put the app and the scooter in one clip. For pairing, lock and unlock problems or firmware updates, dual recording in BetaSuite records your phone's screen and the rear camera into a single video while you're stopped.
- Get a helper for the brake and cut-off tests. Ask someone to film from a safe distance at the side, rather than holding a phone yourself or mounting one on the bars.
- Mark it as it happens. Once you have stopped, add a one-tap marker or a voice note with the time ("power cut out on the climb past the gate").
- Burn the time into the picture. A stamp that is part of the image travels with the file. File metadata is often stripped when a photo is shared or compressed. BetaSuite stamps every photo and video, with optional GPS, weather, season and time zone. More on that in the timestamp camera app guide.
- Photograph wear and loose parts. Tyres, brake pads or discs, the folding latch, the stem, cables and the charging port.
- One issue per photo, clip and note. Name it by what happened ("Power cut-out on the gate climb"), not "IMG 214".
What to send the manufacturer
A good report is short at the top, specific in the middle and backed up at the bottom. See how to write a beta test report for the full structure.
| Section | What goes in it |
|---|---|
| At a glance | Model and serial number, firmware versions for the scooter, display and app, test dates, where you rode (for example private land) and rider weight. Three sentences on how it went. |
| Findings, worst first | Safety issues first (anything involving the brakes, the battery, the folding latch or a sudden loss of power or control), then faults that stop the scooter working, then annoyances. For each one: what happened, what you expected, how to repeat it, how often it happens and the conditions. |
| Ride log | Your log for the test period, as a spreadsheet or CSV, so they can see the pattern behind the findings. |
| Evidence | Time-stamped photos and clips matched to each finding by name or time. |
| What worked | A short list. Engineers also need to know what not to change. |
| Data files | A CSV or JSON of your findings if they ask. BetaSuite reports can ship with both. |
Here is the format for one finding. The values are made up, to show the shape.
Title: Power cuts out on a long climb and returns after about 8 s Severity: High (sudden loss of power) Expected: Holds speed to the top of the climb Actual: Power dropped to zero about 30 s up the slope, no error shown, back after 8 s Frequency: 2 of 3 climbs, both with the battery under 35% Conditions: 9°C, mode 2, 80 kg rider and load, firmware 1.4.2, dry surface, private land Evidence: Photo of the display at the top, stamped 16:42:09
Want to see a finished report? Open the sample report (PDF). It has an At a Glance summary, findings sorted by severity and an image appendix.
Running it in BetaSuite
- Create a project for the scooter, and note the model, serial number and firmware in your first session.
- Import the free protocol below. It has two free-text steps that work as your before-ride and after-ride log.
- Start a session for each ride. Capture the photos and clips the steps ask for while you are stopped, and drop a marker whenever something happens.
- After a few rides, generate a PDF or Word report with an At a Glance summary and findings by severity, plus JSON and CSV data files if you want them.
AI summaries are optional and opt-in. For units under NDA, Confidential Mode blocks cloud AI and cloud uploads, and warns you before you share or export anything. Everything is stored on your device, with no account.
Free BetaSuite protocol: electric scooter ride test
This is a ready-made, 12-step protocol for one ride day with an electric scooter. It was built with the site's own Protocol Builder, so the link below is a real import link. It opens with a free-text log step and has a second one for after the ride, mixes pass/fail checks with choice, multiple-choice and rating questions, and asks for a photo, video or dual recording where the evidence matters. Do the capture steps while stopped or with a helper filming, never while riding, and only ride where it is legal. For the general idea, see the test protocol template.
Electric scooter ride test · 12 steps · free to import and edit
- Before the ride: record the battery percentage, odometer, tyre pressures (if pneumatic), ride mode, outside temperature, wind, your total weight with any load, and the scooter and app firmware versions.
- Power-on and lights: the scooter powers up, the display shows speed and battery, the headlight and rear light work and no error code appears. Photo: the display with the lights on.
- Throttle response: on flat, quiet ground at low speed, the scooter pulls away smoothly in each ride mode, with no surge, delay or cut-out.
- Braking: in a quiet, traffic-free place at low speed, each brake slows the scooter in a straight line with no pulling, grabbing or fade, and the motor cuts as the manual describes. Have a helper film from the side. Never film while riding.
- Hill climb: on a known hill within the rated gradient, the scooter holds a steady speed to the top, with no overheating warning, cut-out or big drop in power. Photo: the display at the top, once you have stopped.
- App and lock: with the scooter stopped, the app pairs, locks and unlocks it, changes ride mode and shows live speed and battery. It stays connected for the whole ride. Record the app and the scooter together.
- Folding: the scooter folds and unfolds easily, the latch locks firmly and there is no play or rattle in the stem afterwards.
- Charging: with the supplied charger, the scooter charges from a known level to full and stops, with no unusual heat, smell or noise. Photo: the display or charger at the end, with the time visible.
- How did the scooter feel to ride?
- After the ride: record the battery percentage, distance, odometer, any error codes, and anything that felt wrong.
- Which problems did you see? Tick all that apply.
- Overall ride feel and confidence. 1 = poor, 5 = excellent.
Show the raw code
How to import it
- On your phone, tap Open this protocol. If BetaSuite is installed, it opens its import sheet with the code filled in. If the link opens in your browser instead, tap Copy code there (or here).
- In BetaSuite, open Test protocols, choose Import and paste the code or link.
- Edit any step to suit your unit, then run it. Your answers are saved to a session and roll up into the report. Protocols, sessions and reports are part of Advanced mode; if you're in Basic mode, Test protocols offers to switch for you.
Want to change the steps first? Open the link in the free Protocol Builder. It runs in your browser with no account, and you can generate a fresh code from your edits. Running a whole beta programme? See how to give every tester the same protocol and merge the results.
When BetaSuite is the wrong choice
BetaSuite covers everything from a single stamped photo to a full report for the manufacturer. It is the wrong tool only when:
- You need data from the scooter itself. BetaSuite doesn't connect to the scooter, battery or display, so it can't read telemetry, error history or power output. You type in or photograph what you see.
- You want a ride tracker. BetaSuite can stamp GPS coordinates on photos and videos if you switch that on, but it isn't a route-recording app and doesn't log speed or elevation. Use a bike computer or your usual tracking app for those, and keep both in your log.
- You want to film while riding. Don't. Stop somewhere safe first, or ask a helper to film.
- You need lab numbers. Braking distance certification, motor torque, battery capacity and water-ingress ratings need proper equipment, not a phone.
- You want to test an app, not hardware. BetaSuite is not a TestFlight or Google Play testing tool. See what a hardware beta testing app needs to do.
Don't need a report? If the manufacturer takes findings through its own portal or form, or you only want stamped photos and video, switch BetaSuite to Basic mode (Settings > App mode). It keeps every capture tool, including dual recording and Instant Capture, and leaves out projects, sessions and reports, so it works as a plain timestamp camera. Attach the files wherever the manufacturer asks, and switch back to Advanced at any time without losing anything.
If you run the programme rather than test in it, see the programme page. For the longer case for the app, see why BetaSuite.
Frequently asked questions
- What should an electric scooter testing log include?
- The date, start time and route; odometer and distance; battery at the start and end; ride mode; rider and load weight; tyre pressure; temperature, wind and surface; firmware versions; any errors with the time; and a quick feel rating. Write the same fields on every ride so you can compare them.
- How do I test electric scooter range against the claimed figure?
- Charge fully, ride a repeatable loop in a fixed ride mode with the same rider, load and tyre pressure, and stop at a set battery level such as 20% rather than riding it flat. Compare kilometres per 10% of battery, or Wh per km if you know the capacity, and read the conditions behind the manufacturer's figure before you compare. Change one variable at a time.
- Is it safe to film while riding?
- No. Don't use your phone while riding. Stop somewhere safe first, then photograph the display, record a short clip and add a note. For brake and cut-off tests, ask a helper to film from the side, and do them at low speed on private ground.
- Can I test an electric scooter on the road?
- Check your local rules first. In many places a privately owned electric scooter is restricted or not allowed on public roads, footpaths or cycle paths, and rules on age, speed limits, lights and insurance differ by region. If you can't ride legally where you live, test on private land with the owner's permission and say so in your report.
- How do I report a battery or brake problem?
- Stop riding safely, photograph the display, then write down the time, ride mode, battery percentage, temperature and what you were doing, and how often it happens. If the battery swells, smells, hisses, gets unusually hot or is damaged, stop using it, don't charge it, keep it away from anything flammable and contact the manufacturer straight away. For a brake fault, don't ride the scooter again until the manufacturer says it is safe.
- Can I use BetaSuite for a pre-release scooter under NDA?
- Yes. Everything is stored on your device with no account. Confidential Mode blocks cloud AI and cloud uploads, and warns you before you share or export anything. Captures still save to your camera roll by default, so if your photos back up to the cloud, turn Camera Roll off in Settings → Save Destinations before you turn Confidential Mode on. Check your NDA first for what you may photograph and what you may send, and by what route.
- Is BetaSuite a ride tracker?
- No. BetaSuite: Tester's Toolkit is a field-testing app for evidence and reports. It can stamp GPS coordinates on photos and videos, but it doesn't record routes, speed or elevation. Use a bike computer or tracking app for those.
- Is BetaSuite a TestFlight alternative, and is it a subscription?
- It isn't a TestFlight alternative. BetaSuite is not an app-beta tool and has no connection to TestFlight or Google Play testing tracks. It is a one-time purchase from the App Store or Google Play, with no subscription, no ads and no account. Each store sets the price.
Related guides
Start testing with timestamped evidence
BetaSuite: Tester's Toolkit burns the date and time into every photo and video, then turns your sessions, markers and findings into a PDF or Word report, on iPhone, iPad and Android. Only need a timestamp camera? Use Basic mode.
One-off purchase · No subscription · No ads · No tracking · Yours for life