PIWTT, The Fifty-Year-Old Agreement Still Moving Cargo Today
PIWTT provides a working inland-water route between Bangladesh and India, but every shipment still depends on the nominated route, vessel, cargo and current operating permission.
The Protocol on Inland Water Transit and Trade gives Bangladesh and India an agreed framework for moving cargo on designated inland-water routes and through notified ports of call. For a principal, the commercial question is not the age of the agreement. It is whether the proposed cargo, vessel, operator, route and port of call fit the current protocol and local operating position. Where Mongla forms part of the plan, use the latest vessel and movement information rather than a historic draft or transit assumption. The movement may involve a sea-going leg, a transshipment or river interface and an inland-vessel leg, each with its own operator, documents and timing. Those links need to be understood before the principal compares the route with a direct ocean or road option.
An agreement older than most people realize
The Bangladesh-India inland-water protocol has operated for decades and has been renewed and expanded over time. It remains an active framework supported by designated routes, ports of call and voyage-permission systems. Because routes and administrative arrangements can be updated, the principal should check the current protocol and voyage-registration position rather than rely on an old route schedule. BIWTA maintains a protocol service route for company and voyage registration, while the Indian side also publishes the protocol framework and route information. That confirms the continuing administrative structure, but it does not remove the need for a shipment-specific voyage and operating check.
What the protocol actually allows
Under PIWTT, eligible inland vessels from both countries can use designated routes and notified ports of call for permitted cargo movements, subject to the protocol and each country’s operating and administrative requirements. The route network connects Bangladesh waterways and ports, including Mongla, with Indian river and seaport gateways. Do not treat every Bangladesh or Indian river terminal as automatically available under the protocol; the intended route and ports of call need to be identified for the shipment. The file should identify the carrying vessel or operator, cargo ownership, Customs route, loading and discharge points and any transshipment at the sea-port interface. A general statement that cargo will move “under protocol” is not enough for a workable local plan.
Why this matters more than the cargo volume suggests
The protocol remains important because it connects seaports and inland markets without sending every shipment through the road corridor. The practical constraints are familiar: available draft, seasonal river condition, conservancy, pilotage, vessel suitability, terminal handling and the readiness of Customs and cargo parties at both ends. A route that is workable in one season or for one vessel should not be copied into another fixture without a fresh check. Dry-season draft, river marks, night-navigation limits, convoy or pilot arrangements and cargo-handling capability can change the practical transit time. The principal should therefore compare the complete route, not only the sea freight or river freight line.
Where Mongla fits into this picture
Mongla’s role under PIWTT is separate from its ordinary ocean-going container, bulk and project-cargo business. A shipment may use Mongla as the sea-to-river interface, but the inland leg then follows the protocol route, vessel and port-of-call requirements. For cargo connected with India’s northeast or another regional destination, PIWTT may offer a workable alternative, but it should be compared against the actual seaport, transshipment, river, Customs and final-delivery chain. At Mongla, the sea-going vessel’s berth or anchorage operation and the onward inland movement should be planned as connected but separate files. Cargo discharge readiness does not by itself confirm that the inland vessel, protocol registration, Customs handover and destination-side acceptance are ready.
Routing Cargo via Mongla or PIWTT Ports of Call?
Send the sea-going and inland-vessel plan where applicable, cargo, quantity, origin and destination, proposed protocol route, ports of call, operator details, ETA, draft and intended Mongla berth or anchorage. CPA can check the Mongla agency and interface requirements and coordinate local communication. Protocol eligibility, voyage registration, inland navigation and cross-border permissions remain with the responsible authorities and operators. Include the proposed handover point, cargo documents, receiver or consignee line, Customs and C&F contacts, and any target delivery window. CPA can report what is ready on the Mongla side and identify the party holding the next action.