How to Schedule Electric Motorcycle Fleet Charging

Can a fleet schedule an electric motorcycle to charge in an off-peak window and still have it ready for the next shift? On the 2025 Zero S, SR, SR-F and SR-S sold in North America, yes — provided the schedule, not the charge target, is set as the outer limit. That distinction is the whole article. The owner manual for these four models describes a setting that lets a rider delay or schedule pack charging to take advantage of off-peak power rates, and it describes a separate Charge Target percentage elsewhere in the same control set. Fleets that treat the two as one promise end up with bikes that quietly stop short of the number someone typed into a phone.

Everything below is bounded to that manual and those four 2025 models. Site electrical capacity, utility rate windows, connector sharing and battery-life outcomes sit outside what the document establishes, and the charge-speed figures a fleet manager usually wants first are simply not in it.

Which Setting Wins on a Scheduled Charge?

The two controls do not run as parallel plans. Charge Target functionality is overridden when the rider has enabled the Delay/Scheduled option, and that option takes precedence; it is adjusted exclusively through the Zero Motorcycles smartphone application. The reason is structural rather than a quirk of this firmware: a pack charges on one timeline, so the machine can hold only one active charging plan at a time. Which means the schedule is the outer boundary of the session and the target is a requested stopping point somewhere inside it.

That ordering matters for a fleet because the settings are made in different places. Someone sets the schedule in the app, someone else may set the target on the dash, and neither screen carries the other person's intent. A target entered and left enabled is not a guarantee once the scheduled option is live; the manual describes no combined mode that satisfies both.

Why the End Time Beats the Charge Target

The manual is blunt about the close of the window: if the pack's Charge Target percentage has not been met before the scheduled End Charging time, charging ceases at the programmed time. The end time is a hard stop and the target is conditional, so a request at the top of the range can leave a bike short if the window was tighter than the request assumed.

My preference, bounded to this model's evidence and not offered as a general law: treat the End Charging time as the commitment and size the Charge Target to fit inside it. Because the cutoff is absolute and the target is not, the only number a fleet can promise the morning shift is the end time; the state of charge at that moment is whatever the window allowed. If you need certainty at six, shorten the target rather than argue with the clock.

The target range runs from 30% to 95% state of charge in 5% increments, and the manual supplies no charge-rate figure at all. Without a rate, nobody can honestly compute how far a given share of pack capacity carries a given bike in a given window, which is the reason to size targets from your own logged results rather than from arithmetic done in a planning meeting.

How Do You Set the Charge Target?

The target is a dash setting, not an app setting. The MODE button moves the value left or right through state-of-charge percentages from 30 to 95 in 5% steps. That step size matters for record keeping: a worksheet that records a round intention is not the setting the bike holds, and comparing what you asked for against what arrived requires the exact step.

More consequential is what happens when nobody enables the target. If the Charge Target option is not enabled, the pack charges to 100% by default, provided it is allowed to fully charge. Skipping the setting is not neutral; it selects full charge. Because a default is still a choice, a fleet that never touches Charge Target has decided on 100% for every bike, every night, whether or not the shift needs it.

Whether a lower target suits your routes is a question the manual does not answer for you. What it establishes is the mechanics: the target exists only while enabled, and it moves between 30 and 95 in 5% increments.

What Is the Fleet Charging Sequence?

A repeatable order for a fleet, following the way the settings take effect.

Confirm that the bike in front of you is one of these 2025 models and that your manual covers it, because the control paths described here belong to that document and installed equipment can vary.

Open the Zero Motorcycles smartphone application and set the Delay/Scheduled option — the named adjustment path for scheduling. The manual does not document the app's screen order, so whoever sets it should record the end time that was entered.

Decide whether a Charge Target belongs in this session. If it does, enable it and set the value on the dash with the MODE button, in 5% steps inside the 30 to 95 range, accepting that with a live schedule the target is a request rather than a promise.

Connect the charging cable and read the charging screen, where the charging delay appears. Leaving the bike before that read means you confirmed an app setting, not a charging session.

Override stays in reserve for a departure that moved, and each use belongs in the log so the standing schedule can be corrected.

The check at every step has the same shape: did the setting land where the plan said, and can I see it on the vehicle rather than only on a phone?

What Does the Charging Screen Confirm?

The only in-person proof that a delayed charge is armed is on the bike, and it requires the cable. With the motorcycle connected to the charging cable, the pack's charging delay is shown on the charging screen. Because the display depends on that connection, the moment of confirmation is plug-in, not app-close. A schedule that looks right on a phone but produces no delay indication at the charging screen is an unconfirmed session.

For a depot, that shifts where the check happens. The person walking the row at night is verifying a screen, not a spreadsheet. A short written standard — connect, look for the delay, note it — costs seconds per bike and catches the mismatch that otherwise surfaces at five in the morning as a flat pack.

When Should a Rider Use Override?

Override is a dash control: highlight and select it, and the charging delay is overridden. Note what it acts on — the delay. It changes when a session starts, so a rider who suddenly needs the bike sooner can begin charging now instead of waiting for the programmed window.

It does not repeal the end time. The cutoff for an unmet target still applies at the programmed End Charging time, so overriding the delay does not turn a too-tight schedule into a completed one. Because the two mechanisms are different, a bike that ends short after an override is telling you something about the window, not about the button.

That is the distinction worth training: Override is for a departure that moved, not for a schedule that was never going to fit. If overrides cluster on the same bikes at the same hour, the standing end time is wrong for that duty cycle and should be changed in the app.

What Would a Small Fleet Trial Show?

Suppose a depot with a handful of these bikes wants to know whether its schedule holds before committing the whole row. The trial needs no charge-rate assumptions; it needs a log with five fields per bike per night: the end time entered in the app, the dash Charge Target if one was enabled, whether the charging screen showed a delay at plug-in, the state of charge at the next shift start, and any Override event.

Read the results as pairs. A bike that showed the delay and met its target before the end time is a schedule that fits. A bike that showed the delay and arrived below target is a window too short for that target, because the end time cuts the session regardless of what was requested. A bike with no delay indication at plug-in never received the schedule, and the fault sits in the setting path or the app handoff rather than in the pack. An Override in the log points at a departure pattern that moved.

None of that depends on invented performance numbers, which is the point. The manual supplies control behavior and constraints; the depot supplies its own measurements. Run the trial across the worst shift in the rotation, since a schedule that only survives quiet days is not a schedule.

What This Manual Leaves to Fleet Policy

The manual's scope is the charging controls on these four 2025 models: the app-adjusted Delay/Scheduled option, the dash Charge Target, the end-time cutoff and the Override control. It does not establish site electrical capacity, your utility's off-peak window, connector sharing, route duty cycle, or any battery-life outcome from charging to a particular percentage.

Because the scope stops at the vehicle, a promise about cost per mile, charge speed or pack longevity needs evidence from somewhere else. Which means the honest deliverable here is a control sequence and a set of buyer questions, not a return figure.

Those questions belong before the first bike is scheduled. Does the utility's off-peak window end before your earliest shift start, or does the end time have to sit earlier than the cheap rate does? Can the operation hold a per-bike schedule, or does one person set a whole row from one phone? Does the shift pattern tolerate a target below 100%, or does route length make the default full charge the only workable setting? Who reads the charging screen at plug-in — the same person every night, or whoever happens to be closing?

Back to the six o'clock row. A bike is ready because two things happened the night before: the charging screen showed a delay when the cable went on, and the state of charge met the target before the programmed end time. If either is missing, the fix is a change to the schedule — an earlier end time, a lower target, a corrected app entry — not optimism about tomorrow. Set the end time first, then choose the target that fits the window you actually have.