Compare NDT Offers with Different Travel-Time Assumptions

Two NDT assignments can quote different hourly amounts while requiring very different journeys. One may involve a short local trip; another may require flights, transfers and repeated travel between home and the project area. Comparing only the paid hourly amount hides that difference. Begin with the actual proposed schedule and identify the travel time that is not already included in paid hours. Then consider the money received, expenses personally paid and time committed under the described assumptions. This is a personal planning comparison, not a calculation of the legally required wage or a statement that a proposed unpaid segment is lawful.

The useful deliverable is a travel-segment worksheet connected to a clearly labeled offer scenario. It should let another reader reproduce the time inputs and see which pay-treatment questions remain unresolved. Avoid compressing every inconvenience into a single adjusted rate. A cash total, an entered time total and a list of practical constraints answer different questions. Keeping them visible helps you recognize an offer that looks stronger on headline pay but depends on more travel, higher costs or a schedule you cannot reasonably accommodate. The final choice remains yours after the actual terms are understood.

Use the same stated work window when comparing two proposals, or explain clearly why the windows differ. Identify the assumed start, duration and travel pattern. A one-week headline should not be compared with a whole assignment containing several return journeys. If the exact dates are uncertain, label the duration as an assumption and count travel for that scenario. The contract tool uses assumed weeks; it does not verify that the project will last that long. A travel plan that depends on another rotation or an early finish therefore needs a separate scenario rather than an invisible adjustment to one input.

List travel events in ordinary language before estimating their duration: initial journey, return journey, movement between project locations or another described segment. Include only the events relevant to the comparison and keep their purpose clear. Avoid counting a round trip once as a total and again as separate legs. A calendar or itinerary can help identify overlaps and overnight boundaries, but do not present an estimated itinerary as a confirmed booking. Record the source of each duration and the reason for any estimate so a later change can be traced to the affected segment.

A quoted flight duration is not necessarily the same as the travel segment you intend to compare. Decide whether your scenario includes the journey to the departure point, transfers, scheduled connections and the journey from arrival to the stated destination. Use the same definition for both offers. Do not add speculative delays as though they were confirmed hours. If uncertainty is material, keep a separate sensitivity scenario with its rationale. A door-to-destination estimate and an aircraft-time estimate can each be useful, but comparing one against the other without explanation creates a misleading difference in the denominator.

Ask whether travel between accommodation and the project is already represented in the proposal or whether you are deliberately comparing only mobilization journeys. Keep that boundary explicit rather than silently mixing daily movement with whole-assignment travel in only one offer. The calculator accepts a total, so it cannot detect inconsistent segment definitions. The worksheet supplies that missing context. When someone challenges the result, you should be able to identify which journeys were counted and how their duration was estimated. This makes the discussion about actual assumptions rather than whether a particular combined-hour figure looks attractive.

Ask the offer owner which travel is included in the proposed paid hours and how other travel is described. Preserve the written answer. The U.S. Department of Labor’s hours-worked guidance distinguishes travel situations in its FLSA discussion. That context means the question cannot be settled by a generic travel label in a calculator. If treatment is disputed or unclear, direct the facts to the responsible employer contact or qualified adviser. This guide does not determine coverage, classification or the legal treatment of a particular journey.

Keep two labels when needed: proposed treatment in the offer and question requiring confirmation. The worksheet may record a segment as not included in the proposed paid hours without declaring that exclusion legally correct. This lets you compare the stated proposal while preserving the unresolved issue. Do not treat a low time-adjusted result as proof of a legal violation, or a high result as proof that the pay arrangement is compliant. The arithmetic describes entered money and time. Legal and contractual interpretation require the actual facts, applicable requirements and responsible review outside the tool.

In the free contract offer comparison, expected paid hours are entered per week and multiplied by the assumed weeks. Travel already included in those paid hours should not also appear in the whole-assignment unpaid-travel input. That would count the same time twice in the combined denominator. Conversely, travel absent from paid hours will not appear in the tool’s time basis unless you enter it in the travel field. Build the segment worksheet first, then total only the segments that belong in each input under the stated scenario.

The tool applies one hourly rate to all entered paid hours in an offer. If travel is paid at a different rate, the full arrangement cannot be represented faithfully as a single-rate offer without separate external calculations and explicit limits. Do not disguise the difference by changing hours to force the desired gross total. That would also distort the time-based result. Keep the rate segments outside the calculator or use it only for a clearly defined single-rate portion. The goal is an understandable comparison, not filling every input at the expense of what its label means.

A long journey can consume time without creating a large personal bill, and a short journey can still involve a significant cost. Record cash and time separately. The tool has whole-assignment fields for expenses you pay and expected cash reimbursements. Include a personally paid expense even when reimbursement is expected, then enter the expected repayment separately. Costs paid directly by the company belong outside both personal cash fields. This avoids treating a reimbursed ticket as no cost and also adding its repayment, which would overstate the personal cash result.

Do not add a reimbursement to paid hours or interpret it automatically as compensation for time. Ask what the payment represents under the actual terms. A fixed travel amount, a receipt-based repayment and a separately paid travel segment may have different meanings. The tool does not classify them for tax or legal purposes. Keep the entered cash basis visible in the worksheet and compare one currency consistently. It does not retrieve ticket prices or convert currencies. Obtain the actual information you need and label estimates so a precise result does not conceal uncertain costs or unresolved payment responsibility.

The calculator shows expected gross hourly pay, cash receipts including reimbursements, entered expenses and cash after those expenses before taxes or other deductions. It also divides gross pay and cash after entered expenses by paid hours plus entered unpaid travel hours. These are different views of the same scenario. The second view can reveal the effect of travel on the time you have included, but it is not a payroll rate, take-home wage or legal minimum-wage test. Read its label carefully and keep the original offered rate beside it.

The denominator is also limited. It excludes other time you did not enter, such as personal preparation or unrelated time away from home. Do not rename the result total earnings per every hour committed unless you have independently defined and calculated that broader basis. Likewise, a long absence can affect your decision in ways the calculator does not value. Record those considerations separately rather than entering arbitrary hours to force a preference. A transparent comparison acknowledges what is counted and leaves room for personal judgment about schedule, recovery time and other commitments.

Consider two entirely fictional four-week offers in USD, each with 40 expected paid hours per week and no entered reimbursements. Offer A uses an invented hourly rate of 50 dollars, 600 dollars of personally paid expenses and eight travel hours outside paid time. Offer B uses an invented rate of 55 dollars, 1,400 dollars of expenses and 40 travel hours outside paid time. These are arithmetic examples, not market rates or recommended compensation. The gross hourly pay is 8,000 dollars for A and 8,800 dollars for B, while both scenarios leave 7,400 dollars after entered expenses before taxes and other deductions.

Offer A has 168 entered paid-and-travel hours, so its cash-after-expenses result is about 44.05 dollars per combined hour. Offer B has 200 combined hours, giving 37.00 dollars on the same limited basis. The higher headline rate therefore does not produce more cash in this invented comparison and consumes more entered time. That does not prove which offer the inspector should choose. It identifies the assumptions responsible for the difference. If travel treatment, costs or duration change, the comparison must be recalculated rather than carrying the original conclusion forward.

Suppose the offer owner clarifies that a previously excluded segment is paid at the same hourly rate. Move that segment into the paid-time basis and remove it from unpaid travel; do not leave it in both places. Check how the weekly input represents the whole-assignment paid total. Preserve the written clarification with the scenario. If the clarified rate differs, stop using the single-rate model for the full offer and calculate the segments externally. A correct adjustment should change only the assumptions affected by the answer, making its impact easier to explain.

You can also compare a longer journey or an additional return trip as a sensitivity scenario. Keep the original proposal and the changed scenario separately labeled. Do not present the more favorable version as confirmed simply because it is plausible. A useful sensitivity exercise shows how much the conclusion depends on one unresolved travel fact and whether that fact is worth clarifying before a commitment. It should not become a prediction of flight delays or project changes. The tool uses the values you enter and has no live itinerary, employer policy or scheduling feed.

The tool lets you identify a subset of expected paid hours as marked guaranteed. Enter only the subset supported by the actual proposal and keep its conditions available for review. The assignment duration is still assumed in the calculation. A weekly hours statement does not automatically guarantee every planned week, every travel reimbursement or a particular finish date. Ask the offer owner what happens if the project shortens or the travel plan changes. The comparison separates pay relying on additional expected hours, but it does not verify that any stated guarantee is enforceable or will be paid.

Travel can interact with that uncertainty. An early finish might reduce paid work without eliminating the return journey, while a schedule extension might create another trip. Recount actual scenario events instead of scaling every travel input in direct proportion to weeks. Keep the current travel worksheet with each calculation so the difference is visible. This is especially useful when one offer has a larger initial travel burden: the cost and time may be less spread out in a shortened assignment. The tool can compare the entered scenario, but the event counting remains your external planning work.

The free tool needs no signup and keeps values in the current page’s memory. Choose the CSV download to retain the entered inputs and calculated results. The export does not contain a custom itinerary or resolve disputed terms, so keep the travel-segment worksheet beside it. Identify the offer version, assumed work window, currency and unresolved questions in your own working record. Avoid adding personal identity documents or confidential customer details to a comparison that may be shared for advice. The recipient usually needs the assumptions, not a complete personnel or project file.

Before sharing, verify that each travel segment appears once, paid hours represent the intended total and all cash fields use the whole-assignment basis. Check that none of the entered reimbursements are already deducted from expenses. Read the result labels instead of reducing the comparison to one impressive figure. If a recipient wants a full payroll or legal assessment, provide the actual terms through the appropriate process. The calculator output is an arithmetic aid with stated limitations, and it remains useful only when those limitations travel with the numbers.

The worksheet’s final column identifies the question that could change the decision: whether a segment is paid, who covers a personal cost, whether another trip is expected or what happens after an early finish. Ask that question directly and retain the response. If the answer changes the scenario, regenerate the calculation and label the new version. This is more effective than asking broadly whether travel is included, because included can refer to tickets, time, accommodation or only part of the journey. A precise question produces a comparison you can actually rely on for planning.