> For the complete documentation index, see [llms.txt](https://documentation.taskmaverick.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.taskmaverick.com/analytics-and-monitoring/overview/review-mission-history.md).

# Review Mission History

The **History** view in Overview shows every Mission that has been **Closed** or **Canceled** — your complete audit trail of past work.

## Why use History?

Once a Mission is completed, it disappears from the [mobile board](/mobile-app/your-mobile-boards.md). But the data — who did it, when, how long it took, what they answered, what Tickets were triggered — lives on in History. This is where you go for post-mortem reviews, compliance checks, and performance analysis.

**Example:** A facility technician completed a repair checklist that triggered a critical-failure Ticket. Weeks later, management pulls up the original response in History — including photos and timestamps — to validate the escalation.

## How to use it

Go to **Overview → select a Board → History**.

### What you see

A detailed table with columns including:

<table><thead><tr><th width="166.6666259765625">Column</th><th>What it shows</th></tr></thead><tbody><tr><td><strong>Name</strong></td><td>Mission name</td></tr><tr><td><strong>Closed By</strong></td><td>Who completed it (or "Canceled")</td></tr><tr><td><strong>Opened At</strong></td><td>When the Mission was posted</td></tr><tr><td><strong>Open</strong></td><td>How long it sat in Open status</td></tr><tr><td><strong>Claimed</strong></td><td>How long the employee worked on it</td></tr><tr><td><strong>Duration</strong></td><td>Total time on the board</td></tr><tr><td><strong>Closed At</strong></td><td>Completion timestamp</td></tr><tr><td><strong>Rating</strong></td><td>Peer rating (if enabled)</td></tr><tr><td><strong>Reference</strong></td><td>Which reference unit (room, equipment, etc.)</td></tr></tbody></table>

Additional columns appear depending on the board type — [Ticket boards](/mobile-app/your-mobile-boards.md#ticket-board) show Source, Triggered By, and [Position](/your-organization/people/positions.md); [Process boards](/processes/how-to-guides/monitor-processes.md) show [Level, Trigger Type, and Activities](/processes/what-are-processes.md#key-concepts) completion percentage.

### Sidebar details

Click any Mission row to open the sidebar with tabs:

<table><thead><tr><th width="192.6666259765625">Tab</th><th>What it contains</th></tr></thead><tbody><tr><td><strong>Response</strong></td><td>All submitted answers, photos, videos — the full record of what the employee provided</td></tr><tr><td><strong>Info</strong></td><td>Basic metadata: board, type, closed by, timestamps. For Tickets: the full Ticket Trail</td></tr><tr><td><strong>Content</strong></td><td>Mission structure and content as configured</td></tr><tr><td><a href="/missions/how-to-guides/tag-questions.md"><strong>Labels</strong></a></td><td>Label totals (if Labels were used)</td></tr></tbody></table>

## Good to know

* History is **read-only** — you can view and export, but not edit past data
* Data can be grouped by Mission, Unit, Team, or Person
* All data can be [**exported to Excel**](/missions/how-to-guides/export-data.md)


---

# 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://documentation.taskmaverick.com/analytics-and-monitoring/overview/review-mission-history.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.