> ## Documentation Index
> Fetch the complete documentation index at: https://docs.levelset.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Debrief

> Close out each part of the day with a short debrief: who it goes to, when it is due, how to file it on the dashboard or in the Levelset app, and how to set your dayparts and questions

A **debrief** is the short form a leader fills in at the end of a **daypart**, one of the stretches a store's day is split into, such as Breakfast, Lunch, Snack and Dinner. It captures how that part of the day ran while it's fresh: what went well, what didn't, who stood out, and what to follow up on.

Debriefs are something Levelset turns on for your organization. Without them, **Debrief** is missing from **Scheduling** in the sidebar; ask Levelset support at [support@levelset.io](mailto:support@levelset.io).

## File a debrief on the dashboard

1. Open **Scheduling > Debrief**. It uses the store selected at the top of the sidebar.
2. Under **Which daypart is this debrief for?**, pick the daypart and the **Date**. It starts on the daypart happening now, the one that just ended, or the next one up.
3. Click **Start debrief** and answer the questions.
4. Click **Submit Debrief**.

Each daypart, area and date takes one debrief. Filing a second says **A debrief for this daypart, area, and date has already been submitted.** Each debrief belongs to one store day, which runs until 4 a.m. the next morning, store time. A debrief nobody files by then is closed as missed and can't be filed afterwards.

## File a debrief in the Levelset app

In the Levelset app, the phone and iPad app your team signs in to, the person a debrief is for gets a **Debrief** task on **Home** and a notification. The task opens 30 minutes before the daypart ends and is due when it ends. Anyone who can file a debrief can also start one from **+** > **Submit Debrief**. Until you set up your store's debrief (edit and save it, and choose who gets it), the app hides Debrief and says **Set up debriefs in the dashboard to use them here.**

## Who gets the debrief

Each daypart's debrief goes to:

1. The person placed in the **Responsible for shift** position on the [setup](https://docs.levelset.io/schedule/setups.md#define-the-positions-and-time-blocks) when the daypart ends, if their role includes Scheduling > Submit Debrief.
2. Where the setup has no responsible position, the people on the setup whose role is one of the daypart's **Roles that complete this**.

With neither, no debrief is created for that daypart, though anyone with Submit Debrief can still file one from the dashboard, or from **+** in the app once your store has set up its own debrief. So mark a **Responsible for shift** position on your setup templates, or pick roles on each daypart, for debriefs to reach anyone.

## Set your dayparts and questions

The dayparts and the questions are set on the debrief form: open **Workflows > Forms**, then the **Routines** tab, and click **Open debrief form** on the **Debriefs** row. The **Dayparts** section lists each daypart with:

* **Name**, for example Lunch.
* **Area**: **Combined** for one debrief for the whole store, or one debrief each for front and back of house.
* **Roles that complete this**, used only where the setup has no responsible position.
* **Active days**, the days of the week the daypart runs.
* **Start** and **End**, each a **Clock time**, or **Store open** or **Store close** with an **Offset (min)**, so Dinner can end an hour after close.

Click **Add daypart** to add one, and **Remove** to delete one. A new organization starts with Breakfast (open to 10:30), Lunch (10:30 to 2:00), Snack (2:00 to 5:00) and Dinner (5:00 to an hour after close), all Combined, every day, and with no roles picked.

Under **Questions** are the debrief's questions. Levelset's default debrief, **Shift Debrief**, asks for a shift summary, team member callouts, what went well, what didn't, action items and follow-ups, notable events, and the team's and the leader's stress from 1 to 10. Add, reorder or delete questions to fit your store. On the Deploy plan, the **Levi-guided** switch has Levi, the assistant built into Levelset, talk the leader through the questions and fill the answers; with it off, the same questions show as a plain form.

Every daypart needs the store's hours, which come from its Google Maps connection on [Store details](https://docs.levelset.io/organization/store-details.md): a store with no hours on record gets no debriefs at all. Without them the page says **This location has no business hours on record, so we can't tell which dayparts apply on any date.** A store also needs its time zone, which has no field: connecting the Google Maps listing sets one when none is set. If the page still says the time zone has not been set, contact Levelset support.

## Who can do what

| If you notice this | The permission behind it |
| - | - |
| **Debrief** is in the sidebar but the page says **Your role doesn't include Submit Debrief** | Scheduling > Submit Debrief |
| No **Submit Debrief** under **+** in the Levelset app | Scheduling > Submit Debrief, in an organization with debriefs and forms, and a store that has set up its own debrief (see [Who gets the debrief](#who-gets-the-debrief)) |

If you're missing something here, ask whoever manages roles in your organization to turn it on. See [Roles](https://docs.levelset.io/team/roles.md).

## Common questions

> **Nobody got a debrief task.**
>
> The store has no hours on record, so no daypart can be placed; connect its Google Maps listing on [Store details](https://docs.levelset.io/organization/store-details.md). Or the setup had no one in the **Responsible for shift** position when the daypart ended, and the daypart has no **Roles that complete this**: mark a responsible position on the setup template, or pick roles on the daypart.

> **The page says There is no debrief form configured for this organization yet.**
>
> Your organization has no debrief form. Ask Levelset support at [support@levelset.io](mailto:support@levelset.io).

> **No dayparts show for a date.**
>
> No daypart runs on that day of the week, or the store has no hours on record for it, which usually means it was closed. Pick another date, or check **Active days** on the debrief form.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.