> For the complete documentation index, see [llms.txt](https://support.incidents.cloud.solarwinds.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.incidents.cloud.solarwinds.com/schedules/schedules-new.md). # Schedules An **on-call rotation / schedule** is essential for effective incident management, ensuring trained personnel are always available to resolve issues. This involves setting clear schedules to distribute workload evenly, considering factors like time zones and expertise to prevent burnout. Utilizing automated tools like Squadcast helps manage complex rotations and escalation paths, ultimately reducing incident resolution times and maintaining service availability around the clock. *** **Best practices** are crucial for maximizing an on-call system's effectiveness. This includes establishing clear [escalation policies](https://support.squadcast.com/escalation-policies/create-and-manage-escalation-policies), thorough documentation for common issues, and regular training. Fostering continuous improvement, providing robust monitoring and alerting tools, and prioritizing engineers' well-being are key to a sustainable and efficient on-call program. *** The **advantages** of a well-executed on-call system like Squadcast, are significant. It guarantees **24/7 coverage** if needed, and rapid incident response, minimizing downtime and boosting customer satisfaction. This approach fosters shared responsibility within the team, improves knowledge sharing, and leads to a more resilient system. By proactively managing incidents, organizations can turn challenges into opportunities for system enhancement. --- # 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://support.incidents.cloud.solarwinds.com/schedules/schedules-new.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.