> For the complete documentation index, see [llms.txt](https://help.fielddoc.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.fielddoc.org/essentials/activities/general-settings/inspection-log.md).

# Inspection Log

<figure><img src="/files/eKRnM1fcrFnVt2sFhMS8" alt="" width="563"><figcaption></figcaption></figure>

IN THIS ARTICLE

What happens once a restoration or conservation activity is completed? It's time to monitor it's impact. Use **Inspection Logs** to track visits to the activity site and share observations of the functionality.

***

## Inspection Logs

Once your restoration or conservation activity is installed to specification, the next critical step is to monitor its ongoing impact. Completing the implementation phase doesn't mean that the work is done - in fact, it marks the beginning of long-term observation and stewardship.

The FieldDoc **Inspection Logs** feature allows the owners of the activity records to systematically track site visits and document post-implementation conditions. This is especially important for ensuring that Best Management Practices (BMPs) are functioning as intended and that any issues are detected early.

## Step-by-Step Instructions

1. Open the **Inspection Log** view within the **Edit Activity** modal.
2. Select '**+ Add inspection report**\`.&#x20;
3. Enter in the date of the inspection.
4. Select if the BMP was functioning, or not functioning.
5. Type in additional notes.
6. Click Save.

The system will log the user who entered the report as "attested by", this is not an editable field.&#x20;

If you have additional documentation, such as photos or pdfs you can add those in the [Documents](/essentials/documents.md) and [Images](/essentials/images.md) tabs within the activity record.

You can add as many inspection reports as you would like to each activity record.

## Dig in! Interactive  Tutorial

{% @arcade/embed flowId="Z1sBzs3pVo98AKNORspp" url="<https://app.arcade.software/share/Z1sBzs3pVo98AKNORspp>" %}


---

# 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://help.fielddoc.org/essentials/activities/general-settings/inspection-log.md?ask=<question>&goal=<endgoal>
```

`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.