Blog

Fuel Authorisation Rollout Example for Fleets

A missing 200 litres may look like a stock variance until someone has to explain it. A proper fuel authorisation rollout example shows how a fleet can replace assumptions, handwritten sheets and shared keys with a clear answer to every dispense: who took it, which vehicle or asset received it, when it happened and why it was permitted.

For a fleet operator, the rollout is not principally an IT project. It is a control project. The technology matters, but the outcome is operational accountability at the pump, without creating a slow or frustrating process for drivers, maintenance teams or mobile fuelling crews.

What a successful fuel authorisation rollout looks like

Consider a regional operator with a depot tank, 48 vehicles, six pieces of plant and a mobile fuelling unit. The business has reliable supply, but weak dispensing controls. The pump is available to anyone with a key, drivers record usage inconsistently, and the office reconciles fuel invoices against vehicle logs at month-end. By then, a discrepancy is difficult to investigate.

The operator decides to introduce smartphone-based pump authorisation and cloud transaction records. Its aim is straightforward: only approved people can dispense, every transaction is recorded immediately, and managers can see exceptions before they become recurring loss.

A good rollout does not begin by giving every employee access. It starts by defining the operating rules that the system will enforce. Which roles may dispense? Which fuel types can each role access? Must a vehicle, asset or job number be selected? Who can approve an emergency transaction? Who receives an alert when usage falls outside expected limits?

Those decisions turn a pump from an uncontrolled asset into a documented point of control.

Stage 1: map the real dispensing workflow

Before hardware is installed, the fleet manager walks through a normal shift at each dispensing point. This includes the main tank, any satellite site and the mobile unit. The purpose is to capture what really happens, rather than what a written procedure says should happen.

At the depot, a driver may arrive before the office opens. At a mobile unit, an operator may fuel plant across several jobs in poor weather and limited connectivity. A maintenance technician may need diesel for a workshop vehicle, while a contractor may occasionally require fuel under a chargeable arrangement. These are different use cases and should not all receive the same permission.

The team records the assets, users, tank capacities, pump types and fuel grades in scope. It also identifies the information needed at the point of dispense. For many fleets, a simple combination of authorised user, vehicle or asset ID, fuel type, quantity, date and location is enough to create a useful audit trail. Others need driver hours, job codes, cost centres or odometer readings to support deeper cost allocation.

There is a trade-off here. More required fields can improve reporting, but too many can delay drivers and encourage workarounds. Require information that will be reviewed and acted upon. If nobody uses a field, remove it from the workflow.

Set a baseline before controls go live

The operator should capture several weeks of current data where possible: delivered litres, tank dip readings, recorded dispenses, vehicle mileage or hours, and fuel card purchases. The figures may not reconcile perfectly – that is often the reason for the project – but they establish a benchmark.

This baseline helps management measure whether the rollout is reducing unexplained variance, improving transaction completeness and shortening reconciliation time. It also reveals operational issues that authorisation alone cannot solve, such as a faulty meter, a leaking line or inaccurate tank readings.

Stage 2: build permissions around roles, not convenience

The most common early mistake is granting broad access because it feels easier. It is easier for a week. After that, shared permissions make exception reviews almost meaningless.

In this rollout, access is assigned by role. Drivers can use diesel at their home depot and must select their allocated vehicle. Plant operators can access the mobile fuelling unit for specified equipment. Maintenance staff have a separate authorisation group with access to workshop fluids. Supervisors can approve exceptions, but approval activity is visible and reviewed.

Permissions should reflect the reality of the operation. A small fleet may only need three groups: drivers, supervisors and administrators. A multi-site operation may require site-based restrictions, fuel-grade controls, spending or volume thresholds, expiry dates for temporary staff, and different rules for company vehicles and customer-owned equipment.

With a system such as FluidSecure™, administrators can add or remove authorised users centrally rather than collecting keys, recoding fobs or waiting for a contractor to visit site. That matters when a driver leaves, a seasonal worker starts or a lost phone needs to be removed from the authorised user list quickly.

Plan for exceptions without weakening security

Every fleet has exceptions. A vehicle may return late with a near-empty tank. A hired lorry may need refuelling. A storm may take down local communications. The answer is not to leave the pump open permanently.

Document who can approve an exception, what evidence is required and how it is recorded. For example, an after-hours issue might require a supervisor approval, a vehicle registration and a short note explaining the reason. The next-day review then confirms whether the transaction was appropriate.

Security works best when people understand that it supports uptime as well as loss prevention. A well-designed exception process keeps vehicles moving while preserving accountability.

Stage 3: install, test and pilot before full release

Installation should be scheduled around the fleet’s working pattern, not merely the contractor’s availability. If the depot has a narrow overnight fuelling window, testing must prove that the new process works during that period.

The pilot group should include experienced drivers, a supervisor, a maintenance representative and at least one person who is less comfortable with new technology. This is deliberate. If the process works only for the most confident users, it is not ready for full deployment.

During a one- or two-week pilot, the project team tests normal and abnormal situations: authorised dispensing, declined requests, wrong fuel selection, a missing vehicle ID, temporary user access, mobile fuelling activity and supervisor overrides. Each test should confirm both the physical result at the pump and the transaction record in the cloud dashboard.

The team also checks whether reports are usable. Can the controller quickly compare dispensed litres against deliveries and tank inventory? Can the operations manager identify fuel issued outside normal hours? Can a supervisor see repeated declines that may indicate a training problem or an attempted policy breach?

A rollout is ready to expand when the answers are clear, not simply when the equipment has been fitted.

Stage 4: train for the moment at the pump

Training should be brief, practical and delivered where people work. A five-minute demonstration beside the pump is often more effective than a lengthy slide deck. Users need to know how to request authorisation, enter the required details, respond to a declined transaction and contact support if something does not work.

Managers need different training. They should know how to add and deactivate users, review transactions, investigate exceptions and run the reports that support reconciliation. Finance teams should understand when data becomes available and how it maps to their existing month-end process.

Do not position the change as surveillance. Be direct: the business is protecting fuel, reducing manual paperwork and making sure honest employees are not left explaining someone else’s unexplained usage. Clear communication reduces resistance and makes policy enforcement more consistent.

Stage 5: review the first 30 days and tighten the controls

The first month after go-live is where value becomes visible. The fleet manager reviews transaction completion, declined attempts, after-hours activity, unusual quantities and fuel-to-mileage or fuel-to-hours patterns. The controller compares physical inventory, supplier deliveries and authorised dispenses more frequently than before.

A small number of declined requests is not necessarily a problem. It may show that the controls are working. Repeated declines for the same person or vehicle deserve attention: perhaps the user was not correctly assigned, the asset list is outdated, or the request falls outside policy.

The operator in this example finds that several drivers were using generic asset descriptions, which made reporting less useful. The fix is simple: clean the asset register, require a valid vehicle selection and coach drivers during shift handover. It also discovers that weekend diesel usage was higher than expected. The transaction history shows it relates to a legitimate Saturday route, so the manager adjusts the authorised schedule rather than treating it as a loss event.

That is the point of real-time records. They allow teams to investigate facts, improve the process and avoid both blind trust and false accusations.

What this rollout changes for the business

Once the process is established, the fleet has more than a locked pump. It has a dependable chain of accountability from authorisation to dispense record to reconciliation. Finance spends less time chasing paper logs. Operations can act on unusual activity while details are still fresh. Managers can remove access immediately when roles change, rather than hoping keys and cards are returned.

The financial return depends on the starting point. A tightly managed small depot may see the largest benefit in saved administration and simpler reporting. A dispersed fleet with open access, mobile fuel units or recurring inventory variances may see faster loss reduction. In either case, the strongest results come from matching the controls to the actual operation, then reviewing the data often enough to act on it.

Start with one site, one clear policy and a pilot group that will give honest feedback. Once every litre has an authorised user and a time-stamped record behind it, better fuel decisions become part of the daily routine.