Skip to content
Alpha

This site is an alpha version and is still being developed in the open - your feedback will help us improve it. See the roadmap. Last updated: 14 October 2026.

Version in force: 0.3.0 (6 October 2026).

Field working and devices

Many Defra staff and partners work on farms, at ports, on rivers and at sea. These draft guardrails make sure the tools they use work where they work, and keep Defra data safe on the move.

Who these guardrails apply to

The core department. Whether the field working and devices guardrails also apply to Defra's arm's length bodies is still to be confirmed.

Puts architecture principle 8. Right tools, right place into practice. See also the proposed field inspection service pattern.

Draft guardrails

These guardrails are new drafts from the guardrail backlog. Comment on them by opening an issue.

GR-FIELD-01 Choose devices that suit the job

Should Choose devices for field work from research into where and how people work - outdoors, in bad weather, wearing gloves, in the dark - not from what is already on the desk.

Why: a tool that cannot be used in the rain or with gloves on will not be used, and staff fall back to paper.

How to meet it: observe field work in discovery, and record the device choice and the reasons in an ADR.

Phases, evidence and status for GR-FIELD-01
Status
Draft
Phases
Discovery, Alpha
Led by
User researcher, Service designer
Evidence
User research on the working environment, and the device choice recorded in an ADR
Automated check
Manual
Maps to
Service Standard 1
DDTS doctrine
7
Owner
Architecture team, last reviewed 2026-10-01, since v0.2.0

GR-FIELD-02 Design field tools to work offline

Should Field tools work without a connection: they download what is needed before a visit, save work on the device, and sync safely when back in signal.

Why: much of rural England and the sea has poor or no mobile coverage. Losing work because the signal dropped destroys trust in digital tools.

How to meet it: test every field journey in flight mode, and decide in an ADR how conflicts are resolved when two people change the same record offline.

Phases, evidence and status for GR-FIELD-02
Status
Draft
Phases
Alpha, Beta, Live
Led by
Interaction designer, Developer
Evidence
Field journeys tested with no connection, including sync after reconnecting and conflict handling
Automated check
Manual
Maps to
Service Standard 5
DDTS doctrine
7
Owner
Architecture team, last reviewed 2026-10-01, since v0.2.0

GR-FIELD-03 Manage and secure every device

Should Devices that hold or access Defra data are enrolled in Defra device management, encrypted, kept patched, protected by a screen lock and able to be wiped remotely if lost.

Why: field devices are lost and stolen more often than office equipment, and may hold personal and sensitive data.

How to meet it: use Defra-managed devices. If a supplier or partner device is needed, agree how it meets the same controls before it is used.

Phases, evidence and status for GR-FIELD-03
Status
Draft
Phases
Alpha, Beta, Live
Led by
Security architect
Evidence
  • Alpha: Device management approach agreed for the devices the service will use
  • Beta: Devices enrolled in Defra device management, with encryption, patching, screen lock and remote wipe confirmed
  • Live: Device compliance monitored, and lost devices wiped
Automated check
Manual
Maps to
Technology Code of Practice 6; Secure by Design principles 7, 8
DDTS doctrine
7
Owner
Architecture team, last reviewed 2026-10-01, since v0.2.0

GR-FIELD-04 Check connectivity before you design

Could Check the mobile and broadband coverage where the service will be used before choosing an approach, rather than assuming it.

Why: coverage maps and real-world signal often differ, especially inside farm buildings and in valleys.

How to meet it: use public coverage data and ask users, and plan for the worst case.

Phases, evidence and status for GR-FIELD-04
Status
Draft
Phases
Discovery, Alpha
Led by
User researcher, Technical architect
Evidence
Connectivity in the places the service will be used checked, and the approach recorded
Automated check
Manual
DDTS doctrine
7
Owner
Architecture team, last reviewed 2026-10-01, since v0.2.0