> For the complete documentation index, see [llms.txt](https://docs.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verifone.com/verifone-central-device-management/verifone-central/asset-tracking/updating-the-file-chain-of-custody.md).
# Updating the File Chain of Custody
Use **File Chain of Custody** to update one device's custody details during asset tracking.
Use it to record a handoff, status change, location update, inspection result, or incident.
### Before you start
Confirm that you know:
* the target device and its current custody stage
* the status, location, or inspection details you need to record
* whether you need to add notes or upload supporting images
Prepare these details when available:
* device **Serial Number**
* current or new custodian
* current or new location
* expected status
* inspection notes and image files
### Open File Chain of Custody
{% stepper %}
{% step %}
### 1. Open the device from **View Devices**
Go to **Device Management** → **Devices** → **View Devices**.
Select the device you want to update.
{% endstep %}
{% step %}
### 2. Or open the device from **Chain of Custody**
Go to **Device Management** → **Reports** → **Chain of Custody**, search for the device, and open the record.
{% endstep %}
{% step %}
### 3. Open **File Chain of Custody**
From **Device Details**, select **File Chain of Custody**.
{% endstep %}
{% endstepper %}
{% hint style="info" %}
You can reach **Device Details** from either **View Devices** or **Chain of Custody**.
{% endhint %}
### Review the page sections
#### General Information
Use this section to confirm the record before you change anything.
These fields are informational:
* **Device Serial Number** — read-only
* **Device Tamper Label ID Number** — the tamper label on the device
* **Shipment Tracking Number** — populated during shipment from the Verifone store
#### Chain of Custody
Use this section to record the new custody state.
Select the status that matches the physical device state:
* **Awaiting deployment** — the device is received by a trusted custodian and stored securely, but not installed yet
* **Deployed** — the device is installed and actively used for payment transactions
* **In Repair** — the device has malfunctioned and has been sent to an authorized repair center
* **Malfunctioning** — the device has a fault, but it has not yet been shipped for repair
* **In-Transit** — the device is moving between approved locations
* **Retired** — the device is removed from service and will not return to operation
* **Lost or Stolen** — the device cannot be accounted for
* **Tampered** — the device or tamper-evident seal shows tamper evidence or a tamper message
You can also update:
* **Location** — choose the current approved location
* **Device Last Known Telemetry** — review the pre-populated previous custodian, location, and status values before saving
#### Device Inspection
Use this section when the custody event also needs an inspection record.
Inspection is typically recorded during:
* **In-Transit Inspection** — while the device is moving between locations
* **Periodic Inspection** — after the device is deployed and active
For inspection:
* answer **Yes** or **No** to whether the device shows no tamper or physical damage
* if the device passes inspection, record any relevant notes
* if the device does not pass inspection, answer the follow-up tamper and physical damage questions
Tamper review can include checks such as:
* a tamper message on the screen
* physical tamper on the device body
* cable or connection tamper
* damaged or tampered labels
Physical damage review can include checks such as:
* screws out of place
* discolored casing
* visible marks on the device
* signs of a skimmer or other theft device
If needed, upload supporting images in **png**, **jpg**, **jpeg**, or **gif** format and add details in **Notes**.
{% hint style="info" %}
Contact the **Solution Provider's Helpdesk** with the device serial number when you need to report an incident.
{% endhint %}
### Verify the result
After you save the update, confirm that:
* the status matches the physical device state
* the custodian and location values are correct
* inspection answers, notes, and images are complete when needed
* the record now supports the next action in the workflow
### Result
You can update one device's custody record with the status, location, inspection, and incident details needed for asset tracking.
### Next steps
* [View device status in Chain of Custody](/verifone-central-device-management/verifone-central/asset-tracking/view-device-status-in-chain-of-custody.md) — review the updated record
* [Configure locations](/verifone-central-device-management/verifone-central/asset-tracking/configure-locations.md) — maintain custody location values
* [Registering the device](/verifone-central-device-management/verifone-central/devices/registering-the-device.md) — continue after deployment
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.verifone.com/verifone-central-device-management/verifone-central/asset-tracking/updating-the-file-chain-of-custody.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.