Summary
In short
- A carrier service failure record is a record used in KnowLogistics that records a carrier failing to deliver the service agreed, covering late collection, missed delivery, refusal or a damaged load. It is built against Contract requirements and forms part of the Claims and Carrier Performance programme.
- Raised per failure. Completed by transport.
- The template holds 41 fields across 4 sections.
- Scoring is service failures, where high is bad.
- Contract requirements is contract requirements. Obligations accepted in a customer or supplier agreement rather than imposed by law.
- It connects to the rest of the library: feeds Carrier Scorecard and Freight Claim.
What it is
What it is
What is a carrier service failure record?
A carrier service failure record is a record used in KnowLogistics that records a carrier failing to deliver the service agreed, covering late collection, missed delivery, refusal or a damaged load. It is built against Contract requirements and forms part of the Claims and Carrier Performance programme.
When is a carrier service failure record completed?
A carrier service failure record is completed at the moment the event happens, rather than reconstructed afterwards. Raised per failure.
When to use it
When to use it, and when not to
This record is one step in a larger programme. Using it for work that belongs to a neighbouring template produces records that are hard to report on later.
Use it for
- The event or activity this record covers has occurred, or is about to
- The workspace is being set up, or the register needs an entry added or retired
- You are running the Claims and Carrier Performance programme and this is one of its steps
- A linked record needs this one to exist: feeds carrier scorecard and freight claim
Not for
- Freight Claim Record, which pursues a claim against a carrier for loss or damage in transit.
- Detention and Demurrage Log, which records time a vehicle or container spent beyond its free period, why, and who is liable.
- Shortage Investigation Record, which investigates stock that left as one quantity and arrived as another, before anybody assumes theft.
- Anything outside KnowLogistics, which belongs in the workspace that owns that process
Standards
What it is built against
Contract requirementsContract requirements
Obligations accepted in a customer or supplier agreement rather than imposed by law.
FAQ
Frequently asked questions
What is the carrier service failure record template based on?+
It is built against Contract requirements. Contract requirements is contract requirements. Obligations accepted in a customer or supplier agreement rather than imposed by law.
What sections does the carrier service failure record contain?+
There are 4 sections: header, impact, carrier response, outcome. Together they hold 41 fields, 32 of which are required.
How many carrier service failure record records should we have?+
This is a singleton. One record per workspace, set up once and maintained, rather than one per event. Other templates refer back to it.
Which programme does the carrier service failure record belong to?+
It is part of Claims and Carrier Performance. Claims filed inside the window with the evidence gathered at the dock.
How is a carrier service failure record scored?+
Scoring is service failures. High is bad. Scores exist to make the form tell you something, not to produce a percentage for its own sake.
Can the carrier service failure record template be changed?+
Yes. Every field, option, score and conditional rule is editable, and the links to other templates come with it. Most teams install it as it is, run it for a cycle, then adjust.
The agents
What the agents do with it
The form is the easy part. Keeping it current, routing it to the right owner and holding the evidence together is the work that actually slips.
Holds the carrier service failure record library against your registers, routes each record to its owner, and keeps the evidence trail together.
Coordinates the crew, rolls completion and exceptions into one view, and holds every write for your approval before it touches a record.
This template lives in KnowLogistics — supply chain execution. Inbound, outbound, inventory, yard, claims, supplier lifecycle and customs.
Meet KnowLogistics→Sources
Sources
- Contract requirements — Contract requirements