Manage Product Capabilities

This page is an internal, high-level summary of what BetterFleet Manage does.

Availability varies by workspace. Some capabilities depend on permissions, feature flags, workspace configuration, and external integrations, so not every workspace will see every surface listed below.

Feature List

1. Sign in and control who can use Manage. Users can log into the right regional environment, while admins manage user accounts, roles, depot access, password resets, MFA, and Microsoft Entra ID SSO. Typical flow: Settings -> Workspace -> Users or Settings -> Workspace -> SSO.
2. See the live operational state of a depot, or all depots. The single-depot Overview shows incidents, charger availability, vehicle charging state, load gauges, and SOC/efficiency metrics; the all-depots beta view provides an aggregated overview of incidents, chargers, and vehicles across sites. Typical flow: open Overview, then switch the depot selector to a specific site or All depots.
3. Monitor chargers in real time. Users can view chargers and connectors by zone, see charger/connector status, connected vehicles, power, SOC, ETA to target SOC, and priority. Typical flow: open Chargers, use quick filters or sorting, then drill into a charger.
4. Operate chargers remotely and troubleshoot without going on site. From charger actions, users can override power, soft reset, remote start/stop, release a locked cable, and inspect recent transactions. Typical flow: Chargers -> ... menu on charger/connector -> action.
5. Monitor vehicle readiness for service. The Vehicles page shows charging status, SOC source, target SOC markers, priority, and attention states so operators can see which vehicles are usable now. Typical flow: open Vehicles, use quick filters like Charging, Not charging, or Requires attention.
6. Respond to incidents and control notifications. Users can review active and past incidents, inspect detailed timelines and troubleshooting info, and configure who gets notified for each rule, including external partners by email/SMS. Typical flow: Incidents -> incident detail or Incidents -> Manage Rules.
7. Manage site load and keep charging within electrical limits. Users can monitor site and circuit load, set circuit capacities and safety margins, choose load-balancing modes and strategies, use fail-safe behavior, and apply time-of-use limits. Typical flow: Load for monitoring, then Settings -> Power -> Circuits for configuration.
8. Improve charging performance with prioritisation and dynamic allocation. Manage supports load following, connector priority levels, vehicle-group priority, and manual overrides so limited power goes to the most important vehicles first. Typical flow: configure load behavior in Settings -> Power, manage vehicle groups and charging priorities in Settings -> Groups where enabled, then watch their effect on Chargers, Vehicles, and Load.
9. Build a depot layout and understand where assets are physically located. Users can create parking blocks, spaces, and site features, link connectors to spaces, and publish the layout to the in-depot map. Typical flow: Settings -> Depot based settings -> Layout -> edit -> publish.
10. Track vehicles in the depot and manage parking positions. Once a depot layout exists, the in-depot map shows live charger/vehicle positions, and users can drag non-charging vehicles into empty spaces or remove them when they leave. Typical flow: Map -> In depot -> Edit vehicle locations. This parking management flow is documented as beta.
11. Track vehicles outside the depot on a live map. With telematics integrated, users can search for vehicles in the selected depot, zoom the map, view live or stale locations, and inspect SOC, odometer, and speed. Typical flow: Map -> Out of depot -> search/select vehicle.
12. Diagnose charger and site behaviour over time. The Timeline view lets users inspect charger load, site load, charging sessions, offline periods, and related incidents across selectable time windows. Typical flow: Timeline -> select charger(s) -> zoom/pan -> click a session or offline window.
13. Plan daily operations and allocate the right EV to the right work block. When enabled, Dispatch lets users import schedules, set up a day of operation, review blocks, and allocate or force-allocate vehicles based on energy readiness and other rules. Typical flow: Settings -> Dispatch to upload GTFS/schedule data, then Dispatch to allocate vehicles.
14. Tune how dispatch recommendations work. When enabled, admins/managers can configure turnover time, extra SOC buffer, energy-estimation mode, and optional physical parking-constraint logic. Typical flow: Settings -> Depot based settings -> Dispatch -> Dispatch Behaviour.
15. Export operational, charging, and energy reports. Users can run reports for charging sessions, vehicle charging summaries, circuit capacity allocation, raw OCPP logs, connectivity, charger performance, sensor reads, site power, and daily EV load, depending on permissions, workspace configuration, and enabled report types. Typical flow: Reports -> choose report -> set filters/date range -> view/download.
16. Schedule reports to be emailed automatically. Admins/managers can schedule supported report types, set recipients, and email report outputs automatically, with the current UI creating daily schedules. Typical flow: Settings -> Reporting -> Scheduled Reports -> Create scheduled report.
17. Configure reporting inputs for cost and carbon analysis. Users can assign utility tariffs and grid emissions factors so charging-session and vehicle-summary reports include charging cost and CO2e. Typical flow: Settings -> Workspace -> Tariffs, then Settings -> Depot settings -> Reporting.
18. Manage commercial charging and roaming access. Workspaces can configure tariffs, roaming access groups, public/guest charging behavior, pre-authorisation, and share charger roaming URLs/QR codes. Typical flow: Settings -> Workspace -> Tariffs / Roaming access, then charger-level roaming links in charger settings. Roaming is documented as beta.
19. Maintain core site and asset master data. Admins/managers can add/edit depots, zones, chargers, charger models, vehicles, vehicle models, telematics providers, and workspace telematics polling settings. Typical flow: Settings -> Workspace for org-wide setup and Settings -> Depot based settings for site-specific setup.
20. Keep vehicle records clean and analysis-ready. Users can bulk upload vehicles, attach telematics devices, merge duplicates, mark vehicles inactive, assign cost centres, and organise vehicles into groups for reporting and charging priority where workspace groups are enabled. Typical flow: Settings -> Vehicles, Settings -> Workspace -> Cost Centres, and Settings -> Groups where available.
21. Generate and manage workspace API keys. Client admins can create, reveal, copy, and revoke account API keys for workspace-level integrations. Typical flow: Settings -> Workspace -> API Keys.

Key Notes

• Several capabilities depend on integrations: telematics for out-of-depot map and some SOC data, OCPP charger connectivity for live charger control, and IoT/power-meter data for dynamic load, fail-safe, and some power reports.
• Several capabilities also depend on feature flags, permissions, or workspace-level enablement, including all-depots overview, dispatch, layout editor, workspace groups and charging priorities, roaming, cost centres, scheduled reports, newer report types, EV load reporting, SSO management, workspace telematics settings, and API keys.
• A few features are explicitly marked beta in the manual: multi-site overview, dispatch, roaming access, and in-depot parking management.
• This page is intended for internal product understanding rather than as a strict mirror of the in-app help manual.