In one of our projects we are facing issues of double dipping.
Use Case: In a distribution center, we have multiple distribution que (in each que there is one data collector and all of them in offline mode). Beneficiary receives good from one que and lined-up to another que and receives the distribution.
Do you have any recommendation how to eliminate that.
This is a common concern for offline entitlement distribution, and there are a few different ways that the problem is approached depending on the situation.
Partition and Triage - Pre-partition individuals by name (or randomly) to only receive distribution by one agent and have one of the individuals involved in distribution triage incoming people into the appropriate stream, this can be configured through case lists and filters, or by actually distributing data differently to different agents.
Post-Distribution Accountability - Don't prevent double dipping during distribution, but record all distributions such that it can be audited later that someone received a distribution twice, and that behavior can be corrected. Reports can be fairly easily configured to track this, and cases can be flagged either for followup, or to flag in a case record that a beneficiary has previously double dipped and should be checked manually next time
Local Token - In high cost / ongoing cases NFC tokens can be distributed to beneficiaries which can hold local data records that a distribution was received. We've worked with teams in the past who've configured such records in CommCare, this is especially effective when distributions can occur in sites which are physically far away.
-Clayton