Plan every charge around the next shift.
TOGL works out what each vehicle needs, when it leaves and how long it can charge. It then plans charging around charger availability, the depot’s power limit and its tariff, while eligible flexibility can be routed through market partners.
Discuss a pilotOn vehicle-to-grid.
TOGL is developing smart charging, depot load management and demand shifting using supported vehicle and charger integrations. Where suitable equipment and integrations are already in place, these capabilities are designed to work without extra TOGL hardware.
The platform is architected for bidirectional flow, and we will support V2G when vehicle availability, charger certification, and market access make it commercially viable at fleet scale.
We do not sell V2G revenue that does not yet exist.
Platform overview
Inputs
Vehicles & telematics
Chargers and their management system
Fleet rules & departure times
TOGL
Vehicle-first orchestration
Next shift.
Site limit.
Tariff.
Outputs
Planned charging schedule
Eligible partner flexibility signal
Readiness rules applied
One decision layer from vehicle need to charging plan.
TOGL starts with the energy each vehicle needs for its next shift. It coordinates that need with available chargers, site demand, the connection limit and the depot tariff. Where assets qualify and a partner provides market access, the same plan can identify charging that may move for flexibility services.
Data inputs
The inputs behind each charging decision.
Vehicle state of charge
Charging status
Location context
Fleet readiness rules
Tariffs and energy prices
Site and substation capacity
Partner flexibility signals where eligible
Charger or platform data where integrations exist
Input availability depends on supported integrations, operator permission and asset type.
Integrations
How TOGL connects to what a depot already runs.
TOGL connects through integration partners. We check the vehicles, chargers and charger management system used at each depot rather than publishing a broad compatibility claim.
Connections through partners
TOGL connects through integration partners. Supported passenger vehicle integrations are live, and the current brand list is available on request.
Checked for each depot
What works depends on the vehicles, chargers and charge point management system at the depot, so TOGL checks the actual setup.
Uses supported equipment
Where suitable vehicles, chargers and integrations are already in place, TOGL is designed to manage charging without extra TOGL hardware.
Send the vehicles, chargers and charge point management system a depot runs, and TOGL will confirm what is supported today and what would need an integration partner.
Request a coverage checkGrid connection intelligence
Assessing how many vehicles a depot may support.
Vehicle duty cycles and charging windows determine the demand. The depot’s confirmed connection limit and existing site load determine how much of that demand can fit before an upgrade may be needed.
Indicative local network capacity
An early view of capacity around the network serving the depot. It does not replace the site's confirmed limit in its connection agreement.
Vehicles the confirmed site limit may support
An assessment using the depot's confirmed connection limit, vehicle duty cycles and charging windows.
Whether an upgrade may be delayed
An assessment of whether better charging schedules could delay or reduce a grid upgrade. The result depends on the site data and operating plan.
What it is built from
Substation capacity data
Indicative network capacity around the substation serving the site. The depot's confirmed limit comes from its own connection agreement.
HGV operator licence data
Where heavy fleets are authorised to operate from, and at what vehicle count, which is what determines the load a depot will eventually need.
Spatial analysis
Depot locations matched to the network serving them, giving an indicative local view that can be checked against the site's confirmed connection limit.
Orchestration logic
How TOGL makes a charging plan.
Calculate what each vehicle needs for its next shift
Check dwell time, charger availability and the site limit
Price the charging windows against the depot tariff
Schedule charging inside the operational constraints
Replan as vehicles and site demand change
Pass eligible flexibility to market partners
Current & roadmap
Capability scope and dependencies.
This table is the precise record of supported, developing and dependency-gated capability. Nothing is described as shipped unless it is.
Capability
Status
Notes
Supported passenger vehicle integrations
Supported OEM brands via integration partners. Current list available on request.
Fleet charging intelligence
Built around operational guardrails and charging context
Depot optimisation
Depends on site data, vehicle data, and charging data
Grid connection intelligence
Substation headroom, vehicles supported before upgrade, and how much of that upgrade load management can defer
eHGV support
In active development for depot orchestration. Vehicle data access depends on OEM API availability
Bus support
Depends on OEM API availability and heavy vehicle integration maturity
Flexibility market participation
Depends on market access, asset eligibility, and aggregator relationships
Vehicle-to-grid (bidirectional) flow
Architected for, not sold. Gated on vehicle availability, charger certification, and market access
What the status labels mean
- Live
- In production with customers or pilot users today.
- Planned
- On the roadmap, dependency-gated, no committed date.
Architecture
Where the orchestration layer sits.
Vehicle data
SoC, location, charging status
TOGL orchestration layer
Rules engine, optimisation logic
Fleet rules
Next shifts, dwell time, site limits
Charging decisions
Optimised schedule output
Reporting & partner workflows
Charging plans, eligible flexibility
Vehicle data
SoC, location, charging status
TOGL orchestration layer
Rules engine, optimisation logic
Fleet rules
Next shifts, dwell time, site limits
Charging decisions
Optimised schedule output
Reporting & partner workflows
Charging plans, eligible flexibility
From charging decisions to investment decisions
See what the plan could change at a working depot.
Vehicle energy needs, available site power and departure times set the boundaries. Within them, a different schedule may reduce simultaneous demand and charging costs. Our illustrated example keeps the same energy requirement and shows why some proposals could become workable while others still need infrastructure changes.
Explore the illustrated charging planTOGL depot optimisation
Security & permissions
Built around permissioned data access.
Access to vehicle and site data is permissioned per organisation, and the failure mode is charging, not stranding: if TOGL cannot reach a vehicle or charger, the site falls back to charging in line with the duty cycle it has to meet. Optimisation is what degrades, never readiness, and never your uptime depending on ours. The exception cases and the override path are set out on the drivers page.
What is true today about hosting, sub-processors, certifications and vulnerability reporting is stated plainly on the security page.
Permissioned access
Data access is granted by users and operators with explicit permission scopes.
Governance by design
Security and governance are design requirements, not add-ons.
User control
Fleet operators retain control over what data is shared, with whom, and for what purpose.
Commercial model
How TOGL is bought.
Pilot scope and commercial terms are agreed directly with each operator. They depend on the fleet, depot and integrations involved. Talk to TOGL about your site and we will explain what taking part would involve.
Revenue share
One model TOGL discusses with operators and energy partners. The scope and share are agreed for each deployment.
API licensing
An integration layer for partners, aggregators and energy market participants.
Enterprise partnerships
OEM, fleet, infrastructure and energy partner arrangements across the commercial ecosystem.
Flexibility market participation is a planned capability, so any share of flexibility value carries the same dependencies as the capability table above: market access, asset eligibility, and aggregator relationships.
Bring us the next shifts and the site constraints.
Bring the vehicle and charger list, departure times, dwell windows, site capacity and tariff. TOGL will work through the charging plan, integration coverage and any partner dependencies.
Discuss a pilotFAQ
How the platform works
How does TOGL decide when a vehicle charges?
TOGL plans charging around the time and energy each vehicle needs for its next shift. It brings supported vehicle and charger data together with departure times, charging windows, the confirmed site limit and electricity tariffs, then tests a charging plan within those constraints.
What data does TOGL need from a fleet?
TOGL uses supported vehicle data, charging status, departure times, charging windows, the depot's confirmed connection limit and energy prices. Data from the charge point management system, which manages the chargers, is used where an integration exists. Vehicle data access depends on the manufacturer offering an API for that model.
Does TOGL support vehicle-to-grid (V2G)?
TOGL does not offer vehicle-to-grid today. V2G depends on suitable vehicles, certified chargers and market access that are not yet in place at fleet scale, so TOGL describes it as Planned.
Which vehicles does TOGL support?
TOGL checks vehicle coverage for each pilot because data and control access varies by manufacturer, model and integration. Supported passenger vehicle integrations are available, while electric HGV and bus scope depends on the interfaces available for those vehicles. The current integration list is available on request.
Will TOGL ever override a depot operator?
TOGL plans inside the depot operator's readiness rules, and operators keep the manual override. If the available time, charger power or site capacity cannot meet a vehicle's requirement, TOGL surfaces the shortfall rather than presenting the vehicle as ready.
Where is fleet data stored, and who can see it?
TOGL keeps fleet data permissioned per organisation, and the fleet operator controls what is shared, with whom and for what purpose. Enquiries submitted through the TOGL website are held in Brevo, which is the system of record for them, and the website itself operates no database. Hosting, sub-processors, certification status and vulnerability reporting are stated on the TOGL security page, and platform-specific data flows are available to prospective partners under NDA.
Which chargers and fleet systems does TOGL work with?
TOGL connects through integration partners and checks what works at each depot. Supported passenger vehicle integrations are live and the current brand list is available on request. Where suitable vehicles, chargers and integrations already exist, TOGL is designed to manage charging without extra TOGL hardware. Contact TOGL with the vehicles, chargers and charge point management system used at the depot.
What commercial models does TOGL offer?
TOGL agrees pilot scope and commercial terms directly with each operator or partner. Terms depend on the fleet, depot, integrations and services involved, so TOGL does not publish a rate card or promise a standard fee, licence model or revenue split.