1. Download the CSV
Use the CSV as the portable source format. One row per client case. Keep it in your own environment — no cloud dependency.
Marine Broker — CSV intake template
Marine Broker Record Sheet
Track client cases — war risk responses, force majeure notices, D&D disputes — across a broker portfolio. Each column maps directly to an ERF field. Produce the structured pack when the record is ready. No translation step.
Vraimony does not connect to your Google account. Start from the free CSV, import it into your own sheet, keep Google optional.
No OAuth
No add-on
CSV portable
ERF-compatible columns
Marine brokers
How to set it up
Ready in under a minute
2. Open a new Google Sheet
Create a blank sheet in your own Google account. Vraimony never requests account access for this step.
3. Import and work
File → Import → upload the CSV. Fill a row per client case. When a case is ready to package, the row becomes the ERF intake.
What is inside
One row per client case — three case types supported
The sheet supports three marine broker case types in one unified structure. Fill the columns relevant to your case type — leave others blank.
| case_ref | case_type | client_role_id | vessel_imo | event_date | cancellation_notice_ref | advisory_ref | deadline | mitigation_steps | underwriter_target | evidence_degree | status |
|---|---|---|---|---|---|---|---|---|---|---|---|
| BROKER-2026-001 | war_risk | CLIENT-REF-A | IMO 9876543 | 2026-03-05 | GARD-CANCEL-2026-0305 | JWC-HORMUZ-2026-03 | 2026-03-07 18:00 UTC | Reroute via Cape, alternative cover sought from [underwriter] | Skuld (alternative) | 8 | Declared |
| BROKER-2026-002 | force_majeure | CLIENT-REF-B | 2026-03-04 | UKMTO-2026-03 | Per contract clause 18.2 | Alternative supplier activated, counterparty notified 2026-03-05 | Counterparty legal | 7 | Declared | ||
| BROKER-2026-003 | demurrage | CLIENT-REF-C | IMO 1234567 | 2026-03-08 | INVOICE-DD-20260308 | Per charterparty clause 7 | Port congestion documented via UKMTO notice | Carrier dispute desk | 6 | Declared |
Required fields (all case types)
case_ref— your unique reference (no PII)case_type— war_risk / force_majeure / demurrageclient_role_id— role identifier, not client nameevent_date— date of the triggering eventdeadline— per contract or notice termsunderwriter_target— who receives the packstatus— PASS / Declared / Unverified
Case-type specific fields
vessel_imo— war risk and demurrage casescancellation_notice_ref— war risk: club notice referenceadvisory_ref— war risk / FM: JWC, BIMCO, UKMTO refmitigation_steps— all types: what was done to mitigateevidence_degree— 1–10 strength score per case
Privacy note: The sheet uses role identifiers (CLIENT-REF-A), not client names or PII. Do not enter policy numbers, vessel owner details, or personal data in the CSV — use reference codes that map to your internal records. Only hashes are sent to the server when you produce a sealed pack.
From sheet to pack
When the row is ready — produce the structured pack
When a case row is complete enough to submit, the CSV row becomes the ERF intake. The sealed pack produces: Evidence Sheet PDF (formatted for underwriter review), ERF JSON receipt, and a no-login review URL you send directly to the underwriter or counterparty.