> 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/getting-started/quickstart.md).

# Quickstart

This page walks you through launching Taskmaverick from scratch. By the end, your team will have Missions appearing on their mobile devices.

***

## How Taskmaverick works

You set up everything on the **web**. Your team completes work on the **mobile app**.

The majority of flows in Taskmaverick revolves around **Missions** — structured tasks that appear on employees' mobile boards at the time you choose. A Mission can be a simple instruction, a checklist, a survey, a training video, a scored test, or an automated alert.

<figure><img src="https://3187329355-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLLw6mmkCzf1jpC9LdKjS%2Fuploads%2FtdorsgHlmSZdsCZ06WSr%2Fhow%20it%20works.jpg?alt=media&amp;token=d519f581-60a5-458b-8823-73ccfbfc899f" alt=""><figcaption></figcaption></figure>

***

## Step 1 — Build your organization

Before creating Missions, tell Taskmaverick who your people are, where they work, and how they're organized.

**Do this in order:**

{% stepper %}
{% step %}

#### Create [<mark style="color:$primary;">Position</mark>](/your-organization/people/positions.md)

Job titles in your company (Chef, Receptionist, Nurse).\
Go to People → Positions
{% endstep %}

{% step %}

#### Create [<mark style="color:$primary;">Units</mark>](/your-organization/units.md)

Your physical locations (Store #12, Downtown Hotel, Warehouse A).\
Go to Units → New Unit
{% endstep %}

{% step %}

#### Create [<mark style="color:$primary;">Team</mark>](/your-organization/teams.md)

Working groups within each location (Kitchen Team, Front Desk, Housekeeping).\
Go to Teams → New Team
{% endstep %}

{% step %}

#### Add [<mark style="color:$primary;">People</mark>](/your-organization/people.md)

Your employees. Assign each person a role, a unit, and a team.\
Go to People → New Person
{% endstep %}
{% endstepper %}

Each person gets login credentials and a [Personal Code](/your-organization/people.md#personal-code) — a 6-digit PIN they'll use to verify actions on mobile.

***

## Step 2 — Create your first Mission

Go to **Missions → In Library → New Mission**.

Pick the type that matches your goal:

<table><thead><tr><th>I want to...</th><th width="137.6666259765625">Choose</th><th>Example</th></tr></thead><tbody><tr><td>Give a simple instruction</td><td>Task</td><td>"Restock paper towels"</td></tr><tr><td>Ask employees questions</td><td>Survey</td><td>"Rate today's team meeting"</td></tr><tr><td>Run an inspection with checkpoints</td><td>Checklist</td><td>"Kitchen closing checklist"</td></tr><tr><td>Deliver training content</td><td>Media</td><td>"New menu walkthrough (video)"</td></tr><tr><td>Test knowledge with scoring</td><td>Test</td><td>"Food safety certification"</td></tr><tr><td>Score a compliance check</td><td>Audit</td><td>"Monthly health &#x26; safety audit"</td></tr></tbody></table>

Fill in the **Title**, **Guide** (short instructions for employees).

Then **Publish** the Mission.

{% hint style="info" %}
**Shortcut:** Instead of building from scratch, import ready-made templates from the Marketplace.
{% endhint %}

[Full guide: Build a Mission](/missions/how-to-guides/build-a-mission.md)

***

## Step 3 — Schedule it

A published Mission won't appear on anyone's device until you schedule it.

Click **Assign** on your Mission:

* **Post to Team Board** → select a unit and team → set start date, time, and repeat pattern
* **Assign to Personal Board** → select specific people → same scheduling options

**Example:** "Kitchen Closing Checklist" → Post to Team Board → Unit: Downtown Restaurant → Team: Kitchen → Every day at 9 PM.

[Full guide: Schedule a Mission](/missions/how-to-guides/schedule-a-mission.md)

***

## Step 4 — Employees complete work on mobile

Your team downloads the Taskmaverick app, signs in, and sees their boards:

* **Personal Board** — Missions assigned to them individually
* **Team Board** — shared Missions anyone on the team can claim (Open → Claimed → Closed)
* **Ticket Board** — automated alerts when something needs attention

An employee taps a Mission, enters their Personal Code, claims it, works through it, and closes it. Done.

[Full guide: Your Mobile Boards](/mobile-app/your-mobile-boards.md) · [Complete a Mission](/mobile-app/perform-a-mission.md)

***

## What to do next

You've got the basics running. Here's where to go deeper:

| When you want to...                                  | Read                                                                                                   |
| ---------------------------------------------------- | ------------------------------------------------------------------------------------------------------ |
| Fine-tune how Missions behave on mobile              | [Mission Settings](/missions/how-to-guides/configure-mission-settings.md)                              |
| Automate multi-step workflows                        | [What are Processes?](/processes/what-are-processes.md)                                                |
| Share a Mission with customers or guests via QR code | [Sharing Missions with External Users](/missions/how-to-guides/share-a-mission-with-external-users.md) |
| Tag questions and calculate inventory totals         | [Labels](/missions/how-to-guides/tag-questions.md)                                                     |
| See what's happening across your organization        | [Understanding Your Data](/analytics-and-monitoring/understanding-your-data.md)                        |
| Build custom reports for leadership                  | [Build a Report](/analytics-and-monitoring/reporting/build-a-report.md)                                |
| Configure SSO, integrations, or billing              | [Organization Settings](/your-organization/organization-settings.md)                                   |

***

## Key terms

<table><thead><tr><th width="187.3333740234375">Term</th><th>What it means</th></tr></thead><tbody><tr><td><strong>Mission</strong></td><td>A structured task — instructions, questions, training, or alerts</td></tr><tr><td><strong>Board</strong></td><td>Where Missions appear on mobile (Personal, Team, or Ticket)</td></tr><tr><td><strong>Unit</strong></td><td>A physical location</td></tr><tr><td><strong>Team</strong></td><td>A working group within a unit</td></tr><tr><td><strong>Schedule</strong></td><td>When and how often a Mission appears</td></tr><tr><td><strong>Ticket</strong></td><td>An automatic alert triggered by a condition</td></tr><tr><td><strong>Process</strong></td><td>An automated workflow chaining Missions together</td></tr><tr><td><strong>Personal Code</strong></td><td>6-digit PIN for verifying actions on mobile</td></tr><tr><td><strong>Global</strong></td><td>Mission goes to Personal Boards</td></tr><tr><td><strong>Non-Global</strong></td><td>Mission goes to Team Boards</td></tr></tbody></table>

***

## Roles

| Role                     | Access                              | Typical person              |
| ------------------------ | ----------------------------------- | --------------------------- |
| **System Admin**         | Full access — web and mobile        | Owner, IT Lead              |
| **Organization Manager** | Schedule and deploy, view reports   | Supervisor, Department Head |
| **Employee**             | Mobile app only — complete Missions | Frontline staff             |

***


---

# 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/getting-started/quickstart.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.