Somewhere, an accountant would log it. A scheduler would check a box. But Manish knew the truth: that report had just saved a captain’s night, a company’s money, and perhaps a few lives.
By 23:30, the Indus Fortune groaned against the dolphins of Berth Delta-7. Mooring lines snaked through the darkness, pulled taut by dockworkers in yellow rain gear. Manish watched from the window, then turned back to his desk.
Vessel: M.V. Indus Fortune IMO: 9472031 LOA: 189m Draft: 10.2m Berthing time (scheduled): 21:00 Berthing time (actual): 23:10 (estimated) Tug deployment: Two ASD tugs requested – approved. Weather: NE wind 22 knots, visibility 3 km, moderate chop Incident log: Bow thruster malfunction. Awaiting tug escort. Citpl Vessel Berthing Report
CITPL (Coastal Integrated Terminal & Port Logistics) ran a tight operation. Delays meant demurrage fees, unhappy clients, and a cascade of paperwork that could bury a man alive. But Manish had been a harbor pilot for twenty-three years before a bad knee grounded him behind a desk. He knew the sea’s rhythms better than the algorithms in the new berthing software.
Manish glanced at the berthing report pinned to his corkboard—a neatly typed document titled . It listed every scheduled ship, cargo type, mooring plan, and risk assessment. The Indus Fortune was marked in red ink: “High Priority / Maneuvering Caution.” Somewhere, an accountant would log it
The CITPL Vessel Berthing Report was more than a form. It was a promise between the land and the sea—a careful, human note in the chaos of tides and steel. Manish signed his name, placed the report in the pneumatic tube, and listened as it whooshed toward the main office.
He poured himself a cold cup of tea and waited for the next blip on the radar. By 23:30, the Indus Fortune groaned against the
“Control to Indus Fortune , report your ETA to Berth Delta-7,” Manish spoke into the radio.