Blog

Site Fuel Authorisation Checklist for Fleets

A pump left available to everyone is not a convenience. It is an uncontrolled cost, a security exposure and a gap in your audit trail. This site fuel authorisation checklist helps fleet operators make every litre traceable to an approved person, vehicle, asset or job before dispensing begins.

For a depot, airport, contractor yard or mobile fuelling operation, authorisation is more than deciding who can use a pump. It defines what they can dispense, where, when and in what quantity. When those rules are connected to reliable transaction records, managers can investigate exceptions quickly rather than trying to reconstruct them from handwritten sheets at month end.

Why a site fuel authorisation checklist matters

Fuel loss is rarely one dramatic event. More often, it is a series of small, unchallenged variances: an unrecorded top-up, a shared access code, a vehicle filled outside its normal shift, or a pump used after an employee has left. Manual processes make these events difficult to see, particularly across several locations.

A clear authorisation process creates accountability at the point of dispense. It also protects legitimate operators. When a driver’s identity, vehicle and quantity are recorded automatically, they are not left answering for a discrepancy caused by someone else.

The right level of control depends on the operation. A small yard with a limited number of named drivers may need simple user permissions and daily review. A multi-site fleet or mobile fuel lorry operation may need location-specific access, vehicle matching, volume limits and instant removal of permissions. The principle is the same: access should be earned, specific and reviewable.

Site fuel authorisation checklist

Use this checklist when setting up a new fuel point, reviewing an existing process or bringing a mobile dispensing unit under control.

1. Define the assets that may receive fuel

Start with the equipment, not the people. Create a current register of every authorised vehicle, plant item, generator, aviation support asset or container that can be fuelled. Each asset should have a unique identifier that matches the identifier used in maintenance, operations and finance records.

Record the fuel type, tank capacity, normal consumption range and home location. These details give your team a baseline for spotting improbable transactions. A 250-litre dispense into a small van, for example, should trigger an immediate question rather than become another line in a spreadsheet.

Do not overlook temporary equipment. Hired plant, seasonal vehicles and contractor assets should be approved for a defined period, then removed when the work ends.

2. Build an authorisation hierarchy

Not every employee needs the same access. Set out who can approve users, amend limits, authorise exceptions and review reports. Keep these responsibilities separate where practical. The person requesting access should not be the only person able to grant it.

A useful structure may include fleet or operations management as system administrators, supervisors as requesters or approvers, and drivers or operators as dispensing users. Finance and senior management may need reporting access without pump access. This reduces the risk that a single shared login gives one person unchecked control.

For smaller teams, roles may overlap. If they do, compensate with a scheduled independent review of authorisations and transactions.

3. Verify the identity of every dispensing user

Shared keys, PINs and fobs defeat the purpose of access control because they make a transaction attributable to a group, not an individual. Each authorised user should have their own secure credential, ideally linked to a mobile phone-based authentication method or another unique identity factor.

Before access is issued, confirm the person’s employment or contractor status, licence or competency where relevant, supervisor approval and required fuelling safety training. Document the date access begins and the date it must be reviewed.

The process should work for shift patterns and poor connectivity without creating shortcuts. If an operator cannot be reliably identified, they should not be able to dispense without a documented emergency procedure and management follow-up.

4. Match users to the right assets and locations

A driver who operates municipal vehicles may have no reason to fuel a construction excavator. A mobile fuel operator may need access to a fuel lorry and approved customer sites, but not the depot’s bulk storage controls. Apply permissions by user, asset group, fuel type and location.

This is where centralised cloud control pays off. Permissions can be added or removed without travelling to each site or reprogramming separate pedestal systems. It is especially valuable when staff move between depots, contractors rotate through a project or a vehicle is reassigned.

Avoid making access too broad simply to reduce administration. A few minutes saved during setup can create months of uncertainty when an unexplained loss occurs.

5. Set sensible transaction limits

Authorisation should include limits, not just a yes-or-no decision. Set maximum litres per dispense based on tank capacity and operational need. You may also set daily, weekly or shift-based limits, depending on how fuel is issued.

Limits need judgement. A rigid cap can delay a legitimate night shift or emergency response, while no cap gives a compromised account too much freedom. Build an exception route for genuine operational needs, requiring a supervisor approval that is recorded against the transaction.

Review limits after route changes, seasonal workloads or fleet replacements. The capacity and expected usage of an electric-hybrid support vehicle will not match an older diesel lorry, and the control settings should reflect that.

6. Require the data needed to reconcile every dispense

A useful fuel transaction should answer basic questions without detective work: who dispensed, what asset received fuel, which pump or mobile unit was used, what fuel was issued, how much was issued, and when and where it happened.

Where your process requires it, capture odometer or hour-meter readings and job, cost centre or customer references. These fields are not administrative clutter. They connect fuel consumption to the work performed and make it easier to identify abnormal usage, maintenance concerns or incorrect allocation.

Automated cloud records are far more dependable than paper logs left in a cab or office. However, the data is only valuable if people know which fields are mandatory and why. Train operators to enter accurate readings, and give supervisors a process for correcting obvious errors without erasing the original audit trail.

7. Protect the physical fuel point

Digital authorisation controls the pump, but physical security still matters. Inspect tank access, hoses, nozzle holsters, cabinets, lighting and camera coverage where appropriate. Ensure emergency shut-offs are visible and tested in line with your safety procedures.

The pump should remain locked when no authorised transaction is underway. Consider how you will secure mobile units during stops, overnight parking and periods when they are left on customer premises. A strong policy cannot compensate for an unattended nozzle or poorly secured bulk tank.

8. Establish a clear exception and emergency process

There will be occasions when the normal path does not fit: a broken-down vehicle, a failed mobile phone, a storm response, a network issue or an urgent out-of-hours requirement. Plan for these events before they happen.

Specify who can authorise an emergency dispense, how the approval is recorded, what information must be captured manually and how quickly the transaction must be entered or reconciled afterwards. Emergency access should be time-limited and reviewed, not treated as a permanent workaround.

This is also the point to state what staff must do if they suspect theft, contamination, a meter discrepancy or unauthorised pump activity. Immediate reporting protects safety, evidence and inventory accuracy.

9. Review authorisations and exceptions on a schedule

Permissions are not a set-and-forget task. Review active users at least quarterly, and more often in high-turnover or high-risk operations. Check leavers, role changes, inactive accounts, contractor end dates and users with unusually broad access.

Transaction reporting should be reviewed against deliveries, tank levels, expected consumption and vehicle activity. Look for repeated round-number fills, dispensing outside normal hours, multiple fuel types assigned to one asset, unusual locations and volume patterns that exceed normal use.

A variance is not automatically theft. It may be a faulty gauge, a maintenance issue, a wrong asset selection or an incorrect delivery record. The benefit of good authorisation data is that your team can investigate facts rather than assumptions.

10. Test removal of access as carefully as approval

The fastest way to prove that your controls work is to test them. When an employee leaves, a contractor completes a job or a device is lost, confirm that access can be removed immediately and that the action is recorded. Test the process periodically rather than waiting for an incident.

Instant deauthorisation is particularly valuable across remote yards and mobile operations. It reduces the window in which an old credential, lost mobile phone or former employee can be used to access fuel.

Turn the checklist into a working control

A checklist is only useful when it becomes part of daily operations. Assign ownership for user approvals, exception reviews, tank reconciliation and periodic access audits. Make the process visible to drivers and supervisors so they understand that fuel accountability protects the fleet, the business and their own work record.

Manage Every Drop supports this approach by connecting authorised users to dispensing events through cloud-based controls and real-time transaction records. The goal is not to create more administration at the pump. It is to replace uncertainty, paper chasing and unmanaged access with practical evidence for every litre issued.

The best time to tighten authorisation is before a discrepancy becomes a loss you cannot explain. Start with one site, test the rules against real shifts and real vehicles, then apply the same disciplined control wherever fuel moves.