> 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/missions/how-to-guides/configure-mission-settings/ensuring-work-gets-done-on-time.md).
# Ensuring Work Gets Done on Time
These settings help you prevent overdue Missions, alert managers when work is stuck, and keep teams focused on what's urgent.
All settings below are configured per Mission in [**Mission Settings**](/missions/how-to-guides/configure-mission-settings.md). They're all optional and off by default.
***
## Stopwatch
Color-codes the Mission timer on mobile so employees can see urgency at a glance — green means just posted, orange means pending, red means overdue.
### Why use Stopwatch?
Without visual urgency cues, all Missions look the same on the board. Employees don't know which ones need immediate attention. Stopwatch solves this by turning time into a color that's impossible to ignore.
**Example:** A hospital sets Stopwatch for cleaning checklists: green for the first hour (just assigned), orange after 1 hour (should be prioritized), red after 2 hours (overdue, needs immediate follow-up).
### How to set it up
1. Open a Mission → **Settings**
2. In **Stopwatch**, define the time thresholds for each color: green → orange → red
3. Save
### How it works on mobile
The Mission card and detail view show a timer that changes color as time passes. The countdown starts when the Mission is posted to the board.
### Limits and rules
* Color coding is **visual only** — it doesn't block employees from completing the Mission
* Works on both [**Personal, Ticket and Team Boards**](/mobile-app/your-mobile-boards.md)
* Each Mission can have its own thresholds, or inherit the organization-wide defaults
***
## Boost Mission on Timer
After a set time, automatically moves the Mission to the **top of the board** and highlights it in red - making it impossible to overlook.
### Why use Boost?
Stopwatch changes color, but the Mission stays in its position on the board. Boost goes further - it physically moves the Mission to the top of the list and marks it as high priority. For time-critical work, this ensures it's the first thing employees see.
### How to set it up
1. Open a Mission → **Settings**
2. Enable **Boost Mission on Timer**
3. Set the time (weeks, days, hours:minutes) after which the Mission should be boosted
4. Save
### How it works on mobile
When the timer threshold is reached, the Mission jumps to the top of the [Open ](/mobile-app/perform-a-mission.md)list and its timer turns red. Employees and managers can also **manually boost** any Mission from the board or [Overview](/analytics-and-monitoring/overview/track-running-missions.md#actions-you-can-take).
### Limits and rules
* Boosted Missions can be **reordered** or **unboosted** manually
* Applies to all Mission types
***
## Ticket on Timer
Automatically triggers a [Ticket](/missions/what-are-missions/ticket.md) alert to management if a Mission stays open or unclaimed for too long.
### Why use Ticket on Timer?
Stopwatch and Boost are visual cues for employees. Ticket on Timer goes a step further - it notifies **management** directly when work isn't getting done. The manager receives an actionable Ticket on their board, not just a color change they might miss.
**Example:** "Clean Coffee Machine" must be done by 8 AM. The manager sets Ticket on Timer with "If Not Closed Within = 45 minutes." At 7:45 AM, if the Mission is still open, a "Coffee Machine Alert" Ticket is triggered to the manager's board.
### How to set it up
1. Open a Mission → **Settings**
2. Enable **Ticket on Timer**
3. Set one or both conditions:
* **If Open Beyond** — how long a Mission can sit in Open before triggering
* **If Not Closed Within** — how long it can sit in Open OR Claimed before triggering
4. Select which Ticket to trigger
5. Save
### How it works on mobile
The triggered Ticket appears on the [Ticket Board](/mobile-app/your-mobile-boards.md#ticket-board) showing: the Ticket name, which condition fired, which Mission triggered it, which board it came from, and who (if anyone) had claimed it.
### Limits and rules
* Ticket on Timer can be added to **other Tickets** but never the same Ticket (no self-triggering)
* Applies to all Mission types
***
## Email Notification
Sends an email reminder to employees when a Mission sits on their board too long without being completed.
### Why use Email Notification?
Missions land on personal boards, and employees might not check their board regularly. Email reminds employees that something is waiting for them.
**Example:** A "COVID-19 Vaccination" survey is assigned to all employees. The admin sets Email Notification to fire after 3 hours. Every employee who hasn't completed it receives an email: "A new Mission appeared on your Personal Board 3 hours ago."
### How to set it up
1. Open a **Global** Mission → **Settings**
2. Enable **Notification**
3. Set one or both conditions:
* **If Open Beyond** — email when the Mission has been Open for this long
* **If Not Closed Within** — email when it hasn't been closed within this time
4. Save
### Limits and rules
* Available **for all Missions** (except Tickets)
* Email is sent to the address in the user's **Primary Email** field
* Each notification includes the Mission name, the trigger condition, and the organization name
***
## Auto-Bounce Back
If an employee claims a Mission but forgets to close it, Auto-Bounce Back automatically returns it to **Open** after a set time — so someone else can pick it up.
### Why use Auto-Bounce Back?
In Taskmaverick, only one instance of a Mission can be Open or Claimed at a time on a board. If someone claims a Mission and leaves without closing it, the board is **blocked** — no new instance can appear, and nobody else can do the work.
**Example:** A cleaning employee claims "Clean Kitchen" at the end of their shift but forgets to close it. The next day, the morning shift can't see the Mission on their board. With Auto-Bounce Back set to 2 hours, the Mission automatically returns to Open — unblocking the board.
### How to set it up
1. Open a Mission → **Settings**
2. Enable **Automatic Bounce Back**
3. Set the time (weeks, days, hours:minutes) after which the Mission should bounce back
4. Save
### How it works on mobile
Nothing visible to employees - the Mission simply reappears in the Open column after the threshold, and the previous assignee is removed.
### Limits and rules
* Bouncing back also **removes the assignee**, freeing the Mission for anyone to claim
---
# 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/missions/how-to-guides/configure-mission-settings/ensuring-work-gets-done-on-time.md?ask=&goal=
```
`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.