Road capacity is not a truck count

Road haulage capacity is a flow produced by vehicles, drivers, roads and terminals operating together. A fleet count is an input stock, not a delivery rate. The useful cycle begins when the vehicle is eligible to receive cargo and ends when it can perform the next compatible service. It includes loading preparation, movement, queues, inspection, unloading, return and any required rest or maintenance. An analysis that counts only loaded travel omits the states that often determine whether another trip is possible.

Vehicle payload should match the cargo and route basis. Gross vehicle capacity is not necessarily the accepted cargo quantity, and a nominal payload may be restricted by route, vehicle configuration, cargo characteristics or applicable rules. The team should identify the relevant technical and legal constraints without substituting a generic industry figure. This paper publishes no truck payload or cycle duration because the canonical app does not calculate them. A real road-stage input requires a validated derivation rather than a plausible-looking fleet multiplication.

Drivers and vehicles may have different availability patterns. A ready vehicle does not imply an available qualified driver, and a driver roster does not repair an unavailable vehicle. Applicable working-time, rest and safety requirements belong in the feasible operating envelope. The analysis should obtain the relevant jurisdiction-specific basis rather than assume that every hour on a calendar can become productive driving. Increasing dispatch pressure without that review can convert an apparent capacity solution into an unacceptable operating practice.

Terminal readiness also enters the cycle. A loading queue can immobilise vehicles before travel begins; a receiving queue can delay return; a documentary hold can occupy cargo and equipment without productive movement. A road expansion proposal should state which transition it improves. More trucks may increase the external queue when the terminal remains constrained. A faster loading process may improve fleet circulation without altering the road. Treating all shortfall as insufficient fleet size prevents the committee from comparing those alternatives intelligently.

Travel capability depends on the route's physical and operating conditions. Road surface, gradients, crossings, traffic interaction and restrictions can affect a permitted vehicle configuration and the consistency of travel. Seasonal conditions can alter access or require a different operating plan. The capacity basis should name the route and the relevant envelope, including the conditions under which movement must stop. It should not treat an annual road-stage capacity as a promise that every journey is feasible in every condition.

A corridor may use public infrastructure shared with communities and other traffic. Its operating plan should account for that shared use and the applicable obligations, rather than define success only as moving more industrial cargo. A queue displaced to a public approach can create a burden outside the terminal's own measurement boundary. A dispatch improvement should therefore be tested against the route and user interfaces that it affects. Local gate performance alone may conceal the external consequences.

An alternative route needs its own compatibility and permission evidence. A line on a map does not establish that the loaded vehicle can use it, that the receiving terminal is reachable or that the movement is authorised. Travel time on an unloaded reconnaissance trip does not demonstrate loaded service. The resilience record should identify which parts of the alternative have been tested and which remain uncertain. Otherwise a nominal detour can be credited as reserve capacity without a feasible deployment path.

Road conditions can also be endogenous to the service. Greater industrial use can increase maintenance needs, change local traffic patterns or affect access arrangements. The expansion basis should identify who bears those consequences and who can authorise the resulting operating regime. The annual app's cost inputs do not calculate road deterioration, public impacts or user-specific delay. Those matters require additional evidence and review, but they should be visible in the service decision rather than silently assumed away.

A vehicle trace can show movement while missing eligibility and custody. A truck can remain stationary for a permitted rest, a mechanical failure, a queue or a cargo hold. The same low speed has different meanings. The cycle record should connect location and movement to loading, release, receiving and resource-status events. An analyst should not infer a cause from a trace alone when the operational record can distinguish those states.

Travel-time reliability should use a declared trip boundary. A report of road segment times does not establish the completed industrial delivery cycle. The full cycle includes terminal and administrative intervals, while a specific segment measure remains useful for diagnosing road conditions. Keep both measures if they serve different decisions. Combining them without explaining their objects and denominators can create an apparent contradiction between a road that performs well and a delivery service that remains unreliable.

A vehicle sample can also be unrepresentative. The most complete traces may belong to newer equipment or preferred contractors, while difficult movements have missing records. Completed trips may exclude vehicles still delayed at the cutoff. The evidence plan should preserve those exclusions and classify them before reporting a representative result. A neat route average based on convenient vehicles should not become a corridor-wide capacity estimate merely because the dataset is large.

An operating trial should record dispatch and arrival management as well as travel. If appointments change, the evaluation should include vehicles that wait outside the gate or are rescheduled before departure. If terminal service improves, track whether vehicles actually return sooner and can undertake the next eligible movement. A shorter local dwell period may be valuable, but it is not equivalent to a greater sustained fleet flow unless the rest of the cycle permits that response.

A road intervention diagnosis should ask whether the service is constrained by vehicle circulation, terminal handling, route access, driver readiness or eligible demand. Each answer changes the candidate action. More vehicles address a circulation-resource limit only when drivers, terminals and routes can support them. Appointment changes address arrival mismatch only when service readiness is credible. Road works address a route condition only when that condition governs the declared service and the improved route remains accessible.

The intervention should carry a falsifier. If added vehicles increase queue length without increasing accepted receipt or resource return, fleet quantity has not demonstrated the expected system gain. If appointment discipline reduces terminal waiting but creates longer upstream holding, the end-to-end effect needs reassessment. If a road improvement increases permissible movement but demand remains lower, the physical benefit may not create additional service. These are testable mechanisms rather than generic statements that every improvement will optimise logistics.

A road-stage annual capacity can enter the canonical app after the separate cycle and operating analysis produces a coherent annual bound. The app then compares that bound with other serial stages. It cannot verify the derivation or simulate traffic, driver rosters and terminal queues. The practitioner should therefore retain the underlying record and review it when the route, vehicle mix or service promise changes. A copied annual input without its basis loses the information needed to judge whether the next comparison remains valid.

A useful truck diagnosis follows the resource that is actually scarce. In a hypothetical shift, vehicles return promptly but drivers cannot take their next admissible assignment; increasing the fleet does not relieve that driver-state limit. In another shift, drivers are ready but vehicles remain occupied at receipt; the candidate remedy lies at the terminal. A route restriction can defeat both branches even when vehicles and drivers are available. The collection instrument should retain these incomplete cycles and pair each with the next permissible assignment, rather than infer readiness from a vehicle arriving home. Comparing the branches identifies whether the design needs more circulation resources, better receipt or a different operating calendar, while preserving the safety and access conditions already established.