Fuel Cards for Construction Companies: A Practical Guide

Construction and civil businesses have a fuel management problem that most other fleets don't: fuel needs to be tracked not just by vehicle, but by job. A ute, an excavator and a generator on the same site might all draw fuel that needs to land against the correct project code for accurate job costing. This guide covers how fuel cards can be structured to solve that problem, along with the plant, jerry can and subcontractor issues specific to construction and civil fleets.

Why construction fuel management is harder than standard fleet fuel

Most fleet fuel guidance assumes a simple model: vehicle buys fuel, cost goes against that vehicle, done. Construction and civil operations layer several complications on top:

• Multiple cost centres per vehicle. A truck or ute might work across two or three different job sites in a single week, and fuel cost needs to be allocated proportionally or at least trackable by date and location.
• Plant and equipment that doesn't have a registration plate. Excavators, generators, compressors, light towers and pumps all consume fuel but aren't part of a standard vehicle-based card program by default.
• Subcontractors and hired plant operating under your project but not your direct payroll, raising the question of who controls their fuel spend and how it's tracked back to the job.
• Project-based margins, where fuel is a direct cost that needs to hit the right job in the accounting system for the project to show accurate profitability — not just a fleet-wide overhead figure.

Job costing by site: getting fuel cost to the right project

Accurate job costing depends on being able to answer: how much fuel did Project X actually consume, separate from Project Y and separate from general overhead running. Fuel card programs help with this in a few ways:

• Card-per-vehicle allocation with location data. Even without site-level card allocation, transaction location and time data lets you map fuel purchases back to which job a vehicle was likely working on that day.
• Card-per-site or card-per-plant-item, where practical, gives a direct read on site-level fuel cost without needing to infer from vehicle movement.
• Reference or job number fields at the point of transaction (where supported) let drivers or operators tag a fuel purchase to a job code directly.
• Reporting exports that integrate with job costing or accounting software reduce the manual re-keying that otherwise eats admin time and introduces errors.

A practical allocation approach

For businesses without a fully integrated system, a workable middle ground is:

1. Assign cards to vehicles and, where volume justifies it, to major static plant.
2. Require drivers/operators to log the job site against each fill (a simple app, text-based log, or paper docket if that's what's already in use).
3. Reconcile the card statement against the site log monthly, allocating cost to job codes.
4. Flag any transaction that doesn't have a matching job entry for follow-up.

This isn't a perfect real-time system, but it's a substantial improvement on lumping all fuel into a single "plant and fuel" overhead line, which tells you nothing about which jobs are actually profitable.

Plant and equipment refuelling

Diesel plant and equipment — excavators, skid steers, generators, light towers, compressors, water pumps — represents a significant and sometimes under-tracked share of fuel spend on civil and construction sites. Two common refuelling models:

• Mobile refuelling (fuel truck or trailer to site), common on larger sites where moving plant to a fuel point isn't practical. This usually runs on a bulk fuel account rather than a card, since the fuel truck itself is the point of purchase.
• Card-based refuelling for plant with jerry cans or portable tanks, common on smaller or shorter-duration sites where a card purchase at a nearby site is more practical than arranging bulk delivery.

Whichever model you use, the same tracking principle applies: fuel drawn for plant needs to be attributed to the job the plant is working on, not left as an unallocated cost.

Jerry can and bulk fuel policy

Jerry cans are common on construction sites for topping up small plant or as an emergency backup, but they come with control and compliance risks worth managing deliberately:

• Storage and transport compliance. Dangerous goods rules apply to diesel and petrol storage and transport, including on vehicles and utes carrying jerry cans between sites. Check current requirements for your state and quantities rather than assuming ute-tray storage is unrestricted.
• Reconciliation difficulty. A jerry can purchase on a fuel card looks the same as a vehicle fill unless it's specifically logged — which means jerry can fuel is one of the easiest categories to lose track of in job costing.
• Theft and misuse risk. Jerry cans are also one of the easier fuel purchase types to misuse, since there's no vehicle odometer or plant meter to sanity-check the volume against.

A simple written jerry can policy — who can authorise a jerry can purchase, what it must be logged against, and a volume threshold that triggers a review — closes most of this gap without heavy administration.

Subcontractor cards and project-level control

Where subcontractors work under your project and you're supplying or reimbursing their fuel, a few structural questions need answering upfront:

• Do subcontractors get their own cards on your account, or do they invoice you separately for fuel? Issuing cards gives you direct visibility and control but adds administrative overhead and requires clear terms on spend limits and accepted fuel types.
• What spend limits and site restrictions apply? Card programs typically allow per-card limits and, depending on the product, restrictions on fuel type or purchase categories — useful for limiting subcontractor cards to diesel only, for example.
• How is subcontractor fuel reconciled against the job? The same job-code discipline described above applies, arguably more so, since subcontractor fuel sitting unallocated is harder to query after the fact once the sub has moved off-site.
• What happens when a subcontractor leaves the project? Cards need to be able to be paused or cancelled quickly, not just left active until someone notices.

Getting this structure right at the start of a project avoids a messy reconciliation exercise at project close-out, when subcontractor fuel spend is hardest to trace back to the correct job.

Project-level reporting: what to ask a fuel card provider for

Not all fuel card programs report at the level construction and civil businesses need. When evaluating a provider, ask specifically about:

Reporting need	Why it matters for construction/civil
Transaction-level location and time data	Lets you map fuel to likely job site even without direct job coding
Custom reference/job code fields	Direct allocation to project at point of sale, where supported
Per-card and per-site spend limits	Controls subcontractor and plant fuel exposure
Exportable reporting (CSV or accounting integration)	Reduces manual re-keying into job costing systems
Consolidated invoicing across vehicle and plant cards	One statement to reconcile instead of several
Odometer/meter capture at transaction	Sanity-checks volume against expected usage, flags anomalies

FuelPoint works with construction and civil fleets on setting up exactly this kind of structure — as an authorised Shell Card Sales Agent for Viva Energy Australia, we help fleets configure card allocation, limits and reporting to match how their projects are actually costed, rather than a generic one-size-fits-all setup.

Putting it together: a fuel structure for a multi-site construction business

A practical structure for a mid-size construction or civil business running several concurrent jobs might look like:

1. Fleet vehicles (utes, trucks) on individual cards with location/time reporting, reconciled monthly against job site logs.
2. Static plant on a mobile refuelling/bulk arrangement if volume justifies it, or card-based jerry can top-ups under a documented policy for smaller sites.
3. Subcontractor cards issued per project with capped limits and a defined cancellation process at project end.
4. Monthly reconciliation allocating all fuel — vehicle, plant, jerry can, subcontractor — against job codes, with exceptions flagged for follow-up.
5. Quarterly review of the overall program: is the reporting still matching how jobs are actually run, and are limits still appropriate as project mix changes?

This structure builds on the general principles in how to reduce fleet fuel costs and the broader fuel card fundamentals covered in fuel cards for business in Australia, applied specifically to project-based cost tracking.

Worked example: allocating a week of mixed fuel spend

To illustrate the allocation approach in practice, consider a civil contractor running two utes, one water truck and a generator across two active job sites in a single week.

Fuel purchase	Vehicle/plant	Job indicated by log	Allocation outcome
Monday fill, Site A servo	Ute 1	Site A (log entry matches)	Allocated directly to Site A
Tuesday fill, Site B servo	Water truck	Site B (log entry matches)	Allocated directly to Site B
Wednesday fill, no log entry	Ute 2	Not logged	Flagged for follow-up — driver contacted to confirm job
Thursday jerry can purchase	Generator (Site A)	Logged against Site A under jerry can policy	Allocated to Site A
Friday fill, Site A servo	Ute 1	Site A (log entry matches)	Allocated directly to Site A

The single flagged transaction (Wednesday) is resolved by contacting the driver before month-end reconciliation, rather than left unallocated in a general overhead line. Across a full month and a larger fleet, this kind of simple exception-based review — rather than attempting to trace every transaction from scratch — is usually enough to get job costing accuracy to a workable level without heavy administrative overhead.

Setting up cost centres and job codes in your fuel account

Where your fuel card provider supports reference or cost-centre fields, setting these up correctly at account level makes ongoing allocation far less manual:

1. Define a consistent job code format that matches your accounting or job costing system, so exports can be matched without manual re-keying.
2. Set default cost centres per card where a vehicle or piece of plant works predominantly on one job, so most transactions are pre-allocated.
3. Use a "general/overhead" code sparingly — for depot running or genuinely shared use — rather than as a default fallback for anything not immediately clear, which defeats the purpose of job-level tracking.
4. Review code usage monthly, checking for a growing "general" balance that might indicate drivers aren't logging jobs consistently.
5. Retire job codes promptly once a project closes, so historical reporting stays clean and new transactions can't be misallocated to a finished job.

Seasonal and project-cycle considerations

Construction and civil fuel spend isn't steady across the year. Wet weather shutdowns, project mobilisation and demobilisation phases, and seasonal peaks in civil works all affect both volume and where fuel is being drawn:

• Mobilisation phases often show a spike in light vehicle and generator fuel use as a site is set up, before heavier plant use ramps up.
• Wet weather or shutdown periods can leave static plant idle but still requiring occasional fuel for maintenance running — worth flagging separately from active production fuel use so job costing isn't distorted.
• Demobilisation typically sees a final cluster of fuel transactions as plant and vehicles are moved off-site, which should still be allocated to the closing project rather than left to land in the following month's general account.

Building these patterns into your monthly reconciliation expectations avoids treating a normal seasonal fluctuation as an unexplained variance.

Comparing card-based and bulk fuel costs for plant

Where a project could reasonably use either card-based refuelling or a bulk/mobile delivery arrangement for plant, a simple cost comparison is worth running before defaulting to whichever was used last time:

Consideration	Card-based (jerry can or ute-mounted tank)	Bulk/mobile delivery
Setup effort	Minimal — uses existing card program	Requires supplier arrangement and site access
Cost efficiency at low volume	Generally more efficient for smaller, shorter jobs	Less efficient unless volume justifies a delivery
Cost efficiency at high volume	Higher per-litre cost and more admin at scale	Generally more efficient for sustained high-volume use
Compliance overhead	Dangerous goods rules apply to storage/transport	Compliance sits mostly with supplier delivery process
Site duration fit	Better for short or intermittent jobs	Better for longer-running, higher-volume sites

Running this comparison per project — rather than assuming one method for every job regardless of size or duration — typically produces a better cost outcome across a mixed project portfolio.

Checklist before starting a new project's fuel setup

1. Confirm which vehicles and plant will be on-site and their expected duration.
2. Decide card-based versus bulk/mobile refuelling for each plant item based on volume and duration.
3. Set up or confirm the job code for the project in your fuel account.
4. Brief drivers and operators on job logging requirements before the first fill.
5. Confirm subcontractor fuel arrangements (cards, invoicing, or a mix) before they mobilise.
6. Set a reconciliation cadence for the project — weekly for large or fast-moving jobs, monthly for smaller ones.
7. Document a cancellation trigger for subcontractor cards tied to project completion or the sub leaving site.

Working through this list at project kickoff, rather than retrofitting fuel tracking once a job is underway, is generally what separates construction businesses with reliable job costing from those still working off an estimate at project close-out.

Frequently asked questions

Can fuel cards track fuel by job site, not just by vehicle?

Fuel cards don't automatically know which job a vehicle is working on, but transaction location and time data, combined with a job reference field where supported and a driver logging process, lets you allocate fuel cost to specific projects with reasonable accuracy.

Should plant and equipment be on a fuel card or bulk fuel account?

It depends on volume and site duration. High-volume static plant on a long-running site often suits bulk/mobile refuelling, while smaller or shorter-duration sites are often more practically served by card-based purchases.

How do we control subcontractor fuel spend on a project?

Options include issuing subcontractors their own cards with capped limits and defined fuel types, or requiring them to invoice fuel separately with documentation. Cards give more direct visibility but require a clear cancellation process when the subcontractor leaves the project.

Are jerry cans a compliance risk on construction sites?

Storing and transporting fuel in jerry cans is subject to dangerous goods rules that vary by quantity and jurisdiction. It's worth confirming current requirements for your state and building a simple written policy covering authorisation, logging and volume limits.

What reporting should we ask a fuel card provider for if we do job costing?

At minimum, transaction-level location and time data, exportable reporting, and — where available — custom reference or job code fields at the point of sale. This is the difference between fuel showing up as an overhead line and fuel showing up correctly against project profitability.

Is it worth setting up job-level fuel tracking for a smaller construction business?

Even without a fully integrated system, a basic version — cards per vehicle, a simple site log, and monthly reconciliation — gives meaningfully better job costing accuracy than an unallocated fuel overhead line, and it scales as the business grows.

How do we handle fuel cost allocation when a vehicle works across multiple jobs in one day?

Where the fuel card doesn't support direct job coding, use transaction time and location data alongside a simple driver log to split cost proportionally, or allocate to the job the vehicle was on for the majority of that day if a precise split isn't practical.

Should a new construction business set up job-level fuel tracking from day one?

Yes, even a basic version — cards per vehicle and a simple site log — is easier to establish early than to retrofit once several projects' worth of unallocated fuel history has already built up.

To set up fuel cards structured around how your projects are actually costed, book a 15-minute fuel spend review with FuelPoint, or check the calculator at [/#calculator] for an indicative view of your fleet's fuel spend.