Approve a registration¶
How to review one submitted application and either approve it, send it back for changes, or archive it. This is the core of a Registration Officer's day.
You need: the Approve action permission (rg:ls:ap:act) and access to the
List of Applicants screen.
Before you start¶
An application only reaches you once a field worker marks it Submitted. While it is In Progress it is still being filled in and you cannot action it.
Steps¶
1. Open your queue¶
In the sidebar, choose Registration → List of Applicants. The table shows one row per application:
| Column | What it tells you |
|---|---|
| Reg No | The application's reference number — click it to open the profile |
| Name | The applicant |
| District | Where they registered |
| Submitted By | The field worker |
| Status | Where the application is in its lifecycle |
Filter the Status column to Submitted to see only what's waiting on you.
2. Open the applicant's profile¶
Click the Reg No to open the full profile. Work through the tabs top to bottom — Personal details, Payment Account, Household, Pregnancy, Children, Documents. Look for the automatic-check badges on each section:
Green means checked, not correct
A green badge means the automatic check passed (for example, the bank account verified). It doesn't replace your judgement — a passed check on a mismatched name still needs a human decision.
3. Take the action¶
Open the Comments & Activity tab and choose Take action. The Choose an action dropdown offers only the moves that are valid from the current status:
| Action | What it does |
|---|---|
| Approve | Send to enrolment — the application becomes a beneficiary |
| Request Edit | Send back for changes — returns it to the field worker |
| Archive | Archive application — removes it from active review |
Request Edit needs a comment
If you choose Request Edit, a comment is required — it's the only way the field worker knows what to fix. The form blocks you with "A comment is required for the Request Edit action" until you add one.
Click Submit Action.
4. Confirm it worked¶
You'll see the toast "Registration status updated." and the profile banner changes to the new status. An approved application now flows to enrolment; a Request for Edit returns to the field worker and comes back to your queue once resubmitted.
What happens next¶
flowchart TD
Q[Your queue: Submitted] --> R{Your review}
R -->|looks good| AP[Approve → Enrolment]
R -->|needs a fix| RE[Request for Edit → field worker]
R -->|not valid| AR[Archive]
RE -.resubmitted.-> Q
AR -.Unarchive.-> Q
style AP fill:#eef0f7,stroke:#3d4479
Approving in bulk¶
For a whole district at once, use Registration → Enrolment Batch instead. A batch is signed off by two officers — a First Verification and a Second Verification, each recording Approved or Rejected. That two-person control is covered in Two-stage batch verification (coming soon).
Related¶
- Registration Officer overview — the full lifecycle and your other tasks
- Not sure what you're allowed to do? Access is set per role — ask a System Administrator.