A rugged tablet succeeds when a field worker can capture the right information, keep it through interruptions, and deliver a verified record to the office. Select the application and workflow first, then test the tablet, dock, input tools, and power arrangement under representative conditions. This guide turns that process into an acceptance trial you can use before a rollout.
Define one complete field job
Describe the job from assignment to accepted record: identify an asset, open its history, enter readings, attach photographs, record location, obtain any required signature, and synchronize. Specify the required operating system and application version before choosing hardware. A desktop Windows program, an Android field application, and a browser form can have very different offline behavior.
List the environmental conditions and accessories that matter: daylight, gloves, permitted cleaning products, rain exposure, shoulder strap, vehicle dock, external scanner, or positioning receiver. Obtain the exact model’s instructions and test evidence for the installed configuration. The rugged-laptop guide explains how to interpret model-specific test reports; apply the same evidence discipline to a tablet and its accessories.
Test capture and synchronization separately
Prepare a small, clearly marked test dataset. Include required fields, a long note, several photographs, and an intentional correction. Download all required maps and records while connected, then confirm the intended work is available with connectivity disabled in a controlled trial.
As a concrete Android example, ArcGIS Field Maps synchronization sends local edits and retrieves server changes. Esri explains that offline edits remain on the device until synchronized and that conflict handling depends on how the service stores data. Configure the map for its intended offline use using the Field Maps preparation guidance. Other applications need their own equivalent checks.
On a narrow screen, scroll the table sideways. Keyboard: focus the table and use the arrow keys.
| Stage | Test | Passing evidence |
|---|---|---|
| Before departure | Open the assignment, map, reference documents, and form offline | Every required item is accessible without a connection. |
| At the asset | Enter values, scan an identifier, take photographs, and save | Correct asset association and readable, complete entries |
| During interruption | Use the app’s documented pause and resume workflow | Saved work returns and remaining work is identifiable. |
| Back online | Synchronize, then inspect the record from another authorized device | Values, attachments, and corrections match the field record. |
| End of shift | Complete normal docking, charging, and handover | Account access, battery state, and outstanding edits are clear. |
Set acceptance criteria before the trial. For example, the team may require every test record and attachment to arrive correctly, plus completion of its normal shift with an agreed power reserve. Derive the reserve from operating needs and measured runtime; a brochure battery figure uses its own test conditions.
Walk through a small example
Fictional inspection: a worker completes 12 asset records with three photographs each. The verification target is 12 records and 36 photographs, with each set linked to the correct asset. If the server contains all 12 records but only 34 photographs, the job remains incomplete. Reconcile the missing attachments against the local records before marking the shift delivered.
Count agreement is one check. Open the photographs, inspect entered units, and verify the location and asset identifiers. Test an intentional conflict using a disposable record so the team understands which edit survives or who resolves it. Keep production records out of experimental conflict tests.
Recover without losing the evidence
When synchronization fails, retain the device and its local data. Record the error, time, account, map or form version, and remaining edits. Avoid deleting the offline area, clearing application storage, or reinstalling while unsynchronized work needs recovery. Esri’s sync guidance links to logging and supported extraction of offline edits; involve the application administrator before taking a destructive recovery step.
Use the field-tablet acceptance record for the trial and handover. It includes record and attachment counts, unresolved issues, and retest ownership. Repeat the affected workflow after application updates, map-schema changes, a new dock or scanner, or a change in field conditions. The tablet-PC guide covers pen and application compatibility in more detail.