Summary
In short
- A load tender record is a record used in KnowLogistics that records a load offered to a carrier, the rate agreed and whether it was accepted or refused. It is built against Contract requirements and forms part of the Outbound and Despatch programme.
- Raised per load. Completed by transport planning.
- The template holds 44 fields across 4 sections.
- Scoring is tender acceptance rate, where high is good.
- 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 Rate Confirmation and Carrier Scorecard.
What it is
What it is
What is a load tender record?
A load tender record is a record used in KnowLogistics that records a load offered to a carrier, the rate agreed and whether it was accepted or refused. It is built against Contract requirements and forms part of the Outbound and Despatch programme.
When is a load tender record completed?
A load tender record is completed at the moment the event happens, rather than reconstructed afterwards. Raised per load.
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 Outbound and Despatch programme and this is one of its steps
- A linked record needs this one to exist: feeds rate confirmation and carrier scorecard
Not for
- Dispatch Release Check, which the final check before a load leaves, covering documents, temperature, securement, seal and count.
- Shipping Document Check, which verifies the bill of lading, packing list, certificates and any regulated documentation before the vehicle moves.
- Proof of Delivery Exception, which records a delivery that did not complete cleanly: refused, short, damaged, late or signed with a notation.
- 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 load tender 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 load tender record contain?+
There are 4 sections: header, tender, if refused, outcome. Together they hold 44 fields, 34 of which are required.
How many load tender 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 load tender record belong to?+
It is part of Outbound and Despatch, Customer and Carrier Onboarding. Loads leaving complete and documented, with exceptions recorded where they happened.
How is a load tender record scored?+
Scoring is tender acceptance rate. High is good. Scores exist to make the form tell you something, not to produce a percentage for its own sake.
Can the load tender 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 load tender 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