### Release Notes Most businesses are becoming tech companies where they have a software service that they provide to their customers. Software services do not get "turned off" at the end of the business day - customers expect 24/7 reliable availability. When things go wrong, you need a a team (or multiple!) that can quickly and effectively respond to service outages. Responding on-call is a stressful job. To manage stress and burn-out, most teams rotate this responsibility to help manage stress and burn-out. GitLab's **on-call schedule management** allows you and your team to create and manage schedules for on-call responsibilities. Alerts received in GitLab via a HTTP endpoint will be routed to the on-call engineer in the schedule for that specific project. https://docs.gitlab.com/ee/operations/incident_management/on_call_schedules.html  ### Problem to Solve Most businesses are becoming tech companies meaning they have a SaaS service that they provide to their customers. SaaS services do not get "turned off" at the end of the business day - customers expect 24/7 reliable availability. This means that when things go wrong, companies need to have a team (or multiple!) that can quickly and effectively respond to service outages. Being the person responsible for helping to restore service outage is being **on-call**. When a team member is on call, they need to be available around the clock. This is a stressful job. To manage stress and burn-out, most companies have a team of responders that take turns being on-call. This requires on-call calendar management tools that allow these teams to create and modify on-call schedules according to their specific rotations. **On-call Schedule Management** is a table-stake of an Incident Management tool. ### Intended users * [Delaney (Development Team Lead)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#delaney-development-team-lead) * [Rachel (Release Manager)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#rachel-release-manager) * [Allison (Application Ops)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#allison-application-ops) * [Dana (Data Analyst)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#dana-data-analyst) ### Further details This work supports the [Incident management](https://about.gitlab.com/direction/monitor/debugging_and_health/incident_management/) direction. ### Design  [Figma file](https://www.figma.com/file/gZF7Vvj1mmZGZFkV9wXTpY/Design-discovery-on-call-scheduling-gitlab-com-and-25995?node-id=372%3A28390) (On-call schedule MVC page) ### Scope of the MVC