The full tour
Everything a fuel log should have been
Built around one constraint the office tools ignore: the work happens where the signal isn't.
Offline-first logging
Fuel Relay assumes you have no signal, because most nights you don't. Every entry saves to the device instantly and joins a sync queue; the app is fully usable for an entire hitch without a single bar.
When coverage returns, at camp Wi-Fi, on a ridge line, or in town, the queue drains automatically with retry backoff, and conflicts resolve without losing a gallon.
- Log a full shift with zero bars
- Entries queue on the device and sync when coverage returns
- Retry backoff that survives one-bar, in-and-out coverage
- Conflict resolution that never drops an entry
Voice entry
Tap the mic on any field and say it: "4512" for the unit, "H Pad" for the location, "98" for gallons. The recognizer is biased toward the units, pads and contractors that fueler has logged before, so "Vantex" lands as Vantex. It holds up over a running pump.
Everything lands in the form first, not the log, so the fueler reviews and corrects before saving. Gloves stay on.
- A mic on every field: unit, location, contractor, gallons
- Text fields match the fueler's own history, so names stay consistent
- Voice fills the form for review before it saves
Auto-suggest from your own history
The units, locations, and contractors a fueler serves barely change week to week. Start typing and Fuel Relay offers the units, locations and contractors that fueler has logged before, learned on the device, never from someone else's data. Entry number forty of the night takes three taps, not thirty keystrokes.
- Unit numbers, locations, and contractors learned per fueler
- Suggestions from the last 50 values that fueler has logged per field
- Works fully offline, with history stored on the device
Smart shift defaults
Start the shift once and the app carries the context: fuel type per entry, the truck you're running, and your starting fuel load. Fuel-remaining math updates with every entry so the fueler always knows what's left on the truck. Multi-truck crews can switch trucks mid-shift without losing the numbers.
- Per-entry fuel type with a shift-level default
- Starting fuel load and live fuel-remaining calculation
Status workflow with clear ownership
Every log moves through an explicit state machine: draft while the fueler works, submitted when the shift ends, then reviewed, or flagged with a note that sends it back. At any moment it's obvious whose move it is, and the transition history is preserved, so month-end never turns into archaeology.
- Draft → submitted → reviewed / flagged → resubmitted
- Flag notes tell the fueler exactly what to fix
- Every transition recorded in the audit trail
Contractor totals, invoice-ready
The point of the log is the invoice. Fuel Relay aggregates gallons by contractor across any date range, and normalizes name variants case-insensitively: Vantex, VANTEX, and vantex are one Vantex, not three line items. Pick the range, export, and attach it to the invoice. Billing that used to take an afternoon takes a minute.
- Gallons aggregated by contractor over any range
- Case-insensitive contractor normalization
PDF, CSV & Excel exports
Every report exports the way your back office wants it: a clean, brandable PDF for the invoice attachment, CSV for the accounting import, Excel for the analyst who wants to pivot. Layout sizes are configurable, the numbers are identical across all three, and the export reflects exactly what was reviewed.
- One report, three formats, identical totals
- Brandable PDF with your logo and color
- Ready to attach to the invoice as-is
Admin live feed
Shifts appear on the dashboard the moment fuelers submit them. No refresh, no chasing. Each card shows the fueler, the truck, contractor totals, and the log's status; review or flag with one tap and the fueler sees it on their next sync. You are looking at tonight's numbers tonight, not reconstructing them three weeks later.
- Real-time updates as logs are submitted
- One-tap review or flag from the feed
- Fuelers see status changes on their next sync
Twenty languages, one crew
Crews aren't monolingual and the app shouldn't be either. The entire mobile experience is localized in twenty languages, including Spanish, Hindi and Bengali, and voice entry follows the language each fueler picks. The admin still gets one consistent, English-normalized report.
- Full app localization in twenty languages
- Voice entry follows the fueler's language
- Reports stay consistent for the admin
Security that holds up
Field data is billing data, so it's treated that way: TLS on every connection, encryption at rest, row-level security scoping every query, and an append-only audit log covering every entry, edit, review, and device reset.
- TLS in transit, encrypted at rest
- Row-level security on every table
- Append-only audit log, every entry and edit timestamped