Voyage Earnings Inputs: Know What Must Be Refreshed

Key takeaways

• Separate observation time, offer validity and applicability to the proposed voyage.
• Keep executable terms distinct from market context and internal assumptions.
• Refresh the inputs capable of changing the decision first.
• Preserve the agreed basis of committed items unless the actual arrangement changes.
• Mark unavailable evidence openly instead of presenting an unsupported point estimate.

Ask what kind of input the number represents

A voyage model can contain several types of information. Some values come from agreed terms. Others come from live proposals, supplier estimates, operational forecasts or internal assumptions. Their refresh needs differ because they play different roles.

An agreed revenue amount should not be replaced automatically by a newer market indication. The indication may help assess a future opportunity, but it does not rewrite the existing agreement. Conversely, an unaccepted proposal should not remain executable in the model after its actual validity or conditions no longer support that use.

Label each important input by status. A short description such as agreed, offered, estimated or assumed is useful when accompanied by the actual scope and evidence. The label alone is not enough: an estimate for another call can still be irrelevant even if it was prepared recently.

The freshness question is therefore whether the input still answers the model's question. Timestamp checks support that assessment, but they do not replace it.

Distinguish three dates

Observation time records when information was obtained or observed. Offer validity concerns the period or conditions under which the counterparty's proposal can be used. Applicability concerns whether the input still fits the voyage being evaluated.

Those are different concepts. A proposal received recently may have been superseded by a revised cargo quantity. A current market observation may never have been an offer available to the vessel. A signed commitment may continue to govern even after its original observation date looks old.

The desk should not invent a universal expiry period. Use actual offer conditions, the provider's stated basis and the business's authorised review process. Where validity is unclear, identify that uncertainty and seek confirmation before treating the value as executable.

A useful model shows the relevant dates or conditions beside the input. It avoids using one updated-at field to imply that every underlying assumption has been checked.

Use a refreshable input register

For a current transaction, the current approved earnings-input register is not provided; obtain current verified information. The unresolved inputs that could change the recommendation are not provided; obtain current verified information. These placeholders require the authorised voyage record; public source unavailable is an acceptable status for private commercial terms.

The register should point to evidence rather than reproduce confidential terms indiscriminately. Its purpose is to make the decision basis inspectable by the people authorised to review it.

Refresh the consequential uncertainty first

Not every input deserves equal effort at every review. Use the model's sensitivity to identify which unresolved values could change the choice between alternatives.

If a minor estimate moves without changing the conclusion across its supported range, a precise update may be less urgent than resolving a major duration dependency. That is a prioritisation judgement, not permission to mislabel the minor estimate as final.

Keep a distinction between accuracy and decision relevance. An input can be uncertain but immaterial to the immediate choice. Another can be only slightly uncertain while sitting close to the threshold that reverses the ranking.

The reviewer should see both. Mark the uncertainty honestly, then explain why the desk is focusing on a particular confirmation. This makes the refresh process serve the commercial decision instead of becoming a ritual of replacing dates.

Fictional case: a newer estimate is the wrong estimate

A fictional desk compares two employment alternatives. Its model contains a port-service estimate for the actual vessel and intended receiving arrangement. Shortly before review, someone replaces it with a more recently received figure from the same general port area.

The new estimate concerns a different service boundary. It excludes work that the first estimate included. The spreadsheet timestamp improves, and the projected contribution rises, but no actual saving has been established.

The reviewer traces the input back to its scope. The desk restores the applicable estimate while requesting a current confirmation for the actual call. It retains the newer figure only as context for a separately defined alternative, with the missing service identified.

The error was not stale arithmetic. It was the assumption that recency implied comparability. A freshness policy based only on age would have encouraged the wrong replacement.

Keep committed and prospective views separate

Once an employment is committed, the review may need two views. One shows the expected result under the actual commitment. Another shows the market context or alternative opportunity relevant to a new decision.

Do not overwrite the first with the second. Doing so can make the original voyage appear to earn terms that were never agreed. It can also obscure the difference between a changing operating estimate and a changing commercial market.

Where a committed input is corrected, explain the reason. Perhaps the original model misunderstood a deduction or omitted an included service. That is a correction to the model, not necessarily a change in the contract.

The same distinction applies to expected receipts. New evidence may alter the assessment of a conditional recovery without altering the underlying claim position. Keep the commercial, legal and cash assumptions sufficiently separate for the responsible reviewers to understand the change.

Expire the use, not just the number

When an input loses support for a particular purpose, state what use is no longer justified. A lapsed proposal may remain useful historical context while no longer supporting an executable comparison. A superseded duration estimate may still explain why the earlier decision was made.

Preserve that history without allowing it to remain the active basis. The current model should identify the supported replacement or show the gap openly.

If no replacement is available, use a clearly labelled scenario range where appropriate, or state that the decision cannot yet rely on a firm result. Do not fill the cell with a precise-looking number merely to keep the table complete.

Common mistakes

One mistake is replacing an applicable input with a newer but differently scoped number. Another is using a market observation as though it were a firm offer available to the vessel.

A third error is refreshing every timestamp while leaving the commercial assumptions untouched. Finally, do not overwrite committed revenue with a current indication and describe the resulting movement as a change in the actual voyage's earnings.

Where Zeaclub fits

Zeaclub supports agentic, AI-assisted operations with a human in control.

Zeaclub provides a multi-party shared workspace for owners, charterers, brokers and port agents.

Explore Zeaclub

Visit the Zeaclub website