> 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/user-guide/planning.md). # Planning By using planning in Newsroom Planner you get a good overview of your planning. You can easily see which plans do not yet have any assignments for and take action on that. In order to get an assignment done, a planning needs to be created. In Newsroom Planner you create plannings that appear in the plan calendar view. The planning may also be created in an event. On the planning you add assignments, such as an assignment for writing articles or taking photos. Below is a calendar view of your planning five days ahead. You get a good overview of how far one particular planning has come in the flow because it is enriched with information depending on how much work has been done. As we described earlier in this guide, the look of the cards (colors, icons, text) is depending on what settings the admin user has made in your organization. In this guide you will see the default setting. If you don't know the date of the plan when you add it, you can choose to make it undated. As soon as you want to plan it, you search for it among the undated plans and add the date. ![](https://content.gitbook.com/content/N4jAJdwyxhJ26rM91BZ7/blobs/4zdkEgmb6d4HkOomuQmx/Overview.png) --- # 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/user-guide/planning.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.