Operations Documentation OfficerAvailable now

Meet Zara. Every vessel call, every voyage, every shipment runs on a pile of documents. Zara owns the pile.

Zara

Operations Documentation Officer · Logistics

Preparing · 14 calls

↳ on it now

14 port calls in preparation. 9 pre-arrival packs ready for submission, 3 crew-change packs assembled with every certificate in validity, 22 requisitions chased to PO this week. 2 documents flagged expiring before the next call.

Calls in prep

Packs ready

Expiring flagged

TL;DRZara owns the paperwork of every vessel call, voyage or shipment: pre-arrival declarations, crew-change packs, requisition chasing, statement-of-facts capture and shipment document assembly. Your team approves every filing.

What Zara does, item by item.

The whole queue, not a sample. Every finding cited back to its source.

Prepares pre-arrival declarations and single-window filings, ready for your team to submit.

Assembles crew-change document packs: certificates, visas, contracts, checked for validity and expiry.

Chases requisitions to PO so spares and stores stop waiting on email threads.

Captures statements of facts into structured timelines you can actually dispute from.

Builds the document pack per shipment or port call and flags what is missing before it matters.

Keeps a live register of every open document item across the fleet or the network.

Your team keeps

·The filing submission
·The master and agent relationships
·Operational decisions

Zara takes

→Pre-arrival and single-window preparation
→Crew-change document packs
→Requisition and document chasing

The line Zara won't cross

Zara never files with an authority or commits the company. She prepares, checks and chases; submission is your team's click, logged every time.

How it earns trust.

Pilot on your history, supervised on your queue, governed always.

Weeks 1-2 · Pilot

Runs on a historical corpus your team already reviewed. You score its findings against what your reviewers caught. No production access.

Then · Supervised

Works the live queue. Every finding is a draft until a named human approves it, and every rejection is logged and measured.

Always · Governed

The envelope never relaxes. Reading, checking, and drafting get automated. Approval stays human, by design.

Learned from

your port and flag requirementsyour document checklistsvoyages your team already closed

Tools

Port and agent emailsSingle-window exportsCrew documentsStatements of factsExcelDrive

The hand-off.

How Zara pings a human when it's your call.

“Zara: the Chennai call needs the pre-arrival declaration by 1800 and the crew list still shows one visa pending. The pack is otherwise ready. Submit as is, or hold for the agent?”

FAQ

The honest answers.

No dodging, no contact-sales-to-find-out.

Who is Zara for?+

Ship managers, port authorities, carriers and 3PLs. If your operation runs on filings, document packs and follow-ups, the shape of the work is the same, and Zara learns your version of it.

Why is this urgent now?+

Maritime single windows became mandatory in January 2024, and the filing load landed on the same operations teams. Real-world marine requisition-to-PO cycles still run 3 to 4 weeks, mostly on email, and one documented crew change gone wrong cost $820,000. The paperwork is now the bottleneck.

Does she submit filings herself?+

No. Every declaration, pack and filing is prepared and checked, then a named person submits it. The approval is logged with the pack.

Put Zara on the queue.

Start with a paid pilot on your historical corpus, finished in weeks. Then a full deployment over 3 to 4 months, with a forward-deployed team working alongside your people.

See it in action