Case Studies

BQPCA Case Study: Building Bhutan's National Certification Platform

Home Blog Case Studies

Case Studies

The Bhutan Qualifications and Professionals Certification Authority (BQPCA) platform is a national system that automates professional certification and qualification processes in Bhutan. It works under the Ministry of Education and Skills Development and gives every stakeholder one central place to apply, pay, track and verify.

The challenge

Professional certification often involves several councils, paper forms, manual fee collection and certificates that are hard to verify. The platform had to bring several bodies onto one system:

  • MHPC: medical and health professionals,
  • HEQC: higher education,
  • TVET-QC: technical and vocational education and training,
  • EPC: engineering professionals.

Each council has its own application types, review steps and rules, but applicants should get one consistent experience.

What the platform does

  • Online certification and accreditation. Applicants submit applications and documents online instead of on paper.
  • Separate portals for individual professionals and for agencies, each with its own login and workflow.
  • Integrated online payments. Fees are paid online and the application moves forward automatically once payment is confirmed.
  • Automated lifecycle. Registration numbers, validity periods and expiry dates are generated by the system, and email notifications go out at each step.
  • Public verification. Anyone, such as an employer or a hospital, can check that a certificate or qualification is genuine.

Engineering approach

A workflow-driven Django backend

The core of the platform is a Django application that models each application as a sequence of states: submitted, under review, approved, payment pending, paid, certified. Business rules such as issuing the registration number and setting expiry dates run when an application moves to a new state. That keeps the rules in one place instead of scattered across screens.

Payment callbacks that can be trusted

Online payments go through a government payment gateway that notifies the platform with a callback when a payment succeeds. Callback handling is one of the most sensitive parts of any payment system, so the integration is built to be idempotent: a callback that arrives twice cannot charge or certify twice. Every callback is recorded for audit, and pending payments are reconciled with the gateway on a schedule.

Containers, staging and Kubernetes

The frontend and backend ship as separate Docker images. Each release gets an explicit version tag and is built for multiple CPU architectures. Releases go to a staging cluster first, where they are tested against realistic data, and are promoted to production only after sign-off. This separation, with its own registry and configuration per environment, is what lets a government system change safely while it's in use.

Results

  • One national platform serving four councils instead of separate manual processes.
  • Applicants can apply, pay and track progress online.
  • Employers and the public can verify credentials instantly.
  • A repeatable release process that lets the platform keep improving after launch.

Lessons for similar projects

  1. Model the workflow explicitly. State machines make complex approval processes testable and auditable.
  2. Treat payment callbacks as untrusted and repeatable. Verify them, record them and make them idempotent.
  3. Invest in staging early. For public-sector systems, a realistic staging environment pays for itself many times over.

Planning a government or regulatory platform? Talk to us about what it takes.