Fuel Tracking for General Contracting

Identify every way fuel is obtained: on-site tanks, slip tanks, fuel trucks, fuel cards at retail stations, and fuel bought in cans. Write these out so the policy covers each one explicitly.

For each source, define the data points that must be recorded (for example, date, equipment/vehicle ID, project, odometer or hour reading, number of gallons or liters, and who fueled). Keep the required fields consistent where possible.

Clarify who is responsible for logging fuel (operators, drivers, yard attendant), who checks logs for completeness (foreman or superintendent), who enters data into the system (office or equipment coordinator), and who reconciles with invoices (accounting).

Decide how to handle cases where fuel entries are missed or obviously wrong (for example, “If you forget to log a fill, notify your foreman immediately and complete a correction form”). Include simple correction procedures in the policy.

Define how quickly fuel logs must be completed (for example, immediately after fueling or by end of day) and what level of accuracy is expected (actual gallons from pump, not estimates).

Compile these decisions into a short written policy. Share it with field leaders, review it in safety or coordination meetings, and store it in an accessible location for future reference.

Decide for each fuel source whether logs will be paper-based (clipboards at tanks), digital (mobile forms, spreadsheets), or a mix. Consider the reality of the environment—some remote sites may still need paper.

Create a simple log form with columns for date, time, equipment/vehicle ID, project or cost code, odometer/hour reading, gallons/liters, fuel type, and person fueling. Keep the layout clear so entries are easy to read and enter later.

Work with whoever manages your software to ensure the system has fields that match your log (equipment ID, fuel quantity, cost, project code, etc.). This keeps data entry straightforward and consistent.

For on-site tanks, fuel trucks, and yard pumps, print enough log sheets and place them in weather-resistant clipboards or binders near the fueling point. Attach pens or markers so there’s no excuse not to fill them out.

If using digital logs, set up shared folders or form links and ensure all relevant staff have access. Provide simple instructions for how to open, complete, and save or submit entries.

Post a short sign at each fueling point that explains, in plain language, what must be recorded after every fueling and where the log or device is located.

From your fleet list, identify all items that consume fuel: on-road vehicles, off-road equipment, generators, welders, pumps, and any other fuel-powered tools. Include make, model, and serial or VIN.

Ensure each asset has a unique ID (asset number or vehicle number) that will be used consistently on fuel logs and in systems. If some items are missing IDs, create and label them clearly on the machine.

Obtain a list of all fuel cards from your fuel vendor(s), including card numbers, driver or vehicle assignments, and any PINs. Confirm no obsolete cards are still listed as active.

Decide whether cards are assigned to specific vehicles, general equipment, or specific drivers. Record these assignments in a simple register, noting which projects they are typically used on.

In your fleet or accounting system, enter or update records so fuel entries can be matched to the correct asset or driver/card. Make sure the same IDs appear on logs and vendor statements.

Identify cards that are no longer needed or are not linked to any active asset or driver. Cancel or deactivate these cards and document the changes to reduce risk of misuse.

Create a one- or two-page handout with screenshots or photos of the fuel log, examples of correctly completed entries, and a short explanation of why accurate fuel tracking is required.

Hold brief meetings with equipment operators, drivers, and yard staff to walk through the procedure. Show them the actual log location and demonstrate filling out an entry after a mock fueling.

For each field on the log, explain what should be written (for example, “Use the actual asset ID sticker on the machine, not a nickname”). Mention common errors such as missing project codes or illegible handwriting.

State clearly that fuel logs are part of the job: every fill must be logged, no exceptions. Explain who will review logs and what happens when patterns of missing or incorrect entries are found.

Allow time for operators and drivers to ask questions about special cases (night work, fueling another crew’s machine, etc.). Answer with specific examples so they feel confident handling these situations.

Plan to revisit fuel tracking procedures in future safety or coordination meetings, especially when staff turnover or new projects cause new people to handle fueling.

Right after fueling, the person fueling should go directly to the fuel log clipboard, tablet, or phone app associated with that fuel source (tank, truck, or card).

Write the correct asset ID and current project or cost code. If fueling a can or small tool, follow company rules for how these are logged (for example, “shop – general” or specific small-tool IDs).

Copy the date and time of the fueling, and the exact gallons or liters from the pump or meter. Avoid rounding more than necessary; use the values shown on the pump or meter.

Read the hour meter or odometer on the equipment or vehicle and record it on the log. This data later helps analyze fuel efficiency and confirms reasonable usage.

Include the initials or full name of the person who fueled, so questions can be routed correctly if something looks off later.

Before leaving, quickly check that all fields are filled in and can be read. Fix any unclear numbers or missing information immediately while the details are still fresh.

Decide how often fuel logs will be turned in (for example, weekly, bi-weekly, or at the end of each project phase). Communicate this schedule to all sites and yard staff.

Make each foreman or superintendent responsible for collecting logs from fueling points on their site and handing them in to the office or scanning them in, depending on your system.

Before submission, have the site lead quickly scan each log page for missing fields, obviously wrong quantities, or patterns of entries missing operator names or project codes.

If something is clearly wrong (for example, no equipment ID), ask the operator or person fueling to correct it before sending logs in. This is easier to fix while people still remember the fill.

Group logs by project and week (or your chosen period) and label them clearly with project name, date range, and site contact. This labeling helps the office process them quickly.

Send physical logs to the main office or scan and upload them to a shared digital folder. Notify the designated equipment or accounting person that new logs are ready for entry.

Decide the order in which you will process documents: logs first, then fuel card receipts, then vendor bulk-delivery invoices. Use the same sequence every cycle to stay organized.

For each line on a log, enter date, equipment ID, project code, gallons/liters, and any other required fields into your system. Double-check asset IDs and project codes against your master lists.

Apply the correct general ledger account (fuel) and job cost code (for example, “equipment fuel – project X” vs “yard fuel – overhead”) based on where and how the fuel was used.

If your system allows, attach scanned copies of the original logs or receipts to the digital entries. This makes future audits and investigations much easier.

After entering a batch, scan for entries with extremely high quantities or impossible combinations (for example, more gallons than a tank can hold). Flag these for follow-up before posting costs.

Once checked, post the fuel entries so they appear in job cost and equipment reports. Back up your data regularly according to company IT policies.

Collect fuel logs, fuel card receipts, and vendor invoices for the same period (for example, one month). Make sure you are comparing matching date ranges.

Compare total gallons and dollars on vendor invoices to the total gallons and costs from your logs and system entries. Note any large differences that cannot be explained by timing.

For each fuel card transaction on the vendor statement, look for a corresponding entry in your logs or system showing which asset or project used that fuel. Flag transactions without a matching internal record.

Contact site leads or cardholders to ask about missing logs or unusual transactions. Correct data entry errors where found, and if a transaction cannot be explained, escalate for further review.

If you find that the vendor invoice includes errors (for example, charged twice for a single fill), request corrections or credits. If internal entries are wrong, correct them in your system with proper notes.

Keep a short record of each reconciliation cycle, noting whether everything matched or what issues were found and resolved. Store this record with your fuel documentation for audit purposes.

Use your system to generate reports showing total fuel used by each asset over a period, along with hours or miles operated. Calculate simple fuel-per-hour or fuel-per-mile metrics where possible.

For each major equipment type, compare reported usage to what you would expect based on manufacturer data or past experience. Look for units using significantly more or less fuel than similar units.

Generate reports showing total fuel costs for each project and fuel cost as a percentage of project volume or equipment cost. Note jobs where fuel appears unusually high relative to others.

Highlight assets or projects with outlier fuel usage. Ask whether heavy usage was expected (for example, very heavy cycles) or whether this may indicate idling, poor operation, leaks, or mis-coded fuel.

Share your observations with superintendents, project managers, and maintenance. Ask for their input on causes and whether changes in operation, scheduling, or maintenance could reduce fuel use.

Agree on specific steps (training, maintenance checks, changes in fueling practices) and recheck fuel metrics in later periods to see if usage improves.

When reconciliation or monitoring flags unusual activity (for example, fueling at odd times, very large fills, or fuel purchased far from any project), record these transactions in a separate investigation log with details and dates.

Check that the suspicious entries are not simply data entry errors, duplicate imports, or timing differences. Compare vendor records, logs, and system entries carefully before assuming misuse.

Confirm that the fuel card or account used was assigned to the asset or person shown. Misassigned cards can make normal usage look suspicious; correct mappings where needed.

Privately ask the cardholder, operator, or supervisor to explain the transaction. Listen to their explanation and compare it to travel logs, job schedules, or other evidence.

If evidence strongly suggests fuel theft or card misuse and explanations do not resolve it, escalate to HR or management according to your disciplinary and investigation policies. Provide a clear summary of facts and documentation.

Based on what you learn, tighten controls such as card PIN rules, card limits, or tank access procedures. Document these changes in the fuel tracking policy and communicate them to all staff.

Choose a small set of metrics to report regularly, such as total fuel cost per month, fuel cost by project, top 10 fuel-using assets, and any flagged anomalies or investigations.

Create a standard report format (spreadsheet or slide) where you can plug in updated numbers each month or quarter. Keep it visual and easy to read for non-technical readers.

Pull updated data from your accounting and fleet systems on your reporting schedule and fill in the metrics, charts, and notes in the report template.

In the report, briefly explain notable trends: rising fuel costs on certain projects, improvements after training, or ongoing high usage in specific areas. Use plain language and concrete examples.

Based on what you see, suggest adjustments such as tightening card limits, changing tank locations, reinforcing idling policies, or adding PM for certain equipment. Be specific about what you recommend and why.

Share the report with operations and finance leadership in a regular meeting or via email. Store each report in a central folder so you can look back over time and see how fuel management has evolved.