Container chassis selection should match the fleet’s real dispatch cases, including loaded trips and empty returns. The container size alone does not establish which arrangements the chassis supports. Buyers should document container types, load status, tractor details, pickup and delivery sites, and terminal requirements before comparing offers.
For an overview of fixed and mixed container configurations, see the container chassis buying guide for 20-foot and 40-foot containers.
List dispatch cases separately
Record each routine journey with container type and size, loaded or empty status, available mass information, and route endpoints. Distinguish confirmed work from possible future assignments. Start with current contracts rather than asking one chassis to cover every hypothetical case.
Confirm supported arrangements
Request drawings showing container positions and locking points for each proposed configuration. Do not infer approval from a product photo. Include tractor information because the complete combination and load distribution require review. Keep unresolved arrangements out of routine dispatch until confirmed.
Plan empty returns and site access
Record empty container identity and route, including cases where return locations differ. Obtain terminal and customer site requirements for space, handling and vehicle acceptance. Confirm them with site operators; do not rely on a previous trip with different equipment.
Compare offers against real work
Ask which cases each proposal covers, which require another setup and which remain unconfirmed. Review the GENRON three-axle container skeleton trailer against the dispatch record and tractor details. Request current drawings and written responses, and retain approved configurations for dispatch staff.
Routine dispatch
For the routine dispatch review, collect a sample of actual dispatch records. Match the evidence to the route and container identity on each job before treating it as part of the offer. Give the comparison sheet a source column with a document identifier, a date and the person who supplied it. If a record only describes a product family, mark it as background and ask for the details applicable to the proposed equipment. That distinction matters because the chassis needs review against the complete dispatch pattern. Keep the underlying document with the review so someone joining the order later can understand the decision without reconstructing it from messages.
Consider this illustrative situation: a frequent empty return is absent from the enquiry. Write down what is known, what still depends on a supplier response and which decision could change if the answer is different. The buyer can then ask one specific question and send the relevant record with it. Ask the respondent to identify the scope of the answer and state any condition that must be met. For a conditional response, note the condition in the comparison sheet, name the person who can resolve it and identify the decision that must wait. This gives the commercial and operating teams the same evidence when they review the proposal.
At the approval meeting, check whether the answer is reflected in the latest documents and whether both parties are reviewing the same revision. Record the accepted position in the order and give the receiving team a practical way to check it. If the answer cannot be confirmed until delivery, agree on the evidence the receiving team should request and how it should report a discrepancy. When the vehicle or assignment changes later, pull the record back into review and identify the affected documents. A brief note recording what changed and why makes the next review faster and keeps the original decision traceable.
Container types
For the container types review, collect the records identifying actual container types and sizes. Match the evidence to the units used on the intended routes before treating it as part of the offer. Give the comparison sheet a source column with a document identifier, a date and the person who supplied it. If a record only describes a product family, mark it as background and ask for the details applicable to the proposed equipment. That distinction matters because the supplier needs the precise operating cases. Keep the underlying document with the review so someone joining the order later can understand the decision without reconstructing it from messages.
Consider this illustrative situation: containers of the same nominal length serve different jobs. Write down what is known, what still depends on a supplier response and which decision could change if the answer is different. The buyer can then ask one specific question and send the relevant record with it. Ask the respondent to identify the scope of the answer and state any condition that must be met. For a conditional response, note the condition in the comparison sheet, name the person who can resolve it and identify the decision that must wait. This gives the commercial and operating teams the same evidence when they review the proposal.
At the approval meeting, check whether the answer is reflected in the latest documents and whether both parties are reviewing the same revision. Record the accepted position in the order and give the receiving team a practical way to check it. If the answer cannot be confirmed until delivery, agree on the evidence the receiving team should request and how it should report a discrepancy. When the vehicle or assignment changes later, pull the record back into review and identify the affected documents. A brief note recording what changed and why makes the next review faster and keeps the original decision traceable.
Loaded conditions
For the loaded conditions review, collect available documents on the actual cargo and container. Match the evidence to the loaded case that the fleet expects to operate before treating it as part of the offer. Give the comparison sheet a source column with a document identifier, a date and the person who supplied it. If a record only describes a product family, mark it as background and ask for the details applicable to the proposed equipment. That distinction matters because the engineering review needs both cases separately. Keep the underlying document with the review so someone joining the order later can understand the decision without reconstructing it from messages.
Consider this illustrative situation: an empty move is used as evidence for a loaded one. Write down what is known, what still depends on a supplier response and which decision could change if the answer is different. The buyer can then ask one specific question and send the relevant record with it. Ask the respondent to identify the scope of the answer and state any condition that must be met. For a conditional response, note the condition in the comparison sheet, name the person who can resolve it and identify the decision that must wait. This gives the commercial and operating teams the same evidence when they review the proposal.
At the approval meeting, check whether the answer is reflected in the latest documents and whether both parties are reviewing the same revision. Record the accepted position in the order and give the receiving team a practical way to check it. If the answer cannot be confirmed until delivery, agree on the evidence the receiving team should request and how it should report a discrepancy. When the vehicle or assignment changes later, pull the record back into review and identify the affected documents. A brief note recording what changed and why makes the next review faster and keeps the original decision traceable.
Empty returns
For the empty returns review, collect the itinerary and dispatch instructions for empty trips. Match the evidence to the terminal involved on each return leg before treating it as part of the offer. Give the comparison sheet a source column with a document identifier, a date and the person who supplied it. If a record only describes a product family, mark it as background and ask for the details applicable to the proposed equipment. That distinction matters because the return leg needs its own site record. Keep the underlying document with the review so someone joining the order later can understand the decision without reconstructing it from messages.
Consider this illustrative situation: return work goes to another location with different access. Write down what is known, what still depends on a supplier response and which decision could change if the answer is different. The buyer can then ask one specific question and send the relevant record with it. Ask the respondent to identify the scope of the answer and state any condition that must be met. For a conditional response, note the condition in the comparison sheet, name the person who can resolve it and identify the decision that must wait. This gives the commercial and operating teams the same evidence when they review the proposal.
At the approval meeting, check whether the answer is reflected in the latest documents and whether both parties are reviewing the same revision. Record the accepted position in the order and give the receiving team a practical way to check it. If the answer cannot be confirmed until delivery, agree on the evidence the receiving team should request and how it should report a discrepancy. When the vehicle or assignment changes later, pull the record back into review and identify the affected documents. A brief note recording what changed and why makes the next review faster and keeps the original decision traceable.
Tractor combination
For the tractor combination review, collect the tractor details and chassis drawing. Match the evidence to the tractor type assigned to the route before treating it as part of the offer. Give the comparison sheet a source column with a document identifier, a date and the person who supplied it. If a record only describes a product family, mark it as background and ask for the details applicable to the proposed equipment. That distinction matters because the buyer needs to document the combinations for review. Keep the underlying document with the review so someone joining the order later can understand the decision without reconstructing it from messages.
Consider this illustrative situation: a substitute tractor is introduced during peak periods. Write down what is known, what still depends on a supplier response and which decision could change if the answer is different. The buyer can then ask one specific question and send the relevant record with it. Ask the respondent to identify the scope of the answer and state any condition that must be met. For a conditional response, note the condition in the comparison sheet, name the person who can resolve it and identify the decision that must wait. This gives the commercial and operating teams the same evidence when they review the proposal.
At the approval meeting, check whether the answer is reflected in the latest documents and whether both parties are reviewing the same revision. Record the accepted position in the order and give the receiving team a practical way to check it. If the answer cannot be confirmed until delivery, agree on the evidence the receiving team should request and how it should report a discrepancy. When the vehicle or assignment changes later, pull the record back into review and identify the affected documents. A brief note recording what changed and why makes the next review faster and keeps the original decision traceable.
Site access
For the site access review, collect the access and handling brief from each terminal. Match the evidence to the pickup and delivery sites named in dispatch before treating it as part of the offer. Give the comparison sheet a source column with a document identifier, a date and the person who supplied it. If a record only describes a product family, mark it as background and ask for the details applicable to the proposed equipment. That distinction matters because operations should confirm that part of the duty. Keep the underlying document with the review so someone joining the order later can understand the decision without reconstructing it from messages.
Consider this illustrative situation: a drawing fits the container but leaves site access unresolved. Write down what is known, what still depends on a supplier response and which decision could change if the answer is different. The buyer can then ask one specific question and send the relevant record with it. Ask the respondent to identify the scope of the answer and state any condition that must be met. For a conditional response, note the condition in the comparison sheet, name the person who can resolve it and identify the decision that must wait. This gives the commercial and operating teams the same evidence when they review the proposal.
At the approval meeting, check whether the answer is reflected in the latest documents and whether both parties are reviewing the same revision. Record the accepted position in the order and give the receiving team a practical way to check it. If the answer cannot be confirmed until delivery, agree on the evidence the receiving team should request and how it should report a discrepancy. When the vehicle or assignment changes later, pull the record back into review and identify the affected documents. A brief note recording what changed and why makes the next review faster and keeps the original decision traceable.
Mixed deployment
For the mixed deployment review, collect a list of combinations with their frequency. Match the evidence to the assignments the fleet expects to support before treating it as part of the offer. Give the comparison sheet a source column with a document identifier, a date and the person who supplied it. If a record only describes a product family, mark it as background and ask for the details applicable to the proposed equipment. That distinction matters because purchasing can compare dedicated units and a mixed fleet on real demand. Keep the underlying document with the review so someone joining the order later can understand the decision without reconstructing it from messages.
Consider this illustrative situation: a rare dispatch case drives a complex configuration. Write down what is known, what still depends on a supplier response and which decision could change if the answer is different. The buyer can then ask one specific question and send the relevant record with it. Ask the respondent to identify the scope of the answer and state any condition that must be met. For a conditional response, note the condition in the comparison sheet, name the person who can resolve it and identify the decision that must wait. This gives the commercial and operating teams the same evidence when they review the proposal.
At the approval meeting, check whether the answer is reflected in the latest documents and whether both parties are reviewing the same revision. Record the accepted position in the order and give the receiving team a practical way to check it. If the answer cannot be confirmed until delivery, agree on the evidence the receiving team should request and how it should report a discrepancy. When the vehicle or assignment changes later, pull the record back into review and identify the affected documents. A brief note recording what changed and why makes the next review faster and keeps the original decision traceable.
Drawing evidence
For the drawing evidence review, collect a marked drawing and written response for each case. Match the evidence to the drawing revision attached to the offer before treating it as part of the offer. Give the comparison sheet a source column with a document identifier, a date and the person who supplied it. If a record only describes a product family, mark it as background and ask for the details applicable to the proposed equipment. That distinction matters because the buyer needs to know which combinations were actually reviewed. Keep the underlying document with the review so someone joining the order later can understand the decision without reconstructing it from messages.
Consider this illustrative situation: a supplier gives a single approval for several cases. Write down what is known, what still depends on a supplier response and which decision could change if the answer is different. The buyer can then ask one specific question and send the relevant record with it. Ask the respondent to identify the scope of the answer and state any condition that must be met. For a conditional response, note the condition in the comparison sheet, name the person who can resolve it and identify the decision that must wait. This gives the commercial and operating teams the same evidence when they review the proposal.
At the approval meeting, check whether the answer is reflected in the latest documents and whether both parties are reviewing the same revision. Record the accepted position in the order and give the receiving team a practical way to check it. If the answer cannot be confirmed until delivery, agree on the evidence the receiving team should request and how it should report a discrepancy. When the vehicle or assignment changes later, pull the record back into review and identify the affected documents. A brief note recording what changed and why makes the next review faster and keeps the original decision traceable.
Dispatch handover
For the dispatch handover review, collect a concise list of accepted combinations and exclusions. Match the evidence to the delivered chassis identifier before treating it as part of the offer. Give the comparison sheet a source column with a document identifier, a date and the person who supplied it. If a record only describes a product family, mark it as background and ask for the details applicable to the proposed equipment. That distinction matters because dispatch needs access to the configuration record. Keep the underlying document with the review so someone joining the order later can understand the decision without reconstructing it from messages.
Consider this illustrative situation: operators see only the marketing model name. Write down what is known, what still depends on a supplier response and which decision could change if the answer is different. The buyer can then ask one specific question and send the relevant record with it. Ask the respondent to identify the scope of the answer and state any condition that must be met. For a conditional response, note the condition in the comparison sheet, name the person who can resolve it and identify the decision that must wait. This gives the commercial and operating teams the same evidence when they review the proposal.
At the approval meeting, check whether the answer is reflected in the latest documents and whether both parties are reviewing the same revision. Record the accepted position in the order and give the receiving team a practical way to check it. If the answer cannot be confirmed until delivery, agree on the evidence the receiving team should request and how it should report a discrepancy. When the vehicle or assignment changes later, pull the record back into review and identify the affected documents. A brief note recording what changed and why makes the next review faster and keeps the original decision traceable.
Changes after delivery
For the changes after delivery review, collect an updated assignment request and the relevant vehicle records. Match the evidence to the new container, site or tractor involved before treating it as part of the offer. Give the comparison sheet a source column with a document identifier, a date and the person who supplied it. If a record only describes a product family, mark it as background and ask for the details applicable to the proposed equipment. That distinction matters because the responsible team must review the changed case. Keep the underlying document with the review so someone joining the order later can understand the decision without reconstructing it from messages.
Consider this illustrative situation: a recently acquired unit is assigned under an old assumption. Write down what is known, what still depends on a supplier response and which decision could change if the answer is different. The buyer can then ask one specific question and send the relevant record with it. Ask the respondent to identify the scope of the answer and state any condition that must be met. For a conditional response, note the condition in the comparison sheet, name the person who can resolve it and identify the decision that must wait. This gives the commercial and operating teams the same evidence when they review the proposal.
At the approval meeting, check whether the answer is reflected in the latest documents and whether both parties are reviewing the same revision. Record the accepted position in the order and give the receiving team a practical way to check it. If the answer cannot be confirmed until delivery, agree on the evidence the receiving team should request and how it should report a discrepancy. When the vehicle or assignment changes later, pull the record back into review and identify the affected documents. A brief note recording what changed and why makes the next review faster and keeps the original decision traceable.
For dispatches that include ISO tank containers, see the 20-foot ISO tank container chassis fit checks.
Frequently asked questions
Does a 40-foot chassis automatically accept every 20-foot arrangement?
No. Confirm the supported positions and locking layout.
Should empty returns be included?
Yes. They are part of the intended duty and affect dispatch planning.
Can a product picture replace a drawing?
No. Request a configuration drawing and written confirmation.
Is the tractor relevant?
Yes. Provide tractor details so the complete combination can be reviewed.
What if a new customer uses another terminal?
Confirm the site requirements and review affected arrangements.
What records should buyers retain?
Keep dispatch cases, supplier responses, approved drawings, exclusions and unresolved issues.