---
title: "Operation Data Logging: What and How to Record — BosNets"
description: "What is operation data logging? Activity logs, timestamps, task and location records, data protection retention rules and after-action review, step by step."
url: https://www.bosnets.com/en/blog/operation-data-logging
lang: en
alternate: https://www.bosnets.com/blog/operasyon-verisi-kaydi
author: "Emir Tanrıver"
datePublished: 2026-11-10
dateModified: 2026-11-10
source: html
---

# Operation Data Logging: What to Record, When and How

[Emir Tanrıver (LinkedIn, opens in a new tab)](https://www.linkedin.com/in/emirtnrvr/) 10 November 2026 12 min read

Operation data logging means keeping a time-stamped record of the messages sent, the tasks assigned, the positions of teams and the decisions taken during a field operation. A well-kept log builds a shared picture while the operation is running, and answers “what happened, and why?” once it is over. This guide covers what to record, what a good log entry looks like, what to watch for under personal data protection rules, and how to use the log in an after-action review.

## In short

- An operation log is made up of five kinds of data: messages, tasks, locations, resources and decisions.
- Every log entry needs at least three things: the time, who, and what happened.
- In Türkiye, keeping records during disaster response and for occupational health and safety is also required by law.
- Location and message records are personal data; how long they are kept and who can access them should be written down in advance.
- The real value of the log shows in the after-action review.

## Contents

1. What is operation data logging?
1. Why keep a log?
1. What does a good activity log look like?
1. Five qualities of a reliable log
1. Personal data: retention, access, destruction
1. Logging when there is no network
1. Learning from the log
1. Operation logging step by step
1. Our approach
1. Where does BosNets fit?
1. Frequently asked questions
1. Sources

## What is operation data logging?

In a search and rescue effort, a power line fault or a construction site drill, the same questions come up: Who is where, which task is at which stage, which piece of information reached whom, and when? Operation data logging keeps the answers in a form you can consult both during and after the incident.

A log is not just a message archive. In practice, five kinds of data are kept together:

**Kinds of data in an operation log**

| Data type | What is recorded? | Which question does it answer? |
|---|---|---|
| Message | Sender, recipient, time, content | Who received the information, and when? |
| Task | Who assigned it, who received it, status changes | Who had the job, and when was it done? |
| Location | Team or individual position, time | Who was where? |
| Resource | Use of vehicles, equipment and supplies | What was used up, what ran short? |
| Decision | Who decided, the reasoning, the time | Why was this course chosen? |

The first four can largely come out of the communication system on their own. The fifth, the reasoning behind a decision, usually needs a person to write it down. Seeing this split from the start, when you plan the log, avoids the trap of assuming “the system records everything anyway”.

## Why keep a log?

A log does three jobs. The first is real-time coordination: the coordination centre can see the picture without asking the field again and again. The second is review: once the operation is over, you discuss what worked and what did not on the basis of the records. The third is accountability: when a decision or an accident is questioned later, the answer comes from a document, not from memory.

In Türkiye this is not left to choice either. The [Regulation on Disaster and Emergency Response Services](https://mevzuat.gov.tr/MevzuatMetin/3.5.20135703.pdf) (the Turkish regulation that sets out how public bodies respond to disasters) makes regular and continuous reporting the rule during disasters and emergencies. Under the same regulation, field assessment teams report their first findings to an incident tracking desk, and the information gathered is entered on maps and the database in use. The regulation also makes it the rule to keep records, as far as possible, of all resources used in response work. After the response, the service groups prepare reports covering the problems encountered, their solutions and an analysis of the experience.

On corporate sites, a similar obligation comes from occupational health and safety. Under Article 14 of Türkiye’s [Occupational Health and Safety Law No. 6331](https://www.mevzuat.gov.tr/mevzuatmetin/1.5.6331.pdf), the employer keeps a record of all occupational accidents and occupational diseases, carries out the necessary investigations and prepares the related reports. The article also requires incidents that caused no injury or death, but had the potential to harm a worker, the workplace or work equipment, to be investigated and reported. Investigating these incidents properly depends on knowing who was where at the time and when each warning was given. We also covered this from the field side in our post on [construction site team communication](/en/blog/construction-site-team-communication).

## What does a good activity log look like?

A good model for an activity log is the Activity Log (ICS 214) form used in the United States’ incident command system. In the [completed example form](https://www.usfa.fema.gov/downloads/pdf/covid19/ics_form_214_example_covid19.pdf) published by the U.S. Fire Administration, a medical unit leader’s 24-hour shift can be read line by line. The structure of the form is a good starting point when designing your own log:

**Fields in the ICS 214 Activity Log form**

| Field on the form | Purpose |
|---|---|
| Incident name | Identifies which incident the record belongs to. |
| Operational period | Start and end date and time; frames the shift. |
| Name, position, home agency | Identifies the person keeping the log and their role. |
| Resources assigned | Lists the people on the team, their positions and units. |
| Date/time and notable activities | The time and a short description of each event. |
| Prepared by | Name, title, signature and time of preparation. |

The entries on the example form are short and concrete: the time, the address attended, the supplies used, the moment the unit went back into service. Times are written in 24-hour format and pages are numbered. A good log entry contains no commentary; it states what happened.

## Five qualities of a reliable log

A log is only useful if it can be trusted. The following five qualities turn the log from a subject of argument into the basis for one:

- **Timestamp:** Every entry needs a time, and every source should write against the same clock. Different devices with different clocks scramble the order of events.
- **Identity:** It should be clear who sent a message and who assigned a task. Write the role and the person’s name rather than “HQ”.
- **Integrity:** Records should not be silently changed afterwards. If a correction is needed, add it as a new entry, with its time.
- **Continuity:** If logging stops when the network goes down, the most critical minutes are left blank.
- **Accessibility:** The log should be readable during the operation too; an archive that is only opened afterwards adds nothing to coordination.

## Personal data: retention, access, destruction

Location and message records belong to named workers, so they are personal data. Türkiye’s [Personal Data Protection Law No. 6698](https://www.mevzuat.gov.tr/mevzuatmetin/1.5.6698.pdf) (known as KVKK, Türkiye’s counterpart to data protection laws such as the GDPR) defines personal data as any information relating to an identified or identifiable natural person. Article 4 of the law requires personal data to be processed for specified, explicit and legitimate purposes; to be relevant, limited and proportionate to the purposes for which they are processed; and to be kept only for the period laid down in the relevant legislation or needed for the purpose.

Under Article 7, when the reasons for processing no longer exist, personal data are erased, destroyed or anonymised. Article 12 obliges the data controller to take the necessary technical and administrative measures to prevent unlawful processing and access and to safeguard the data.

The details are set out in the [Regulation on the Erasure, Destruction or Anonymisation of Personal Data](https://www.kvkk.gov.tr/Icerik/5441/KISISEL-VERILERIN-SILINMESI-YOK-EDILMESI-VEYA-ANONIM-HALE-GETIRILMESI-HAKKINDA-YONETMELIK). Under this regulation, the data controller sets the interval for periodic destruction in its retention and destruction policy, and that interval may in no case exceed six months. All erasure, destruction and anonymisation operations are also recorded, and those records are kept for at least three years, other legal obligations aside.

In practice, this means writing down the purpose of the operation log, the retention period and the access rights before logging begins. We covered which questions to ask at the selection stage in our guide on [choosing a mobile field communication app](/en/blog/mobile-field-communication-app). This section is general information; consult your legal department for periods specific to your organisation.

## Logging when there is no network

Most logging plans rest on one assumption: messages pass through a server, and the server records them. When the network goes down, teams turn to radio, face-to-face talk or paper, and the log scatters with them. After the incident, the person responsible for records tries to build a timeline from different people’s notebooks and memories.

There are two ways to close this gap. The first is to write a handwritten log into the plan: who keeps it, which form they use and where the record is handed in at the end of the operation must be clear. The second is to use a data channel that works and records messages even without a network. The two are not mutually exclusive; some information, such as the reasoning behind decisions, is written by hand anyway.

Radio has a place of its own here. Radio carries voice instantly and keeps its role in the field. A channel that carries written messages, locations and task status complements radio and produces data that can go straight into the log. We compared the options in our post on [infrastructure-free communication](/en/blog/what-is-infrastructure-free-communication).

## Learning from the log

The log is most useful at the moment the operation ends. The World Health Organization’s 2019 [guidance for after action review](https://www.who.int/publications/i/item/WHO-WHE-CPI-2019.4) describes the method as a way to review the actions taken in response to an event, and also as a routine management tool for continuous learning and improvement. The guidance lists four formats: the debrief, the working group, the key informant interview, and a mixed method that combines them.

Whichever format you choose, the meeting should rest on the records. Without a log, a review turns into the version remembered by whoever speaks loudest. With one, the questions become concrete: How many minutes passed between the first report and the first task? Which team became unreachable, and at what time? Which instruction was given twice? We described a similar frame for the post-crisis stage in our post on [communication in crisis management](/en/blog/crisis-management-communication).

## Operation logging step by step

1. **Write down the purpose**State in one paragraph why you keep the log: coordination, review, legal requirements, or all of them.
1. **Choose the data types**Decide which of messages, tasks, locations, resources and decisions you will keep, and in how much detail.
1. **Assign a records officer**Name one person and a backup for the handwritten log, and prepare the form in advance.
1. **Set the time and identity rule**Make sure every record is written against the same clock and under a role name.
1. **Define retention and access**Write down the retention period, the destruction schedule and who can access which records.
1. **Test the no-network scenario**Switch phones off during a drill and check whether logging continues without a gap.
1. **Schedule the review**After every operation and drill, hold a review based on the records and feed the lessons back into the plan.

## Our approach

When designing BosNets, we treated logging as part of communication rather than a by-product of it. We wanted every message and task that passes through the network to be stored with a timestamp, without needing a separate logging step.

Making sure the log does not stop the moment the network goes down was also a basic choice for us. That is why the system works over the internet when there is a network and over the mesh network the devices form when there is not, and leaves the same record in both cases.

We cared about letting the organisation decide where its records live. On a private closed network, records are kept on the organisation’s own server; the organisation sets the retention period and the access rights.

— Emir Tanrıver, BosNets co-founder

## Where does BosNets fit?

BosNets is the communication layer that automatically collects the message, task and location data in a logging plan. [BosLog](/en/boslog), the management interface opened in a web browser, works as the screen of the coordination centre: who is where, which task is at which stage, which message was delivered when. All communication is archived with timestamps; after the operation, which information was delivered when can be verified from the records. Tasks are assigned to field workers, their status is tracked, and at the end of a shift or operation the communication and task records can be reported.

In the field, the team shares written messages, locations and tasks with BosApp. When there is no network, phones join the mesh network through BosMag devices; BosLog keeps working as long as it is connected to the network, even without the internet. Message contents are encrypted with AES-256. The limits are clear too: BosNets does not carry voice calls, and it does not write the reasoning behind decisions for you. That stays the records officer’s job.

## Frequently asked questions

### Is an operation log the same as an incident report?

No. An operation log is the raw, time-stamped record kept while the incident is running. An incident report is the assessment written from those records after the operation ends. A good report cannot be written without a good log.

### Does logging employees’ locations breach Turkish data protection law?

Location is personal data, so the principles of KVKK must be followed: a specified and legitimate purpose, processing that is limited and proportionate to that purpose, retention only for as long as needed and appropriate security measures. Consult your legal department for an assessment specific to your organisation.

### How long should records be kept?

There is no single period. KVKK takes as its basis the period laid down in the relevant legislation or needed for the purpose. Write the period into your retention and destruction policy; under the regulation, the periodic destruction interval may not exceed six months.

### Does BosNets take the place of radio?

No, it complements radio. Radio carries voice instantly; BosNets carries written messages, location and task information, and keeps a record of them.

## Sources

- [Regulation on Disaster and Emergency Response Services (Official Gazette of Türkiye, 18 December 2013, No. 28855), in Turkish](https://mevzuat.gov.tr/MevzuatMetin/3.5.20135703.pdf)
- [Occupational Health and Safety Law No. 6331, in Turkish](https://www.mevzuat.gov.tr/mevzuatmetin/1.5.6331.pdf)
- [Personal Data Protection Law No. 6698 (Official Gazette of Türkiye, 7 April 2016, No. 29677), in Turkish](https://www.mevzuat.gov.tr/mevzuatmetin/1.5.6698.pdf)
- [Regulation on the Erasure, Destruction or Anonymisation of Personal Data (Official Gazette of Türkiye, 28 October 2017, No. 30224), in Turkish](https://www.kvkk.gov.tr/Icerik/5441/KISISEL-VERILERIN-SILINMESI-YOK-EDILMESI-VEYA-ANONIM-HALE-GETIRILMESI-HAKKINDA-YONETMELIK)
- [FEMA / U.S. Fire Administration: Activity Log (ICS 214), completed example](https://www.usfa.fema.gov/downloads/pdf/covid19/ics_form_214_example_covid19.pdf)
- [World Health Organization: Guidance for after action review (AAR), 2019](https://www.who.int/publications/i/item/WHO-WHE-CPI-2019.4)

- Operation Logging
- Activity Log
- Data Protection
- Field Operations

## Related pages

- [BosLog management interface](/en/boslog)
- [Communication for field operations](/en/operational-communication)
- [Communication in Crisis Management: A Guide](/en/blog/crisis-management-communication)
- [How to Choose a Mobile Field Communication App](/en/blog/mobile-field-communication-app)

## Let’s plan your operation log together

Let’s talk about which data should be recorded in your field operations, and how, and plan a demo together.

[Get in Touch](/en/contact)
[All posts](/en/blog/)