In September 2024 I took part in discussing building permit procedures with a World Bank delegation, as head of the working group of government entities concerned with building permits. The published coverage of the meeting mentions topics including procedures, documents, timeframes and e-services. That experience gives me a way into reading the service from the perspective of the service user, who wants to know the path to getting their application completed.
Three angles on the service
The Business Ready methodology covers the regulatory framework, public services and operational efficiency. I borrow this separation into pillars here to organise the questions, not to assess or rank anything.
From the regulatory angle, I ask how clear a requirement is and where it comes from. From the service angle, I ask how the service user obtains information and how they submit documents. Operations, for their part, mean following what happens to an application once it has been submitted. A rule may be clear while the explanation given to the service user falls short, or the interface may be good while the application passes through reviews whose status is never shown.
What does processing time mean?
I prefer to break time down into periods that can be understood: review time within the entity, the time the service user takes to complete missing items, and time spent waiting for another entity to respond. Rolling these periods into a single average can hide the real cause of a delay and make the problem harder to address precisely.
Comparisons mean more when we specify the type of application, its complexity, and where measurement starts and ends. Management follow-up needs stable definitions, so that an apparent improvement is not simply the result of a change in how things are counted. Exceptions should also be kept and explained rather than removed from the picture.
Coordination as the service user sees it
As I see it, coordination shows its effect when an applicant finds consistent requirements, clear messages and a known route for enquiries. One place to start is reviewing the points where an application passes from one entity to another: what data moves across? Who verifies it? And is the service user being asked for information that another entity already holds?
The most useful follow-through from dialogues like this, I find, is to turn general questions into definitions, data and follow-up steps that the team can review and improve step by step.