Voyage-estimate access: separate inputs and model changes

Key takeaways

• Define permissions around the estimate's inputs, calculations and outputs.
• Keep model changes distinguishable from edits to a particular voyage case.
• Give reviewers the evidence they need without granting unnecessary editing rights.
• Check what an assistant can retrieve as well as what its user can see.
• Test permissions with realistic tasks and deliberately restricted material.

Map the objects that require control

An estimate is more than one spreadsheet or screen. It can contain source messages, quotations, vessel assumptions, commercial scenarios, formulas, comments and a summary intended for a particular audience. Those objects may require different handling.

Identify which information is specific to the current case and which belongs to a reusable model. A preparer may need to change a voyage quantity while the underlying calculation logic remains subject to a separate review process.

Also identify outputs created from the estimate. An internal comparison can contain material that should not be included in a counterparty-facing summary. Permission to read the internal record does not answer who may receive each derived document.

The design below is an original business worksheet. It does not claim that a particular platform supports these distinctions, and it leaves implementation to the organisation's security and system specialists.

Describe the requested action precisely

Avoid a single broad permission called work on estimate. Instead, describe whether the user needs to add a source, propose an assumption, accept a change, edit a formula or distribute an output.

These distinctions help reviewers understand the consequence of an access request. Editing a quoted amount in a case and changing the rule that applies that amount across every case are materially different activities.

NIST's SP 800-162 definition of attribute-based access control considers attributes of users, resources, requested operations and sometimes environmental conditions when evaluating authorisation.

That technical concept provides context for asking specific business questions. It does not require the desk to adopt a particular access-control architecture or imply that job titles alone are an adequate design.

Propose permissions by estimating responsibility

The organisation may combine responsibilities, but it should preserve their meaning. A combined role should not make it impossible to identify whether someone acted as preparer, model reviewer or commercial decision-maker.

Test the limits as well as the permitted actions. A reviewer opening the necessary evidence is only part of the check; the team should also verify the behaviour when that role attempts a change outside its accepted scope.

Consider the assistant's information reach

If an assistant retrieves material from connected records, review the retrieval scope explicitly. A narrow user interface does not by itself establish what information the connected process can access or include in a response.

Ask specialists to demonstrate the configured behaviour with approved test material. Can a user preparing one case obtain an unrelated negotiation record through a question or generated summary? Can the assistant cite a source the user is not entitled to inspect? The appropriate expected behaviour should be defined before the test.

Do not solve a missing-access problem by sharing a colleague's credentials or moving restricted material into an unrestricted folder. Use the organisation's authorised request process and preserve the business reason for any additional access.

Keep the user informed when evidence cannot be retrieved. The assistant should not conceal an access limitation by inventing a substitute value or presenting an unsupported answer as complete.

Separate case edits from model revisions

Give the estimating team a visible way to propose a model change. The proposal should explain the intended calculation, the cases affected and the evidence used to verify the result.

Do not let a correction made for one voyage silently alter other estimates. A local exception may be appropriate for a particular case without becoming the default formula or inclusion rule for future work.

The reverse problem also matters. If a model revision affects active estimates, identify which cases require review. A user viewing an older result should be able to understand which calculation basis produced it.

Access controls alone do not make a model correct. Combine them with a review process that checks meaning and arithmetic, using the responsible people for the commercial and technical questions involved.

Fictional case: a local correction changes every scenario

A fictional analyst notices that a voyage's special service arrangement does not fit the estimate's ordinary charge treatment. The analyst has broad editing access and changes a shared calculation rule to make the current case appear correctly.

The same rule is used by other scenarios whose service arrangements differ. Their outputs change even though their preparers have not revised the underlying assumptions. The problem is discovered when a reviewer asks why a comparison moved without new source evidence.

The team restores a reviewed model basis and separates the case-specific treatment from the reusable rule. It introduces a visible proposal route for model changes and tests what ordinary preparers can alter. Affected estimates are reviewed before further reliance.

This fictional case illustrates a boundary between editing a commercial case and changing the model used by other cases. The appropriate permission design should make that distinction visible and reviewable.

Review the output audience

Before distributing a result, identify what the recipient needs. An internal reviewer may need source detail and alternative assumptions; an external recipient may need only a specifically approved commercial summary.

Test generated documents and exports, not just the main estimate view. A summary can unintentionally include comments, hidden alternatives or source references that were never intended for its audience.

Retain the qualifications necessary to understand the approved output. Restricting confidential information should not turn a provisional estimate into an apparently confirmed statement. The output owner must balance appropriate disclosure with accurate meaning.

Revisit permissions as involvement changes

Temporary cover, revised responsibilities and completed assignments can change what access a person needs. Define who reviews those changes and how the resulting configuration is confirmed.

Keep the business owner involved. Administrators can implement a requested role, but they may not know whether a person still needs access to the underlying commercial records. The request should supply that purpose clearly.

When an exception grants broader capability than usual, record its scope and review condition. Do not allow an exceptional arrangement to become the unexamined model for every later user.

Common mistakes

Avoid treating all estimate editing as one permission, giving case preparers unnoticed control over shared formulas or checking only the visible screen. Review the assistant's retrieval and output paths too.

Another mistake is assuming that access approval establishes commercial authority. Permission to prepare or inspect an estimate does not by itself authorise the decision it supports.

Where Zeaclub fits

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

Zeaclub offers digitalised procedures across the voyage workflow.

Explore Zeaclub

Explore Zeaclub