Create a defensible transaction record
Individual credentials and asset identification make it easier to demonstrate who drew fuel, for which vehicle or item of plant, at what location and in what quantity.
Industry solution
Council fleet fuel control Records by department.
Manage fuel across refuse fleets, highways vehicles, grounds equipment, minibuses, plant and shared operational depots. We can provide controlled access and reporting by vehicle, driver, department, site or cost centre.
Local-authority fleets serve different functions but often draw fuel from common infrastructure. A consistent fuel management process can improve accountability, support internal recharging and give authorised teams clearer visibility across several depots and user groups.
Understanding the operation
One control framework for a mixed public-service fleet.
Council and authority depots may support waste collection, highways, parks, passenger transport, property services and emergency support. Vehicles range from large refuse collection units to vans, cars and specialist plant, each with different usage patterns and reporting needs.
Fueltek can structure access and transaction records around departments, vehicles and sites while keeping the refuelling process straightforward for drivers. Central reporting can then support audit, budget review, internal allocation and stock planning.
The system should reflect governance responsibilities as well as fleet operations. User administration, data correction, department ownership and report access all need clear internal owners.
Benefits for public-sector fleets
One fuel estate. Clear departmental accountability.
Local-authority depots can serve refuse vehicles, highways teams, parks, workshops, plant and partner organisations. A controlled system can provide one practical refuelling process while preserving the user, asset, service area, site and product information required for responsible public-resource management.
Separate teams without duplicating systems
Permissions and reporting groups can distinguish council services, contractors or partner organisations while suitable users share the same managed infrastructure.
Monitor storage as well as dispensing
Tank stock, deliveries, capacity and selected alarms can be reviewed alongside pump transactions. Bunding, tank condition and current storage duties still require active inspection and maintenance.
Modernise in manageable stages
Existing depots can be surveyed, prioritised and upgraded with a common data model, allowing local operational needs to be retained while reporting becomes more consistent.
Typical operational problems
Keep shared depot fuel attributable to the right service.
Mixed fleets with different operating patterns
Refuse vehicles, highways plant, minibuses and support vans do not refuel in the same way. The system needs a common control method without losing the distinctions required for useful reporting.
Departments share depot fuel
A shared pump can serve several budgets and service areas. Transactions must be allocated accurately if the authority uses the data for internal charging or cost review.
Audit and accountability requirements
Anonymous access, shared keys and incomplete logs make it difficult to demonstrate who dispensed fuel and why a transaction belongs to a particular vehicle or department.
Several sites and user groups
Vehicles and staff may move between depots, while local teams manage daily operation. Permissions and reports need to work both locally and centrally.
Day-to-day workflow
Record the vehicle and user behind each departmental fuel issue.
1. Identify the authorised user
A council employee, contractor or approved service user presents their individual credential.
2. Select vehicle and department
The vehicle is identified and associated with the appropriate department, service or cost-centre structure.
3. Dispense the approved product
Diesel, AdBlue or another compatible configured product is released and recorded against the transaction.
4. Report and allocate
Authorised managers can review usage by service, vehicle, depot, user or reporting period and export information for further processing where required.
Relevant capabilities
Connect access, products and departmental reporting.
FT4000 control and identification
Define individual access for drivers, depot users and permitted external organisations. Connect the fuel issue to the relevant vehicle or plant record, with any mileage or other readings confirmed for the selected terminal and workflow.
FMO reporting around responsibilities
Agree the service areas, cost centres and fleet groups that reports need to reflect. Define the records and review process needed for internal allocation, including who corrects data and who is authorised to see each report.
Connected sites with local access
Standardise depot, vehicle and user names as sites are added. Confirm local permissions and communications alongside central reporting, drawing on the phased approach described in the Cheshire West Recycling project.
Product-specific managed dispensing
Specify the tank supply, dispenser and access process for each product. Compare the integrated AP or Twin arrangement with dedicated FT4000AB AdBlue dispensing where required, and confirm each product path against the vehicles and equipment in scope.
Operational value
Review depot activity against service responsibilities.
Department allocationAssign recorded quantities to the correct service or cost centre.
Improved auditabilityRetain user, vehicle, product, time and site details for each issue.
Mixed-fleet visibilityReview road vehicles, plant and support assets in one structured system.
Depot comparisonCompare connected locations using consistent names and reports.
Customer projects
Accountability across working council depots.
Our local-authority projects include replacement of a decades-old depot facility and phased installations across household-waste and recycling locations.
A complete depot replacement
The council replaced ageing storage and management equipment while keeping disruption to normal depot activity to a minimum.
- 60,000-litre dual-product storage for diesel and gas oil
- Two FT4000 units with TankWatch and online reporting
- Individual permissions for 145 diesel users and 24 gas-oil users, with mileage capture
For your project: review the physical fuel layout alongside user permissions and transaction fields. Blackburn with Darwen’s replacement combined dual-product storage, two FT4000 units, individual access and mileage capture.
Read the Blackburn with Darwen case studyA phased multi-site programme
The programme expanded from larger depot equipment to additional household-waste and recycling locations over several phases.
- Initial 40,000-litre installation with managed dispensing
- Further higher-flow equipment at Ellesmere Port
- Five additional compact sites delivered in a later phase
For your project: define how new sites join the existing access and reporting process. Cheshire West Recycling’s later phase added five compact installations within an agreed mobilisation window while extending the wider network.
Read the Cheshire West Recycling case studyPublic procurement, site access, environmental controls, data ownership, user administration and service continuity should all be defined in the project brief before equipment is selected.
Implementation approach
Define the records before the depot rollout.
Your site enquiry can include the departments, depots, fuel products and external user groups in scope, together with the vehicle and cost-centre records already used. Identify who maintains users and assets, corrects records and reviews reports. Include internal allocation requirements and the shift windows available for each phase of installation and training.
- Identify every department, depot, external user group and fuel product included in the project.
- Standardise vehicle, plant, user, cost-centre and service-area records before configuration.
- Agree who can create users, amend assets, correct transactions and access each type of report.
- Review cross-depot vehicle access and contractor arrangements with operational managers.
- Confirm any internal recharge, export or finance-data requirements before finalising fields.
- Plan a phased rollout and training process that accounts for different depot shifts and service teams.
Recommended next steps
Helpful answers
Sector questions answered.
Can several council departments use the same fuel point?
Yes. Users, vehicles and transactions can be organised by department, service area or cost centre so the shared infrastructure still produces attributable records.
Can contractors or partner organisations be included?
Approved external users can be configured within a separate group and given appropriate access. Commercial, governance and data responsibilities should be agreed before use.
Can road vehicles and plant be held in the same system?
Yes. Different asset types can be represented with suitable identifiers and reporting groups, including internal asset numbers where no registration is available.
Can fuel usage be exported for internal charging?
Fuel transaction data can support internal allocation and further processing. The exact export, integration and finance workflow should be confirmed during specification.
Can vehicles use more than one authority depot?
Yes, where multi-site permissions are configured to allow it. Each transaction can retain the site where fuel was issued.
Can existing council tanks and pumps be retained?
They may be reused when compatible, serviceable and suitable for controlled metering. Each depot requires an assessment before integration is confirmed.
Sector detail
Waste and recycling fleet operations
Returning fleets and changing users
Plan access around collection rounds, depot returns and shared vehicles. Review identifiers when drivers or assignments change, and define how non-road equipment is recorded.
Separate sites, comparable records
Agree site and product labels, stock responsibilities and reporting periods. The Cheshire West Recycling project provides a specific multi-tank example; its scope does not establish a standard site configuration.
