For: Field teams and coordinators
The useful outcome: A tested offline reference outline
Choose field questions first
List the questions people must answer without a connection, such as a process step, a site contact, or a safety escalation path approved by the team. Build around those questions rather than copying a whole repository.
- Gather recurring questions from field staff
- Identify the content owner for each answer
- Exclude material not approved for the kit
Make each answer findable
Use short section names, terms staff recognize, and compact checklists. Include source owners so people know who can clarify a disputed instruction later.
- Use familiar vocabulary in headings
- Keep checklists short enough to scan
- Include escalation context where authorized
Test in the likely setting
Download the draft, disconnect the test device, and ask someone to locate several answers under time pressure. Record missing terms and improve the headings.
- Disable connectivity for the test
- Search with real field terms
- Record results for the next revision
Questions, answered.
What belongs in a field kit?
Approved, stable reference material that a team is authorized to use and can understand away from its usual systems.
How is the kit updated?
Updates are manual: revise the approved source material, create a replacement file, and distribute it by the method the team agrees.