> 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/controlling-mission-execution.md).
# Controlling Mission Execution
These settings help you prevent rushed or delayed work, let employees trigger Missions on demand, and make training content accessible anytime.
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.
## Minimum Claimed Duration
Prevents employees from closing a Mission **too quickly** — a warning appears if they try to close before the minimum time has passed.
### Why use Minimum Claimed Duration?
Some tasks must take a certain amount of time to be done properly. A 30-minute break should actually last 30 minutes. A safety inspection shouldn't be "completed" in 60 seconds. This setting enforces a time floor.
**Example:** A company uses Taskmaverick to track employee breaks. A "Lunch Break" Task has Minimum Claimed Duration set to 30 minutes. If an employee tries to close it after 10 minutes, a warning modal appears reminding them the break should last at least 30 minutes.
### How to set it up
1. Open a Mission → **Settings**
2. Enable **Minimum Claimed Duration**
3. Enter the minimum time threshold
4. Save
### Limits and rules
* Applies to **all Mission types**
* The warning is informational — it does not physically block the employee from closing
## Claimed Duration
Monitors whether a Mission is completed **too quickly or too slowly** — and can automatically alert employees, trigger [Tickets](/missions/what-are-missions/ticket.md), or assign [follow-up training](/missions/what-are-missions/media.md).
### Why use Claimed Duration?
Minimum Claimed Duration only catches "too fast." Claimed Duration monitors both directions: if someone takes 10 minutes on a task that should take 30, or 2 hours on a task that should take 15 minutes, something is wrong. This setting catches both cases and can respond automatically.
**Example:** A cleaning checklist should take 20–40 minutes. The admin sets Short Claim at 10 minutes (suspiciously fast — probably not done properly) and Long Claim at 60 minutes (too slow — might need help). If the short threshold is hit, a training Media Mission is auto-assigned to the employee's personal board.
### How to set it up
1. Open a Mission → **Settings**
2. Enable **Claimed Duration**
3. Configure **Short Claim**, **Long Claim**, or both:
* Set the time threshold
* Choose a standard or custom alert message
* Optionally, trigger a **Ticket** and/or a **Media Mission** with their own time thresholds
4. Save
### How it works on mobile
After completing the Mission, a notification alert appears on the board showing the message — e.g. "This Mission should not be claimed less than 20 minutes."
### Limits and rules
* Applies to **all Mission types**
* When a Media Mission is triggered, it's posted to the [**Personal Board**](/mobile-app/your-mobile-boards.md#personal-board) of the employee who completed the Mission
## On Demand
Lets employees trigger a Mission outside its regular schedule — when the work needs to happen right now, without waiting.
### Why use On Demand?
Schedules cover routine work, but real life isn't always routine. Equipment breaks unexpectedly. A spill needs cleaning now, not in 2 hours. On Demand gives employees the power to pull the right Mission from a library and post it immediately — no need to call a manager or wait for the schedule.
**Example:** "Clean Coffee Machine" normally appears every 4 hours. On a busy Sunday morning, the barista needs it after just 2 hours. They open the On Demand library on mobile, select the Mission, and it appears on the board instantly.
### How to set it up
1. Open a Mission → **Settings**
2. Enable **On Demand**
3. Save
### Restricting access
Use **Available For** to control who can see the Mission in the On Demand library. You can restrict by [Team](/your-organization/teams.md) and/or [Group](/your-organization/groups.md).
**Example:** A "Driver Safety" Media Mission should only be available on demand to the Drivers Team — not visible to office staff.
### How it works on mobile
1. On any [Team or Personal Board](/mobile-app/your-mobile-boards.md) → tap **On Demand (+)** or use **Menu → Make Request**
2. Enter [Personal Code](/your-organization/people.md#personal-code)
3. Select the Mission from the available list
4. The Mission appears on the board immediately
### Limits and rules
* On a **Personal Board**, On Demand Missions go directly to **Claimed** status (skipping Open)
* On a **Team Board**, admins can choose **Post** or **Post and Boost** (high priority)
* Available for all types **except Tickets**
## Knowledge Base (Viewable in Mobile Library)
Makes [Media](/missions/what-are-missions/media.md) Mission content accessible anytime from a mobile Knowledge Base — employees can revisit training material without claiming or closing anything.
### Why use the Knowledge Base?
Scheduled training happens once. But employees often need to **review** material weeks later — a recipe they forgot, a procedure they're unsure about, a safety protocol they want to double-check. The Knowledge Base gives them permanent, self-service access.
**Example:** A "Crisis Management" media training is scheduled monthly. Two weeks after completing it, an employee wants to review the material. They open the Knowledge Base on their Personal Board and watch it again — no quiz, no claim, no reporting impact.
### How to set it up
1. Open a **Media** Mission → **Settings**
2. Enable **Viewable in Mobile Library**
3. Set **Available For** to control who can see it — restrict by [Team](/your-organization/teams.md), [Group](/your-organization/groups.md), or [Position](/your-organization/people/positions.md). "All" means no restrictions.
4. Save
### How employees access it
On mobile: Personal Board → menu → **Knowledge Base**. The employee sees a filterable list of available Media Missions and can open any of them.
### Limits and rules
* Available **only for Media Missions**
* [**Quizzes**](/missions/what-are-missions/media.md#how-to-create-a-media-mission) **are not included** in the Knowledge Base view — it's for reference only
* No reporting on how many times employees re-watch content
---
# 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/controlling-mission-execution.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.