> For the complete documentation index, see [llms.txt](https://docs.cw.crisisworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cw.crisisworks.com/system-administration/configuring-the-system/imports/register-items/agvic-impact-assessment.md).

# Assessments (AgVic)

This page explains how to use the AgVic Impact Assessment import option. AgVic Impact Assessment V1 - comments only (match on address)

## Overview

The AgVic Impact Assessment is used by Victorian councils to add Agriculture Victoria comments into existing Recovery [Cases](broken://pages/Sfj9Pht3MY5OyzcTaJAs). This is used to help assess the extent to which farm/s have been impacted.

This is usually performed for a specific event.

Refer to the register page for general instructions:

{% content-ref url="/pages/QP6MVwI3qEAEvatbmPc3" %}
[Imports](/system-administration/configuring-the-system/imports.md)
{% endcontent-ref %}

### Considerations

When importing consider the following:

* **Code Field** - use this to match to the address an [Asset](broken://pages/eIC3EKq3W5hWtAu59Baw) (using a property number)

#### Categorisations

* **Event** - set this to the specific event you need to import to
* **Region** - set this to your council's region
* **Tag** - use an 'agvic' tag to keep track of comments from Agriculture Victoria

## Import File <a href="#instructions" id="instructions"></a>

A CSV format file is required with the correct field mappings.

Refer to the Import Field Mappings section in the [Import Instructions](/system-administration/configuring-the-system/imports.md#import-instructions) section for the latest import file requirements.

## Import Steps

To import the file:

1. Refer to the general instructions in [Imports](/system-administration/configuring-the-system/imports.md).
2. In the General section select **Type**: *Register Items*
3. For **Parsing Rule:** select *AgVic Impact Assessment V1 - comments only (match on address)*
   1. **Overwrite parser defaults** is usually set
   2. **Match Rule** is usually set to *Update only*
4. Under **Import File:** use the **Add file** button
5. Save and Check Results


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.cw.crisisworks.com/system-administration/configuring-the-system/imports/register-items/agvic-impact-assessment.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.