> 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/tracking-and-rewarding-work-quality.md). # Tracking and Rewarding Work Quality These settings help you measure how well work is done, motivate employees through rewards, and automatically escalate quality issues to management. 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. *** ## Rating After a Mission is completed, team members can **rate the quality of work** on a scale of 1 to 5. Ratings feed into a calculated [**Work Quality**](/analytics-and-monitoring/reporting/report-sections-at-a-glance.md#performance-report) metric for each employee. ### Why use Rating? Managers can't personally inspect every completed task. Rating turns the team into quality reviewers — peers who work alongside each other and can verify whether the job was done properly. It's built-in quality control without extra management overhead. **Example:** A manager creates "Wipe the Glass Display" and enables Rating with a period of "Until Next Occurrence." John closes the Mission at 8:30 AM. His teammates Samantha (rated 4), Rick (rated 5), and July (rated 4), check the display and submit their ratings. The manager sees the average score on the web — no need to inspect in person. ### How to set it up 1. Open a Mission (Task, Checklist, or Ticket) → **Settings** 2. Enable **Rating** 3. Set the **Rating Period** — how long ratings are accepted after the Mission is closed: * **6 hours** * **12 hours** * **Until Next Occurrence** — ratings stay open until the same Mission appears again on the board 4. Save ### How it works on mobile After a Mission is [closed](/mobile-app/perform-a-mission.md#close-a-mission), a **Rate** icon appears on the Mission card in the Closed column Any team member can tap it, enter their Personal Code, and submit a rating (1–5) The card shows the initials of everyone who has rated ### Limits and rules * Available for [Task](/missions/what-are-missions/task.md), [Checklist](/missions/what-are-missions/checklist.md), and [Ticket](/missions/what-are-missions/ticket.md) only * The employee who completed the Mission **can also rate themselves** * Only peers from the **same** [**Team**](/your-organization/teams.md) can rate * [Personal Code](/your-organization/people.md#personal-code) is required for every rating to verify permissions *** ## Ticket on Rating Automatically triggers a [Ticket](/missions/what-are-missions/ticket.md) alert when a Mission receives a poor quality [rating](#rating) — so management is notified immediately when work quality drops. ### Why use Ticket on Rating? Rating alone collects data passively — someone has to review it. Ticket on Rating makes quality monitoring **active**: the moment a score drops below your threshold, management gets an alert they have to act on. **Example:** "Clean Glass Doors" has Ticket on Rating enabled. If any single rating is below 3, or if the average rating after the rating period falls below 4, a Ticket is sent to the manager's board: "Quality issue with Clean Glass Doors — John Smith, Team A." ### How to set it up 1. Enable **Rating** first (required prerequisite) 2. Enable **Ticket on Rating** 3. Set one or both thresholds: * **If Any Rating is below** — triggers on a single poor rating (values: 2, 3, 4, or 5) * **If Average Rating is below** — triggers after the rating period ends and the average is calculated (values: 1.25–5, in 0.25 steps) 4. Select the Ticket to trigger for each threshold 5. Save ### How it works on mobile The triggered Ticket appears on the [Ticket Board](/mobile-app/your-mobile-boards.md#ticket-board) showing: Mission name, which condition fired (single or average), who performed the Mission, and which board. ### Limits and rules * Requires **Rating** to be enabled first * "If Average Rating" is calculated only **after the Rating Period closes** * Available for the same Mission types as Rating *** ## Points Employees earn **reward points** (1–999) every time they complete a Mission. Points accumulate over time and can be exchanged for real rewards. ### Why use Points? Points turn Mission completion into a **motivation system**. Employees aren't just doing tasks — they're earning something tangible. Combined with management tracking in [Reporting](/analytics-and-monitoring/reporting/report-sections-at-a-glance.md#points-report), Points create a visible connection between effort and reward. **Example:** "Check Food Freshness" appears 4 times per day and is worth 20 Points each. An employee who completes all four earns 80 Points per day. At the end of the month, the company exchanges every 50 Points for an Amazon gift card. ### How to set it up 1. Open a Mission → **Settings** 2. Enter a value in the **Points** field (1–999) 3. Save ### How it works on mobile The Points value is displayed next to the Mission type on the Mission card and in Mission details. When an employee closes the Mission, the Points are added to their total. ### Tracking Points View each employee's accumulated Points in [**Reporting → Performance Report**](/analytics-and-monitoring/reporting/report-sections-at-a-glance.md#statistics-performance-and-points) on the web. ### Limits and rules * Available for **all Mission types** * Only whole numbers — no decimals or special characters * Maximum value is 999 *** --- # 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/tracking-and-rewarding-work-quality.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.