> 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/schedule-a-mission.md).

# Schedule a Mission

A Mission won't appear on anyone's mobile device until you schedule it. Scheduling tells the system *when* the Mission should appear, *where* it should land, and *how often* it should repeat.

This page covers all the ways to get Missions onto [employee boards](/mobile-app/your-mobile-boards.md) — including scheduled deployment, references, and on-demand triggering.

## Choose where the Mission goes

Every Mission is either **for** [**Teams**](/mobile-app/your-mobile-boards.md#team-board) **or** [**Personal**](/mobile-app/your-mobile-boards.md#personal-board) **execution.**

**Personal Missions examples:** "Submit weekly timesheet" · "Food Safety Training" · "Sexual Harassment Survey"

**Team Missions examples:** "Daily kitchen cleaning" · "Weekly inventory count" · "Shift handover checklist"

{% hint style="info" %}
[**Tickets**](/missions/what-are-missions/ticket.md) **cannot be scheduled** — they're triggered automatically by conditions in other missions.
{% endhint %}

## Three ways to assign (schedule)

<table><thead><tr><th width="293.333251953125">Action</th><th>What it does</th></tr></thead><tbody><tr><td><strong>Post to Team Board</strong></td><td>Creates a schedule on a team's shared board at a location</td></tr><tr><td><strong>Assign to People Directly</strong></td><td>Creates a schedule directly for specific employees</td></tr><tr><td><strong>Assign to People by Team</strong></td><td>Creates a schedule for specific employees in relation to the location they work in</td></tr></tbody></table>

## How to schedule

### On the web

{% stepper %}
{% step %}

#### Select a Published Mission

Missions -> In Library -> Click on a Mission.
{% endstep %}

{% step %}

#### Click Assign Mission

Click **Assign**.
{% endstep %}

{% step %}

#### Select assignment type

Select: Post to Team, People Directly, or People by Team.
{% endstep %}

{% step %}

#### Select the destination

Select the destination — [teams in units](/your-organization/teams.md#how-to-add-a-team-to-a-unit), or [specific people](/your-organization/people.md).
{% endstep %}

{% step %}

#### Set the schedule

<table><thead><tr><th width="223">Field</th><th>Options</th></tr></thead><tbody><tr><td><strong>Start date</strong></td><td>Any future date</td></tr><tr><td><strong>Repeat</strong></td><td>Never · Daily · Weekly · Monthly · Custom (every X weeks, specific days)</td></tr><tr><td><strong>Frequency</strong></td><td>Once per day · Time Period (every X hours) · At specific times</td></tr><tr><td><strong>End date</strong></td><td>A specific date, or Indefinitely</td></tr><tr><td><strong>Based on Previous</strong></td><td>Next Mission appears only after the previous one is closed</td></tr></tbody></table>
{% endstep %}

{% step %}

#### Confirm

Apply the schedule.

You can schedule to **multiple teams or people at once** — no need to repeat the setup.
{% endstep %}
{% endstepper %}

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLLw6mmkCzf1jpC9LdKjS%2Fuploads%2FgubNrH17VVDYGJSd4K02%2FSchedule%20a%20Mission.gif?alt=media&token=4431f556-e4a9-4771-81a0-e30edf9fa3a2>" %}

### On mobile

Admins can schedule from the mobile Mission Library: select a Published Mission → **Assign** → choose action → set destination and schedule → **Confirm**.

## Good to know

* Each Mission can have **one schedule at a time** — creating a new one replaces the old
* Only [**Published** Missions](/missions/how-to-guides/publish-a-mission.md) can be scheduled
* Schedules can only be set for **future dates**
* A Mission's **deployment status** shows **Idle** (not scheduled) or **Active** (has a schedule)
* You can stop or edit schedules from the **Deployed tab** in the [Team Library or Organization Library](/missions/where-to-find-your-missions.md) sidebar
* When using **Based on Previous**, the next Mission won't appear until the previous one is closed — useful for tasks that must happen in sequence
* If a **schedule conflict** exists (same Mission already scheduled for the same team/person), the system warns you and lets you compare the old and new schedules before overwriting


---

# 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/schedule-a-mission.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.