US Chartering Decision Tree: Decide What Information Comes Next

Use the tree to narrow the next action

A chartering decision tree is most useful when it identifies the next information needed to progress a cargo enquiry. It should not promise to choose a vessel or settle a contract from a few answers. Its purpose is to prevent the team from requesting a detailed price before the transport concept is clear, or from collecting low-value details while a decisive uncertainty remains unresolved.

For a Houston industrial exporter, the first useful branch might distinguish an exploratory project from a shipment with a confirmed commercial need. A later branch might ask whether the shipping configuration is sufficiently defined for a meaningful enquiry. The tree should reflect the actual process and the people responsible for each answer.

ASQ describes flowcharts as process maps that can include actions, inputs, decisions and participants. ASQ flowchart guidance.

The design below is an original commercial application. It emphasizes decision dependencies rather than a universal sequence that every US cargo must follow.

Start with the decision the user is trying to make

Ask whether the immediate objective is feasibility, a budget, a firm proposal or a review of changed terms. These objectives require different levels of information. A preliminary budget can sometimes proceed with clearly stated assumptions; a final commitment needs the relevant confirmations and authority. The tree should route the enquiry according to that purpose.

Next identify the cargo and movement at a practical level. If the commodity or shipping configuration is unknown, request the information that determines which service concepts should be considered. If the cargo is defined but the destination arrangement is uncertain, direct attention there. Do not require the same attachment set for bulk grain and packaged machinery simply because the form can store both.

Use each branch to produce a specific action: request a current piece list, confirm the intended receiving facility, clarify the delivery objective or seek the responsible party's review. A branch ending in incomplete is less useful than one explaining what is missing and why it matters to the next decision.

Give unknown its own path

A binary yes-or-no design can force users to guess. If a question asks whether a cargo is accepted, the answer may be not yet reviewed. That is neither rejection nor confirmation. Provide an unknown or pending path that identifies the evidence and decision-maker needed to resolve it.

Separate a user's assertion from supporting evidence. Someone may say the cargo dimensions are final while attaching an earlier drawing. The tree can request reconciliation without declaring the shipment unsuitable. This helps the team improve the information basis while preserving the distinction between a data-quality issue and a technical decision.

ONE's special-cargo booklet distinguishes initial enquiry, quotation, technical review and booking confirmation. ONE special-cargo booklet.

That documented sequence is one carrier example of stages serving different purposes. The proposed tree should route work to the relevant stage, not treat completion of an enquiry form as confirmation of a booking.

Walk through a fictional branching case

Imagine a hypothetical Houston exporter seeking a budget for a machine that is still being prepared for shipment. The product model is known, but the final shipping base and accessory arrangement are not. The customer's destination is known at city level, while the receiving facility remains undecided.

A poorly designed tree might ask for a freight target and immediately rank transport options. A more useful tree first asks whether the uncertain configuration could affect the service concept. If the answer is yes or unknown, it requests the current drawing and a description of the expected changes. It can still permit a preliminary budget discussion, provided the assumptions and limitations remain visible.

After the shipping configuration is confirmed, the next branch asks whether the destination handoff is sufficiently defined for the requested scope. If the exporter wants only a port-to-port budget, a broader destination area may support an initial comparison. If it wants delivery to the final facility, the missing receiving details become essential to that broader request.

The same cargo therefore follows different paths depending on the decision objective. The tree is useful because it asks the next relevant question, not because it forces every enquiry through every possible field.

Avoid false precision in branch conditions

Use conditions that users can answer from actual evidence. A question such as is the shipment high risk is too vague unless the organization defines the term and assigns the assessment. A more useful branch asks whether a required specialist review has been completed for the current proposal, then routes pending cases appropriately.

Do not embed technical acceptance limits or legal rules without a maintained authoritative basis and responsible owner. A commercial tree can identify that such a review is needed without attempting to reproduce it. This keeps the tool useful as a coordinator while avoiding unsupported decisions outside the team's competence.

Where a branch depends on a number, identify the unit, source and reason for the threshold. Internal commercial thresholds should be labeled as company policy rather than industry standards. Changes to those thresholds should be reviewed because they can alter which enquiries receive attention and which are deferred.

Test the tree with difficult examples

Use completed enquiries to see whether the proposed paths would have asked the right questions in time. Include incomplete, contradictory and changing cases, not only clean examples. A tree that works for a fully documented shipment may fail precisely where users need it most.

Watch for loops that repeatedly request the same information without explaining the unresolved issue. Give users a route to an accountable person when the available choices do not fit. Record why manual intervention was needed so the process owner can decide whether the tree should change or whether the exception should remain human-led.

Measure the usefulness of the next action rather than the number of completed fields. Did the branch resolve a decision-relevant uncertainty? Did it send the question to the right party? Did it avoid unnecessary requests? Those observations provide a better basis for improvement than a completion percentage alone.

Keep the final commercial choice with the team

The tree's output should summarize the current objective, the next action, the evidence required and the responsible person. If the enquiry is ready for a proposal, it should say what that readiness means and which confirmations remain separate. It should not silently convert workflow progress into authority to accept terms.

Bring several real enquiry paths to Zeaclub to discuss a proposed chartering decision tree. The aim is a practical US workflow that directs attention to the next useful question, supports informed human decisions and learns from exceptions without pretending that a branching form can replace commercial judgment.

Sources

Related articles