Sabbir Ahmed Nahid: Who among us has not faced this? To open a bank account, buy a SIM, renew a trade license or admit a child to school, we give the same NID photocopy, the same two passport-size photos and the same certificates. Now many offices have websites, so we go to the computer shop, scan everything and upload. And then? Many times we still have to bring the hard copy to the office, stand in the line, and hear “come again tomorrow.”
In the last two decades, Bangladesh has done a lot in the digital sector, and we must give credit for it. But many of us think digitalization means only changing paper into screen. If people still give the same papers, wait for the same signatures and run from one table to another, then what has really changed? Only the paper has gone inside the computer.
Three words, three meanings
We often mix up three words. Digitization is only changing the format: a paper record becomes a scanned copy, a register khata becomes an Excel sheet. Digitalization means using technology to change the way we work, so the service becomes simpler and faster. Digital transformation is the biggest change, where the institution itself changes how it works, takes decisions and serves people.
There is an easy test. If all the computers in an office are switched off tomorrow, will the office go back to exactly the same steps on paper? If yes, then honestly speaking, it was only digitized, not digitalized.
Fix the process first
Suppose a service needs six documents and four approvals. If we put the same form online, it does not help much. The applicant may save some rickshaw fare, but he still waits the same number of weeks. Many steps exist only because a paper file had to travel from one desk to another. So first we should simplify the process, then standardize it, and only then automate it. If the floor is broken, putting a new carpet on it will not help.
Let the system do the work, not the citizen
Once the process is simple, we should automate it boldly. Let me give some examples from our daily life. If nothing has changed, the trade license should renew itself when the fee is paid, no papers needed. A job portal should check SSC and HSC results directly from the education board, so our young people do not need to run after a gazetted officer for attestation. When someone reaches the eligible age, the system should check the NID data and offer the old age allowance, without any application. The citizen should get an SMS at every step, so he does not need to visit the office only to ask, “Sir, what happened to my file?”
But we must be careful. If the data is wrong, automation will repeat the same mistake a thousand times. So every automated decision needs human oversight and an easy way to complain.
Why do we give the same data repeatedly?
This problem we hardly discuss, and it happens in two ways. First, we give the same data many times for the same service. A businessman renews his trade license every year, and every year he submits the same papers, though nothing has changed. Second, we give the same documents again for each government service. The papers we give to one office, we give again to the next, and then again to the next. Parents give the same birth certificate for school admission, then for board registration, then for the stipend.
One government office does not take the information from another, so the citizen becomes the carrier of his own data. The result is duplicate records, the same name spelt in different ways, and lost time and money for ordinary people.
The answer is the “once-only” principle. A citizen gives a piece of information to the government only once, and any authorized office takes it from the official source with proper permission. Using the National e-Service Bus, the Surokkha vaccine registration system checked NIDs more than 12 crore times, without asking anyone for a photocopy. We should build on such shared systems, instead of making a separate portal for everything.
Sharing data needs strong security
But every connection between two systems is also a door, and every door needs a good lock. In 2023, because of a weakness in the birth and death registration website, personal data of around 5 crore citizens became open on the internet.
An officer should see only the data he needs for his work. Data should be encrypted, every access should be recorded, and data should be shared only for a clear purpose. If an office only needs to know whether an NID is valid, it should get a simple “yes” or “no”, not the person’s full profile. The Personal Data Protection Ordinance 2025 recognizes citizens as the owners of their data. People will use digital services only when they can trust them.
Digital for everyone
We must also ask: for whom are we building these systems? According to the Bangladesh Bureau of Statistics, only 53.4 percent of people use the internet, and in rural areas it is only 43.6 percent. Women are also behind men. If a service is “online only” and a village woman has to pay the computer shop in front of the Upazila office to apply, then the service is online, but it is not for her.
Persons with disabilities are the users we forget the most. Around 46 lakh people, 2.8 percent of our population, live with a disability. Yet many government websites still do not work properly with screen readers. A blind person gets stuck on buttons without labels or on a picture CAPTCHA. A deaf person cannot use an OTP that comes only by voice call. A person who cannot give a fingerprint is locked out if biometric is the only way to verify. And a person with disability often has to prove his disability again and again for every service. For him, the once-only principle is a matter of dignity.
These problems are not costly to fix if we plan from the beginning. Accessibility standards should be a must in every software contract, and services should be tested with persons with disabilities before launch. There should always be an alternative to fingerprint, simple Bangla language, and Union Digital Centers to help those who need it. As the disability rights movement says, “Nothing about us without us.” A service that is easy for a person with disability becomes easier for everyone.
Who owns the software?
When the vendor’s contract ends, many offices find that they do not have the source code, the documents are incomplete, their own staff are not trained, and even for a small change they need a new contract. In 2024, banks and fintechs struggled to verify customers’ NIDs when a key data-sharing arrangement was cut over a dispute. So the institution must own the code, control the data and passwords, train its own staff and keep an exit plan. We can outsource the work, but we should never outsource the control.
Technology is the easy part
Even good software fails if the office does not change. We often see an application submitted online, then printed and moved through the office in a physical file. Officers enter data in the system but also keep their own Excel sheet, “just in case.” So the office runs two systems and pays the cost of both. This is not a software problem; it is a leadership problem. Digital change needs a senior leader who owns it, clear rules on which record is official, and regular training.
Then comes life after the project. When a donor-funded project ends, the budget often stops, security updates stop, trained people leave, and slowly the system dies. The maintenance budget and in-house skills must be planned from day one.
From digital platforms to digital institutions
Bangladesh has real achievements like e-GP and mobile financial services. The next step is harder. Before we call any office “digital,” let us ask a few simple questions. Did we simplify the process? Did we let the system do the work? Do we still ask people for data we already have? Is the data safe? Can a rural woman or a person with disability use the service without a middleman? Do we own the system, and will it keep running after the project ends?
Going paperless is a good milestone. But our real goal should be an institution that thinks, works and serves people differently because of technology. That is the difference between having digital systems and becoming a digital institution.
The author is a digitalization and systems architecture specialist with more than 18 years of experience in e-governance and digital public infrastructure in Bangladesh.

