> For the complete documentation index, see [llms.txt](https://help.tahua.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.tahua.io/product-news/2026/readme/add-assessment-status-field-to-the-application-report-data-source.md).

# Add Assessment Status field to the application report data source

A new "Assessment Status" field is now available when building reports from the application data source. This field summarises the overall assessment progress for each application based on its assigned assessments.

## Status values

* **Assessed** — at least one assessment has been completed
* **In Progress** — at least one assessment has been started but none are complete
* **Not Started** — no assessments have been started (or no assessors are assigned)

## How it works

The field aggregates all non-deleted assessments for each application and derives a single status value. It follows the same logic used in the admin assessment status display. Like other computed fields (Payment Status, Contract Status), the join is only included when the field is selected in the report, so there is no performance impact on reports that don't use it.


---

# 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.tahua.io/product-news/2026/readme/add-assessment-status-field-to-the-application-report-data-source.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.