> ## Documentation Index
> Fetch the complete documentation index at: https://docs.agrihub360.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Applications Log

> Spray and fertiliser records in one place.

## What It Tells You

The **applications log** is what went on which field, at what rate, on which date. The rest of the app is built from it. The nutrient plan reads it to show what remains. The NVZ and Nmax checks read it to say whether the field is inside its limit. The SFI evidence and the spray log read it for the claim pack and the MAPP check. The models read it too. The [BYDV](/models/bydv) count restarts from the last aphicide in the log. The [nitrogen timing](/models/nitrogen-timing) model only knows what has been applied if it is recorded here.

## How It Works

Record each application in the field as you do it, with or without signal. An entry made offline is sent when the phone reconnects. Each spray product is checked against the MAPP register at entry. Its approval status is stored with the record.

<Frame caption="Each entry in the log has a date, a product and its check status.">
  <img src="https://mintcdn.com/agrihub360/wfAnTqlaZU94FIHH/images/guides/applications-log.svg?fit=max&auto=format&n=wfAnTqlaZU94FIHH&q=85&s=62197c2a718c04df0539814a14cb2d83" alt="A top-down field with a sprayer beside a list of log entries with date blocks, product bars and ticks." width="800" height="450" data-path="images/guides/applications-log.svg" />
</Frame>
