> For the complete documentation index, see [llms.txt](https://docs.navigaglobal.com/newsroom-planner/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.navigaglobal.com/newsroom-planner/master.md).
# What is Newsroom Planner?
Newsroom Planner is an editorial planning tool for the Newsroom, covering calendar events, planning of jobs as well as assignments to your staff. It's an integrated part of the Creation Tools.
## Overview
You have three different types of planning in Newsroom Planner.
1. **Events.** Let your teams manage, browser and search events, like press conferences, football games, concerts or other events. A calendar event covers all info you need about the event, like date and time, description, links, images, category and other tagging.
2. **Plans.** It's about story planning. When you decide to cover an event, you need an easy way to create, browse and filter your stories. A plan is like a folder for your content, with meta data, links and other info you need.
3. **Assignments.** Is a part of a planning , and is used to tell who is doing what and when. It's about resource planning.
These three components are interconnected. At an event you add a plan, on a plan you add assignments. Further on in this manual, this will become clearer. (If you do not want to add a plan to an event you do not have to, but an assignment always needs a connection to a plan.)
{% hint style="info" %}
This manual is done with a standard setup. It is possible to configure Newsroom Planner which means that your application can vary to some extent.
{% endhint %}
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.navigaglobal.com/newsroom-planner/master.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.