---
key: record-field-work-on-an-asset
title: Record field work on an asset
audience: staff
section: operational-assets
routes: ["/assets/field"]
permissions: ["assets.records.read"]
features: ["operations.assets"]
since: 0.0.1
updated: 0.0.1
status: published
summary: From the technician screen, run an inspection checklist, report a problem, log service or a meter reading, upload proof, and sign a van or kit in or out.
keywords: [inspection, checklist, report a problem, odometer, hours, meter reading, upload photo, certificate, custody, sign out a truck]
related: [scan-an-asset-in-the-field, check-which-assets-are-ready-to-dispatch, find-an-operational-asset, let-a-blocked-asset-go-out-with-a-readiness-override]
---

In the sidebar, open **Equipment & Fleet**, then **Field Scan**. The page address is `/assets/field`. Open an asset first ([[scan-an-asset-in-the-field]]); each button on its card opens one panel.

## Before you start

- Each panel has its own permission; without it you see a note such as **Checklist permission required**. The standard Technician role cannot record here.
- A green message means Nova took the action; a refused one then moves to **Conflicts**.

## Steps

1. To run an inspection, press **Checklist**. Under **Field Checklist Completion**, choose a **Template** or keep **Manual field checklist**, and add a **Summary**. With a template, answer each item (**Pass** or **Fail**, a number, or text); required items must be answered. With the manual checklist, set **Passed** and **Blocks operation**. Press **Submit checklist**.
2. To report a problem, press **Issue**. Under **Field Issue Reporting**, type a **Title** such as "Hydraulic leak", choose a **Severity** (**Warning** or **Blocking**), set **Blocks operation**, add a **Description** and press **Report issue**.
3. To log service, a restock or a charge, press **Service** (**Restock** and **Charge** in **Field quick actions** open it filled in). Pick a **Service program**, or keep **Manual service capture** and choose a **Manual action type**. Set the **Outcome**, write a **Summary**, add a **Meter type** and **Meter reading** if you took one (a meter-based program needs one), then press **Submit service event**.
4. To log a meter reading, press **Meter**. Under **Field Meter Capture**, **Meter type** starts as odometer; change it to the meter you read, spelled as it is set up for the asset (for example hours). Enter the **Reading value**, optionally the **Reading unit** (mi or km for an odometer), and press **Submit meter reading**. A reading lower than an earlier one is refused.
5. To upload proof or a certificate, press **Document**. Under **Field Evidence Capture**, enter a **Title**, choose a **Document type**, set **Severity** and, if it runs out, **Expiry**. Leave **Requirement code** and **Requirement label** empty unless your office gave you one. Choose the photo or PDF under **Evidence file** and press **Submit document**. Offline, the file uploads when you reconnect.
6. To sign the asset out to yourself, press **Custody**, then **Take custody**. Press **End custody** when you hand it back; only the person holding it sees that button.

## What you see

- A **Blocks operation** checklist, a failed item the template marks as blocking, or an issue with **Blocking** severity or **Blocks operation** set to **Yes** stops the asset being dispatched. A blocking issue stays that way until it is closed or someone overrides it ([[let-a-blocked-asset-go-out-with-a-readiness-override]]).
- A document counts once someone verifies it on the asset's page. Until then the asset shows a warning, or is blocked if you chose **Blocking**.
- **Contents** opens **Contents And Transfer**. Find parts with **Asset search**; **Replace contained asset** swaps one, **Transfer contained asset** moves one to a **Destination container**.
- **Supplies** opens **Supply Requirement View**: what should be stocked and what is short.

## If something looks different

- "Meter type and reading value are required." or "Document title is required.": fill in what it names. Nothing was sent.
- **Conflicts** goes up: open **Queue** and read the reason, such as "Meter reading is lower than an earlier recorded value.", "title is required" (an issue sent without a **Title**) or "Version mismatch. Refresh and retry." (someone changed the asset first). **Retry** resends the same thing, so fix the cause first or **Dismiss** it and redo it.
- **Take custody** refused with "Asset is not dispatch-eligible for this workflow." or "Asset already has an active or pending assignment.": it is blocked or already signed out.
- "This custody record can only be ended by an authorized operator using the current assignment version.": someone else holds the asset, or your role cannot end custody.

[[route:/assets/field|Open Asset Field]]