SMP 365 Chain of Responsibility

What is SMP 365 Chain of Responsibility?

SMP 365 Chain of Responsibility connects consignment information, duty-holder records, load plans, restraint checks, dispatch reviews, exceptions and assurance. It is designed to help teams see the evidence surrounding a transport activity across the people involved, rather than treating dispatch as an isolated final checkbox.

The product organises records; it does not determine which legal duties apply or certify a movement as compliant. Responsibilities and operating requirements must be assessed for the actual transport activity and jurisdiction. The consignment record includes jurisdiction context so that the relevant assessment can be considered rather than assuming the same rules apply everywhere.

Start with the consignment and the people involved

Consignment records identify the movement through a number, origin, destination, goods and handling information, and load context. Related duty-holder records capture the role, organisation, internally accountable person, assigned duty and evidence requirement. This gives an operational review more substance than a contact list alone.

Map your real handovers before configuration: who supplies the information, who checks it and who must respond when something changes? A named organisation does not automatically establish acceptance of a responsibility. Agree how the relevant evidence will be obtained and reviewed, especially where transport providers and loading teams work in different systems.

Keep load planning distinct from restraint inspection

Load-plan records hold the vehicle combination, load mass, approved payload, distribution and dimensions, and the authority for the stated limit. Restraint-check records separately capture the method reference, actual inspection, verification outcome and competent verifier. Keeping these records distinct helps reviewers understand which evidence supports planning and which describes what was actually inspected.

The software does not calculate a safe restraint method or validate the suitability of a vehicle combination merely because values have been entered. Your qualified operational process must establish the applicable methods and limits. Demonstrate how a changed load is reviewed against both the plan and the inspection evidence.

Bring the evidence together at dispatch

The dispatch record brings together accepted load-plan and restraint-inspection references, driver and vehicle authority checks, route and schedule review, restrictions and dispatch authority. The aim is to make the basis of the decision visible to the person responsible for release.

A review should distinguish “information supplied” from “information accepted”. During a demonstration, ask to follow a consignment with an unresolved restriction, not just a completed example. Agree who can make the dispatch decision, how missing evidence is handled and how a decision is reconsidered when the vehicle, load or operating circumstances change. Software completion is not an independent assessment of roadworthiness or fitness for dispatch.

Use exceptions to improve the next movement

Exception records capture the type of issue, observed facts, immediate response and revalidation evidence. This creates space to distinguish what happened from what someone believes caused it. For example, a loading discrepancy should retain the evidence of the discrepancy and the review that followed, not disappear into a general comment against the consignment.

Assurance records provide jurisdiction-assessment context, duty-holder evidence, findings and a review date. Use these reviews to ask whether recurrent information gaps sit with a particular handover or process. Closing an exception is more useful when the supporting response can be understood, rather than simply changing its status.

Fit the workflow to your transport operation

The system is relevant to organisations coordinating transport evidence across dispatch, loading, operations and external providers. Start with representative consignments and the documents already exchanged. Agree identifiers and ownership before migrating registers so records remain recognisable to the teams who use them.

Confirm how information will reach the Microsoft-based workflow and what access external parties require. Any connection to fleet systems, telematics, scheduling or carrier portals needs a defined integration scope. The existence of a consignment record does not imply live tracking. Test an ordinary movement and a changed or held consignment to check that the proposed configuration supports both routine work and exceptions.

Chain of Responsibility questions