Timesheet and Payroll Software for NDT Field Crews: FIFO, Per Diem, and Multi-State Rules

A four-person UT and RT crew rolls into a refinery turnaround outside Port Arthur on a Sunday night. Two techs are two weeks into a 21/7 rotation out of Beaumont, one drove in from a pipeline integrity job in Oklahoma, and the fourth just came off a 14/14 hitch on an offshore platform in the Gulf. By the time the office runs payroll for that period, someone is reconstructing per diem days from a paper log, guessing which state gets withholding for which day, and hoping the six hours spent waiting on a permit-to-work Tuesday morning don't turn into a wage claim eight months from now. This is an ordinary week for most NDT service companies running traveling field crews — one that generic payroll software was never built to handle.

Standard payroll platforms assume an employee who clocks in at one location, in one state, on a predictable weekly schedule. NDT field crews break every one of those assumptions at once: technicians rotate on fly-in/fly-out schedules, cross state lines mid-pay-period, work on federally funded projects that trigger certified payroll reporting, and log hours from locations with no cell signal. Getting it wrong creates exposure under the Fair Labor Standards Act, state departments of revenue, and, on Davis-Bacon work, the Department of Labor — one of the areas where purpose-built NDT ERP software earns its keep over a generic timesheet app or a spreadsheet.

FIFO Rotations: Tracking On-Rotation, Off-Rotation, Travel, and Standby Days

Fly-in/fly-out and drive-in/drive-out rotational scheduling is standard on offshore platforms, remote pipeline right-of-way work, and turnaround-heavy refinery sites, where housing a crew locally for the full project is impractical. Common patterns include 14/14, 21/7, 28/14, and shorter 7/7 rotations, each reshaping a pay period in ways flat hourly timesheets don't naturally capture.

The complexity isn't the on-rotation hours themselves — those are usually straightforward hourly or per diem-supplemented time. It's everything adjacent to them:

• Travel days. A technician flying to a heliport for a platform changeover, or driving six hours to a remote compressor station, may or may not be compensable depending on the hour it falls in and whether work is required during it — a distinction the FLSA treats specifically.
• Standby and waiting-on-weather time. Offshore work routinely stalls for weather holds, fog delays, or a platform on lockdown. Whether that time is paid depends on whether the technician is free to use it personally or must stay ready to work — "engaged to wait" versus "waiting to be engaged."
• Off-rotation and rotation-boundary days. Off-rotation time is unpaid by default, but easy to mis-bill against per diem or mis-accrue against overtime averaging if the system doesn't separate rotation cycles from calendar pay periods — and because a 14/14 cycle rarely aligns with a biweekly calendar, a pay period often spans the tail of one hitch and the start of the next.

A spreadsheet can technically hold all of this, but it can't enforce it — nothing stops a coded travel day from silently becoming a full workday, or a weather hold from disappearing because nobody logged it. Timesheet software built around rotation patterns lets a schedule template define the rotation up front and keeps travel, standby, and worked time as distinct, auditable categories rather than one undifferentiated "hours" column.

Per Diem: Tax Home, GSA Rate Tables, and the Paper Trail That Protects Everyone

Per diem is where NDT payroll intersects most directly with federal tax law, and it's where money quietly leaks — either to the IRS through under-substantiated reimbursements getting reclassified as wages, or to the company through per diem paid on days that shouldn't have qualified. The governing concept is "tax home" under Internal Revenue Code Section 162(a)(2): an employee can only receive tax-free per diem while traveling "away from home" for business. Tax home generally means the area of the employee's regular or main place of business, not a personal residence — which matters for a workforce dispatched out of a shop or yard in one town while living in another.

Two conditions tend to break the tax-free treatment for NDT crews specifically. An assignment expected to last, or that actually lasts, beyond roughly a year at one location is generally treated as indefinite rather than temporary, shifting the tax home itself to that location, at which point per diem for it becomes taxable wages. And a technician with no regular main place of business and no regular place of abode — an itinerant, in IRS terms — has no tax home to travel away from, so per diem paid is taxable regardless of distance traveled. Neither is an edge case: a technician bouncing between six-week turnaround assignments with no fixed home shop hits the first trigger; one parked past a year on a single long-duration contract hits the second.

The common reference point for reimbursement is the General Services Administration's per diem rate tables, published annually by locality for lodging and a combined meals-and-incidentals rate. Private employers aren't required to use GSA rates, but most NDT companies anchor their policy to them because it lines up with the IRS's accountable-plan and substantiation guidance, published periodically through Revenue Procedures — a far simpler audit position than an employer-invented flat rate that revises on its own schedule and needs refreshing every cycle, not hardcoded once and forgotten.

The recordkeeping burden is what most shops underestimate. To qualify as tax-free under an accountable plan, an expense needs a business connection, substantiation within a reasonable time, and return of any excess over the allowance. For a technician relocating between job sites every one to three weeks, the system has to track, day by day, which locality's rate applied, whether lodging was employer-provided or self-paid, and travel days versus full site days — reconstructed months later from memory, that's exactly how per diem ends up requalified as wages during a payroll tax audit.

Multi-State Withholding When the Crew Truck Crosses a State Line

A technician based out of a Houston shop works a turnaround in Baton Rouge one month and a pipeline job near Cushing, Oklahoma the next. Texas has no state personal income tax, so the home-state side is simple — but Louisiana and Oklahoma both do, and both generally require withholding on wages earned for work physically performed within their borders, regardless of where the employee lives or the company is headquartered. That technician can generate withholding obligations in two or three states in a single quarter, each with its own registration requirements and withholding tables, and, in some cases, a day-count or dollar threshold before nonresident withholding attaches. A few state pairs offer reciprocity, but most states an NDT crew is likely to cross — including the Gulf Coast states — do not.

Generic payroll software is built around an employee having one home work state that rarely changes. NDT payroll needs the opposite: a withholding state updatable mid-pay-period, state-by-state tax tables that stay current without manual lookup, and a clean way to allocate one pay period's wages across two or three states when a rotation changes mid-cycle. Getting it wrong risks back-withholding assessments from a state that never received filings it was owed, sometimes discovered years later during an unrelated audit.

Certified Payroll and Davis-Bacon Compliance on Federal Turnarounds

NDT technicians doing inspection work tied to federal or federally funded construction — a Corps of Engineers project, a VA hospital expansion, a federally funded pipeline rehabilitation — fall inside the Davis-Bacon Act's reach once the contract triggers prevailing wage requirements. That means weekly certified payroll reporting on Form WH-347 or an approved electronic equivalent, showing each worker's classification, daily hours, rate of pay, and fringe benefit contributions, with a signed statement of compliance.

The recurring friction point for NDT specifically is classification. Davis-Bacon wage determinations are built around construction trades, and "NDT technician" frequently doesn't appear as a named classification for a given county and contract type. Contractors then work through the conformance process — requesting an additional classification and rate through the contracting officer and, ultimately, the Department of Labor, using a fitting comparison to an existing classification. Underpaying against the correct rate is a straightforward violation with back-wage liability; an unsupported conformance request can be rejected after the crew was already paid under it, forcing a retroactive correction. Recordkeeping stacks on top of everything else, most defensible when hour types are already tagged by job and location rather than reconstructed from a general ledger.

FLSA Overtime Exposure Unique to Traveling Technicians

The FLSA's overtime rules apply the same 40-hour weekly threshold to NDT technicians as to any other nonexempt hourly worker, but travel and standby time create the gray areas that generate real wage-and-hour risk. Under the Department of Labor's travel-time regulations (29 CFR Part 785), ordinary commuting isn't compensable, but travel that is part of a technician's principal activity — job site to job site during the workday — generally is. Overnight travel is more nuanced: a passenger's travel outside normal working hours is typically not compensable, but travel cutting across normal working hours is, even on a day the technician wouldn't otherwise have worked, such as a Sunday travel day ahead of a Monday job start.

Standby time follows a related but distinct test: time a technician can't use effectively for their own purposes — held at a muster point during a weather delay, waiting in a yard for a permit-to-work — is generally hours worked, even with no inspection happening; time genuinely free of duty is not. Misclassifying "engaged to wait" as unpaid downtime is a common source of wage claims in turnaround-heavy work, and it compounds — excluded standby hours skew that week's overtime too. Federal law sets a weekly threshold only, but a handful of states impose their own daily overtime rules, which matters for crews rotating into those states.

Capturing Time From a Compressor Station With No Signal

None of the categorization above matters if the underlying entry never happens accurately, and NDT field conditions are hostile to real-time data capture. A technician on an offshore platform, at a compressor station, or inside a tank during a confined-space RT shoot often has no cellular signal for hours or days. Mobile timesheet capture built for this environment has to work fully offline — logging start times, job and task codes, travel segments, and standby periods locally — then sync automatically once connectivity returns, with nothing to remember or reconcile against a paper backup.

This is also where per diem day-type, job coding, and rotation status ideally get captured at the same point of entry as the hours themselves, rather than as a separate step at the office weeks later. A technician who logs "standby — waiting on weather" at 7:40 a.m. on a disconnected tablet, synced that evening once back in cell range, produces a far more defensible record than a paper timesheet filled in from memory. For companies already running NDT reporting software in the field, tying time capture into the same mobile app used for inspection data removes a second offline-sync problem.

Job Costing Tie-In: Labor Cost Per Job, Not Reconstructed Weeks Later

Labor is usually the largest cost against any NDT job, and the one most often tracked with the longest lag. When timesheets exist as a payroll-only input, the office doesn't know the real labor cost on a turnaround until payroll closes — sometimes two or three weeks after the work, past any chance to adjust crew size or raise a change order while the job is still running. Feeding field-captured timesheets directly into job costing closes that gap: hours logged against a job number in the field — worked, travel, standby, per diem days — roll into that job's labor cost in near real time instead of being reconstructed from a payroll register later. That matters most on time-and-materials turnaround work, where a same-week labor breakdown is a real credibility advantage with the client, and internally for catching a crew running long on a fixed-fee scope before it closes out underwater.

Union Crews, Fringe Benefit Reporting, and Apprenticeship Ratios

Union NDT technicians, common on pipeline and heavy industrial work staffed through building trades locals, add another reporting layer. Fringe benefits — health and welfare, pension, training fund contributions — are typically calculated per hour worked and remitted to trust funds on the schedule set by the collective bargaining agreement, reported in the categories trust administrators require, broken out separately from straight wages. On Davis-Bacon jobs, fringe contributions also count toward meeting prevailing wage — an employer can satisfy part of that obligation through bona fide fringe contributions rather than cash, but only if properly documented. Apprenticeship ratios matter on union and Davis-Bacon work alike: contracts and wage determinations frequently cap the ratio of apprentices to journey-level workers on a crew, and exceeding it, even inadvertently, is a compliance finding regardless of pay accuracy — one a system tracking classification can flag at scheduling, before dispatch.

Turnaround Surges: Onboarding a Wave of Contract Technicians in Days, Not Weeks

A two-to-three-week refinery or petrochemical turnaround routinely requires bringing on a wave of contract technicians well beyond steady-state headcount — sometimes doubling or tripling crew size for the outage and releasing most of that surge staff once the unit is back online. That compressed timeline is unforgiving of slow onboarding: a technician showing up Monday needs to be in the payroll system, correctly classified, assigned the right withholding state, and set up to log hours from day one.

If certification verification, payroll setup, per diem assignment, and timesheet access are separate manual steps across separate tools, a surge of a dozen or twenty contract technicians turns onboarding into its own project alongside the turnaround — and mistakes made under that time pressure are exactly what produce a misclassified withholding state or a wrong per diem policy surfacing weeks later. An NDT ERP platform keeping certification records, payroll setup, and field timesheet access in one system lets a surge hire move from offer to first correctly logged hour in a single pass, and it's where companies staffing up fast lean on Atlantis NDT Academy and broader NDT training relationships for qualified technicians on short notice.

Getting the System Right Before the Next Turnaround, Not During It

None of these problems — FIFO rotation accounting, per diem substantiation, multi-state withholding, certified payroll, FLSA travel and standby time, offline field capture, job costing, or surge onboarding — is exotic on its own. What makes NDT payroll genuinely difficult is that one technician, on one hitch, can trigger several at once: a Louisiana turnaround week with a weather-hold standby day, a per diem entry substantiated against the applicable locality rate, and hours that need to land correctly on a certified payroll report if the job is federally funded. Payroll software built around how NDT crews actually work, rather than adapted from a retail template, keeps that complexity from becoming a compliance risk or a week of manual reconciliation every pay period.