Picture a farmer from Sankri, a village in Mori tehsil at the far western edge of Uttarkashi district. Sankri sits 195 kilometres from the district headquarters. The man has a land boundary dispute, or a pension that has not arrived for three months, or a water source that a contractor has blocked while building a road. He needs to speak to the District Magistrate.
Here is what that conversation actually costs him.
Day one: he boards the first bus at dawn, changes vehicles at Barkot, arrives at Uttarkashi in the afternoon. He finds a place to stay — a dharamshala or a relative's floor if he is lucky, a lodge if he is not. He goes to the Collectorate, waits, is told the DM has a review meeting. He can come tomorrow. Day two: he is back at the gate by nine. He waits through the morning. He gets five minutes, sometimes ten. His problem is noted. He is told to submit a written application and wait for a response. Day three: he returns home. The bus fare, one night's cost, two days of food, the day's wages he could not earn — the total is somewhere between ₹1,500 and ₹2,000. For a small farmer in the upper Bhagirathi valley, that is not a minor inconvenience. It is a significant fraction of a week's income.
And it does not guarantee resolution — only the chance to be heard.
This is not a story about one village or one farmer. It is the operational reality of governance in a district where the farthest blocks are three to four hours from headquarters on mountain roads, where winter snowfall cuts off entire panchayats for weeks, and where the administrative geography simply does not allow citizens to treat the DM's office the way a city resident might treat a ward office down the street.
The question we set out to answer was not how to make the journey cheaper. It was whether the journey was necessary at all.
The Limits of the Grievance Portal
India has no shortage of digital grievance infrastructure. CPGRAMS connects citizens to every ministry and state department. Uttarakhand has its own public grievance portal. Most district websites have a contact form. None of them quite solve the problem we are describing.
The existing portals are built around the logic of the complaint: fill a form, receive a registration number, wait for a department to process it. This design assumes the citizen knows which department to address, can articulate their problem in writing, and is willing to wait in a queue whose depth they cannot see. For an educated urban resident with a service delivery complaint, this works adequately.
For the farmer from Sankri — or from Bhatwari, 40 kilometres up the Gangotri road, or from the remote villages of Rawain in Mori tehsil — the form-based model breaks down. Problems are often inter-departmental. They are often urgent. They require context, tone, and emotion that a text field cannot carry. And critically: the form has no face on the other side.
What the farmer made a three-day journey for was not a ticket number. It was a conversation — the certainty that a human being in authority had looked him in the eye and understood the problem.
Sankalp Sanwad: The DM's Office on Your Phone
In early 2025, working alongside the Office of the District Magistrate, Uttarkashi, we designed and built Sankalp Sanwad — a live video call platform that brings that conversation to wherever the citizen is standing. The mechanic is straightforward and deliberately so.
जिलाधिकारी से सीधी बात — बिना सफर, बिना इंतज़ार.
Direct conversation with the District Magistrate. No travel. No waiting.
The DM's dashboard shows the live queue, each citizen's village and block, their interaction history, uploaded documents, and tools to tag departments and add official remarks. A widow in Purola checking on a stalled pension. A gram pradhan in Bhatwari flagging a road contractor dispute. A farmer from Dunda logging in on a Tuesday and speaking to the DM.
What This Model Gets Right
The reason citizens make the journey to the Collectorate is not bureaucratic — it is human. They want to be seen. A live video call replicates that dynamic: the DM is present, the citizen is present, there is a real exchange. The DM sees the face and hears the voice of the person whose problem is on the dashboard. That matters.
The virtual waiting room with token numbers and estimated wait times is not a minor feature — it is the core of why the platform works. It converts an indefinite, unpredictable wait into a structured, knowable one. Dignity in waiting is itself governance.
Every interaction is tagged by village and block. Over months, this builds something the district administration has never had before: a live map of where grievances are concentrating, which blocks are most underserved, which departments are being flagged most frequently. The platform is not just solving individual problems — it is generating the evidence base for systemic ones.
The Case for Replication
Uttarkashi is not an unusual case. Every hill district in Uttarakhand — Chamoli, Pithoragarh, Rudraprayag, Bageshwar — has the same geographic reality: a headquarters that is functionally unreachable for a large share of its population without significant cost and multiple days of effort.
The platform was designed, built, and launched within the district's own authority and existing budget. No new legislation. No state IT procurement cycle. A motivated DM, a clearly defined problem, and a small technical team were sufficient. This is the model for replication: not a state scheme cascaded down, but a district prototype demonstrated up.
The threshold question for any District Collector is not "can we afford this?" It is simpler: can we afford to keep asking a farmer from Sankri to spend ₹2,000 every time he needs five minutes with us?
Sankalp Sanwad is live at sankalpsanwad.com, running out of the District Administration, Uttarkashi.
Governance in the hills has always demanded more creativity than governance on a plain. The distances are longer, the winters harder, the margins thinner. The least the system can do is meet citizens where they are.
And where they are, increasingly, is on a phone — looking to see if the DM is online.