Blog

Multi-Site Fuel Governance Guide for Fleets

A fuel variance at one depot is frustrating. The same variance repeated across six depots, two mobile fuel units and multiple shifts becomes a governance problem. This multi site fuel governance guide is built for fleet leaders who need to know who dispensed fuel, into which asset, at what time, and why every litre is accounted for.

The challenge is not simply buying fuel at the right price. It is maintaining control after delivery, when stock moves from a tank into vehicles, plant or portable equipment. Without consistent controls, each site can develop its own workarounds: shared keys, handwritten logs, delayed meter readings and permissions that remain active long after an employee or contractor has left.

Good fuel governance replaces these gaps with a standard operating model. It gives operations, finance and maintenance teams the same dependable record of every dispense event, wherever it happens.

What fuel governance means across multiple sites

Fuel governance is the set of rules, responsibilities and records that control how fuel is received, stored, issued, measured and reconciled. At a single location, a supervisor may be able to oversee the process informally. Across a network, informal control does not scale.

Each depot may have different tank sizes, operating hours, vehicle types and staffing arrangements. Mobile fuel units add another layer of complexity because the point of dispensing travels between yards, worksites and customer locations. Governance creates a common baseline without forcing every site into an impractical one-size-fits-all process.

The objective is straightforward: only authorised people should be able to dispense, each transaction should identify the user and asset, and the records should support prompt stock reconciliation. When these controls are in place, fuel becomes a managed inventory rather than an uncontrolled operating cost.

Start with one policy, then set site-level rules

A central fuel policy should define the controls that cannot vary by location. This includes who can authorise users, which information must be captured at dispensing, how frequently tanks are reconciled, how discrepancies are investigated and who receives exception reports.

Local managers still need room to address practical conditions. An airport operation with 24-hour access requirements will not operate exactly like a regional lorry depot. A mobile fuelling crew may need a different approval workflow from a fixed tank. The standard should therefore set the required outcome, while allowing the local process to fit the site.

Define ownership before installing technology

Technology records transactions, but people remain accountable for acting on them. Assign a central programme owner, usually a fleet, operations or finance leader, with responsibility for the governance standard and reporting cadence. Each location should also have a named site owner responsible for physical stock, tank condition and local adherence.

Finance should own the reconciliation review or have clear visibility of it. Maintenance should be involved where fuel use can expose an asset issue, such as excessive idling, unauthorised use or a failing fuel system. Security and health and safety teams may also need defined roles, particularly where access rules affect contractors and hazardous-area procedures.

When everyone owns fuel, no one owns it. Named responsibilities make it clear who investigates a variance and who has authority to close it.

Control access at the pump, not after the fact

Paper logs and shared fobs create records that are easy to miss, alter or complete later from memory. They also leave the pump available to anyone who has physical access to the yard. That is not a control system. It is a request for good behaviour.

A stronger model requires user authorisation before a pump can dispense. The transaction should capture the user identity, date and time, vehicle or equipment identifier, fuel type and volume issued. Where relevant, odometer or engine-hour readings add another useful layer of control because they connect fuel consumption to asset activity.

Smartphone-based authorisation is particularly effective for dispersed fleets. Permissions can be granted, changed or removed centrally without collecting keys or visiting every depot. If a driver changes role, a contractor finishes work or a handset is lost, access can be removed immediately rather than waiting for a site manager to update a local system.

This does not mean every employee requires the same access. A good permission structure distinguishes between users who fuel a specific vehicle, supervisors who approve exceptions, maintenance personnel who fuel equipment and administrators who manage records. Restrict fuel types and access windows where operationally appropriate. The principle is least privilege: give each person the access they need, and no more.

Make every dispense transaction usable in a reconciliation

Capturing data is only valuable if the data can answer practical questions. Can you compare tank stock against recorded issues? Can you identify a transaction with no vehicle assignment? Can you see whether a unit was fuelled twice in an unusual period?

For each dispense, require the details needed to support both operations and finance. At minimum, record the authorised user, asset, location, product, quantity and timestamp. Add mileage or hours where it is realistic and reliable to collect. For mobile fuel units, record the dispensing vehicle or unit as well as the receiving asset so fuel remains traceable through the full chain of custody.

Avoid making data entry so burdensome that users bypass it. The right balance depends on the fleet. A high-throughput depot may prioritise fast user and vehicle identification, while a specialist plant operation may justify additional job, project or customer fields. Test the workflow with the people who fuel vehicles in rain, darkness and shift-change pressure, not only with office staff.

Reconcile stock on a fixed rhythm

The central reconciliation question is simple: does physical stock reasonably match deliveries, recorded issues and known adjustments? The process is not always perfectly exact. Temperature, tank geometry, measurement methods and timing can all create small differences. What matters is setting an acceptable tolerance and investigating recurring or material exceptions.

A practical multi-site process usually combines daily transaction review with scheduled physical stock checks. High-volume sites may need daily dip or gauge readings. Lower-volume locations may reconcile weekly, provided they are secure and variances remain within tolerance. Fuel delivery records should be entered or imported promptly, not held until month end.

Use the same variance calculation and reporting format across the estate. If one site reports litres issued and another reports monetary value only, central oversight becomes slow and unreliable. Standardisation also helps identify which locations need support rather than judgement.

Investigate exceptions quickly

A variance is a signal, not automatic proof of theft. It may result from an unrecorded delivery, an incorrect tank reading, a meter issue, unauthorised dispensing or a data-entry error. Start with the transaction record, delivery documentation and physical measurement. Then check for unusual activity, such as repeated fuelling outside normal shifts, unknown asset identifiers or volumes that do not match tank capacity.

Speed matters. A discrepancy discovered six weeks later is harder to explain and almost impossible to correct. Establish an escalation threshold and response time for every site. Small, repeated losses deserve attention too. They often reveal weak access practices before the financial impact becomes significant.

Use central reporting to compare sites fairly

Multi-site governance should make performance visible without drowning managers in reports. A central dashboard should show fuel received, fuel issued, current stock, variance, transactions by user and asset, and exceptions requiring follow-up. Managers should be able to move from a network view to a specific transaction without requesting spreadsheets from each depot.

Comparison needs context. A site with more idling equipment, colder weather or longer yard movements may use more fuel than another. Review consumption alongside operating activity, mileage, engine hours, route type and fleet mix. Governance is not about penalising a site for legitimate use. It is about separating legitimate use from unexplained loss.

Trend reporting is often more valuable than a single monthly figure. A gradual increase in fuel per kilometre, repeated out-of-hours dispensing or a tank variance that creeps upwards can identify a problem early. The best reports prompt a conversation and an action, rather than becoming another document filed away at month end.

Choose technology that works at every location

Legacy pedestal-based systems can deliver control, but they may be expensive to install, difficult to maintain and impractical for mobile dispensing. For many fleets, the better approach is a rugged, cloud-connected system that secures the pump, authorises users by smartphone and creates an auditable transaction at the point of issue.

Manage Every Drop supports this model with FluidSecure™, helping fleets apply central permissions and consistent transaction capture across fixed tanks and mobile fuel units. The value is not merely the hardware. It is the ability to establish a common control standard while reducing the maintenance burden associated with complex, site-specific infrastructure.

Before selecting a system, examine the conditions it must handle. Consider poor mobile coverage, outdoor temperatures, hazardous-area requirements, existing pumps, mobile unit layouts and the information your finance team needs for reconciliation. Ask how authorisations are removed, how data is retained when connectivity drops, and how quickly support is available when a pump is critical to operations.

Treat governance as an operating discipline

Fuel controls weaken when they are introduced as a one-time project. New drivers join, assets move between depots, tanks are replaced and local shortcuts reappear. Review access permissions regularly, train users on the reason for the process and refresh site procedures after operational changes.

A quarterly governance review is often enough to assess recurring variances, inactive users, missing asset data, local exceptions and required improvements. Larger or higher-risk operations may benefit from a monthly review. Keep the meeting focused on evidence and corrective action, not blame.

The most useful first step is to map one fuel journey from delivery to vehicle across every site. Where the chain of custody breaks, your next control is clear.