Google Play · Android
The reporting process, status and notification features, and the October 17 release notes.
01 / The challengeThe road is visible.
The road is visible.
The route to a response
should be, too.
Someone walking past a broken footpath can see the problem immediately. Knowing which office maintains that stretch, what information to send, and how to follow up is a different task.
The service brings the report and its context together. A photograph explains the issue; location and road-network information help establish where it belongs; a report history gives the person a place to return.
- 01 / RESPONSIBILITY
Where should this go?
Road ownership is not always obvious from the street. The reporting journey needs to connect a place with the office responsible for that road.
- 02 / USEFUL CONTEXT
What does the office need?
A general complaint is hard to locate. A photo, a precise map position, and severity make the observation more specific and easier to understand.
- 03 / FOLLOW-THROUGH
What happened next?
A submission should have a visible next step. Status updates and a report history help people follow the response without starting a new conversation each time.
At the public launch, OnlineKhabar described complaint tracking and information about the agency responsible for roads outside the federal network.
02 / The citizen journeyFrom noticing a problem
From noticing a problem
to following a report.
A small number of clear steps turns a street-level observation into a report with context.
Show the problem.
Photograph the pothole, damaged footpath, or road issue. The image gives the office a concrete starting point.
Confirm the place.
Use GPS or a nearby landmark to identify the location. Check that the map pin matches the affected stretch.
Add the context.
Choose the severity and review the road and office shown for the report before submitting.
Submit the report.
Send the photo and location together. The app links the report to road-network information for routing.
Follow the response.
Return to the report for status updates, notifications, and conversations with the road office.
A report has a life after submission.
This is a simplified status journey. The app can show additional states; a report does not automatically move through every stage.
SubmittedIn ProgressResolved
03 / The connected experienceThe same service.
The same service.
Two different sets of needs.
Explore the citizen app and the office workspace. Each view has a different job, with a report providing the connection.
For the person using the roadA clear place to start.
A clear place to start.
A reason to return.
The home screen puts the reporting action and existing reports together, making follow-up part of the experience.
Start with evidence.
Photos, a location, and severity help explain the problem beyond a general complaint.
Know where the report belongs.
The Android routing preview shows the matched road and road office before submission.
Keep the conversation in context.
Report history, notifications, and in-report messaging help keep follow-up connected to the original issue.
Features and release details are described in the official app listings. Screenshot numbers are interface examples, not current service totals.
For the team handling the workA shared view of reports,
A shared view of reports,
places, and progress.
The dashboard preview organizes the office side around the report queue and an operational overview.
A queue with context.
Report summaries and navigation for reports and an unassigned queue give the workspace a clear starting point.
Location alongside the work.
Map View, search, and officer navigation appear alongside the report-management areas in the supplied preview.
A place for operational records.
The preview includes completed-work logging, monthly reports, bulk export, and an activity feed.
Dashboard preview supplied by Trasier. The figures shown are sample interface data.
The useful connection is the report and the context around it.
- Photographic evidence
- Location and road context
- Responsible-office information
- Status updates and conversation
04 / From the fieldFive places.
Five places.
A more visible record.
Explore before-and-after photographs from the company’s October field update: potholes, footpath paving, waterlogging, and damaged asphalt.
BeforeAfterSamakhushi–Tokha, Kathmandu
Pothole repair example from Trasier’s October 16, 2026 company update, which attributes the road work to Kathmandu Division.
05 / The public recordA service that grows
A service that grows
through real use.
A dated view of the launch, company field updates, and the published Android release. Each entry links to the record behind it.
A formal public launch.
Launch reporting describes Road Division Kathmandu introducing the app after a trial, with an initial focus on around 472 km of federal roads in Kathmandu Valley.
Independent launch reporting · OnlineKhabarA company update on the Valley network.
Trasier’s update describes bringing Lalitpur and Bhaktapur into the reporting network. The update describes a wider reporting network within Kathmandu Valley.
Company product update · TrasierThe work outside the screen.
The team publishes field photographs and observations from the first two months, including the five before-and-after road examples shown in this case study.
Company field report · TrasierA clearer reporting and follow-up experience.
The Android release notes describe office messaging, routing previews, clearer Nepali maps, notifications, and offline report sending.
Official Android release notes · Google Play
Coverage is about responsibility.
A location on a map and an office actively handling reports are different things. Check the road and office shown in the app for the area you want to report.
A status is part of the record.
Report updates make the response easier to follow. Prioritization and repair work remain with the responsible road office; the software does not set a universal repair deadline.
Personal information has a purpose.
Photo and location information support the reporting process. The product privacy policy explains data handling, and the account-deletion page explains the available deletion route.
06 / Useful detailsThe questions
The questions
behind the report.
Practical answers for people using the app and teams exploring how a connected reporting service works.
Explore the product pageWhat kinds of issues can someone report?
The published app descriptions include potholes, cracks and other road damage, broken footpaths, and flooded road stretches. A useful report combines a photograph with location and severity information.
Does this cover every road in Nepal?
Coverage depends on road ownership and participating offices. Launch reporting focused on Kathmandu Valley’s federal roads, followed by dated company updates about Valley expansion. Review the matched road and road office in the app instead of assuming nationwide coverage.
Can a report be prepared without internet?
The October 17 Android release notes describe saving reports without a connection and sending them automatically when connectivity returns. Follow the app’s feedback to confirm whether a report has been submitted.
What happens after a report is submitted?
The app provides report history, status updates, and notifications. The published Android release also describes messaging with the road office inside the complaint, keeping follow-up associated with that report.
Does submitting a report guarantee a repair?
No repair time or outcome is guaranteed by submission. The road office assesses the issue, priorities, and the work to be carried out. The before-and-after photographs here are selected examples from the company’s field report.
Where can I read about privacy and account deletion?
Read the Sadak Sujhav privacy policy for the product’s published data practices and the account-deletion instructions for the available request process.
Can another public-service team discuss a similar platform?
Yes. Contact Trasier about a civic platform and describe the people, the service, the responsible teams, and the information that needs to flow between them.
07 / Read the detailsA case study with
More stories from the team A case study with
a public record.
Product details and reporting reviewed 24 October 2026. Official listings describe product features; company updates provide the field photographs and dated rollout observations.
App Store · iPhone & iPad
The product description, supported issue examples, and availability on Apple devices.
OnlineKhabar · 17 September
The public launch through Road Division Kathmandu and initial federal-road coverage in Kathmandu Valley.
Trasier’s October field notes
The October 11 coverage update and October 16 field report provide the rollout account, road photographs, and repair attribution.
Your next public-service challengeMake the connection
Discuss your project Make the connection
work for your community.
Tell us who needs the service, who runs it, and where the current process becomes difficult. We can explore a useful next step together.