> For the complete documentation index, see [llms.txt](https://docs.eventication.com/event/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eventication.com/event/planning/dashboard.md). # Dashboard The planning **Dashboard** gives you a quick overview of how well your crew planning is filled. Instead of clicking through every station and substation to see who is scheduled, it adds up the whole picture for you: how many shifts and work hours are already assigned, and how many are still open. You will find it under **Planning → Dashboard**. It only shows the stations and substations you are allowed to see, so what you get depends on your moderator access. ### What the numbers mean Every job you plan on a station needs a certain number of people. The dashboard compares what you need with what is already filled in: * **Filled** — shifts that already have someone assigned to them. * **Needed** — how many are required in total. * **Open** — what is still left to fill. * **%** — how far along you are, as a percentage. The same comparison is shown two ways: by **number of shifts** and by **work hours**. Work hours are counted per person, so three people on a four‑hour job count as twelve filled hours. ### Different views You can look at the same planning from several angles using the tabs at the top: * **Dashboard** — the overall summary, broken down per station. * **Per station** — filled versus open, one row per station. * **Per substation** — the same, one row per substation. * **Per day** — how well each event day is filled. * **Per hour** — the busiest and quietest hours of a single day. A job counts towards every whole hour it overlaps, so a shift from 09:30 until 12:15 shows up in 09:00, 10:00, 11:00 and 12:00. You can narrow any of these views down to a single station or substation using the filters at the top. ### Members The **Members** tab flips the picture around and looks at your crew instead of your stations. It answers questions like: * How many hours is each member scheduled for? * Who signed up as available for a day but has not been given a shift yet? * How many people are scheduled for fewer than a certain number of hours? Because availability is not tied to a specific station, a station or substation filter will narrow the scheduled hours, but not the number of available members — someone is available for the whole event, not for one station. This makes it easy to spot members who are under‑used and days where you still have people available to fill your open shifts. Use the **filter** button on this page to narrow the numbers down to what you are planning for right now: * **Days** — the form opens with everything ticked, so you untick the days you are not interested in. Unticking a whole group counts the whole group again, which means your selection can never end up empty by accident. * **Substations** — grouped under their station. The station itself is not a filter of its own, so a station and a substation can never contradict each other. * **Fewer than this many work hours** — only show members below a certain number of scheduled hours. Leave it empty to show every member. * **Only show members that are available but have no shift at all** — the people you can still put to work. The chart stays on everybody in scope while the table below it is narrowed down to the members that match your filter, so you keep both the whole picture and your selection in view. --- # 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://docs.eventication.com/event/planning/dashboard.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.