Skip to main content
dossima

Claims software guide · 9 min read

How to organise a marine claim file from email

Updated 16 November 2026

A stack of white ring binders on a white surface
Photo: Beatriz Pérez Moya on Unsplash

For most claims teams the claim file is not one place. It is a mailbox, a shared drive and a spreadsheet that someone updates when there is time. This guide sets out a tool-neutral way to organise a marine claim file from email: one reference, one folder, one index and one log.

Why the file falls apart

A claim arrives as a stream of messages. A surveyor sends a report, the owner forwards a letter, the broker asks for an update, the carrier replies after three weeks. Each message lands in one person's mailbox. The attachment is saved to a drive, sometimes under another name, and the spreadsheet lists some of it. The file exists only as long as the person who built it is at their desk.

The same pattern appears at claims-settling agents, in broker claims teams and with insurer claims handlers. The documents differ: delivery receipts and outturn reports in cargo, repair quotations and class reports in hull and machinery. The failure is the same: nobody can say quickly which documents are in, which version is current and what was asked of whom. The rest of this guide is a set of habits against that.

Invented example. A cargo claim has twelve emails over three weeks. Survey report v1 arrives on a Monday and v2 on a Thursday. Both sit in different mailboxes, and the one saved to the drive is called "survey final". A colleague takes over and quotes a damage date from v1. Nobody notices until the carrier's reply cites v2. With one reference, versioned filenames and an index entry that says "v2 received 12 March, supersedes v1", the colleague would have seen it at once.

Step by step: set up the file

  1. Create the claim reference when the claim is opened and use it in the folder name, in every subject line and in every filename.
  2. Create one folder per claim in a shared location with a fixed set of subfolders (see below). Do not use personal folders as the file.
  3. File each email and each attachment into the claim folder on the day it arrives. Save the email itself as well when its text carries facts.
  4. Name every document with the naming convention, never overwrite it and add a new version when a document is revised.
  5. Enter every document in the index with its status and every request in the request log.
  6. At each handover or review, check the index against the folder and the log against the mailbox.

One reference in every subject line

Choose a short reference that does not repeat and does not carry personal data, for example year, number and line of business. Put it at the start of every subject line you send, and ask parties you write to regularly to keep it when they reply. Third-party replies often drop it or change the subject, so add the reference when you file a message that arrives without it, not later.

A reference helps in two ways. Search finds all messages of a claim in one query, and a colleague who has never seen the claim can reconstruct it from the mailbox if the folder is incomplete.

Folders and a naming convention

Keep the folder structure the same for every claim, so that people know where to look. A small set is enough, such as: incoming documents, outgoing correspondence, surveys and reports, financial documents, and working notes. Avoid deep trees. The index does the work of telling people what is in the file.

A filename should tell you what the document is without opening it. A common pattern puts the claim reference first, then date, party, document type and version. For example: 26-0417_2026-03-12_Surveyor_Survey-report_v2.pdf. Use the date of the document, not the date you saved it, and write dates in a sortable order (year, month, day). Keep names plain: no spaces that break links, and no "final" or "final2".

  • Claim reference first, so that files group together in any list.
  • Date of the document in year-month-day order.
  • Party that produced it (surveyor, owner, carrier, broker, insurer).
  • Document type in plain words (survey report, invoice, delivery receipt, notice of claim).
  • Version as v1, v2, v3. A new version never replaces an old one.

Keep every version

Surveyors revise reports, yards revise quotations and brokers revise summaries. Each revision can change a fact: a date, an amount or a conclusion. Keep all versions in the folder. In the index, mark which version is current and which are superseded, and add the date you received each one.

When a statement relies on a document, name the version. "Damage first noticed 12 March (survey report v2, page 2)" can be checked. "Damage first noticed 12 March" cannot. The same applies to emails: if an email text carries a fact, file the email as its own document.

The index: what is in, what is missing

The index is a list of the documents the claim needs, not only the ones you have. Start it from a checklist for the type of claim and add documents as the claim develops. Each line has the document, who provides it, a status and a date. Our guides on marine cargo claim documents and hull and machinery claim documents list the documents by stage, and the checklists page collects printable lists.

DocumentWho provides itStatusDate and note
Survey reportSurveyorReceived v2, v1 superseded12 Mar, v2 changes the damage date
Delivery receiptReceiverRequestedRequested 14 Mar, chased 21 Mar
Commercial invoiceShipperMissingNot yet requested
Notice of claimAgentSentSent 15 Mar to the carrier by email and courier
Carrier's replyCarrierAwaitedAcknowledged 18 Mar, no substance yet

Statuses can be simple: expected, requested, received, superseded, not needed. What matters is that "requested" always carries a date. A missing document with no request date is a gap nobody owns.

A log of requests and chasers

Keep a separate log of what you asked, of whom, when, and what came back. One line per request and one per chaser. It answers the questions that arrive later: when did we first ask the receiver for the delivery receipt, and who replied? It also supports notice and recovery steps, where the date of a message can matter. For time limits and notice, see our guides on time bars and notice of claim to the carrier, and confirm each period for your claim.

  • Date and time the request was sent, and the channel (email, call, courier).
  • To whom, with the role (receiver, surveyor, carrier).
  • What was asked, in one line, with the reference to the document in the index.
  • Reply received, with date, or the chaser date and the date you plan the next one.

Who said what, and on which page

Facts in a claim come from documents, and the same fact can appear in two documents with different values. Record each fact with its source: document, version and page or paragraph. A short facts note in the file helps: date, fact, source, and whether another document gives a different value. Where two documents disagree, note both and the source of each. Do not choose between them in the note. That decision belongs to the person handling the claim and, where it concerns cover or liability, to those who decide it under the contract and the law.

For calls and meetings, write a short note on the day: who, when, what was said, what was agreed. File it with the claim reference. A note written the same day is easier to rely on than a recollection written a month later.

Handover to a colleague

A file is well organised if a colleague can take it over in an hour without asking the previous handler. A short handover note helps: where the claim stands, what is outstanding, what was last sent and what is due next. Point to the index and the request log rather than retelling them. Check three things before handing over: the folder matches the index, the log matches the mailbox, and the current version of each document is marked.

Also move mailbox content that only you can see. A claim thread that lives only in one person's inbox disappears from the file when that person is away. Use a shared mailbox or a rule that files claim emails into the claim folder.

Personal data, retention and GDPR

Claim emails and attachments often contain personal data: names and contact details of crew, surveyors, claimants and brokers, and sometimes statements, medical details or identity documents. Where the GDPR applies, three principles from Article 5 shape the file. Data must be adequate, relevant and limited to what is necessary for the purpose (data minimisation). It must be accurate, and inaccurate data must be corrected or erased without delay. It may be kept in a form that identifies people for no longer than is necessary (storage limitation).

In practice, file what the claim needs and leave out unrelated private content from forwarded threads. Keep statements factual and verified, and avoid speculation about people in emails and notes. Agree a retention rule for closed files. The EDPB guide for small businesses recommends an internal retention policy for each purpose, with a procedure for deleting or anonymising data once it is no longer needed. How long a closed claim file must be kept depends on legal and contractual obligations and on your own policy. Check them with your compliance contact.

What to look for in software

You can run this method with folders, a spreadsheet and discipline. Software earns its place when it does the filing and the bookkeeping for you: it ties emails and attachments to a claim, keeps versions, shows the index with status and keeps the request log. Our guide on marine claims management software sets out the criteria to check, so this guide does not repeat them. Whichever tool you use, test it against the habits above: can a colleague find the current version of a document, and the date you asked for the missing one, in a minute?

Common gaps in a claim file built from email

  • Attachments that exist only in a mailbox.
  • Two copies of a document with different names and no record of which is current.
  • A document marked "requested" with no date or recipient.
  • No log of chasers, so nobody knows when a party last replied.
  • A fact quoted without a document, version or page.
  • Notes of calls kept in notebooks or not at all.
  • Personal data copied into emails and notes beyond what the claim needs.
  • No rule for how long a closed file is kept.

Not legal advice. This guide describes working practice. Data protection duties, retention periods and the notice and time limits of a claim depend on the law, your contracts and your own policies. Confirm them for your claim and your organisation.

FAQ

What should a naming convention contain?

The claim reference, the date of the document, the party that produced it, a plain document type and a version. Put them in a fixed order so that files sort sensibly.

Should I keep superseded versions?

Yes. Mark them as superseded in the index and keep them in the folder. A revision can change a fact, and a statement made earlier may rely on the old version.

How long should I keep a closed claim file?

It depends on legal and contractual obligations and on your retention policy. The GDPR sets the principle of storage limitation but no period. Check with your compliance contact and apply one rule to every file.

Is a shared drive enough?

It can be, with discipline: the same folders, the same naming, an index and a log for every claim. Problems start when the drive and the mailbox drift apart. That is where software that ties the two together starts to pay off.

Dossima files these documents into one claim file per claim from your inbox and folders, keeps every version and shows what is still missing. The decision stays with you.

Sources

More guides

See Dossima first.

Leave your work email and we'll be in touch to schedule your demo.

We only email you about Dossima. Privacy Policy.