It’s Just a Procedure, Or Is It?

Engr. Elaine Macatangay Morales, MPA  |  6 August 2025

I recently went to the NBI satellite office at our City Hall to get an NBI clearance. I had done what many of us are now encouraged to do, go online. I registered through the portal, filled out the necessary fields, chose my appointment slot, paid through one of the listed payment channels, and prepared my valid IDs. Everything seemed in place.

I arrived on time, expecting a smooth process. After all, this is 2025 — we have online systems, a digital government, and years of experience operating this clearance system. The NBI staff, to their credit, were organized. They knew the process well, guided people at every step, checked our documents, and gave clear instructions. Signages were visible, and there was a system of queuing using rows of stainless steel and plastic chairs.

But somewhere between the lines of people, the repeated instructions, the hand-filled slips of paper, the biometrics scanning, and the final queue for clearance release, I realized this wasn’t a problem of individual efficiency. The issue was the procedure itself. It was being followed and still, it wasn’t working well.

The Design vs. The Execution

It’s easy to assume that when something feels disorganized, someone must not be doing their job. But this experience reminded me: sometimes, everyone is doing exactly what they’re supposed to and it still doesn’t flow.

The procedure being carried out was built on disjointed components. The form I filled out online didn’t match the staff’s database, requiring corrections at the counter. The queuing resembled a round of musical chairs: you moved forward one seat at a time until you finished a step, then lined up again.

Some chairs were damaged or unstable. The signages told you which step was coming and you followed because you were told, not because the process made intuitive sense. And when you finally reached the final counter, you hoped for a same-day release unless the screen flashed “You Have a Hit.”

A “hit” means that either you or someone with a similar name has a criminal or questionable record on file, and further verification is needed. When this happens at a satellite office, your clearance won’t be released that day. You’re asked to return 18 to 20 working days later, regardless of whether the match is legitimate. In contrast, if you go to the NBI’s main or central office, even applicants with a “hit” can receive their clearance on the same day because they have on-site verification capabilities.

Why can’t satellite offices offer the same capability? If the main office can verify in real time, why not extend similar infrastructure to branches that serve just as many applicants daily?

That said, the NBI process includes commendable features. There are special queues for senior citizens, PWDs, pregnant women, and a group labeled “first time job applicants.” This last category caught my attention, not because it’s problematic, but because of how it’s phrased. It seems to assume that first-time NBI clearance applicants are necessarily first-time job seekers. But that isn’t always the case. Perhaps “first-time NBI clearance applicants” would be a more accurate label. Small wording choices matter, they shape how people see themselves, and how the system sees them.

What Procedures Are Supposed to Do

In quality management, particularly ISO 9001:2015, documented procedures are more than compliance tools. They represent an organization's promise: that it knows how to do its work, can do it consistently, and will improve how it serves.

A good procedure should ensure A.C.E.S. — Adequacy (are the steps sufficient and correct?), Conformance and Compliance (do they meet legal and technical requirements?), Effectiveness (are intended results achieved?), and Efficiency (are time and resources used well?). Lastly, it should be Suitable — fitting the context, capacity, and objectives of the organization.

Using this lens, the NBI clearance process raises questions. Is the procedure adequate? It covers the basics, but with repetition and manual correction. Is it conforming? Technically yes, IDs are verified, biometrics are taken, names are screened. But is it effective? Not entirely, as shown by delays caused by “hit” statuses. Efficient? Not when people wait for hours despite pre-registration. Suitable? Only if the goal is to maintain the status quo, not to deliver a user-friendly service.

In fact, the intersection of systems thinking, quality assurance, and science, technology and innovation (STI) is essential in designing procedures that not only meet present needs but are also responsive to change. Technological tools alone won’t fix bad design but when guided by sound systems and quality frameworks, STI becomes a powerful enabler of better governance and public service.

A Systems Problem, Not a Personnel Problem

It’s tempting to ask for better customer service or shorter queues. But as we’ve seen in healthcare, education, and transport, systems don’t improve just by asking people to work harder. The procedures must be re-examined.

When systems inherit outdated processes and simply digitize parts of them, the core issues remain. Online registration doesn’t fix verification bottlenecks. Scheduled appointments don’t prevent queues if slots aren’t calibrated to capacity. More signs, chairs or counters can’t entirely fix a process that wasn’t designed with the user in mind.

To improve this, we must see procedures as both technical documents and living structures, ones that evolve with feedback, demand, and policy goals. Clause 10 of ISO 9001 calls for continual improvement based on data, customer feedback, and audits. But that only happens when organizations treat procedures not as static manuals, but as dynamic systems that drive performance.

Rethinking Our Approach

Public service procedures, especially those used by thousands daily, can’t afford to be merely “followed.” They must be actively improved. Even something as routine as getting an NBI clearance becomes a stress test for government systems, showing how well vision translates into experience.

And the real test is not whether the procedure exists, but whether it works. Are people being served fairly, quickly, respectfully? Are staff supported by the system or compensating for its flaws? Are we adjusting based on real user feedback?

More Than Just a Checklist

Procedures aren’t just about process. They’re about trust. When citizens line up, follow steps, and wait their turn, they’re placing their trust in the system — trusting that it’s designed to work, and to work for them.

When that trust is broken, when systems feel arbitrary, confusing, or burdensome, people lose confidence, not just in the service, but in the institution.

And so, procedures matter. Not because they’re technical but because they reflect who the system is really serving and how.