Duplicate Management
PCH-SIG automatically detects potential duplicates between households to ensure registry integrity.
Access
Side menu: Social Registry > Duplicates
Required permission: registre.doublons_view
Types of detected duplicates
The system identifies several types of duplicates:
| Type | Description | Example |
|---|---|---|
| Phone | Same phone number | 2 households with phone 771234567 |
| Name + Locality | Same name in the same locality | "Mamadou Diop" x2 in Thies |
| Mobile Money | Same Mobile Money number | 2 households with MM 771234567 |
| GPS coordinates | Identical geographic position | Same latitude/longitude |
Risk level
Each detected duplicate has a risk level:
| Level | Score | Description |
|---|---|---|
| High | 80-100 | High probability of real duplicate |
| Medium | 50-79 | Possible duplicate, verification needed |
| Low | < 50 | Similarity detected but probably distinct |
The score is calculated based on the number of matching fields and their importance.
Management interface
Overview
The page displays statistics:
- Detected: Total number of duplicates
- Untreated: Awaiting action
- Confirmed: Marked as true duplicates
- Ignored: Marked as false positives
- Merged: Merged households
Duplicate list
Each duplicate shows:
- Duplicate type (icon)
- The 2 households concerned
- Similarity score
- Treatment status
- Detection date
Filters
| Filter | Options |
|---|---|
| Status | All, Untreated, Confirmed, Ignored, Merged |
| Type | Phone, Name, Mobile Money, GPS |
| Risk level | High, Medium, Low |
Examine a duplicate
Click on a duplicate to see details:
Side-by-side comparison
| Field | Household A | Household B |
|---|---|---|
| Code | MEN-2024-001 | MEN-2024-089 |
| Head | Mamadou Diop | Mamadou Diop |
| Phone | 771234567 | 771234567 |
| Locality | Thies | Thies |
| Size | 5 | 5 |
| Collection date | 01/15/2024 | 03/20/2024 |
Identical fields are highlighted.
Actions on a duplicate
Ignore
If it is not a real duplicate (false positive):
- Click on Ignore
- Add an explanatory comment (optional)
- Confirm
The duplicate is marked as ignored and no longer appears in the untreated list.
Required permission: registre.doublons_check
Confirm
If it is a real duplicate:
- Click on Confirm
- Add a comment
- The duplicate is marked for merging
Merge
To merge two households into one:
- Click on Merge
- Choose the main household (which will be kept)
- Verify the information that will be merged
- Confirm
The merge:
- Keeps the main household
- Transfers members from the other household
- Transfers associated payments and beneficiaries
- Archives the deleted household
Required permission: registre.doublons_merge
Merging is irreversible. Verify carefully before confirming.
Manual verification
To launch a duplicate verification:
- Click on Check duplicates
- The verification runs in the background
- Newly detected duplicates appear in the list
Verification can be scheduled automatically by the administrator.
Best practices
Prevent duplicates
- Check if the household exists before creating it
- Use phone search
- Validate GPS data in the field
Treat duplicates
- Treat high-risk duplicates as a priority
- Document decisions with comments
- Contact the field in case of doubt
Merging
- Always choose the household with the most recent/complete data
- Check associated payments before merging
- Inform field teams about the merge