Trucker Payroll essentials: accuracy, compliance, and cash-flow visibility

Trucker Payroll is the set of processes used to calculate, document, and pay drivers and related workers in the trucking sector. When done well, it reduces disputes, supports regulatory compliance, and improves workforce stability—especially when pay includes miles, hours, accessorials, per-diems, and incentive programs. The very critical starting point is to build a payroll workflow that converts trip and work data into consistent pay statements, with audit-ready records and clear exceptions handling. Done badly, payroll becomes a recurring operational “incident”: drivers question totals, dispatch and operations get pulled into back-and-forth clarifications, finance absorbs unplanned rework, and compliance reviews can uncover missing documentation that should have been captured at the time the work occurred.

In practice, “Trucker Payroll” is rarely just a payroll run. It’s a chain of decisions that begins at the moment a driver accepts work, is recorded across dispatch events and telematics signals, is confirmed through customer paperwork or settlement sheets, and is finalized into an accounting-ready payroll register. That chain needs to be designed as a controlled system—one with stable rules, reliable inputs, and traceable outputs—rather than as a monthly scramble. The more complicated the pay structure becomes, the more the payroll engine must be disciplined: consistent definitions, standardized codes, documented calculations, controlled approvals, and repeatable validation steps.

Why payroll accuracy matters more in trucking than in many other industries

In transportation operations, pay is rarely a simple hourly rate. It often involves variable driving time, route distance, detention time, load handling, layover arrangements, and sometimes multiple pay components across a single pay period. Drivers may earn differently depending on where and when the work happens, what equipment is involved, whether a load is short, whether an appointment runs late, whether accessorial work is authorized, and whether special conditions apply (hazmat, team operations, regional pay differences, or customer-specific arrangements). As a result, payroll errors can quickly become operational problems: drivers may lose trust, managers may miss budget signals, and compliance reviews can surface gaps in documentation.

From an industry perspective, the guiding principle is straightforward: pay should reflect the work performed and should be traceable back to source records. This is where trucker payroll systems—whether manual spreadsheets, payroll software integrated with transportation data, or full fleet management stacks—must show consistency across scheduling, time capture, trip settlement, and payment processing. Accuracy is not only about the final number; it’s about the credibility of the path that created that number.

In many trucking organizations, payroll also becomes the “truth baseline” for driver performance. Even when a driver is not formally evaluated using payroll, disputes over pay create indirect friction that can affect safety culture, retention, and readiness. A driver who believes payroll is frequently wrong may communicate less effectively about appointment timing, may be less likely to report issues promptly, or may be more likely to challenge operational instructions later. Conversely, when payroll calculations are consistent and explainable, drivers are more likely to provide accurate data and follow standardized procedures—because they can see that the system rewards correct reporting.

Accuracy matters for cash-flow visibility as well. If payroll is being calculated with inconsistent rules or ad-hoc adjustments, finance loses predictability. The organization may not know how much labor cost it is truly incurring until after settlement. That can cause downstream issues: delayed payments to contractors, reduced ability to plan staffing for demand spikes, and reactive budgeting rather than proactive management.

What typically makes Trucker Payroll complex (and how expert teams manage it)

Trucking payroll complexity usually comes from five primary drivers of variance:

• Compensation mix: base pay plus variable elements such as mileage-based pay, hourly wages, bonuses, and accessorials (e.g., stop-off pay or unloading assistance). Some fleets have multiple rate cards depending on route type, equipment class, customer, or time of day.
• Hours and timekeeping: Hours of Service (HOS) recordkeeping affects how time is categorized and documented, which can indirectly impact payroll classifications. Even when HOS time does not directly determine pay, the way time is captured and stored often determines how payroll components are derived.
• Trip and settlement logic: how the company defines start/end times, payable mile calculations, and detention thresholds determines pay outcomes. For example, when exactly does “detention” begin? Does it count only after a threshold in minutes? Are there maximums? How does a cancellation or reassign affect the timeline?
• Adjustments: re-weighments, customer delays, short loads, pay corrections, training time, or equipment issues require structured change control. Adjustments are where audit trails and approval discipline matter most, because they often happen outside the normal flow.
• Multi-state or cross-border operations: different jurisdictions can add administrative complexity related to withholding, reporting, and wage and hour rules. Even if the trucking work is consistent, documentation requirements and tax practices may not be.

Industry top practice is to treat payroll inputs as “data,” not as “notes.” That means standardized codes for pay elements, consistent naming conventions for accessorials, and a controlled approval path for exceptions. When payroll depends on subjective interpretation without a documented policy, disputes become more likely. For instance, if one manager treats loading/unloading time as included in a per-mile rate while another manager treats it as separately payable accessorial time, two drivers performing similar work can receive different compensation without clear rationale.

Expert teams manage this complexity by designing the payroll workflow around a “pay rules library” and a traceable event model. Instead of focusing only on the payroll run, they focus on how work is represented in the system: what events exist (arrival, door-in, door-out, loading start, loading end, tarp/re-tarp, detention threshold reached), what attributes each event has (timestamp, location, appointment identifier, authorization status), and what mapping rules convert those events into pay components.

Expert considerations for structuring pay components in a payroll workflow

Specialists who advise fleets typically recommend designing payroll pay components before selecting tools. A workable blueprint often includes:

• Pay rules library: a written policy mapping each pay element to a source field (e.g., miles, time stamps, activity codes) and a formula (rate x quantity, caps, thresholds). For example, the rules library should specify whether the detention rate applies after 30 minutes, whether detention is payable in 15-minute increments, whether it pauses for breaks, and whether maximum detention per stop exists.
• Data capture standards: consistent driver check-in/out, standardized detention or layover triggers, and clear definitions of “loaded miles” versus “empty miles.” Data capture standards also include how missing data is handled (e.g., “if time stamp missing, use POD timestamp if within X hours” only if allowed by policy).
• Exception management: a documented method for disputed entries (e.g., missing timestamps, route adjustments) with required supporting evidence. Exceptions should not be informal; they should follow structured categories and include evidence requirements, such as detention confirmation from customer or a signed accessorial authorization.
• Approvals and segregation of duties: separation between data entry, review, and final payroll sign-off reduces operational and financial risk. A common best practice is to ensure that the same person who enters a correction is not the person who approves final payroll without independent review.
• Audit-ready retention: payroll reports and supporting documents should be stored in a way that can be retrieved quickly for internal review and compliance. This includes maintaining snapshots of pay statements, rule versions used in payroll calculations, and supporting source artifacts.

These elements don’t require “one magic system.” They require a clear operational design that remains stable even when volume or staffing changes. A payroll workflow should survive turnover: if a payroll administrator leaves, a new person should be able to follow documented rules and understand how totals were computed. The pay rules library should ideally be versioned and tied to effective dates, because trucking compensation structures can change when rate cards update or customers renegotiate accessorial policies.

In addition, structure matters because it improves explainability. A driver may not care about internal system logic, but they do care whether the system can clearly explain why they earned a certain amount. The more your pay components and supporting documents align, the easier it is to answer questions like “Why did my detention pay change?” or “Why did my empty miles differ from last period?”

Cost control and budgeting: what fleets should track alongside payroll

Payroll is not only a cost line—it is also a performance signal. Expert payroll programs often align with operational metrics such as:

• Cost per mile (or cost per dispatched load): helps evaluate how pay mix changes with route patterns. When cost per mile fluctuates, finance can inspect whether it is driven by mileage rates, accessorials, detention trends, or overtime.
• Detention and accessorial trends: sustained increases can indicate dispatch, customer scheduling, or appointment performance issues. A rise in detention hours could point to consistent appointment delays at certain customer docks.
• Overtime frequency (where applicable): may reveal capacity or scheduling constraints. Some fleets may have overtime policies based on certain employment models; others may treat certain pay components differently.
• Payroll correction rates: recurring corrections point to data capture or rule-definition gaps. If corrections are frequent, the system is not truly standardized.

When payroll is structured with transparent pay logic, finance teams can forecast staffing cost more reliably and avoid reactive “end-of-month” surprises. This forecastability is critical in trucking because revenue cycles, fuel costs, and customer billing schedules can be uneven. If payroll cost can be projected earlier, leadership can plan hiring, dispatch capacity, and contract adjustments with more confidence.

Cash-flow visibility improves when payroll is integrated with settlement and billing schedules. A fleet that can estimate weekly labor cost per load or per route can reconcile with customer invoices and understand profit margins sooner. In contrast, fleets that only compute payroll at the end of the month often discover margin erosion late, after detention or accessorial costs have accumulated.

It’s also useful to track the “time-to-resolution” for payroll exceptions. When corrections are made quickly and explained clearly, disputes shrink. When corrections drag on for multiple pay cycles, the organization experiences not only financial cost (rework) but also reputational cost (driver retention risk).

Compliance background: how payroll processes relate to wage-and-hour obligations

Trucker Payroll intersects with wage-and-hour requirements, recordkeeping expectations, and employment classification considerations. While exact obligations vary by jurisdiction and employment model, the operational takeaway is universal: companies should be able to demonstrate how wages were calculated and how time and work were recorded.

For reliable background, the U.S. Department of Labor (DOL) provides general guidance on wage payment and recordkeeping expectations through the Fair Labor Standards Act (FLSA). In addition, the U.S. Equal Employment Opportunity Commission (EEOC) offers resources relevant to nondiscrimination in compensation practices. For trucking-specific recordkeeping topics, agencies such as the Federal Motor Carrier Safety Administration (FMCSA) publish documentation standards for Hours of Service. These official sources help fleets ground their payroll policies in current regulatory framing.

Compliance in trucking payroll is not just about whether a driver was paid the right amount. It’s also about whether you can produce proof. During audits or investigations, regulators may focus on questions like:

• Were hours recorded accurately and consistently?
• Were deductions or reimbursements handled according to policy and law?
• Were bonuses, incentives, and accessorial payments treated consistently and documented?
• Were changes to pay rules communicated and applied correctly?
• Are employees classified correctly, and are compensation structures consistent with that classification?

Even when a fleet believes its pay rules are correct, incomplete documentation can still create compliance risk. For example, detention pay may depend on customer confirmation, but if those confirmations are not reliably captured and retained, the fleet may not be able to justify decisions later. Likewise, if pay adjustments are frequently made without structured evidence, regulators and auditors may view the system as uncontrolled.

A key compliance mindset is to separate “operational reality” from “pay representation.” Operational reality is what happened on the road and at the dock. Pay representation is how those events are recorded in your system for payroll purposes. A compliant payroll process ensures pay representation matches operational reality as closely as possible, using clear definitions and evidence requirements.

Important: pricing and “supplier” context for payroll services

Many fleets compare vendors and internal solutions when building or upgrading their payroll workflow. However, pricing for payroll platforms or service providers varies substantially by features, number of drivers, pay complexity, and integrations. Therefore, any discussion of “price information” should be handled through verified vendor quotes and contract terms.

Instead of assuming fixed costs, expert procurement teams generally compare suppliers using the same criteria: integration with transportation data sources, data accuracy controls, reporting capability, compliance support, implementation effort, and clarity of contract responsibilities. If your procurement documents include a specific Trucker Payroll price, ensure it’s tied to the scope (modules, support hours, processing volume, and customization).

To avoid misunderstandings, procurement documentation should specify at least:

• What data sources are included (dispatch, telematics, time capture, settlement, accessorial logs, customer-provided documents).
• What payroll events and pay components are supported out-of-the-box versus customized.
• What approval workflows exist and who configures them.
• What reporting outputs are available (pay statements, payroll registers, exception reports, audit trails).
• What service-level expectations exist for data processing and issue resolution.

In trucking payroll, the “hidden cost” is often operational: mapping pay rules, training staff to use the workflow, and managing exceptions. Some systems appear cheaper up-front but require heavy manual reconciliation. Conversely, an integrated platform might cost more but reduce correction rates and improve cash-flow forecasting. The right comparison should consider total cost of ownership, including rework and dispute resolution overhead.

Practical implementation approach: from data capture to pay release

An expert rollout plan usually moves in stages, because payroll risk grows when systems go live without validated pay logic. A safe approach is to start with one pay group, validate each pay component, and only then expand to additional driver fleets or routes.

Implementation typically includes four layers:

• Data ingestion: making sure dispatch events, telematics logs, timestamps, and settlements arrive in a consistent format, with reliable field mapping.
• Pay rules mapping: configuring formulas and thresholds in a pay rules library, with version control and effective date handling.
• Validation and exception workflows: ensuring the system can identify missing data, flag unusual cases, and route exceptions for approval with evidence requirements.
• Payroll execution and statement delivery: producing payroll registers and pay statements, with reconciliation steps and an auditable approval trail.

A common failure mode during implementation is not the calculation logic itself but the mismatch between how operations record events and how the payroll engine expects to receive them. Therefore, validation should include operational scenarios: delays, cancellations, split loads, partial unloading, re-weighments, driver substitution, and customer-specific accessorial variations. The goal is to test payroll logic against real-world variability, not just the “happy path.”

Conditions and requirements (comparison, sources, and a step-by-step guide)

The following supplement is designed to help you evaluate options for trucker payroll operations without relying on assumptions. Replace your internal definitions where needed so the policy remains consistent.

Beyond the comparison table, you should explicitly evaluate how each option handles the realities of trucking payroll:

• Missing timestamps: What happens when a driver’s check-in/out is incomplete? Is there a fallback method approved by policy?
• Overlapping pay events: For example, detention could overlap with layover, or accessorials could be claimed during a time window that is also used for hourly pay. How does the system prevent double-paying or incorrectly attributing time?
• Rate changes mid-period: When rates update, what is the effective date logic? Are old rates preserved for past work?
• Customer-specific agreements: Can the system support multiple rate cards or special exceptions while maintaining audit trails?
• Correction workflows: How are pay corrections logged, approved, and tracked? Can you report on correction frequency and reasons?

Sources (for policy and recordkeeping context)

• U.S. Department of Labor (DOL): guidance on wage payment and recordkeeping under the Fair Labor Standards Act (FLSA).
• U.S. Equal Employment Opportunity Commission (EEOC): compensation and nondiscrimination resources relevant to pay practices.
• U.S. Department of Transportation / FMCSA: Hours of Service framework and associated recordkeeping considerations for motor carriers.

When applying these sources, fleets typically translate regulatory framing into operational policies: what records to capture, how long to retain them, how to document exceptions, and how to ensure consistency in compensation decisions. While this content supports general considerations, legal counsel and HR/compliance specialists should be involved for final policy decisions for your specific employment model and operational jurisdictions.

Step-by-step guide to run Trucker Payroll with fewer disputes

1. Define pay components in writing: List each element used for driver pay (base, miles, hourly, detention, layover, bonuses, accessorials). Specify the formula, caps, thresholds, and eligibility rules. For example, define whether accessorials require authorization before work begins or whether they can be authorized after the fact with evidence.
2. Standardize source data codes: Ensure events such as detention start/end, loading/unloading, and route milestones use consistent activity codes. Create a codebook that dispatch and operations can follow, and ensure that training materials reflect the codebook rather than ad-hoc interpretations.
3. Set time and mileage rules: Establish how miles are counted (e.g., loaded miles only) and how time is categorized (e.g., payable detention versus non-payable waiting). Include boundary rules (rounding rules, minimum payable increments, and how to handle partial events).
4. Create an approval workflow: Require review by operations for mileage/time classifications and by finance for payroll totals. Document who approves exceptions and under what circumstances. Ensure approvals are logged and tied to specific pay statements and source events.
5. Run a validation payroll cycle: For the first run (and after rule changes), reconcile driver-level pay outputs against a manual sample and require sign-off. Validation should include both “normal” scenarios and “edge” scenarios: missing data, unusually long detention, load cancellation, and special customer instructions.
6. Document corrections before release: Track every correction with a reason code and evidence. Avoid “silent” edits that cannot be traced later. Corrections should be reviewed for pattern trends, not only for individual accuracy.
7. Release pay statements and capture feedback: Provide drivers with clear explanations for major pay changes, particularly when accessorials or mileage calculations differ. Build a feedback loop that routes questions to the responsible team quickly.
8. Review exception trends quarterly: If detention disputes or missing timestamp corrections happen frequently, adjust data capture or operational dispatch instructions. Use exception data to improve the upstream workflow.

To make these steps operational rather than theoretical, fleets often implement a “pay operations calendar.” This calendar defines key dates: when dispatch cutoff occurs, when telematics data is considered complete, when exceptions must be submitted, when payroll calculations begin, and when statements are released. A calendar reduces confusion and prevents late changes that can destabilize the payroll process.

Another useful discipline is to maintain a “pay scenario library” with examples of common and complex cases. For instance, record a sample scenario for “detention begins after 30 minutes, payable in 15-minute increments, capped at X hours per stop,” and another for “stop-off pay requires route milestone confirmation.” New payroll staff can validate decisions using this scenario library, reducing inconsistency.

Conditions/requirements to consider before going live

• Data readiness: confirm that dispatch systems, telematics, time capture tools, and customer load data provide the fields your pay rules require. Include tests for data delays: what if a settlement record arrives late?
• Policy governance: ensure payroll rules are version-controlled and updated through a change management procedure. If rules change, the system should preserve prior logic for past work.
• Role permissions: limit access to payroll rule changes and final payroll approvals to reduce errors and internal control failures. Permissions should reflect real responsibilities: data entry, review, approval, and audit access.
• Record retention: establish retention timelines consistent with your jurisdiction and internal compliance policy. Retention should cover both payroll outputs and supporting evidence used for calculations.
• Security and privacy: protect personally identifiable information used in payroll processing. Use least-privilege access, secure storage, and controlled exports.

Going live also requires testing your exception handling under load. If your fleet has seasonal volume spikes, the payroll system needs to remain stable when many events post simultaneously. Test how the system behaves when multiple drivers have exceptions during the same pay cycle and ensure the approval workflow doesn’t become a bottleneck. Delays in approvals can push payroll close windows and create late corrections, which in turn increases disputes.

Additionally, consider the operational training required for the workflow. Even the best payroll engine can fail if dispatch codes are not entered correctly or if driver time stamps are inconsistent. Therefore, implement training and feedback loops: teach staff what “correct data” looks like and provide mechanisms for correcting misentries quickly.

Frequently asked questions about Trucker Payroll

FAQ 1: What is included in “Trucker Payroll” beyond base wages?

Trucker Payroll typically includes base wages plus variable components such as mileage or hourly pay, detention or layover reimbursements (when treated as payable elements), accessorial payments, and incentive bonuses. It should also include the documented adjustments that explain why a specific driver’s total differs from expected amounts.

In many trucking environments, “pay beyond base wages” is where the majority of disputes originate. This is why fleets should treat incentive and accessorial rules with as much rigor as base wage calculations. Incentive programs often depend on performance definitions (on-time pickup, delivery adherence, safety milestones, fuel efficiency thresholds, or maintenance compliance). Those definitions must be captured as objective criteria with a traceable source, not as subjective manager notes.

FAQ 2: How do fleets reduce disputes over miles and time calculations?

Disputes usually decline when the fleet uses standardized definitions (e.g., loaded miles rules, detention thresholds) and ensures payroll inputs come from consistent source records. A practical step is to run pay validations on a sample basis each pay cycle and maintain evidence for exceptions.

Fleets can also reduce disputes by designing driver-friendly explanations. For example, if loaded miles are calculated from a settlement report, include a line on the pay statement or an accompanying detail page that shows the miles source and the rate applied. For detention, include the timestamps used and the threshold logic (e.g., “detention paid from 10:45 after a 30-minute threshold; total 2.5 hours at $X/hr”). Even if the driver doesn’t understand all payroll logic, they can verify the key inputs.

Another effective technique is “pre-pay review.” Before payroll release, run a quick review for high-variance components: if a driver’s accessorial total is dramatically different from their normal pattern, flag it for review. This reduces the number of drivers who discover discrepancies only after payroll is finalized.

FAQ 3: Should payroll be handled internally or by a supplier?

It depends on fleet size, pay complexity, integration needs, and internal capacity. Many fleets start with internal workflows for basic needs, then move toward software or integrated platforms as accessorial volume and rule complexity increase. Procurement should focus on verified scope and proven workflows rather than assumptions about cost or implementation time.

From a decision standpoint, you should ask whether internal payroll can maintain the necessary discipline: documented pay rules, controlled approvals, version control, and audit-ready retention. If internal staffing is stretched, the organization may experience increased correction rates and inconsistent enforcement of pay rules. A supplier can help standardize execution, but you still remain responsible for policy correctness and data accuracy—so the evaluation should focus on how the supplier supports your operational realities.

Additionally, if you use a supplier, ensure you understand where your organization’s control points still reside. Many disputes are ultimately resolved by operations and finance decisions, not by the payroll engine itself. A good supplier will provide visibility into calculations and logs so you can trace outcomes back to source events.

FAQ 4: What records should be retained to support payroll calculations?

At minimum, retain the payroll register, pay component breakdowns, driver pay statements, approvals, and the source data that drives pay outcomes (e.g., timesheets, settlement reports, and accessorial logs). Exact requirements vary by jurisdiction and employment classification, so align retention with your compliance program and legal counsel.

To make retention practical, define a retention matrix. For each record type—dispatch event logs, time stamps, detention approvals, accessorial authorizations, adjustment requests, pay statement history, and payroll registers—specify: storage location, ownership, access permissions, retention duration, and deletion policy. Without this, fleets sometimes keep too much data indefinitely (creating security cost) or keep too little (creating compliance risk).

Also consider audit readiness in terms of retrieval speed. During a dispute, managers may need to pull supporting evidence quickly. Therefore, retention strategy should support fast retrieval by driver, pay period, and exception category—not only by internal system IDs.

FAQ 5: How often should payroll rules be reviewed or updated?

Many organizations review payroll rules on a scheduled basis (for example, quarterly or semiannually) and also after operational policy changes such as new detention practices, updated rate cards, or new incentive programs. Any change should be version-controlled and tested before full deployment.

Rule updates should not be treated as “configuration tweaks” only. Because payroll affects driver livelihoods and compliance risk, changes should be managed like business-critical policy. A mature process includes: proposal, approval, documentation, test scenarios, effective date assignment, and communication to stakeholders. For drivers, communication may be as simple as an updated pay policy sheet or an internal FAQ explaining what changed and when it becomes effective.

Incentive programs in particular require careful review. Incentive criteria sometimes change based on customer billing definitions or internal performance metrics. When those definitions change, the pay representation must change too—otherwise drivers may perform work under the old criteria but be evaluated under the updated criteria without clarity.

FAQ 6: Are there localization concerns for payroll when operations extend beyond a single region?

Yes. When operations span multiple jurisdictions, wage-and-hour rules, withholding/reporting practices, and documentation norms can vary. While general operational principles remain the same, fleets should consult relevant legal or HR compliance resources to ensure the payroll policy matches local requirements in each operating area.

Localization concerns also include practical operational differences. Some regions may require different documentation practices for time capture at certain customer sites, or may have differing norms around appointment windows and proof-of-delivery. Therefore, localization is not only legal—it’s also operational. When localization affects pay (for example, how certain reimbursements are treated), the pay rules library should support different logic by region or by contract type.

FAQ 7: What are common payroll risks for fleets?

Common risks include incorrect pay rules, inconsistent time capture, missing timestamps, unapproved manual adjustments, unclear accessorial definitions, and insufficient audit trails. Expert teams mitigate these through standardized definitions, controlled approvals, validation runs, and exception trend reviews.

It can be helpful to categorize risks into “input risk,” “logic risk,” and “execution risk.” Input risk is when source data is incomplete or inconsistent. Logic risk is when pay formulas or thresholds are incorrect or not aligned with policy. Execution risk is when approvals are skipped, updates are made without version control, or payroll runs are performed outside the approved workflow. Many disputes trace back to one of these categories.

For each risk category, you can build controls: data completeness checks, rule validation tests, approval workflow enforcement, and change logs. When risk controls exist, payroll becomes more resilient and less dependent on individual knowledge.

Conclusion: treat Trucker Payroll as a controlled system, not a monthly scramble

Trucker Payroll becomes very effective when it is treated as an operational system: clear pay rules, reliable source data, controlled approvals, and audit-ready documentation. Whether you choose internal workflows, payroll software, or an integrated transportation approach, the core objective remains consistent—accurate pay that reflects the work performed and stands up to internal and external scrutiny. When your payroll process is designed for traceability and consistency, drivers gain confidence, managers gain visibility, and the organization gains stability across cycles.

To make this approach sustainable over time, fleets should invest in ongoing improvement rather than one-time implementation. That means regularly reviewing exception trends, refining data capture standards, updating pay rules with version control, and training teams so that “correct data entry” becomes the norm. In trucking, where operational variability is inevitable, the difference between a dispute-prone payroll and a dispute-resistant payroll is not the absence of variability—it’s the presence of disciplined, documented logic and dependable evidence. When payroll is built this way, it becomes a strategic asset: it supports compliance, improves retention, strengthens cash-flow planning, and reduces the operational noise that can distract teams from safety and service quality.