> For the complete documentation index, see [llms.txt](https://help.besmart.software/be.smart-site-management/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.besmart.software/be.smart-site-management/site-management/markings/use-cases-for-markings.md). # Use-cases for markings ### Risk management When project has begun or is about to begin, risk management is one of most important tasks. Risk management is traditionally done document based, meaning that there is just text, maybe reference to a location. Site Management turns the mentality upside down, what if all the risks are fixed to a location or an area. Create a marking to a specific location by exact coordinates or draw an area to highlight the risk. Give the marking a title and more detailed description. The most important thing is to add a tag, for example “Risk”. Use the priorities etc., to further describe the risk. Once there are multiple markings, with a “Risk” -tag, there is a possibility to create a filter which only shows markings with “Risk” -tag. This leads to an easy and visual risk management tool. ### Site inspection Site inspections are done for example daily or weekly. The goal is to find possible areas that might cause issues and help plan ahead. Whether there is something blocking the next workphase or the detour for the site is not guided well enough. During the next site inspection open Site Management from a mobile device. While inspecting it is possible to create markings to correct locations, even add pictures to describe the issue. Allowing everyone within the site to see the possible issues. A transparent way of communicating what is happening on the site. --- # 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://help.besmart.software/be.smart-site-management/site-management/markings/use-cases-for-markings.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.