On Baishak 14, 2083, a Monday, the Ministry of Physical Infrastructure and Transport called a session to gather feedback on a draft that had been quietly circulating for weeks: proposed guidelines that would, if enacted, require every public transport vehicle in Nepal to carry GPS tracking, CCTV cameras, an emergency button, and digital payment support.
NepTrack was in that room. Kaushal Joshi, Hari Prasad Chaudhary, and Alok Joshi attended the full session. What came out of that meeting was a clearer picture of what compliance will actually require, and why most operators are not prepared for what is coming.
Here is everything the draft says, broken down for fleet operators, along with what NepTrack formally submitted as suggestions to strengthen the framework.
What the draft actually proposes
The draft, made available for public consultation by the Ministry of Physical Infrastructure and Transport, proposes a full technology overhaul of Nepal's public transport system. You can read the official notice here.
It covers four main areas: GPS tracking connected to a central control system, CCTV surveillance with AI capability, GPS-enabled emergency assistance buttons, and digital payment with QR code ticketing.
No implementation deadline has been set. The Ministry is still reviewing submissions. But operators who have watched how Nepal's transport regulations move know: the gap between draft and mandatory can close faster than expected.
GPS means a central connection, not just a device
This is the requirement most operators misread.
The draft does not simply say vehicles must have a GPS device. It requires GPS tracking connected to a central control system, meaning the device must transmit in real time to a licensed, monitored platform, be accessible by authorities when required, and maintain historical trip data.
A cheap SIM-based tracker sending coordinates to nobody does not satisfy this. A device connected to a platform not recognised by DoTM's central infrastructure will not satisfy this either.
DoTM has been working on the central control layer. When it is operational, operators connected to compliant platforms will transition automatically. Operators running disconnected hardware will need to replace everything from scratch, under deadline pressure.
CCTV: two cameras, three months, and an AI layer still being defined
Every public vehicle must carry at least two CCTV cameras. Taxis are currently exempt. Footage must be stored for a minimum of three months.
The draft also references AI facial recognition and passenger counting. That clause generated the most discussion at the MOPIT session. The Ministry did not provide technical specifications for how this AI layer would work or which platforms would be certified to deliver it. That detail is still being finalised.
Cameras cannot be standalone recording units. They need to be networked, with footage accessible remotely, and eventually integrated with whatever system DoTM certifies. Operators who install basic DVR cameras now may need to replace them again when certification standards are published.
Emergency buttons: the liability shift operators are not expecting
Every vehicle must have an emergency assistance button that, when pressed, sends a GPS-enabled location alert to a monitoring centre.
The button needs to be hardwired into the vehicle's GPS system so that a single press transmits both an alert and a live coordinate simultaneously. A panic button that sends a text to a driver's personal phone does not meet this requirement.
Once emergency buttons are mandated, a system failure during an incident becomes direct legal exposure for the operator. This is already the standard in school transport regulations across several Indian states. Nepal is moving in the same direction. Getting this right before a deadline is not optional.
Digital payments: closing the revenue gap
The draft includes mandatory digital payment support and QR code ticketing on all public vehicles.
This is partly about passenger convenience. Mostly it is about creating an auditable revenue trail. QR ticketing data connected to a route management platform lets authorities verify that reported passenger numbers and actual collections match. For operators running clean books, this is a straightforward addition. For those still handling cash informally, it requires a full operational change.
The QR system will need to connect to the same central platform as GPS and emergency data, so that trip and payment records can be reconciled in one place. Separate systems for each requirement will create gaps that auditors and DoTM inspectors will find.
Five vendors will not deliver compliance, they will deliver a maintenance problem
GPS device from one vendor. CCTV kit from another. Emergency button sourced separately. Digital payment terminal bolted on top. Each reporting to its own app, its own server, its own support line.
That approach will not satisfy the draft's intent, and it will not hold up operationally.
The draft's central control system requirement means all data from GPS, CCTV, emergency alerts, and passenger counts must feed into one accessible platform. If your hardware speaks five different protocols to five different servers, connecting to that central layer becomes either impossible or very expensive to retrofit.
Consider what happens when the emergency button stops working on a Pokhara-Kathmandu route vehicle on a Tuesday morning. You are calling four different support lines, none of whom can see each other's systems, while the vehicle is on the road. Operators who have tried the multi-vendor approach already know this problem well.
What NepTrack submitted to the Ministry
NepTrack attended the MOPIT session not just to observe but to put specific suggestions on record. Here is what we formally submitted for the Ministry's consideration.
Data retention of 5 years, not 3 months. The draft specifies three months of CCTV footage retention. For GPS trip data, the framework is silent. We proposed that all trip history, GPS logs, and event data be retained for a minimum of five years. Three months is insufficient for insurance claims, legal disputes, accident investigations, and route performance audits. Immutable five-year records protect both operators and passengers.
Mandatory data sovereignty. All vehicle tracking data generated in Nepal must be stored on servers physically located in Nepal. Several GPS platforms currently operating in the Nepali market route data through servers in India or Singapore. If a public transport vehicle's live location, passenger count, and emergency alert history is stored outside Nepal, that data is subject to foreign jurisdiction and inaccessible to Nepali authorities in a timely manner. The draft should explicitly require Nepal-hosted infrastructure for any DoTM-compliant platform.
Certified device compliance list. The draft does not specify which GPS hardware will be recognised as compliant. Without a certified device list, operators have no way to know if the hardware they purchase will meet DoTM's central control requirements. We proposed that the Ministry publish and maintain an approved device list with clear technical specifications, updated as hardware standards evolve.
Integrated platform requirement. The draft lists four technology requirements but does not specify that they must function as a single integrated system. We proposed that compliant platforms be required to demonstrate end-to-end integration: GPS data, CCTV status, emergency alerts, and digital payment records must be accessible from one dashboard and reportable to the central control system through one API. This removes the multi-vendor loophole and ensures the data actually flows.
API access for government integration. The central control system the draft envisions will only work if compliant platforms can connect to it programmatically. We proposed a mandatory open API standard so that the Ministry's central system can pull data from any certified platform in real time, without requiring manual data submission from operators.
Bikram Sambat reporting as standard. All reports, logs, and compliance records submitted to DoTM should be generated in Bikram Sambat format. Using AD dates for government compliance documents in Nepal creates unnecessary conversion overhead and audit errors. This is a small change with significant practical value for operators and officials alike.
What integrated compliance looks like in practice
One platform connecting GPS tracking, geofencing alerts, CCTV integration, emergency SOS, and digital payment data into a single dashboard. One device set on the vehicle. One operations view. One support contact when something fails.
NepTrack is built for exactly this. The platform runs on Nepal's actual network conditions including LBS fallback for hill routes where GPS signal drops, stores trip history for five years on Nepal-hosted servers, and reports in Bikram Sambat with Nepali language support. It is the only GPS tracking platform in Nepal that provides open API access for third-party integration and real-time data streaming.
If you are evaluating your fleet infrastructure now, before the deadline is announced, that is the right time. Retrofitting thirty vehicles after a compliance notice arrives is expensive and disruptive. Getting the right system in place before the mandate makes the transition straightforward.
Explore the full platform, see how it applies to public transport fleets, or talk to the team directly on the contact page.
