Revoking a registration

Hey all :wave:

We are research requirements for a feature called Revoke a registration. As part of our integration work with MOSIP (National ID) but applies regardless.

This is when a declaration has been registered:

  • fraudulently
  • by mistake

It therefore cannot be corrected and must be revoked.

Questions that would be great to have your input on:

  1. What reasons would a registration be revoked in your country? (for a birth, death, marriage etc)
  2. What supporting documents would be necessary if any to revoke a registration?
  3. Who would be responsible for revoking registration and approving them in your country?
  4. Any other requirements we must consider?

Many thanks,

1 Like

A registration shall be revoked where;
(a) a person has under the law ceased to be a citizen of Uganda;
(b) the registration is based on inaccurate or incomplete information;
(c) the registration was obtained by fraud, false representation, bribery or deceit;
(d) the card needs to be re-issued due to a defect;
(e) double or multiple registrations have taken place; or
(f) there is an order of court for cancellation of registration


The powers to a revoke a registration and approving them ought to be vested in the Registrar General under recommendation from the National Registration and Citizenship Control Board or Committee. Basically the committee ought to sit and review the application and thereafter make a recommendation to the Registrar.


Many thanks Paul for your insights.

Could a high level process be?

  1. Registrar searches for record
  2. Clicks Revoke
  3. Adds reason and uploads any supporting documentation
  4. Registrar sends for approval
  5. Committee reviews record, reasoning and supporting documents (In OpenCRVS or prints?)
  6. An official approves or rejects the request
  7. If Approves, the Registrar is notified and the record is archived
  8. If Rejects, the Registrar is notified with the reason for the rejection
1 Like

The process of cancelling the registration on a person based on:

a) Where a person has under the law ceased to be a citizen of Uganda

b) The registration was obtained by fraud, false representation, bribery or deceit, multiple registrations by an individual (duplicates on the NIR).

c) Order of court for cancellation of a person
Primary Actors a) Subject of cancellation

b) Immigration


d) Court

e) Informant
Secondary Actors a) NIRA

b) Immigration

c) Informants
Description This use case details processes of cancellation of the registration of a person based on reasons outlined in the scope above.
Pre-Condition a) The subject of cancellation and the informant must exist on the NIR and either of the following shall apply:

b) A request from the applicant to denounce citizenship or

c) Notification from DCIC on cancellation of citizenship or

d) Court order or

e) Informant notification

f) Deduplication
Basic Flow Step1:

a) NIRA receives application for cancellation through either of the following:

• An application from the subject of the cancellation or informant raised through the web portal/mobile app via police for investigation and confirmation.

• A cancellation notification from DCIC through the NIRA-DCIC system interface

• A Court order submitted physically to NIRA and uploaded into the system

b) System receives the application

c) NIRA verifies the NIN of Subject of cancellation and the NIN of the applicant in the case where the application is by the informant.

d) NIRA officer reviews the application and makes a decision to proceed or reject/ escalateor request for more information.

e) If the decision of the NIRA officer is to proceed with the cancellation, the system shall capture this decision and in addition send a notice of the intention to cancel to the subject of cancellation.

f) The system shall flag the application under investigation.

Step 2:

g) The system shall facilitate capture of response from the subject of cancelation and uploading of additional information e.g. evidence of proof of service

h) System should trigger reminders (SMS, email etc) to the subject of cancellation within aconfigurable period of time before the expiry of the required response time of 15days.

Step 3:

i) System shall facilitate scheduling of a hearing date and notifying the subject of cancellation of the same date.

j) They system shall facilitate capture of the proceedings of the hearing to include therecommended decision and forward for decision.

k) The system shall facilitate decision on the recommendation of the hearing (approve/stay).

l) Record/NIN(s) will be cancelled if management decision is to cancel

m) In the case of duplication, the system should generate a notice of multiple registrationsfor prosecution process.

n) Card is cancelled

o) Update the TPI
Alternate Flow Step 1(a)

a) If Email sending fails; system gives an error message

b) If management decision in step 3 is not to cancel, a notification to that effect shall be sent back to the subject of cancellation and the NIN of the subject of cancellation shall remain active.

c) System shall send notification to the informant of the management decision taken.
Post Condition The System

a) Update Part 1 or 2 and 3 and TPI

b) Update the list of cancelled NINs at NIRA portal

c) The old ID if printed must be cancelled if the decision of management is to cancel
Conclusion The record of the subject of cancellation is cancelled on the NIR and all related system components are updated.
Business Rules 1. Asubject of cancellation under this category should be flagged as one under management review.

  1. The subject of cancellation should be able to respond to the notice online and in case they are not able, manual responses will apply.
1 Like

This is a vexing problem for CRVS all around the world guys, not only revocation, but editing rights as well. The birth database is a honeypot for wrongdoings. Mischief usually occurs at BC creation, or years later to usurp identity. The best mechanism I can think of is attaching and/or linking to Health records/external entities for BC creation (multiple pieces of documents - prenatal clinics/village leaders/hospital-midwife affidavits/etc). As for post creation editing of record, we need to get approval from multiple parties, a triple lock type of scenario (Registrar/someone else up the chain, and perhaps a 3rd party - electoral body or healthcare leadership). The idea is to frustrate and reduce illegitimate BCs. It is also important not to overburden the approval channel, lest it become a simple rubber stamp, which means a thorough exercise of verification of data accuracy at the beginning.

1 Like

thank for question .