Evos

Laytime & demurrage claims · Shipowners & vessel operators

Demurrage earned and claimed without a post-fixture backlog.

Builds laytime statements from the SOF and files demurrage claims before the time bar. Today it runs on people — checking, chasing, and keying it by hand, one case at a time.

The reality

Builds laytime statements from the SOF and files demurrage claims before the time bar.

SOF arrives from agent — calculates laytime, identifies 2.4 days on demurrage, files claim inside the time bar. That is the shape of the work, over and over — and every case is a person’s time.

An Evos operator owns that loop end to end: it laytime & demurrage claims runs the job without a person driving each step, on the systems your team already uses.

How the operator runs laytime & demurrage claims

The outcome

−50% of demurrage-desk work off the team

Demurrage earned and claimed without a post-fixture backlog.

  • SOF arrives from agent — without a person driving it
  • Handled on the systems your team already uses
  • A full, auditable trail on every decision

Common questions

Laytime & demurrage claims

What does the Laytime & demurrage claims operator do?
An Evos operator owns that loop end to end: it laytime & demurrage claims runs the job without a person driving each step, on the systems your team already uses.
What impact does the Laytime & demurrage claims operator have?
−50% of demurrage-desk work off the team. Demurrage earned and claimed without a post-fixture backlog.
How does the Laytime & demurrage claims operator work?
Watches the systems and channels where the work lands, and picks it up the moment it appears. Runs the core of the job — the decisions and actions — without a person driving each step. Resolves the case and writes the result back to your systems of record, with a full trail.

More operators in Shipowners & vessel operators

See the full catalogue →

The operations workforce you don’t have to hire.