Make the field record usable beyond the device.

One reading, two responsibilities

Consider a hypothetical organisation in Lebanon recording readings from its own equipment. A field colleague sees an asset marked A-204 and enters the displayed value. The office uses a French equipment term, while the field instructions are in Arabic. We would first establish whether a mobile app is useful for this recurring task, then design the record around that specific distinction: what was observed and what the office decides to do with it.

Make the identity and unit unambiguous

A stable Latin asset identifier can connect the field record to the approved equipment list. It should remain readable beside Arabic instructions rather than being translated into a new identifier. A suitable Arabic reviewer must assess digit entry, decimal presentation and unit labels in the actual screen. The responsible team confirms the measurement and unit; the software does not infer them from a photograph.

For the worked example, the office term for A-204 maps to the same asset record. An unfamiliar French label must not cause a colleague to create a second asset. We can provide an approved cross-reference and a way to flag an unknown label for review. The business decides who maintains that mapping.

Keep observation separate from correction

If the office suspects a mistyped value, retain the submitted observation and record the proposed correction with its reason and responsible reviewer. An office estimate is a different kind of value; it must not silently replace a measured reading. The user should be able to see which value was observed, which was proposed later and which the responsible person accepted.

A record captured on the device but still waiting to reach the service is not yet an accepted reading. Test an interrupted submission and a repeated send of the same record so the office does not mistake a duplicate for a second observation. These are tests on the devices and connection conditions in the agreed project, not claims about connectivity across Lebanon.

Choose the release responsibilities

Agree who reviews Arabic wording and office terminology, who can correct a record, and who controls device access and app distribution. We can develop the recording and review software; the client retains responsibility for equipment operation and any required professional assessment. Describe the actual reading, asset list and office decision so we can assess a useful first scope.