# A task

> The task screen shows the label of a task, its intake checklist, any request to you, the result of its audit, and the actions you can take.

Source: https://docs.horizon-audit.online/docs/dashboard/task

The task screen shows where one task stands and what it needs. It has the label of the task, the intake checklist, any request to you, and the result once the audit is published.

## The top of the screen

| Field  | What it shows                                                                                         |
| ------ | ----------------------------------------------------------------------------------------------------- |
| Path   | The place of the task in your archive.                                                                |
| Digest | The hash of the task's files as they were read.                                                       |
| Label  | Where the task stands. See [task states](/docs/reference/task-states).                                |
| Band   | The difficulty band, once the task has one. See [difficulty bands](/docs/reference/difficulty-bands). |

## The intake checklist

"Intake checklist" shows how the task stands against the intake standard. It names the version of the standard. While the task is held to the standard, it shows "Checking". After that, it lists every rule by its id, each with one result.

| Result      | What it means                                                            |
| ----------- | ------------------------------------------------------------------------ |
| Met         | The task meets the rule.                                                 |
| Missed      | The task does not meet the rule. The line beside it says what is needed. |
| Not reached | The task came back to you before this rule was checked.                  |
| In review   | An engineer is looking at this rule.                                     |

## A request: "Needs from you"

When the label is "Needs from you", the screen has a section with the same name. It has one line for each thing that is needed. How you answer depends on the request.

- **The environment build stopped at something outside the task's files.** Put it right, then choose "Check again". The same task is held to the intake standard again. The dashboard offers "Check again" only when every open request can be met in this way.
- **The task's files must change.** The screen says so. A changed task is sent as a new submission under a new collection name. You withdraw this one. See [fix and resubmit](/docs/guide/fix-and-resubmit).

A request never says how to change the task.

## Withdraw a task

Choose "Withdraw" to remove a task that has no published result. A dialog asks "Withdraw this task?". Choose "Withdraw" to confirm, or "Keep it" to go back. A withdrawn task is not audited, and this cannot be undone.

## The result

"Result" appears when the verdict is published. It shows the verdict, "Clean" or "Flawed", and the "Time taken".

| Section  | What it shows                                                                                                   |
| -------- | --------------------------------------------------------------------------------------------------------------- |
| Findings | One link for each finding. A finding gives the "Flaw location", "How we established it" and "What this is not". |
| Flags    | Everything worth a look. The screen says: "A flag does not decide the verdict."                                 |

In a finding, "Open the saved output" opens the output of the run that a step rests on. The saved outputs are the proof. See [read a verdict](/docs/guide/read-a-verdict).

A result is final for the task as it was audited. The digest at the top of the screen identifies those exact files.