Choosing Devices for Field Data Collection in India
Choosing devices for field data collection in India
For most NGO field data collection in India, a mid-range Android phone with at least 4 GB of RAM, 64 GB of storage and a large battery is enough. Choose tablets only when forms are long, include maps or tables, or are filled with the respondent looking at the screen. The decision that matters more is how you manage devices: who owns them, how they are locked, and what happens to data after upload. This guide covers both. For which app to install, see our 2026 comparison of offline data collection apps for NGOs.
Phone or tablet?
| Use case | Phone | Tablet |
|---|---|---|
| Short monitoring forms (under 15 minutes) | ✓ Best | Overkill |
| Long household surveys with rosters | Works | ✓ Easier to read |
| Map-based work (Survey123, field mapping) | Works | ✓ Better |
| Showing pictures or videos to respondents | Small screen | ✓ Better |
| Walking long distances, two-wheeler travel | ✓ Pocketable | Bulky, breaks more |
| Workers already own a smartphone | ✓ BYOD possible | Needs purchase |
ASHA-style frontline workers and community mobilisers usually do better with phones. Enumerators on a four-week survey often prefer tablets.
Minimum specs we recommend
These are working minimums from our projects, not vendor requirements. Check your chosen app’s current Android version support before buying.
- Android, not iOS. Every tool in our list supports Android, and devices cost far less.
- 4 GB RAM or more. Forms with long lookup lists (all villages in a district) slow down on 2–3 GB devices.
- 64 GB storage or more if you capture photos or audio audits.
- 5,000 mAh battery or larger, plus a 10,000 mAh power bank per worker for multi-day trips.
- Dual SIM. Coverage varies by village; a second network often means a successful upload on the same day.
- A recent Android version with security updates, so device encryption and app updates work.
- Readable in sunlight. Test outdoors before a bulk order.
Budget for 5–10% spare devices. Phones get dropped, lost and soaked.
Shared devices or personal phones (BYOD)?
| Organisation-owned devices | Personal phones (BYOD) | |
|---|---|---|
| Upfront cost | Higher | Low (add a data allowance) |
| Control over apps and updates | Full | Limited |
| Data security | Easier to enforce | Personal apps share the phone |
| Worker acceptance | High | Mixed; some resent work data on their phone |
| Lost device response | Wipe remotely | Ask the worker |
For sensitive data (health, child protection, survivors of violence) we recommend organisation-owned devices with a device management tool that can lock and wipe them. For low-risk monitoring forms, BYOD with a monthly data allowance works and is far cheaper.
Device rules that matter under DPDP
India’s DPDP Act makes your organisation responsible for “reasonable security safeguards” for personal data, and the Rules’ core obligations apply from 13 May 2027. On field devices that means:
- Screen lock on every device, PIN or pattern, no exceptions.
- Encrypted forms for sensitive data, so submissions cannot be read on the device. Kobo, ODK and SurveyCTO support this.
- Delete after upload. Configure the app to remove sent submissions from the device.
- No WhatsApp forwarding of photos or lists of beneficiaries.
- A device register so you know which device was where, with whom, and when it was wiped.
Our plain-English DPDP Act guide for NGOs explains the wider obligations.
Worked example: equipping a 40-person field team
A livelihoods nonprofit (anonymised) runs a monthly monitoring form across 40 field staff in three districts, plus a one-time baseline.
- Monitoring: BYOD with a ₹300 monthly data allowance per worker, app locked with a PIN, sent forms deleted from the device.
- Baseline: 20 organisation-owned tablets for a six-week survey, then reused for training sessions.
- Spares: 2 tablets and 4 power banks held by the district coordinator.
- Charging: each worker charges devices and power banks at the block office before field days.
- Updates: forms are updated only on Mondays, and supervisors check each device shows the latest form version before field days. This stops old-version submissions, a common source of sync conflicts.
Device register template
| Device ID | Model | IMEI (last 4) | Assigned to | Area | App + version | Encryption on? | Last wipe | Status |
|---|---|---|---|---|---|---|---|---|
| TAB-014 | (model) | 4821 | Field officer, Block A | Block A | ODK Collect vX | Yes | 02/11/2026 | In use |
Keep the register in your MIS rather than a loose spreadsheet once you pass about 30 devices.
Common mistakes
- Buying the cheapest device in bulk before testing your actual form on it.
- No plan for charging in areas with long power cuts.
- Updating forms mid-week, so half the team submits to an old version.
- Leaving months of submissions on devices because nobody set auto-delete.
Old form versions and shared devices are also behind many duplicate records. Read offline sync conflicts and how to prevent them before you roll out.
Not sure your field set-up will survive the next survey round? Take the free nonprofit technology assessment. Start the free technology assessment →