Digital operations
Preparing digital devices for a field mission
Test offline access, battery readiness and data protection before relying on a device in the field.
1. Define uses.
List necessary functions: reading documents, completing forms, taking authorized photographs or communicating observations. Assign an owner to each device and a person responsible for the data. Confirm device use is accepted at the site before deployment. This general guidance does not replace formal risk assessment, IT and confidentiality policies or specific workplace restrictions. Separate operational tools from approved emergency communication arrangements so one untested application is not the team’s only safety link.
2. Secure access.
Apply approved updates before departure with enough time to verify operation. Test individual accounts, locking and authentication under organizational policy. Grant only necessary access and avoid shared accounts. Verify encryption where policy requires it, along with the approved process for lost access. Report a noncompliant device to support; do not disable security controls to bypass a connection problem. Confirm support contacts are accessible even if the device cannot sign in.
3. Test offline.
Download approved versions of maps, procedures and forms, then run a test without connectivity. Check reading, data entry and preservation of local records before leaving. Clearly identify document version and date so obsolete copies can be detected. Arrange an approved fallback if the application fails. A readable screen does not prove forms remain saved or data will synchronize correctly; test the full workflow with non-sensitive sample records before relying on it.
4. Prepare power.
Charge devices and provide approved, compatible power sources in good condition. Check cables, connectors and protection against conditions specified by the manufacturer. Avoid prohibited heat or dust exposure and use equipment only within its approved operating conditions. Damaged devices or batteries must be withdrawn and reported; do not improvise repairs. Confirm expected endurance through a representative test rather than relying solely on the charge indicator shown at the start of the day.
5. Control collection.
Collect only necessary and authorized information. Check photography permissions and confidentiality conditions before recording. Link each observation to the correct site, task and date without adding unnecessary personal data. Store files in approved locations and verify that saving succeeded before closing the application. Do not use personal messaging or storage services to transmit information the organization must protect. Review the record for accuracy while corrections can still be checked with the field team.
6. Close the mission.
On return, synchronize through an approved channel and verify complete receipt, duplicates and any conflicts. Have essential data confirmed before deleting a local copy under the applicable policy. If a device is lost or stolen, report promptly to the designated contact without attempting dangerous physical recovery. Document battery, connectivity and entry difficulties to improve the next deployment. Keep unresolved synchronization errors visible and assign an owner rather than assuming an upload indicator proves completion.
7. Verify navigation and emergency readiness.
Test offline maps for the planned route and compare GNSS coordinates with a known point. Record coordinate format, units, geodetic datum and estimated accuracy to prevent ambiguous locations. Provide compatible spare power and cables; check manufacturer heat, dust, water and impact limits rather than assuming rugged equipment tolerates everything. Test encrypted backups and restoration under approved policy. Confirm approved radios, permitted frequencies and applicable satellite equipment authorization before transmitting. Test the tracking contact, check-in schedule and missed-contact escalation using primary and backup channels. A phone must not be the sole emergency communication method for the mission.