Guidelines For Income Verification
Guidelines For Income Verification
1) General recommendations related to App installation. To offer the best user experience,
we recommend the following
❖ Installation
Kindly download the app from the official CRID LC website. An updated version of the app is
now available for download at http://cridlc.edisha.gov.in.
❖ Compatibility
At present, Income verification App is compatible with all Android mobile devices. As of now the
app is not IOS compatible.
❖ The app does not work after downloading, please follow these instructions: -
● Check if the app is downloaded from WhatsApp
● If this is the case, remove the app from your phone.
● Please visit the CRID LC website to download the app
● Reinstall the app.
2
3) Issues related to app unable to load
❖ The LC member is unable to see the lower portion of the screen including important features
such as submit/ok button. Issue date- 29-01-2002
● This is a technical issue and has been resolved soon.
❖ The LC member is unable to see or select LC Code. This may be due to internet connectivity
issues or wrong/missing mapping of the LC member to LC or the user is not using the updated
version of the app.
❖ The LC member is unable to see data in his login. This issue generally occurs when there are
some server/database level technical faults. The PPP technical and domain teams keep
watching for such errors and these are resolved at the earliest. The LC member may
communicate the issue when they experience it, to their respective District CRID Information
Managers (DCRIM). The PPP technical team continuously works on minimizing the recurrence
of such issues.
❖ The data in the login is not properly fetched. This was a technical issue and it has been
resolved.
❖ The LC member is not able to see the mobile number of the families. This issue has been
resolved.
❖ The LC member is not able to upload data for more than 5 members. This issue has been
resolved.
❖ Team lead is not able to mark the families untraceable on the app. This issue has been
resolved.