System and method for multi-vertical real time logistics coordination

The cloud-based logistics platform addresses inefficiencies in multi-industry logistics by automating job creation, load splitting, and compliance verification, achieving rapid coordination, enhanced compliance, and sustainable operations across construction, waste management, and refrigerated transport.

WO2026232192A1PCT designated stage Publication Date: 2026-11-12TIPPERTEC HOLDINGS PTY LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/AU2026/050450
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-05-07
Filing Date
2026-05-06
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

Existing logistics coordination systems across multiple industries like construction, waste management, and refrigerated transport face inefficiencies due to manual processes, leading to delays, errors, non-compliance, and cash flow issues, with existing solutions lacking real-time compliance checks, automated load splitting, and multi-vertical adaptability.

Method used

A cloud-based logistics platform that automates job creation, load splitting, driver matching, and compliance verification, integrating real-time GPS tracking, geofencing, and payment processing, with a dynamic load-splitting engine and machine learning for optimized load distribution across diverse industries, ensuring regulatory adherence and instant payments.

Benefits of technology

Reduces coordination time from hours to seconds, enhances compliance, improves cash flow, and ensures operational efficiency through automated workflows and real-time tracking, while supporting scalability and environmental sustainability metrics.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure AU2026050450_12112026_PF_FP_ABST
    Figure AU2026050450_12112026_PF_FP_ABST
Patent Text Reader

Abstract

A computer-implemented system (1000) and method (200) for coordinating road-transport logistics across construction, waste, refrigerated and freight verticals. A shipper client device (106) provides a job request specifying a pickup location, a delivery location and a quantity of material to a server of a computer system (102) over a network (104). A load-splitting engine partitions the job request into a plurality of load data files in dependence on truck capacity, material type and regulatory constraints. A matching engine assigns each load data file to a respective carrier client device (107) located in a carrier truck. A compliance module verifies driver licences, vehicle permits and certifications via external APIs in real time. A GPS-driven tracking module uses geofencing to automate job status updates and to calculate carbon emissions. WebSocket communication carries job offers, bid notifications and live location data between the server and the client devices (106, 107).
Need to check novelty before this filing date? Find Prior Art

Description

SYSTEM AND METHOD FOR MULTI-VERTICAL REAL TIME LOGISTICS COORDINATION Field of the Invention

[0001] The present invention relates to a system and method for system and method for multi-vertical real time logistics coordination and in particular to a method for system and method for multi-vertical real time logistics coordination for the construction, waste management, refrigerated transport and general freight industries.

[0002] The invention has been developed primarily for use in / with construction industry and will be described hereinafter with reference to this application. However, it will be appreciated that the invention is not limited to this particular field of use.Background of the Invention

[0003] There are significant inefficiencies in logistics coordination across multiple industries (construction, waste management, refrigerated transport, general freight), where manual processes — phone calls, emails, or paper-based scheduling — result in delays, errors, and non-compliance with regulatory requirements. Previously, coordinating trucks for large-scale material haulage (e.g., 1 ,000 tonnes of rubble) required site supervisors to manually contact multiple operators, track truck availability, verify compliance (e.g., licenses, permits), and handle payments off-platform, leading to fragmented workflows, high error rates, and cashflow delays for drivers. Existing solutions, such as basic dispatch software or marketplace platforms, lack real-time compliance checks, automated load splitting for diverse vehicle types, integrated payment / factoring, and multi-vertical adaptability, often focusing on single industries like construction or freight.

[0004] Any discussion of the background art throughout the specification should in no way be considered as an admission that such background art is prior art, nor that such background art is widely known or forms part of the common general knowledge in the field in Australia or any other country.Summary of the Invention

[0005] The invention seeks to provide a system and method for multi-vertical real time logistics coordination which will overcome or substantially ameliorate at least some of the deficiencies of the prior art, or to at least provide an alternative.

[0006] A preferred embodiment of the invention provides automating job creation, load splitting, driver matching, compliance verification, real-time tracking, and payment processing within a single platform, reducing coordination time from hours to seconds, ensuring regulatory adherence, and improving cash flow for operators through instant payment options.

[0007] The preferred embodiment of the invention provides a cloud-based logistics platform that automates the scheduling, dispatch, and tracking of trucks across multiple industries (construction, waste, refrigerated transport, freight). It uses a dynamic load-splitting engine to divide large jobs into optimized loads based on truck capacity, compliance, and route constraints. Real-time GPS tracking, geofencing, and WebSocket-driven notifications ensure transparency, while integrated compliance checks (e.g., license verification via APIs) and payment / factoring services streamline operations. A bidding system allows tip sites and carriers to set dynamic pricing, with the platform applying a service fee. The platform’s microservices architecture and machine learning enhance scalability and matching efficiency.

[0008] In its preferred embodiment the platform has many advantages including providing multi-vertical support. It handles diverse industries (construction, waste, refrigerated, freight) with tailored load and compliance requirements, unlike single-industry platforms.

[0009] The preferred embodiment of the platform provides automated compliance. It provides real-time verification of driver licenses, vehicle permits, and certifications via API integrations, reducing legal risks absent in manual or semi-automated systems.

[0010] The preferred embodiment of the platform provides integrated financial services. It offers payment processing and factoring (instant driver payments), addressing cash-flow delays not solved by competitors.

[0011] The preferred embodiment of the platform provides dynamic load splitting. It automatically divides jobs into optimized loads based on truck capacity, material type, and regulatory constraints, improving efficiency over manual splitting.

[0012] The preferred embodiment of the platform provides real-time workflow automation. It uses GPS, geofencing, and WebSockets for live tracking, status updates, and automated job completion, minimizing manual intervention.

[0013] The preferred embodiment of the platform provides scalable architecture. It provides cloud-native microservices and open APIs enable global deployment and integration with enterprise systems, unlike rigid legacy platforms.

[0014] The preferred embodiment of the platform provides environmental impact tracking. It provides logs of distance, time, and trips to calculate carbon emissions, offering unique sustainability analytics.

[0015] The preferred embodiment of the invention provides a cloud-based, multi-vertical logistics platform that automates the coordination, dispatch, and tracking of trucks for industries including construction, waste management, refrigerated transport, and general freight. It integrates advanced technical features such as dynamic load splitting, real-time compliance verification, GPS-driven workflow automation, payment processing with factoring, and a bidding system for tip sites and carriers. The platform operates on a microservices architecture with open APIs, WebSockets for real-time communication, and machine learning for optimised matching and pricing.

[0016] According to one aspect of the invention, there is provided a computer-implemented system for multivertical logistics coordination comprising a load-splitting engine configured to divide a job volume into optimized load files based on one or more of truck capacity, material type, waste type, job type, unit rate, and regulatory constraints. The system further includes a matching engine using machine learning to assign loads to drivers based on one or more of capacity, proximity, compliance, and performance. A compliance module is provided which integrates with external APIs to verify one or more of driver licenses, vehicle permits, and certifications in real time. The system also includes a payment module for processing driver payments via a third-party gateway. A GPS-driven tracking module with geofencing is configured to automate job status updates and calculate carbon emissions. A bidding module is provided that enables tip sites to set opening prices and receive bids from carriers, with a service fee applied to excess bids. The system operates using a microservices architecture with WebSockets to enable real-time communication. The system is further configured to coordinate logistics across vertical industries including one or more of construction, waste, refrigerated, and freight industries.

[0017] According to another aspect of the invention, the system further comprises a fixed and floating charge module that secures credit via vehicle assets, with such charges registered on a personal propertysecurities register. Electronic signatures required to execute and authorise the registrations are captured via a mobile application.

[0018] According to another aspect of the invention, the bidding module is configured to apply a service fee to carrier bids exceeding the tip site’s opening price, with all bids managed and presented via an administrative portal.

[0019] According to another aspect of the invention, the tracking module is configured to log distance travelled, time in transit, and trip counts in order to calculate CO2 emissions, the calculation being based on fuel type and consumption associated with the vehicle used.

[0020] According to another aspect of the invention, there is provided a method for coordinating multi-vertical logistics, the method comprising receiving a job request including volume, material, and location data; splitting the job into load files using a dynamic algorithm; matching the loads to drivers based on capacity, compliance, and proximity; verifying driver and vehicle compliance via real-time API queries; tracking job progress using GPS and geofencing; processing payments and offering payouts to drivers; and calculating carbon emissions based on route data and vehicle parameters.

[0021] According to another aspect of the invention, there is provided a logistics coordination system comprising a plurality of user interfaces including at least a shipper interface, a carrier interface, and a tip site interface, each configured to allow corresponding users to input, receive, and view logistics-related data. The system further includes a backend system configured to dynamically partition transport jobs into load assignments based on parameters including vehicle capacity, material type, and regulatory compliance. The backend system is further configured to automatically verify driver and vehicle compliance using real-time external data sources, to facilitate job bidding initiated by tip site operators and responded to by carriers (including automatic application of platform fees), to provide a financial service that enables instant payment to carriers with deferred recovery from shippers or tip site operators, and to track operational metrics to calculate estimated carbon emissions associated with completed jobs. The system also includes a communication layer operable to transmit real-time updates between the user interfaces and the backend system.

[0022] According to a further aspect of the invention, the backend system comprises a load allocation module that is configured to reallocate unaccepted or cancelled loads to alternate available carriers.

[0023] According to another aspect of the invention, compliance verification within the backend system is performed using APIs that are connected to external licensing, registration, or permit databases.

[0024] According to another aspect of the invention, the financial service is implemented through an integrated payment gateway and includes invoice generation, payout to the carrier, and delayed receivables collection from the contracting shipper or tip site operator.

[0025] According to another aspect of the invention, the tip site interface is configured to allow a tip site operator to set an opening bid price, with the backend system applying a service fee to final carrier bids that exceed the set price.

[0026] According to another aspect of the invention, the calculation of carbon emissions is based on one or more of the following parameters: distance travelled, fuel type, load weight, and vehicle class.

[0027] According to another aspect of the invention, the communication layer of the system utilises WebSocket technology to push real-time updates including job offers, bid notifications, and live location tracking.

[0028] According to another aspect of the invention, the user interfaces are configured to enable drivers to submit delivery confirmation using one or more of digital signatures, photographs, or geolocation data.

[0029] According to another aspect of the invention, the backend system includes a machine learning module configured to rank carriers based on one or more of the following: historical job completion data, compliance rate, bid responsiveness, or user feedback scores.

[0030] According to another aspect of the invention, the backend system is implemented using a cloud-native microservices architecture, allowing for the independent scaling and deployment of various backend modules.

[0031] According to a further aspect of the invention, there is provided a method of coordinating logistics operations, the method comprising receiving, via a user interface, a transport job request including at least a pickup location, drop-off location, material type, and volume or weight; partitioning the job into one or more load assignments based on truck capacity, compliance requirements, and material constraints; verifying in real time the compliance status of available carriers using external data sources relating to licensing, permits, and vehicle registrations; dispatching load offers to compliant carriers via a real-time communication channel; receiving acceptance or rejection of load offers and reallocating unaccepted loads to alternate carriers; where the transport involves a tip site, initiating a bidding process in which the tip site sets an opening bid price and carriers submit competitive offers; processing payment to the selected carrier upon confirmation of delivery, optionally via an instant payment and factoring service; recording operational data including distance, time, and load characteristics; and calculating estimated carbon emissions for the job based on the recorded operational data.

[0032] According to another aspect of the method, the step of partitioning the job includes applying rules to distinguish between transport jobs in different industry verticals, including but not limited to waste, construction, or refrigerated logistics.

[0033] According to another aspect of the method, the step of partitioning the job is performed using an adaptive job-partitioning algorithm. The optimisation routine dynamically sizes each load data file using live fleet capacities, legal axle limits and traffic density. This reduces server-side matchmaking loops and network chatter. This improves processor efficiency and lowers API call volume leading to better computer performance.

[0034] According to another aspect of the method, the step of verifying compliance comprises querying one or more third-party APIs for current driver license status, vehicle registration data, and permit validity.

[0035] According to another aspect of the method, the step of reallocating loads occurs automatically where no response is received from a carrier within a predetermined timeframe.

[0036] According to another aspect of the method, the bidding process includes applying a service fee to the final accepted carrier bid, the fee being calculated as a percentage above the tip site’s opening price.

[0037] According to another aspect of the method, delivery confirmation includes submission of one or more of timestamped photographs, digital signatures, and geolocation metadata via a mobile application.

[0038] According to another aspect of the method, the method further comprises registering a fixed or floating charge over a carrier’s vehicle asset through a secured electronic transaction, and recording the charge on a personal property register.

[0039] According to another aspect of the method, the carbon emissions calculation is based on fuel consumption profiles associated with vehicle class, load weight, and route characteristics.

[0040] According to another aspect of the method, the method further comprises ranking carriers using a machine learning algorithm, the ranking being based on one or more of job completion history, compliance records, and user feedback.

[0041] According to another aspect of the method, all backend processes are executed within a cloud-native microservices environment and communicate with user devices via WebSocket protocols.

[0042] According to another aspect of the invention there is provided a system for arranging the pickup of a predetermined volume of material from a first location and the delivery of the material to a second location, the system including: a first client device for receiving data for defining the first location, the second location and the predetermined volume of the material; a second client device for receiving data on a plurality of carrier trucks, the data including a volume capacity of each respective carrier truck; a processor for receiving the data from the first client device and the data from the second client device, the processor using the data to create a job data file that includes data on the number of carrier trucks required to pickup the predetermined volume of material, the processor further creating a plurality of load data files including the volume of material to be picked up by each carrier truck, one load data file being created for each required carrier truck wherein the processor further sends each respective load data file for each carrier truck to a plurality of third client devices located in each respective carrier truck.

[0043] Preferably the first client device further receives a plurality of attributes of the material to be picked up. Preferably the second client device further received a plurality of attributes of each respective carrier truck. Preferably the sum of the volume of material to be picked up by each carrier truck is equal to the predetermined volume of material. Preferably at least one third client device located in each respective carrier truck is sent more than one load data file to thereby complete consecutive pickup and delivery of material equal to the number of load data files received. Preferably the volume of material that each carrier truck can carry is different from at least one other carrier truck. Preferably the load data file further includes the first location and the second location. Preferably a driver in each respective carrier truck can accept the load details received at the respective third client device and if accepted the third client device sends an accept data file to thee processor to initiate the load job for that carrier truck. Preferably the driver in each respective carrier truck can reject the load details received at the respective third client device wherein upon rejection the third client device sends a reject data load file to the processor and wherein the processor upon receiving the reject data load file creates a further load a data file and sends this to another third client device located in another carrier truck.

[0044] According to another aspect of the invention there is provided a computer-implemented method for arranging the pickup of a predetermined volume of material from a first location and delivery of the material to a second location, the computer-implemented method comprising the steps of: receiving from a user on a client device the predetermined volume of material, the first location and the second location; receiving from the user on the client device the attributes of at least one carrier truck to pickup the material, the attributes including at least the volume capacity of the at least one carrier truck; the client device forwarding data received from the client device to a processor, the processor using the data received from the client device to create a job data file including a determination of the number of carrier trucks required to pickup and deliver the predetermined volume of material from the first location to the second location, the processor further creating a plurality of load data files each load data file including the volume of material to be picked up by each respective carrier truck, one load data file being created for each required carriertruck and wherein the processor further sends each respective load data file for each carrier truck to a plurality of carrier client devices located in each respective carrier truck.

[0045] Preferably the one or more client devices are selected from a group comprising smartphones and tablets having at least a camera, a microphone and a Global Positioning System (GPS). Preferably the computer-implemented method further comprising the step of receiving and tracking the one or more locations of the one or more carrier trucks, thereby tracking the location of the one or more carrier trucks.

[0046] According to another aspect of the invention there is provided a computer system comprising: a memory unit configured to store machine-readable instructions; and a processor operably connected with the memory unit, the processor obtaining the machine-readable instructions from the memory unit and being configured by the machine-readable instructions to implement the method as described above.

[0047] It should be noted that the web server, client computing device and the computer readable storage medium provide the same or similar advantages as the advantages provided by the corresponding computer implemented method, some of which are described herein. Additionally, the web server and / or client computing device provides the advantage of deployment across a computer network, such as the Internet, providing distribution, access and economy of scale advantages. Furthermore, the computer readable storage medium provides further advantages, such allowing the deployment of computer instructions for installation and execution by one or more computing devices.

[0048] According to another aspect of the invention there is provided a computer-implemented system for coordinating road-transport of material between a pickup location and a destination, the system comprising: (a) a server in network communication with (i) a shipper client device, (ii) a plurality of carrier client devices each associated with a respective carrier vehicle, and (iii) at least one tip-site client device; (b) a database storing, for each of a plurality of loads, a load record that includes (i) a load identifier, (ii) a state value drawn from an enumerated state set comprising at least an OFFERED state, an ACCEPTED state, an IN-TRANSIT state and a TIPPED state, and (iii) a current revision token; (c) a load-partitioning module configured to receive, from the shipper client device, a job request specifying a quantity of material, the pickup location and the destination, and to generate from the job request a plurality of load data files each defining a respective one of the loads in dependence upon (i) a vehicle volume capacity associated with one of the carrier client devices, (ii) one or more regulatory constraints applicable to the material, and (iii) a vehicle attribute received from the carrier client device; (d) a publish-subscribe communication channel between the server and each of the carrier client devices, in which each carrier client device maintains a persistent subscription to the server and the server publishes load data files to the carrier client devices over the subscription only on the occurrence of a state-change event, such that the carrier client devices do not poll the server for load data; (e) an idempotent state-transition interface exposed by the server, configured to receive from a carrier client device a state-transition request comprising (i) the load identifier, (ii) a requested state value drawn from the enumerated state set, and (iii) a revision token previously issued by the server in respect of the load identifier; the server being configured to apply the requested state transition to the corresponding load record only when the received revision token matches the current revision token in the database, and on each successful transition to atomically update the current revision token in the database and to return an updated revision token to the carrier client device; (f) a geofence engine configured to transmit to each of the carrier client devices, in respect of an assigned load, geofence polygon data defining at least one of the pickup location and the destination, thecarrier client device being configured to evaluate locally, using a position signal obtained from a positioning sensor of the carrier client device, whether the carrier vehicle has entered or exited a geofence defined by the polygon data, and to transmit to the server, over the publish-subscribe channel, only a geofence statechange event, the geofence state-change event being formatted as a state-transition request to the idempotent state-transition interface; and (g) a compliance verification module configured, prior to the server publishing a load data file to a carrier client device under (d), to issue a non-blocking compliance request to one or more external compliance data sources via an asynchronous worker pool, the server releasing a request-handling thread upon dispatch of the compliance request and resuming processing of the request asynchronously upon receipt of a compliance response via a callback, the load data file being published only on receipt of a compliance response indicating that the carrier client device satisfies one or more applicable regulatory criteria; wherein, on the occurrence of a network-induced retransmission or duplication of a state-transition request received from a carrier client device, the idempotent state-transition interface causes the corresponding load record to converge to a single canonical state independent of the order or multiplicity of receipt of those requests.

[0049] Preferably the load-partitioning module further generates the load data files in dependence upon a vertical-specific attribute injected at runtime from a JSON schema registry, the database storing all load records against a single underlying table irrespective of the vertical to which the load belongs. Preferably the system further comprising a blockchain-anchoring module configured to hash a plurality of statetransition events occurring within a rolling time window into a Merkle tree and to commit only the resulting root hash of the Merkle tree to a blockchain network. Preferably the load-partitioning module is further configured to use a trained machine-learning model to rank the carrier client devices by reference to historical completion data, historical compliance data and feedback data stored in the database, and to generate the load data files in dependence upon the ranking. Preferably the geofence state-change event under (f) causes the idempotent state-transition interface to transition the corresponding load record from the IN-TRANSIT state to the TIPPED state without further user input. Preferably the database further stores, in respect of each load record, a vertical identifier drawn from a set comprising at least construction, waste, refrigerated and general freight, and the load-partitioning module applies a vertical-specific regulatory constraint set to the partitioning under (c) in dependence upon the vertical identifier.

[0050] According to another aspect of the invention there is provided a computer-implemented method of coordinating road-transport of material between a pickup location and a destination, the method being performed by a server in communication with a shipper client device, a plurality of carrier client devices and at least one tip-site client device, the method comprising: (a) receiving from the shipper client device a job request specifying a quantity of material, a pickup location and a destination, and partitioning the job request into a plurality of load data files each in dependence upon a vehicle volume capacity, one or more applicable regulatory constraints, and at least one vehicle attribute received from a carrier client device; (b) for each load, storing in a database a load record comprising a load identifier, a state value drawn from an enumerated state set comprising at least OFFERED, ACCEPTED, IN-TRANSIT and TIPPED, and a current revision token; (c) issuing, prior to publication of a load data file to a carrier client device, a non-blocking compliance request to one or more external compliance data sources via an asynchronous worker pool, releasing a request-handling thread upon dispatch and resuming asynchronously on receipt of a compliance response via a callback; (d) publishing the load data file to the carrier client device over apersistent publish-subscribe channel only on receipt of a compliance response indicating compliance, and only on the occurrence of a state-change event; (e)transmitting to the carrier client device geofence polygon data defining at least one of the pickup location and the destination, and receiving from the carrier client device only a geofence state-change event evaluated locally by the carrier client device against a position signal obtained from a positioning sensor; (f) exposing an idempotent state-transition interface that receives from a carrier client device a state-transition request comprising the load identifier, a requested state value and a revision token previously issued by the server, applying the requested state transition to the corresponding load record only when the received revision token matches the current revision token in the database, and atomically updating the current revision token in the database upon each successful transition; (g) on receipt of a duplicated or out-of-order state-transition request, returning the load record to a single canonical state independent of the order or multiplicity of receipt of those requests.

[0051] Other aspects of the invention are also disclosed.Brief Description of the Drawings

[0052] Notwithstanding any other forms which may fall within the scope of the present invention, a preferred embodiment of the invention will now be described, by way of example only, with reference to the accompanying drawings in which:

[0053] Figure 1 shows a network of computing devices on which the various embodiments described herein may be implemented in accordance with an embodiment of the present invention;

[0054] Figure 2 shows a computing device on which the various embodiments described herein may be implemented in accordance with an embodiment of the present invention;

[0055] Figure 3 shows a schematic diagram of a blockchain network;

[0056] Figure 4 shows a schematic diagram of a system and method for multi-vertical real time logistics coordination, including software modules preferably used by the system and method for multi-vertical real time logistics coordination;

[0057] Figure 5 is an exemplary environment of computing devices to which the various embodiments described herein may be implemented;

[0058] Figure 6 illustrates computer-implemented method for pickup and delivery of material and creation of job data files and load data files, in accordance with an embodiment of the present invention;

[0059] Figure 7 illustrates an information flow diagram for sending and receiving load data files to a carrier truck client device, in accordance with an embodiment of the present invention; and

[0060] Figure 8 illustrates an information flow diagram for sending and receiving a job data file to a user device, in accordance with an embodiment of the present invention.Description of Embodiments

[0061] It should be noted in the following description that like or the same reference numerals in different embodiments denote the same or similar features.System of computing devices

[0062] Figure 1 shows a system 1000 of computing devices adapted for use as an system and method for multi-vertical real time logistics coordination, and on which the methods described below may be carried out.

[0063] As such, the system 1000 includes a server 1100 for serving web pages to one or more client computing devices 1200 over the Internet 1300.

[0064] In a preferred embodiment, the server 1100 is a web server having a web server application 1110 for receiving requests, such as Hypertext Transfer Protocol (HTTP) and File Transfer Protocol (FTP) requests, and serving hypertext web pages or files in response. The web server application 1110 may be, for example the Apache™ or the Microsoft™ IIS HTTP server.

[0065] The server 1100 is also provided with a hypertext preprocessor 1120 for processing one or more web page templates 1130 and data from one or more databases 1140 to generate hypertext web pages. The hypertext preprocessor may, for example, be the PHP: Hypertext Preprocessor (PHP) or Microsoft Asp™ hypertext preprocessor. The web server 1100 is also provided with web page templates 1130, such as one or more PHP or ASP files.

[0066] Upon receiving a request from the web server application 1110, the hypertext preprocessor 1120 is operable to retrieve a web page template from the web page templates 1130, execute any dynamic content therein, including updating or loading information from the one or more databases 1140, to compose a hypertext web page. The composed hypertext web page may comprise client-side code, such as Javascript, for Document Object Model (DOM) manipulating, asynchronous HTTP requests and the like.

[0067] The database 1140 is adapted for storing user account data representing one or more user accounts for users. Such user account data is created by the server 1100 during a user registration process. In this manner, the server 1100 is adapted to update the user account data in relation to the appropriate user account.

[0068] The server 1100 will be connected to a verifiable data registry such a blockchain network 1500 including a plurality of nodes 1510 in which the data stored in server 1100 will be preferably replicated by each node in the blockchain. The server will preferably be connected to the blockchain network 1500 via a universal resolver node on the blockchain network.

[0069] Blockchain nodes can be located on any kind of device (mostly computers, laptops or even bigger servers). All nodes on a blockchain are preferably connected to each other and they constantly exchange the latest blockchain data with each other so that all nodes stay up to date. The nodes store, spread and preserve the blockchain data. A full node contains a full copy of the transaction history of the blockchain. Nodes check if a block of transactions is valid and accept or reject it. Nodes save and store blocks of transactions to store the blockchain transaction history. Nodes broadcast and spread this transaction history to other nodes that may need to synchronize with the blockchain transaction history.

[0070] A blockchain node is typically implemented as a service to provide an Application Programming Interface (API) for inter-node communication as well as client-node communication. The APIs are typically implemented as Remote Procedure Call (RPC) over HTTP or WebSocket, including JSON-RPC, gRPC with Protocol Buffers (Protobuf) and the like. Blockchain nodes may include miner nodes, full nodes, hidden nodes, listening nodes and lightweight nodes.

[0071] It is anticipated that a wide variety of alternative verifiable data registries as discussed above may be used instead of a blockchain. However, in the embodiments described a blockchain is used to exemplify the concept of a verifiable data registry. Using a blockchain as a verifiable data registry has the additional benefit of being immutable.

[0072] Each node 1510 in the blockchain network may be a server 1100 or similar computing device as will be described below. Each node in the blockchain network will preferably be represented and / or managed by a separate provider.

[0073] Client computing devices 1200 are preferably provided with a browser application 1210, such as the Google Chrome™, Mozilla Firefox™ or Microsoft Internet Explorer™ browser applications. The browser application 1210 requests hypertext web pages from the web server 1100 and renders the hypertext web pages on a display device for a user to view.

[0074] Client side code is also downloadable as applications on the client computing device 1200 and / or server 1100, in order to facilitate the operation of and / or interaction with the system and method for multivertical real time logistics coordination. Such applications could, for example, be downloaded from the Apple App Store™, Google Play™, or the like.

[0075] Client side code may also be provided as blockchain enabled code for suitable users of the system. Such blockchain enabled code may be configured for reading and writing directly to a node of the blockchain, or for communicating via a remote node such as a universal resolver node.

[0076] Client computing devices 1200 may communicate over the Internet 1300 via fixed line or wireless communication, for example using known networks of cellular communication towers 1400.

[0077] Further, as shown in figure 3, a verifiable data registry in the form of blockchain network 1500 is shown as an interconnected network of servers 1100, preferably connected overthe Internet 1300 of nodes. Alternate computing devices could also be used as a node of a blockchain.

[0078] As each block of the blockchain is formed, the block is replicated identically over each or most of the node in the blockchain. If any one of the ledgers is interfered with or altered, this may be easily checked by comparison to the rest of the ledgers. As mentioned previously, each of the servers may be connectable to the Internet and may be accessed by personal computing devices 1200, for example via wireless cellular communication towers 1400. Alternately the blockchain network may be accessed through a universal resolver node on the blockchain network.Computing device

[0079] Figure 2 shows a computing device 500. In a preferred embodiment, the computing device 500 takes the form of a server 1100 as described above. In this manner, the computing device 500 is adapted to comprise functionality for communication with the Internet 1300, storage capability (such as the database 1140) for storing user account data, records of communications, and the like.

[0080] However, it should be noted that the computing device 500 may be adapted for use as the client computing devices 1200 as is also shown in Figure 1. In this manner, the computing device 500 may comprise differing technical integers in order to achieve the functionality as set out below.

[0081] In other words, the technical integers of the computing device 500 as shown in Figure 2 are exemplary only and variations, adaptations and the like may be made thereto within the purposive scope of the embodiments described herein and having regard for the particular application of the computing device 500.

[0082] In particular the steps of the system and method for multi-vertical real time logistics coordination, as described in further detail below, can be implemented as computer program code instructions executable by the computing device 500.

[0083] The computer program code instructions may be divided into one or more computer program code instruction libraries, such as dynamic link libraries (DLL), wherein each of the libraries performs a one or more steps of the method. Additionally, a subset of the one or more of the libraries may perform graphical user interface tasks relating to the steps of the method.

[0084] The computing device 500 preferably comprises semiconductor memory 510 comprising volatile memory such as random access memory (RAM) or read only memory (ROM). The memory 510 may comprise either RAM or ROM or a combination of RAM and ROM.

[0085] The computing device 500 comprises a computer program code storage medium reader 515 for reading the computer program code instructions from computer program code storage media 520. The storage media 520 may be optical media such as CD-ROM disks, magnetic media such as floppy disks and tape cassettes or flash media such as USB memory sticks.

[0086] The device further comprises I / O interface 530 for communicating with one or more peripheral devices. The I / O interface 530 may offer both serial and parallel interface connectivity. For example, the I / O interface 530 may comprise a Small Computer System Interface (SCSI), Universal Serial Bus (USB) or similar I / O interface for interfacing with the storage medium reader 515. The I / O interface 530 may also communicate with one or more human input devices (HID) 540 such as keyboards, pointing devices, joysticks and the like.

[0087] The I / O interface 530 may also comprise a computer to computer interface, such as a Recommended Standard 232 (RS-232) interface, for interfacing the device 500 with one or more personal computer (PC) devices 550. The I / O interface 530 may also comprise an audio interface 560 for communicate audio signals to one or more audio devices (not shown), such as a speaker or a buzzer.

[0088] The device 500 also comprises a network interface 570 for communicating with one or more computer networks 580, such as the Internet 1300. The network 580 may be a wired network, such as a wired EthernetTM network or a wireless network, such as a BluetoothTM network or IEEE 802.11 network. The network 580 may be a local area network (LAN), such as a home or office computer network, or a wide area network (WAN), such as the Internet or private WAN. The device 500 can also include an antenna 575 configured for wireless communication with network 580.

[0089] The device 500 comprises an arithmetic logic unit or processor 590 for performing the computer program code instructions. The processor 590 may be a reduced instruction set computer (RISC) or complex instruction set computer (CISC) processor or the like. The computing device 500 further comprises a storage device 600, such as a magnetic disk hard drive or a solid state disk drive for storing data and / or software instructions.

[0090] Computer program code instructions may be loaded into the storage device 600 from the storage media 520 using the storage medium reader 515 or from the network 580 using network interface 570. Alternatively, computer program code instructions may be loaded into the storage device 600 from an online resource via the network 580 and network interface 570.

[0091] During the bootstrap phase, an operating system and one or more software applications are loaded from the storage device 600 into the memory 510. During the fetch-decode-execute cycle, the processor 590 fetches computer program code instructions from memory 510, decodes the instructions into machine code, executes the instructions and stores one or more intermediate results in memory 510.

[0092] In this manner, the instructions stored in the memory 510, when retrieved and executed by the processor 590, configures the computing device 500 as a special-purpose machine that may perform the functions described herein.

[0093] The computing device 500 can also include an audio / video interface 610 for conveying video signals to a display device 620, such as a liquid crystal display (LCD), light emitting diode (LED) display, organic light emitting diode (OLED) display, cathode-ray tube (CRT) or similar display device.

[0094] The device 500 preferably includes a communication bus subsystem 630 for interconnecting the various devices described above. The bus subsystem 630 may offer parallel connectivity such as Industry Standard Architecture (ISA), conventional Peripheral Component Interconnect (PCI) and the like or serial connectivity such as PCI Express (PCIe), Serial Advanced Technology Attachment (Serial ATA) and the like. The computing device 500 can also include a clock device 640 configured for providing accurate time stamps for use by the processor 590.

[0095] Preferably the client computing device that is operable by a user of the system and method for multivertical real time logistics coordination will by a mobile device such as a mobile phone, laptop, tablet or similar device and will have a near filed communications (NFC) chip 650 installed, which may operate in conjunction with a suitable NFC antenna 660 in order to transmit and receive signals using the NFC protocol. Such an NFC chip 650 and antenna 660 can receive NFC or similar electromagnetic signals from similarly equipped devices. In alternative embodiments it is envisage that alternative protocols may be used where NFC is mentioned in describing the functionality below, such as Bluetooth™, or any of the IEEE802.11 protocols, however these are not preferred.

[0096] It is further anticipated that the computing device can include a physical random number generator 670. However, in alternative embodiments it is envisaged that the random number generator may be provided as part of a software module.

[0097] Lastly, it is anticipated that the computing device 500 can include a camera 680. The camera can be used to scan and / or input documents. The camera 680 may be connected via the I / O interface 530 or may be built into the computing device.S YS TEM A ND METHOD FOR MUL Tl- VER TICA L REA L TIME L OG / S TICS COORD / NA NON

[0098] An embodiment of a SYSTEM AND METHOD FOR MULTI-VERTICAL REAL TIME LOGISTICS COORDINATION is shown in figures 4, showing a schematic diagram of the various devices, and systems, together with their software modules. Preferably, communications between the various devices and / or systems are over a secure communications network.

[0099] The system architecture is designed to support a comprehensive logistics platform comprising mobile applications, a web portal, robust backend logic, and a set of integrated microservices. The mobile applications serve three primary user groups. The Driver / Carrier App enables drivers to manage their availability, accept or reject job offers, navigate routes via the Google Maps API, and submit delivery proof using photos, digital signatures, and geotags. It also includes real-time notifications and a bidding interface for jobs posted by tip sites. The Shipper App allows users to create transport jobs by specifying pickup and drop-off addresses, material types, volumes or weights, and preferred schedules. This app also provides real-time tracking, price estimates, and automated invoice generation. The Tip Site App is a dedicated interface that lets waste disposal sites post jobs with configurable bid prices, review carrier bids, and uploadnecessary regulatory documents such as Section 143 EPA certificates. Each post supports a single waste type and date selection.

[0100] The web portal offers both shippers and tip sites a centralized dashboard to manage jobs, monitor progress, and access analytics. Underpinning all interfaces is a powerful backend / server logic layer. The Job Coordination and Matching Engine uses proximity, vehicle compliance, capacity, and equipment type to match jobs with suitable drivers, incorporating machine learning to rank driver performance. The Load Allocation Module dynamically splits large jobs into smaller loads based on truck capacities, reassigning them as needed. A Compliance Module interfaces with third-party APIs like Equifax and RMS to validate licenses and registrations in real time. The Payment and Factoring Module, integrated with Stripe, manages invoicing and allows drivers to receive instant payments for a fee, with Tipaload recovering the funds from customers later. Real-time communication is enabled through WebSockets, delivering push notifications and live GPS data. A centralized database stores job records, load data, user profiles, compliance logs, and transaction histories, while an Analytics Engine tracks KPIs, estimates carbon emissions, and predicts pricing and routing based on historical trends.

[0101] The platform supports several microservices and integrations, such as APIs for fleet management and project software, PPSR for charge registration against vehicles, and the Weather Channel API to aid in scheduling. User interaction is monitored through Google Analytics. The operational flow is divided into six functional stages. During onboarding, users register with business and licensing information, while drivers activate tracking by toggling their availability. In the job creation phase, shippers specify job details which are then split into load files, and tip sites can post jobs with set bid prices. Dispatch and matching involve the algorithm assigning loads to compliant, nearby, and appropriately equipped drivers who can accept or reject offers in real time. The pickup and transit phase features live GPS tracking and geofencing that auto-updates job statuses. During unloading and delivery confirmation, drivers provide proof of delivery, while tip sites upload compliance documents. Finally, the rating, payment, and analytics stage sees mutual user reviews, automated invoice generation, driver factoring, and ongoing performance and emissions tracking.

[0102] Technically, the system includes key features such as dynamic load splitting, API-driven real-time compliance checks, a flexible bidding mechanism, GPS-based geofencing, seamless Stripe payments, and environmental impact logging. It also includes PPSR-based financial security mechanisms for vehiclebased credit. The platform relies on modern hardware and software, utilizing smartphones with GPS and internet access, cloud infrastructure (AWS or Google Cloud), and backend systems built with Node.js or Python. Real-time capabilities are achieved via WebSocket, and machine learning models enhance job matching and pricing efficiency.

[0103] The present invention provides numerous technical and commercial advantages over existing logistics coordination systems. Chief among these is operational efficiency, as the invention automates traditionally manual tasks such as job dispatch, load allocation, and documentation, reducing coordination times from several hours to mere seconds. The system also offers robust compliance assurance, with realtime verification of driver credentials, vehicle registrations, and required permits via third-party integrations, thereby significantly mitigating legal and regulatory risk. Architected as a cloud-native platform, the invention is inherently scalable, capable of supporting deployment across diverse industries and international markets without compromising performance. Enhanced transparency is achieved throughcontinuous GPS tracking and geofencing mechanisms, enabling real-time visibility of transport activity for all stakeholders, including shippers, carriers, and disposal site operators. Furthermore, the system incorporates financial innovation by integrating payment processing and factoring capabilities, thereby addressing common cash flow challenges experienced by independent drivers and smaller carriers. A further advantage is the system’s focus on environmental sustainability, as it continuously monitors and logs carbon emissions data, supporting environmentally conscious decision-making and regulatory reporting. Finally, the invention improves usability by providing role-specific interfaces tailored to the operational needs of shippers, carriers, and tip site personnel, ensuring an intuitive and efficient user experience across the entire supply chain.

[0104] In the preferred embodiment the geofencing uses edge-cached geofence evaluation. Geofence polygons are shipped once to each driver app and evaluated locally. Only a state-change (enter / exit) is sent upstream. This reduces server CPU load and mobile data usage.

[0105] The invention advantageously provides an integration of several distinct and technically advanced components that collectively redefine the operational framework of digital logistics platforms. Notably, it introduces a multi-vertical load splitting engine capable of dynamically partitioning transport jobs across varied industry sectors — such as construction, waste management, and refrigerated logistics — based on contextual parameters including truck capacity, material classification, and compliance requirements. This is combined with automated compliance verification, wherein real-time API integrations are embedded directly into the dispatch workflow to validate licenses, permits, and vehicle registrations, ensuring regulatory adherence at the point of transaction. A further aspect of novelty resides in the integration of a factoring module, enabling instant driver payments within the platform — a financial functionality not commonly embedded in conventional logistics systems. The invention also incorporates a tip site bidding system, wherein disposal sites set opening bid prices and carriers competitively respond, with the system automatically applying platform fees (e.g., 1% to tip sites and 20% to carrier bids), thereby streamlining the pricing and fulfillment of waste and material transport tasks. In addition, the system features environmental analytics, continuously tracking operational metrics such as distance, duration, and trip frequency to calculate CO2emissions, supporting data-driven sustainability initiatives. Another novel feature is the credit security mechanism, wherein fixed and floating charges are registered against vehicle assets on the Personal Property Securities Register (PPSR) using in-app electronic signatures. These innovations are tightly integrated within a cloud-native, microservices-based architecture that employs WebSocket communication for real-time updates and machine learning algorithms for intelligent dispatch and pricing together constituting a significant advancement.

[0106] A further feature of an embodiment of the invention provides event-driven push architecture. The back-end publishes loads via WebSockets / Firebase rather than polling. Carrier devices maintain a lightweight subscription channel that wakes only on relevant events. This advantageously cuts idle CPU cycles and bandwidth on both server and device.

[0107] In one embodiment the step of partitioning the job is performed using an adaptive job-partitioning algorithm. The optimisation routine dynamically sizes each load data file using live fleet capacities, legal axle limits and traffic density. This reduces server-side matchmaking loops and network chatter. This improves processor efficiency and lowers API call volume leading to better computer performance.

[0108] A further feature of an embodiment of the invention provides an asynchronous credit-risk microservice pipeline. Using this feature risk calls (using systems such as Equifax and CreditorWatch) are queued in a non-blocking worker pool; the main request thread releases instantly and is resumed by callback, avoiding thread starvation. This demonstrates improved concurrency handling and lower request latency.

[0109] One embodiment of the present invention aims to provide advantages in increasing efficiency in scheduling carrier trucks in the case of a builder or construction workers and finding work in the case of the truck owner and truck driver. Those ordering carrier trucks, also called dump trucks or dumper trucks, to pickup and drop off material can choose to the type of truck they require at each particular work site. The type of truck can vary in accordance with truck sizes, load sizes and number of trips required. Those ordering trucks can also request different payment methods being hourly hire, load or tonne rate, short or long hauls. Truck owners, drivers or fleet owners can more efficiently schedule load jobs in and ensure more efficient usage of trucks. The system can also match available trucks with one off or recurring jobs to ensure better utilisation.

[0110] In a preferred embodiment of the invention there is provided a system for arranging the pickup of a predetermined volume of material from a first location and the delivery of the material to a second location. The system includes a first client device for receiving data for defining the first location, the second location and the predetermined volume of the material. The system includes a second client device for receiving data on a plurality of carrier trucks, the data including a volume capacity of each respective carrier truck. A processor is provided for receiving the data from the first client device and the data from the second client device, the processor using the data to create a job data file that includes data on the number of carrier trucks required to pickup the predetermined volume of material. The processor further creates a plurality of load data files including the volume of material to be picked up by each carrier truck, one load data file being created for each required carrier truck. The processor further sends each respective load data file for each carrier truck to a plurality of third client devices located in each respective carrier truck. In this way the data file received at each carrier truck is customised to provide load details forthat carrier truck ensuring that the carrier truck received instructions for required load that each carrier truck must pickup and deliver. This also allows each carrier truck to pickup a different amount of material according to it's capacity or available space (if pickup up multiple loads at the same time) and take the material to the same location as the other carrier trucks or a different location for drop off and dumping if necessary.

[0111] The first client device provides a user interface to receive from the user of that device a plurality of attributes of the material to be picked up from the user. This includes the volume of material and the type of material for example sand, gravel, demolition waste, hazardous waste and the like.

[0112] The second client device provides a user interface to receive from the user of that device a plurality of attributes of each respective carrier truck. This includes the volume capacity of the carrier truck and other attributes type of truck such as standard dump truck, semi trailer end dump truck, transfer dump truck, truck and pup, superdump truck, semi trailer bottom dump truck, double and triple trailer bottom dump truck, side dump truck, roll-off trucks, truck size, wheel base size and the like. Accordingly, the volume of material that each type of carrier truck can carry is generally different from the other types other carrier trucks.

[0113] As would be understood the processor creates load data files such that the sum of the volume of material to be picked up by each carrier truck is equal to the predetermined volume of material as defined in the job data file which is also equal to the information defined by the creator of the job.

[0114] Each carrier truck includes a third client device that can receive or more load data file to thereby complete consecutive pickup and delivery of material equal to the number of load data files received. As would be understood, the load data file received at each carrier truck third client device also includes the first pickup location and the second drop off location. Upon receipt of the load data file at the third client device each respective carrier truck can accept the load details received at the respective third client device and if accepted the third client device sends an accept data file to the processor to initiate the load job for that carrier truck. The driver in each respective carrier truck can choose to reject the load details received at the respective third client device wherein upon rejection the third client device sends a reject data load file to the processor and wherein the processor upon receiving the reject data load file creates a further load a data file and sends this to another third client device located in another carrier truck. In this way truck drivers can accept and reject job loads according to their availability. If a driver accepts a job then the carrier truck device (third client device) notifies the system processor which then can update the job data file that that particular load has been accepted. If a job load has been rejected or refused then the carrier truck device notifies the system processor which then updates the job data file that a particular load has been rejected. The system processor then creates a new load data file and sends this to another carrier truck device, either one that was not previously offered a job or alternatively it offers a second or subsequent load to an already allocated carrier truck. This can be done according to the time allowed on the job and if there is sufficient time for the carrier truck to pickup and drop off the load and get back to the pickup site again for a subsequent load.

[0115] Another preferred embodiment provides a computer-implemented method for arranging the pickup of a predetermined volume of material from a first location and delivery of the material to a second location. The computer-implemented method comprising the steps of: receiving from a user on a client device the predetermined volume of material, the first location and the second location; receiving from the user on the client device the attributes of at least one carrier truck to pickup the material, the attributes including at least the volume capacity of the at least one carrier truck; the client device forwarding data received from the client device to a processor, the processor using the data received from the client device to create a job data file including a determination of the number of carrier trucks required to pickup and deliver the predetermined volume of material from the first location to the second location, the processor further creating a plurality of load data files each load data file including the volume of material to be picked up by each respective carrier truck, one load data file being created for each required carrier truck and wherein the processor further sends each respective load data file for each carrier truck to a plurality of carrier client devices located in each respective carrier truck.

[0116] The one or more client devices are selected from a group comprising smartphones and tablets having at least a camera, a microphone and a Global Positioning System (GPS).

[0117] The computer-implemented method further comprising the step of receiving and tracking the one or more locations of the one or more carrier trucks, thereby tracking the location of the one or more carrier trucks.

[0118] Another preferred embodiment provides system for arranging the pickup of a predetermined volume of material from a first location and the delivery of the material to a second location. The system includes a first client device configured to receive data defining the first location, the second location, and the predetermined volume of material to be transported. A second client device is also provided, which is configured to receive data on a plurality of carrier trucks. This data includes the volume capacity of each respective carrier truck and may include additional attributes such as the type of material the carrier truck is licensed to carry and applicable regulatory constraints. The system further includes a processor in communication with both the first and second client devices. The processor is configured to receive the data from both client devices and to use this data to generate a job data file. The job data file includes a determination of the number of carrier trucks required to pick up the predetermined volume of material. The processor then creates a plurality of load data files, with each file specifying the volume of material to be picked up by a respective carrier truck. One load data file is created for each carrier truck, and the processor transmits these files to third client devices located within each respective carrier truck. The system is further configured such that the first client device also receives a plurality of attributes relating to the material to be picked up, while the second client device receives various attributes of each respective carrier truck. The processor uses this information to divide the job into optimised loads, taking into account the attributes of the material, the volume capacity of the carrier trucks, and relevant regulatory constraints. The processor is also operable to verify licenses, permits, and carrier truck status through integrations with external APIs. Each carrier truck includes a GPS device in communication with the processor, allowing the system to track the routes taken by the carrier trucks for analytics purposes, including the calculation of CO2emissions.

[0119] In one embodiment, the sum of the volumes of material allocated to be picked up by each carrier truck is equal to the predetermined volume of material specified for transport. In a further embodiment, at least one third client device located in a respective carrier truck may receive more than one load data file, allowing the driver of that truck to complete consecutive pickups and deliveries of material corresponding to the number of load data files received. In another embodiment, the volume of material that each respective carrier truck is able to carry may differ from that of at least one other carrier truck, thereby allowing the system to optimise load distribution based on differing truck capacities. In an additional embodiment, each load data file may further include data specifying both the first location (pickup location) and the second location (delivery location), enabling the driver to access full job details through the third client device. In yet another embodiment, the driver of each respective carrier truck is able to accept the load details received via the third client device. Upon acceptance, the third client device sends an accept data file to the processor, which then initiates the load job for that specific carrier truck. In a related embodiment, the driver of each respective carrier truck is also able to reject the load details received on the third client device. Upon such rejection, the third client device sends a reject data load file to the processor. The processor, upon receiving this rejection, creates a new load data file and sends it to another third client device located in a different carrier truck.

[0120] In another embodiment of the invention there is provided a computer-implemented method for arranging the pickup of a predetermined volume of material from a first location and the delivery of the material to a second location. The method includes the step of receiving, from a user on a client device, the predetermined volume of material, the first location, and the second location. It further includes the stepof receiving, from the user on the client device, the attributes of at least one carrier truck designated to perform the pickup. These attributes include at least the volume capacity of the truck. The client device forwards this data to a processor, which uses it to create a job data file that includes a determination of the number of carrier trucks required to perform the transport. The processor also creates a plurality of load data files, each specifying the volume of material to be picked up by a respective carrier truck. One load data file is created for each required carrier truck, and each file is transmitted to a carrier client device located within the respective truck. The processor is further configured to divide the job into optimised loads based on the attributes of the material, the volume capacity of the truck, and any relevant regulatory constraints. The processor additionally verifies the licenses, permits, and operational status of each carrier truck via API integrations.

[0121] In one implementation of the above-described method, the one or more client devices used by users are selected from a group comprising smartphones and tablets, each of which is equipped with at least a camera, a microphone, and a Global Positioning System (GPS) module. In a further implementation, the method includes the step of receiving and tracking the locations of one or more carrier trucks during job execution. The processor is configured to monitor and track the truck routes in real time, enabling the generation of analytics data that includes, among other things, CO2emission calculations based on the distance travelled.

[0122] Figure 5 illustrates an exemplary environment 100 of computing devices to which the various embodiments described herein may be implemented. Figure 1 illustrates one or more client devices 106, 1061 ...106n associated with one or more user located at job sites. The one or more user are selected from a group comprising, but not limited to, construction workers, builders, employees, drivers, technicians and installation professionals working on a worksite located in a construction area. The illustrates the one or more client devices 106, 1061...106n may be selected from a group comprising smartphones, tablets etc. The one or more client devices 106, 1061...106n are include one or more input devices (such as a keyboard, a camera, microphone etc.) (not shown) and one or more output devices (such as a display screen, speaker etc.) (not shown).

[0123] Figure 5 illustrates one or more client devices 107, 1071...107n associated with one or more user located in carrier trucks sites. The one or more users are selected from a group comprising, but not limited to, carrier truck drivers or carrier truck workers. The one or more client devices 107, 1071...107n may be selected from a group comprising smartphones, tablets etc. The one or more client devices 107, 1071...107n include one or more input devices (such as a keyboard, a camera, microphone etc.) (not shown) and one or more output devices (such as a display screen, speaker etc.) (not shown).

[0124] In case of a smartphone, the one or more input devices and the one or more output devices may be integrally provided. For example, in touch-input based camera-enabled smartphone no external devices need to be connected. Additionally, the one or more client devices 106, 1061...106n and 107, 1071...107n are envisaged to include Global Positioning System (GPS) configured provide a location of the smartphone and thereby the worker, when queried using appropriate protocols. The location may be in the form of, but not limited to, geographical coordinates. The one or more client devices 106, 1061...106n and 107, 1071 ...107n are connected with a network 104. The network 104 may be one of, but not limited to, a LocalArea Network (LAN) or a Wide Area Network (WAN). The network 104 may be implemented using a number of protocols, such as but not limited to, TCP / IP, 3GPP, 3GPP2, LTE, IEEE 802.x etc.

[0125] Further connected to the network 104 is a computer system 102. The computer system 102 may be a portable computing device, a desktop computer or a server stack. The computer is envisaged to include computing capabilities such as a memory unit 1022 configured to store machine readable instructions. The machine readable instructions may be loaded into the memory unit 1022 from a non -transitory machine-readable medium such as, but not limited to, CD-ROMs, DVD-ROMs and Flash Drives. Alternately, the machine readable instructions may be loaded in a form of a computer software program into the memory unit 1022. The memory unit 1022 in that manner may be selected from a group comprising EPROM, EEPROM and Flash memory. Further, the computer system 102 includes a processor 1024 operably connected with the memory unit 1022. In various embodiments, the processor 1024 is one of, but not limited to, a general-purpose processor 1024, an application specific integrated circuit (ASIC) and a field-programmable gate array (FPGA).

[0126] Further connected to the network 104 is a data repository 108. The data repository 108 may be a cloud-based storage or a local storage. In any manner, the data repository 108 is envisaged to be capable of providing the data to any of the computing devices connected with the network 104, when the data is queried appropriately using applicable security and other data transfer protocols. The data repository 108 is envisaged to store one or more profiles associated with a plurality of workers. The one or more profiles comprise, but not limited to, respective names, respective ages, respective locations of worksites, respective tasks assigned, respective work shift schedules and respective contact details. Various embodiments of the present invention may now be understood with the exemplary environment 100 as a reference.

[0127] Figure 6 illustrates a computer-implemented method 200 for creating data files for booking and scheduling for the pickup and drop-off of material or goods. The one or more construction worker having the associated one or more client devices 106, 1061 ...106n are registered on the computer system 102. For registration they may need to provide details such as, but not limited to, respective names, respective ages, respective work experience, respective field of work, and respective contact details using the one or more client devices 106, 1061 ...106n. Using the details, the processor 1024 may generate the one or more of profiles corresponding to the respective one or more worker and store the same in the data repository 108.

[0128] . The one or more carrier drivers’ having the associated one or more client devices 107, 1071 ,1 ...107n are registered on the computer system 102. For registration they may need to provide details such as, but not limited to, carrier truck attributes, carrier truck volume capacity, respective names, respective ages, respective work experience, respective field of work, and respective contact details using the one or more client devices 107, 1071 ...107n. Using the details, the processor 1024 may generate the one or more of profiles corresponding to the respective one or more worker and store the same in the data repository 108.

[0129] The computer-implemented method begins at step 210 when a construction worker creates a job order defining the pickup and drop off points and the volume of material to be picked up along with any other material attributes.

[0130] At step 220 the job data is sent to system 102 which creates the job data file at step 230. An example job data file is below.

[0131] JOB NUMBER: 100

[0132] PICKUP LOCATION: 1 GRAND AVENUE CAMELIA NSW 2130 AUSTRALIA

[0133] DROP OFF LOCATION: 4 BARCLAY ROAD NORTH ROCKS NSW 2151 AUSTRALIA

[0134] MATERIAL TYPE: CONSTRUCTION WASTE

[0135] MATERIAL VOLUME: 1000 TONNES

[0136] CARRIER TRUCK ATTRIBUTES: 20 TONNE

[0137] CARRIER TRUCK LOADS REQUIRED: 50

[0138] At step 240 the system creates the plurality of loads data files required. In this case 1000 tonnes of material needs to be moves and the carrier truck chosen and / or suitable for the site is a 20 tonne carrier truck. As such the system has calculated that 50 loads are required and therefore 50 load data files are created. An example of a load data file is below.

[0139] LOAD JOB NUMBER: 1000:100 (1 OF 50)

[0140] PICKUP LOCATION: 1 GRAND AVENUE CAMELIA NSW 2130 AUSTRALIA

[0141] DROP OFF LOCATION: 4 BARCLAY ROAD NORTH ROCKS NSW 2151 AUSTRALIA

[0142] MATERIAL TYPE: CONSTRUCTION WASTE

[0143] MATERIAL VOLUME: 20 TONNES

[0144] LOAD TRIPS: 1

[0145] At step 250 each of the load data files are sent to one or more of the carrier truck client devices 107, 1071 ...107n. The carrier truck drivers can choose to quote on the job and / or accept a predetermined price for the job. They can accept or reject the load job as desired. At 260 each devices 107, 1071 ...107n sends either an accept or reject reply back to the system 260 to update the job data file at 270. If required, new load data files are created and sent to additional available carrier truck client devices 107, 1071...107n.

[0146] At step 280 the system receives updates on each load job and updates the job data file as necessary. When all loads are completed the job data file is updated and marked as completed. Invoices can be generated to charge the construction company and pay the carrier truck drivers.

[0147] FIGURE 7 illustrates a computer-implemented method 300 for sending the load data files to the carrier truck client device 107. The load data file is sent to the client device 107 for acceptance or rejection. If accepted, the device is used to update the system 102 on the load job status and to update the JOB DATA FILE. Upon completion the device 107 notifies the system to update the JOB DATA FILE.

[0148] FIGURE 8 illustrates a computer-implemented method 400 for sending job details to the system 102 from the construction worker client device 106. The job details of the material to be collected and the carrier truck requirements are sent to the system 102. The system creates the JOB DATA FILE and send this along with pricing to the client device 107 for acceptance or rejection. If accepted, the device is used to update the system 102 on the load job status and to create the JOB DATA FILE. Load job updates are send to the device 106 along with an invoice once all the loads are competed and the job finished. The user can use device 106 to update the job details such as amending the amount of material to be collected or cancelling the job either completely or partially.

[0149] The system allows constructions workers and / or companies to receive consolidated invoices for each job even if the rate charged for each carrier truck load is different. It should be understood that thesystem allows a consolidated invoice to be charged to the construction company even if the carrier trucks come from a plurality of different suppliers in the event that one carrier truck supplier does not supply all the carrier truck loads.

[0150] In one embodiment once a job is posted by the construction company the carrier truck drivers or contractors may bid on each load so that the price may vary according to each load in accordance with how busy each supplier may be. In this case additional load data files may be generated and sent to all available carrier truck devices and the final load data files may be sent once a quote is received from a carrier truck driver and confirmed by the construction client.

[0151] In some embodiments the drop off location of the material can be different in the event that a particular tip site can only take a portion of the material to be dropped off.

[0152] The preferred embodiment of the invention provides a comprehensive logistics coordination platform designed to overcome the limitations of conventional, single-industry systems by supporting multiple verticals, including construction, waste management, refrigerated transport, and freight. Unlike existing solutions that are narrowly focused, the system is capable of handling distinct load configurations and regulatory requirements unique to each industry. A key feature of the invention is its automated compliance verification, which performs real-time checks on driver licenses, vehicle permits, and relevant certifications through API integrations. This reduces the risk of regulatory breaches typically associated with manual or semi-automated compliance checks.

[0153] The preferred embodiment the invention uses blockchain anchoring via Merkle batching - the system hashes all load-completion events in a rolling 10-minute Merkle tree. Only the root hash is committed on-chain (element 1510 in Fig. 1), slashing transaction cost while retaining immutability. This results in significant storage and cost optimisation which results in a computer-level improvement.

[0154] The preferred embodiment of the invention uses an idempotent load-state machine wherein each load transitions through enumerated states (OFFERED — > ACCEPTED — > IN-TRANSIT — > TIPPED). The API enforces idempotent PUTs with revision tokens to eliminate race conditions in spotty mobile coverage. This improves data integrity and fault-tolerance which is a core computer-science advance.

[0155] The preferred embodiment of the invention uses a dynamic schema loader where vertical-specific attributes (e.g. asbestos flag, bitumen temperature) are injected at runtime from a JSON schema registry. The database remains single-table, avoiding costly migrations. This provides a technical solution to multivertical extensibility.

[0156] In some embodiments the system further incorporates integrated financial services, including payment processing and factoring functionality, which enables instant payments to drivers and addresses the persistent cash flow issues common in the industry — capabilities not generally offered by competing platforms. To enhance operational efficiency, the system includes a dynamic load splitting engine that automatically divides job volumes into optimized loads based on parameters such as truck capacity, material type, and applicable regulatory constraints. This eliminates the need for manual allocation and significantly streamlines the dispatch process.

[0157] In some embodiments the system comprises a sophisticated real-time workflow automation layer leverages GPS, geofencing, and WebSocket technology to provide live vehicle tracking, automated job status updates, and confirmation of delivery events. This reduces reliance on human intervention and increases system reliability. Built on a cloud-native microservices architecture, the system offers highscalability and flexibility, supporting global deployment and seamless integration with third-party enterprise software via open APIs. Additionally, the system includes environmental impact tracking, logging operational data such as distance, duration, and number of trips to calculate carbon emissions. This feature delivers actionable sustainability insights that are largely absent in traditional logistics platforms.Functionality

[0158] The functionality of the various embodiments described above will now be explained with reference to the flowcharts shown in the figures. In a discussion of the functionality below, communications between parties are preferably over a secure communication network.Interpretation

[0159] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. It will be further understood that terms used herein should be interpreted as having a meaning that is consistent with their meaning in the context of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein. For the purposes of the present invention, additional terms are defined below. Furthermore, all definitions, as defined and used herein, should be understood to control over dictionary definitions, definitions in documents incorporated by reference, and / or ordinary meanings of the defined terms unless there is doubt as to the meaning of a particular term, in which case the common dictionary definition and / or common usage of the term will prevail.

[0160] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used herein, the singular articles “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise and thus are used herein to refer to one or to more than one (i.e. to “at least one”) of the grammatical object of the article. By way of example, the phrase “an element” refers to one element or more than one element.

[0161] The term “about” is used herein to refer to quantities that vary by as much as 30%, preferably by as much as 20%, and more preferably by as much as 10% to a reference quantity. The use of the word ‘about’ to qualify a number is merely an express indication that the number is not to be construed as a precise value.

[0162] Throughout this specification, unless the context requires otherwise, the words “comprise”, “comprises” and “comprising” will be understood to imply the inclusion of a stated step or element or group of steps or elements but not the exclusion of any other step or element or group of steps or elements.

[0163] The term “real-time” for example “displaying real-time data,” refers to the display of the data without intentional delay, given the processing limitations of the system and the time required to accurately measure the data.

[0164] As used herein, the term “exemplary” is used in the sense of providing examples, as opposed to indicating quality. That is, an “exemplary embodiment” is an embodiment provided as an example, as opposed to necessarily being an embodiment of exemplary quality for example serving as a desirable model or representing the best of its kind.

[0165] The phrase “and / or,” as used herein in the specification and in the claims, should be understood to mean “either or both” of the elements so conjoined, i.e., elements that are conjunctively present in somecases and disjunctively present in other cases. Multiple elements listed with “and / or” should be construed in the same fashion, i.e., “one or more” of the elements so conjoined. Other elements may optionally be present other than the elements specifically identified by the “and / or” clause, whether related or unrelated to those elements specifically identified. Thus, as a non-limiting example, a reference to “A and / or B”, when used in conjunction with open-ended language such as “comprising” can refer, in one embodiment, to A only (optionally including elements other than B); in another embodiment, to B only (optionally including elements other than A); in yet another embodiment, to both A and B (optionally including other elements); etc.

[0166] As used herein in the specification and in the claims, “or” should be understood to have the same meaning as “and / or” as defined above. For example, when separating items in a list, “or” or “and / or” shall be interpreted as being inclusive, i.e., the inclusion of at least one, but also including more than one, of a number or list of elements, and, optionally, additional unlisted items. Only terms clearly indicated to the contrary, such as “only one of’ or “exactly one of,” or, when used in the claims, “consisting of’ will refer to the inclusion of exactly one element of a number or list of elements. In general, the term “or” as used herein shall only be interpreted as indicating exclusive alternatives (i.e. “one or the other but not both”) when preceded by terms of exclusivity, such as “either,” “one of,” “only one of,” or “exactly one of.” “Consisting essentially of,” when used in the claims, shall have its ordinary meaning as used in the field of patent law.

[0167] As used herein in the specification and in the claims, the phrase “at least one,” in reference to a list of one or more elements, should be understood to mean at least one element selected from any one or more of the elements in the list of elements, but not necessarily including at least one of each and every element specifically listed within the list of elements and not excluding any combinations of elements in the list of elements. This definition also allows that elements may optionally be present otherthan the elements specifically identified within the list of elements to which the phrase “at least one” refers, whether related or unrelated to those elements specifically identified. Thus, as a non-limiting example, “at least one of A and B” (or, equivalently, “at least one of A or B,” or, equivalently “at least one of A and / or B”) can refer, in one embodiment, to at least one, optionally including more than one, A, with no B present (and optionally including elements other than B); in another embodiment, to at least one, optionally including more than one, B, with no A present (and optionally including elements otherthan A); in yet another embodiment, to at least one, optionally including more than one, A, and at least one, optionally including more than one, B (and optionally including other elements); etc.

[0168] Bus

[0169] In the context of this document, the term “bus” and its derivatives, while being described in a preferred embodiment as being a communication bus subsystem for interconnecting various devices including by way of parallel connectivity such as Industry Standard Architecture (ISA), conventional Peripheral Component Interconnect (PCI) and the like or serial connectivity such as PCI Express (PCIe), Serial Advanced Technology Attachment (Serial ATA) and the like, should be construed broadly herein as any system for communicating data.In accordance with:

[0170] As described herein, ‘in accordance with’ may also mean ‘as a function of and is not necessarily limited to the integers specified in relation thereto.Composite items

[0171] As described herein, ‘a computer implemented method’ should not necessarily be inferred as being performed by a single computing device such that the steps of the method may be performed by more than one cooperating computing devices.

[0172] Similarly objects as used herein such as ‘web server’, ‘server’, ‘client computing device’, ‘computer readable medium’ and the like should not necessarily be construed as being a single object, and may be implemented as a two or more objects in cooperation, such as, for example, a web server being construed as two or more web servers in a server farm cooperating to achieve a desired goal or a computer readable medium being distributed in a composite manner, such as program code being provided on a compact disk activatable by a license key downloadable from a computer network.Database:

[0173] In the context of this document, the term “database” and its derivatives may be used to describe a single database, a set of databases, a system of databases or the like. The system of databases may comprise a set of databases wherein the set of databases may be stored on a single implementation or span across multiple implementations. The term “database” is also not limited to refer to a certain database format rather may refer to any database format. For example, database formats may include MySQL, MySQLi , XML or the like.Wireless:

[0174] The invention may be embodied using devices conforming to other network standards and for other applications, including, for example other WLAN standards and other wireless standards. Applications that can be accommodated include IEEE 802.11 wireless LANs and links, and wireless Ethernet.

[0175] In the context of this document, the term “wireless” and its derivatives may be used to describe circuits, devices, systems, methods, techniques, communications channels, etc., that may communicate data through the use of modulated electromagnetic radiation through a non-solid medium. The term does not imply that the associated devices do not contain any wires, although in some embodiments they might not. In the context of this document, the term “wired” and its derivatives may be used to describe circuits, devices, systems, methods, techniques, communications channels, etc., that may communicate data through the use of modulated electromagnetic radiation through a solid medium. The term does not imply that the associated devices are coupled by electrically conductive wires.Processes:

[0176] Unless specifically stated otherwise, as apparent from the following discussions, it is appreciated that throughout the specification discussions utilizing terms such as “processing”, “computing”, “calculating”, “determining”, “analysing” or the like, refer to the action and / or processes of a computer or computing system, or similar electronic computing device, that manipulate and / or transform datarepresented as physical, such as electronic, quantities into other data similarly represented as physical quantities.Processor:

[0177] In a similar manner, the term “processor” may refer to any device or portion of a device that processes electronic data, e.g., from registers and / or memory to transform that electronic data into other electronic data that, e.g., may be stored in registers and / or memory. A “computer” or a “computing device” or a “computing machine” or a “computing platform” may include one or more processors.

[0178] The methodologies described herein are, in one embodiment, performable by one or more processors that accept computer-readable (also called machine-readable) code containing a set of instructions that when executed by one or more of the processors carry out at least one of the methods described herein. Any processor capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken are included. Thus, one example is a typical processing system that includes one or more processors. The processing system further may include a memory subsystem including main RAM and / or a static RAM, and / or ROM.Computer-Readable Medium:

[0179] Furthermore, a computer-readable carrier medium may form, or be included in a computer program product. A computer program product can be stored on a computer usable carrier medium, the computer program product comprising a computer readable program means for causing a processor to perform a method as described herein.Networked or Multiple Processors:

[0180] In alternative embodiments, the one or more processors operate as a standalone device or may be connected, e.g., networked to other processor(s), in a networked deployment, the one or more processors may operate in the capacity of a server or a client machine in server-client network environment, or as a peer machine in a peer-to-peer or distributed network environment. The one or more processors may form a web appliance, a network router, switch or bridge, or any machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine.

[0181] Note that while some diagram(s) only show(s) a single processor and a single memory that carries the computer-readable code, those in the art will understand that many of the components described above are included, but not explicitly shown or described in order not to obscure the inventive aspect. For example, while only a single machine is illustrated, the term “machine” shall also be taken to include any collection of machines that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein.Additional Embodiments:

[0182] Thus, one embodiment of each of the methods described herein is in the form of a computer-readable carrier medium carrying a set of instructions, e.g., a computer program that are for execution on one or more processors. Thus, as will be appreciated by those skilled in the art, embodiments of the present invention may be embodied as a method, an apparatus such as a special purpose apparatus, an apparatus such as a data processing system, or a computer-readable carrier medium. The computer-readable carrier medium carries computer readable code including a set of instructions that when executedon one or more processors cause a processor or processors to implement a method. Accordingly, aspects of the present invention may take the form of a method, an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of carrier medium (e.g., a computer program product on a computer-readable storage medium) carrying computer-readable program code embodied in the medium.Carrier Medium:

[0183] The software may further be transmitted or received over a network via a network interface device. While the carrier medium is shown in an example embodiment to be a single medium, the term “carrier medium” should be taken to include a single medium or multiple media (e.g., a centralized or distributed database, and / or associated caches and servers) that store the one or more sets of instructions. The term “carrier medium” shall also be taken to include any medium that is capable of storing, encoding or carrying a set of instructions for execution by one or more of the processors and that cause the one or more processors to perform any one or more of the methodologies of the present invention. A carrier medium may take many forms, including but not limited to, non-volatile media, volatile media, and transmission media.Blockchain

[0184] A blockchain is a collection of information that is stored electronically in blocks on one or more computer systems, the blocks storing sets of information and being chained onto a previously filled block, forming a chain of data known as the blockchain. New information that follows a freshly added block is compiled into a newly formed block that will also be added to the chain and preferably time stamped once the block is filled. Blockchains are typically implemented as a decentralised, distributed network, in which a plurality of nodes of the network are synchronised to store the same blockchain information.Implemen ta tion:

[0185] It will be understood that the steps of methods discussed are performed in one embodiment by an appropriate processor (or processors) of a processing (i.e., computer) system executing instructions (computer-readable code) stored in storage. It will also be understood that the invention is not limited to any particular implementation or programming technique and that the invention may be implemented using any appropriate techniques for implementing the functionality described herein. The invention is not limited to any particular programming language or operating system.Means For Carrying out a Method or Function

[0186] Furthermore, some of the embodiments are described herein as a method or combination of elements of a method that can be implemented by a processor of a processor device, computer system, or by other means of carrying out the function. Thus, a processor with the necessary instructions for carrying out such a method or element of a method forms a means for carrying out the method or element of a method. Furthermore, an element described herein of an apparatus embodiment is an example of a means for carrying out the function performed by the element for the purpose of carrying out the invention.Connected

[0187] Similarly, it is to be noticed that the term connected, when used in the claims, should not be interpreted as being limitative to direct connections only. Thus, the scope of the expression a device A connected to a device B should not be limited to devices or systems wherein an output of device A is directly connected to an input of device B. It means that there exists a path between an output of A and an input of B which may be a path including other devices or means. “Connected” may mean that two or more elements are either in direct physical or electrical contact, or that two or more elements are not in direct contact with each other but yet still co-operate or interact with each other.Embodiments:

[0188] Reference throughout this specification to “one embodiment” or “an embodiment” means that a particular feature, structure or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Thus, appearances of the phrases “in one embodiment” or “in an embodiment” in various places throughout this specification are not necessarily all referring to the same embodiment, but may. Furthermore, the particular features, structures or characteristics may be combined in any suitable manner, as would be apparent to one of ordinary skill in the art from this disclosure, in one or more embodiments.

[0189] Similarly it should be appreciated that in the above description of example embodiments of the invention, various features of the invention are sometimes grouped together in a single embodiment, figure, or description thereof for the purpose of streamlining the disclosure and aiding in the understanding of one or more of the various inventive aspects. This method of disclosure, however, is not to be interpreted as reflecting an intention that the claimed invention requires more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive aspects lie in less than all features of a single foregoing disclosed embodiment. Thus, the claims following the Description of Embodiments are hereby expressly incorporated into this Description of Embodiments, with each claim standing on its own as a separate embodiment of this invention.

[0190] Furthermore, while some embodiments described herein include some but not other features included in other embodiments, combinations of features of different embodiments are meant to be within the scope of the invention, and form different embodiments, as would be understood by those in the art. For example, in the following claims, any of the claimed embodiments can be used in any combination. Specific Details

[0191] In the description provided herein, numerous specific details are set forth. However, it is understood that embodiments of the invention may be practiced without these specific details. In other instances, well-known methods, structures and techniques have not been shown in detail in order not to obscure an understanding of this description.

[0192] It will be appreciated that the methods / apparatus / devices / systems described / illustrated above at least substantially provide a system and method for multi-vertical real time logistics coordination.

[0193] The system and method for multi-vertical real time logistics coordination described herein, and / or shown in the drawings, are presented by way of example only and are not limiting as to the scope of the invention. Unless otherwise specifically stated, individual aspects and components of the system andmethod for multi-vertical real time logistics coordination may be modified, or may have been substituted therefore known equivalents, or as yet unknown substitutes such as may be developed in the future or such as may be found to be acceptable substitutes in the future. The system and method for multi-vertical real time logistics coordination may also be modified for a variety of applications while remaining within the scope and spirit of the claimed invention, since the range of potential applications is great, and since it is intended that the present invention be adaptable to many such variations.Terminology

[0194] In describing the preferred embodiment of the invention illustrated in the drawings, specific terminology will be resorted to for the sake of clarity. However, the invention is not intended to be limited to the specific terms so selected, and it is to be understood that each specific term includes all technical equivalents which operate in a similar manner to accomplish a similar technical purpose. Terms such as "forward", "rearward", "radially", "peripherally", "upwardly", "downwardly", and the like are used as words of convenience to provide reference points and are not to be construed as limiting terms.Different Instances of Objects

[0195] As used herein, unless otherwise specified the use of the ordinal adjectives “first”, “second”, “third”, etc., to describe a common object, merely indicate that different instances of like objects are being referred to, and are not intended to imply that the objects so described must be in a given sequence, either temporally, spatially, in ranking, or in any other manner.Combinations of features in embodiments

[0196] Different features are described in different embodiments in this specification, however it is envisaged that any features shown in any embodiment described may be used with any other features in any other embodiment in any combination, unless this is not logically possible.Comprising and Including

[0197] In the claims which follow and in the preceding description of the invention, except where the context requires otherwise due to express language or necessary implication, the word “comprise” or variations such as “comprises” or “comprising” are used in an inclusive sense, i.e. to specify the presence of the stated features but not to preclude the presence or addition of further features in various embodiments of the invention.

[0198] Any one of the terms: including or which includes or that includes as used herein is also an open term that also means including at least the elements / features that follow the term, but not excluding others. Thus, including is synonymous with and means comprising.Scope of invention

[0199] Thus, while there has been described what are believed to be the preferred embodiments of the invention, those skilled in the art will recognize that other and further modifications may be made thereto without departing from the spirit of the invention, and it is intended to claim all such changes and modifications as fall within the scope of the invention. For example, any formulas given above are merely representative of procedures that may be used. Functionality may be added or deleted from the blockdiagrams and operations may be interchanged among functional blocks. Steps may be added or deleted to methods described within the scope of the present invention.

[0200] Although the invention has been described with reference to specific examples, it will be appreciated by those skilled in the art that the invention may be embodied in many other forms.Chronological order

[0201] For the purpose of this specification, where method steps are described in sequence, the sequence does not necessarily mean that the steps are to be carried out in chronological order in that sequence, unless there is no other logical manner of interpreting the sequence.Markush groups

[0202] In addition, where features or aspects of the invention are described in terms of Markush groups, those skilled in the art will recognise that the invention is also thereby described in terms of any individual member or subgroup of members of the Markush group.Industrial Applicability

[0203] It is apparent from the above, that the arrangements described are applicable to the Construction: Moving earth, gravel, demolition waste; Waste Management: Skip bin and commercial waste transport; Refrigerated Transport: Perishable goods delivery; General Freight: Palletized goods, containers; Environmental Analytics: Carbon emission tracking for sustainability reporting; Regulatory Compliance: Automated verification fortransport licenses and permits industries.

Claims

Claims1. A computer-implemented system for multi-vertical logistics coordination, comprising:a) a load-splitting engine configured to divide a job volume into optimized load files based on one or more of: truck capacity; material type; waste type; job type; unit rate; and regulatory constraints; b) a matching engine using machine learning to assign loads to drivers based on one or more of: capacity; proximity; compliance; and performance;c) a compliance module integrating with external APIs to verify one or more of driver licenses; vehicle permits; and certifications in real time;d) a payment module for processing driver payments via a third-party gateway;e) a GPS-driven tracking module with geofencing to automate job status updates and calculate carbon emissions;f) a bidding module enabling tip sites to set opening prices and carriers to bid, with a service fee applied to excess bids;g) a microservices architecture with WebSockets for real-time communication;wherein the system coordinates logistics across vertical industries including one or more of construction; waste; refrigerated; and freight industries.

2. The system of claim 1 , further comprising a fixed and floating charge module securing credit via vehicle assets, registered on a personal property securities register, with electronic signatures captured via a mobile application.

3. The system of claim 1 , wherein the bidding module applies a service fee to carrier bids exceeding the tip site's opening price, with bids managed via an admin portal.

4. The system of claim 1 , wherein the tracking module logs distance, time, and trips to calculate CO2 emissions based on fuel type and consumption.

5. A method for coordinating multi-vertical logistics, comprising:a) receiving a job request with volume, material, and location data;b) splitting the job into load files using a dynamic algorithm;c) matching loads to drivers based on capacity, compliance, and proximity;d) verifying driver and vehicle compliance via real-time API queries;e) tracking job progress with GPS and geofencing;f) processing payments and offering driver payouts;g) calculating carbon emissions based on route data.

6. A logistics coordination system comprising:a) a plurality of user interfaces comprising at least a shipper interface, a carrier interface, and a tip site interface, each configured to enable corresponding users to input, receive, and view logistics- related data;b) a backend system configured to:(i) dynamically partition transport jobs into load assignments based on parameters including vehicle capacity, material type, and regulatory compliance;(ii) automatically verify driver and vehicle compliance using real-time external data sources; (iii) facilitate job bidding initiated by tip site operators and responded to by carriers, including automatic application of platform fees;(iv) provide a financial service to enable instant payment to carriers with deferred recovery from shippers or tip site operators;(v) track operational metrics to calculate estimated carbon emissions associated with completed jobs;c) a communication layer operable to transmit real-time updates between the user interfaces and the backend system.

7. The system of claim 6, wherein the backend system comprises a load allocation module that reallocates unaccepted or cancelled loads to alternate available carriers.

8. The system of claim 6, wherein the compliance verification uses APIs connected to external licensing, registration, or permit databases.

9. The system of claim 6, wherein the financial service is implemented via an integrated payment gateway and includes invoice generation, payout to the carrier, and delayed receivables collection from the contracting party.

10. The system of claim 6, wherein the tip site interface enables a tip site to set an opening bid price, with the backend applying a service fee on final carrier bids exceeding the set price.

11. The system of claim 6, wherein the carbon emission calculation is based on one or more of:distance travelled, fuel type, load weight, and vehicle class.

12. The system of claim 6, wherein the communication layer utilises WebSocket technology to push updates including job offers, bid notifications, and live location tracking.

13. The system of claim 6, wherein the user interfaces enable drivers to submit delivery confirmation comprising digital signatures, photographs, or geolocation data.

14. The system of claim 6, wherein the backend system includes a machine learning module configured to rank carriers based on one or more of: historical job completion, compliance rate, bid responsiveness, or feedback scores.

15. The system of claim 6, wherein the backend system is implemented using a cloud-native microservices architecture, enabling independent scaling of modules.

16. A method of coordinating logistics operations, the method comprising:a) receiving, via a user interface, a transport job request comprising at least a pickup location, dropoff location, material type, and volume or weight;b) partitioning the job into one or more load assignments based on truck capacity, compliance requirements, and material constraints;c) verifying in real-time the compliance status of available carriers using external data sources for licensing, permits, and vehicle registrations;d) dispatching load offers to compliant carriers via a real-time communication channel;e) receiving acceptance or rejection of load offers and reallocating unaccepted loads to alternate carriers;f) where the transport involves a tip site, initiating a bidding process in which the tip site sets an opening bid price and carriers submit competing offers;g) processing payment to the selected carrier upon confirmation of delivery, optionally via an instant payment and factoring service;h) recording operational data relating to distance, time, and load details; andi) calculating estimated carbon emissions for the job based on said operational data.

17. The method of claim 16, wherein the step of partitioning the job includes applying rules to distinguish between transport jobs in different verticals, including waste, construction, or refrigerated logistics.

18. The method of claim 16, wherein the step of verifying compliance comprises querying third-party APIs for current license status, vehicle registration, and permit validity.

19. The method of claim 16, wherein the step of reallocating loads occurs automatically if no response is received from a carrier within a predetermined timeframe.

20. The method of claim 16, wherein the bidding process includes applying a service fee to the final accepted carrier bid, calculated as a percentage above the tip site’s opening price.

21. The method of claim 16, wherein delivery confirmation includes submission of one or more of:timestamped photographs, digital signatures, and geolocation metadata via a mobile application.

22. The method of claim 16, further comprising registering a fixed or floating charge over a carrier’s vehicle asset via a secured electronic transaction and recording the charge on a personal property register.

23. The method of claim 16, wherein the carbon emissions calculation is based on fuel consumption profiles associated with vehicle class and trip characteristics.

24. The method of claim 16, further comprising ranking carriers using a machine learning algorithm based on job completion history, compliance records, and user feedback.

25. The method of claim 16, wherein all backend processes are executed in a cloud-native microservices environment and communicate with user devices via WebSocket protocols.

26. A system for arranging the pickup of a predetermined volume of material from a first location and the delivery of the material to a second location, the system including:a first client device for receiving data for defining the first location, the second location and the predetermined volume of the material;a second client device for receiving data on a plurality of carrier trucks, the data including a volume capacity of each respective carrier truck and one or more of: the type of material the carrier truck is licensed to carry; and regulatory constraints;a processor for receiving the data from the first client device and the data from the second client device, the processor using the data to create a job data file that includes data on the number of carrier trucks required to pickup the predetermined volume of material, the processor further creating a plurality of load data files including the volume of material to be picked up by each carrier truck, one load data file being created for each required carrier truck wherein the processor further sends each respective load data file for each carrier truck to a plurality of third client devices located in each respective carrier truck;wherein the first client device further receives a plurality of attributes of the material to be picked up;wherein the second client device further receives a plurality of attributes of each respective carrier truck;wherein the processor divides the job into optimised loads based on the attributes of the material to be picked up, the carrier truck volume capacity and regulatory constraints;wherein the processor verifies licenses, permits and carrier truck status via API integrations;wherein each carrier truck includes a GPS in communication with the processor and the processor tracks carrier truck routes for analytics including CO2 emissions.

27. The system according to claim 26 wherein the sum of the volume of material to be picked up by each carrier truck is equal to the predetermined volume of material.

28. The system according to claim 26 wherein at least one third client device located in each respective carrier truck is sent more than one load data file to thereby complete consecutive pickup and delivery of material equal to the number of load data files received.

29. The system according to claim 28 wherein the volume of material that each carrier truck is can carry is different from at least one other carrier truck.

30. The system according to claim 26 wherein the load data file further includes the first location and the second location.

31. The system according to claim 26 wherein a driver in each respective carrier truck can accept the load details received at the respective third client device and if accepted the third client device sends an accept data file to the processor to initiate the load job forthat carrier truck.

32. The system according to claim 31 wherein the driver in each respective carrier truck can reject the load details received at the respective third client device wherein upon rejection the third client device sends a reject data load file to the processor and wherein the processor upon receiving the reject data load file creates a further load a data file and sends this to another third client device located in another carrier truck.

33. A computer-implemented method for arranging the pickup of a predetermined volume of material from a first location and delivery of the material to a second location, the computer-implemented method comprising the steps of:

34. receiving from a user on a client device the predetermined volume of material, the first location and the second location;receiving from the user on the client device the attributes of at least one carrier truck to pickup the material, the attributes including at least the volume capacity of the at least one carrier truck; the client device forwarding data received from the client device to a processor, the processor using the data received from the client device to create a job data file including a determination of the number of carrier trucks required to pickup and deliver the predetermined volume of material from the first location to the second location, the processor further creating a plurality of load data files each load data file including the volume of material to be picked up by each respective carrier truck, one load data file being created for each required carrier truck and wherein the processor further sends each respective load data file for each carrier truck to a plurality of carrier client deviceslocated in each respective carrier truck, wherein the processor divides the job into optimised loads based on the attributes of the material to be picked up, the carrier truck volume capacity and regulatory constraints; wherein the processor verifies licenses, permits and carrier truck status via API integrations.

35. The computer-implemented method as claimed in claim 34, wherein the one or more client devices are selected from a group comprising smartphones and tablets having at least a camera, a microphone and a Global Positioning System (GPS).

36. The computer-implemented method as claimed in claim 35, further comprising the step of receiving and tracking the one or more locations of the one or more carrier trucks, thereby tracking the location of the one or more carrier trucks and wherein the processor tracks carrier truck routes for analytics including CO2 emissions.

37. A computer-implemented system for coordinating road-transport of material between a pickup location and a destination, the system comprising:(a) a server in network communication with (i) a shipper client device, (ii) a plurality of carrier client devices each associated with a respective carrier vehicle, and (iii) at least one tip-site client device;(b) a database storing, for each of a plurality of loads, a load record that includes (i) a load identifier, (ii) a state value drawn from an enumerated state set comprising at least an OFFERED state, an ACCEPTED state, an IN-TRANSIT state and a TIPPED state, and (iii) a current revision token;(c) a load-partitioning module configured to receive, from the shipper client device, a job request specifying a quantity of material, the pickup location and the destination, and to generate from the job request a plurality of load data files each defining a respective one of the loads in dependence upon (i) a vehicle volume capacity associated with one of the carrier client devices, (ii) one or more regulatory constraints applicable to the material, and (iii) a vehicle attribute received from the carrier client device;(d) a publish-subscribe communication channel between the server and each of the carrier client devices, in which each carrier client device maintains a persistent subscription to the server and the server publishes load data files to the carrier client devices over the subscription only on the occurrence of a state-change event, such that the carrier client devices do not poll the server for load data;(e) an idempotent state-transition interface exposed by the server, configured to receive from a carrier client device a state-transition request comprising (i) the load identifier, (ii) a requested state value drawn from the enumerated state set, and (iii) a revision token previously issued by the server in respect of the load identifier; the server being configured to apply the requested state transition to the corresponding load record only when the received revision token matches the current revision token in the database, and on each successful transition to atomically update the current revision token in the database and to return an updated revision token to the carrier client device;(f) a geofence engine configured to transmit to each of the carrier client devices, in respect of an assigned load, geofence polygon data defining at least one of the pickup location and thedestination, the carrier client device being configured to evaluate locally, using a position signal obtained from a positioning sensor of the carrier client device, whether the carrier vehicle has entered or exited a geofence defined by the polygon data, and to transmit to the server, over the publish-subscribe channel, only a geofence state-change event, the geofence state-change event being formatted as a state-transition request to the idempotent state-transition interface; and (g) a compliance verification module configured, prior to the server publishing a load data file to a carrier client device under (d), to issue a non-blocking compliance request to one or more external compliance data sources via an asynchronous worker pool, the server releasing a request-handling thread upon dispatch of the compliance request and resuming processing of the request asynchronously upon receipt of a compliance response via a callback, the load data file being published only on receipt of a compliance response indicating that the carrier client device satisfies one or more applicable regulatory criteria;wherein, on the occurrence of a network-induced retransmission or duplication of a statetransition request received from a carrier client device, the idempotent state-transition interface causes the corresponding load record to converge to a single canonical state independent of the order or multiplicity of receipt of those requests.

38. The system of claim 37, wherein the load-partitioning module further generates the load data files in dependence upon a vertical-specific attribute injected at runtime from a JSON schema registry, the database storing all load records against a single underlying table irrespective of the vertical to which the load belongs (1J170).

39. The system of claim 37, further comprising a blockchain-anchoring module configured to hash a plurality of state-transition events occurring within a rolling time window into a Merkle tree and to commit only the resulting root hash of the Merkle tree to a blockchain network (1J168).

40. The system of claim 37, wherein the load-partitioning module is further configured to use a trained machine-learning model to rank the carrier client devices by reference to historical completion data, historical compliance data and feedback data stored in the database, and to generate the load data files in dependence upon the ranking.

41. The system of claim 37, wherein the geofence state-change event under (f) causes the idempotent state-transition interface to transition the corresponding load record from the INTRANSIT state to the TIPPED state without further user input.

42. The system of claim 37, wherein the database further stores, in respect of each load record, a vertical identifier drawn from a set comprising at least construction, waste, refrigerated and general freight, and the load-partitioning module applies a vertical-specific regulatory constraint set to the partitioning under (c) in dependence upon the vertical identifier.

43. A computer-implemented method of coordinating road-transport of material between a pickup location and a destination, the method being performed by a server in communication with a shipper client device, a plurality of carrier client devices and at least one tip-site client device, the method comprising:(a) receiving from the shipper client device a job request specifying a quantity of material, a pickup location and a destination, and partitioning the job request into a plurality of load data fileseach in dependence upon a vehicle volume capacity, one or more applicable regulatory constraints, and at least one vehicle attribute received from a carrier client device;(b) for each load, storing in a database a load record comprising a load identifier, a state value drawn from an enumerated state set comprising at least OFFERED, ACCEPTED, IN-TRANSIT and TIPPED, and a current revision token;(c) issuing, prior to publication of a load data file to a carrier client device, a non-blocking compliance request to one or more external compliance data sources via an asynchronous worker pool, releasing a request-handling thread upon dispatch and resuming asynchronously on receipt of a compliance response via a callback;(d) publishing the load data file to the carrier client device over a persistent publish-subscribe channel only on receipt of a compliance response indicating compliance, and only on the occurrence of a state-change event;(e) transmitting to the carrier client device geofence polygon data defining at least one of the pickup location and the destination, and receiving from the carrier client device only a geofence state-change event evaluated locally by the carrier client device against a position signal obtained from a positioning sensor;(f) exposing an idempotent state-transition interface that receives from a carrier client device a state-transition request comprising the load identifier, a requested state value and a revision token previously issued by the server, applying the requested state transition to the corresponding load record only when the received revision token matches the current revision token in the database, and atomically updating the current revision token in the database upon each successful transition;(g) on receipt of a duplicated or out-of-order state-transition request, returning the load record to a single canonical state independent of the order or multiplicity of receipt of those requests.