Loading content
On-call describes the structured rotation of responsibilities for operations teams to quickly detect, escalate, and remediate incidents. It includes scheduling, alerting, runbooks and post-incident reviews for continuous improvement. Well-designed on-call processes reduce downtime and distribute operational knowledge across the organization.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Theoretical construct: explains a term, principle, or mental model.
What you need to understand to reason about a domain.
On-call is an organized duty in which named people can respond to relevant incidents outside their regular working hours.
On-call duties grew in safety- and utility-critical settings where problems must be handled beyond office hours. Always-on online services carried the pattern into software teams, adding rotating schedules and escalation paths.
A baton moves between people according to a schedule: an alert reaches the responsible role, who assesses impact, stabilizes the service, and hands off or escalates when authority or expertise is insufficient.
A schedule distributes duty periods across several people predictably.
Defined paths bring in additional expertise or decision authority.
Documented steps support initial assessment and incident stabilization.
On-call creates clear response capacity for critical services. Fair schedules, realistic alert thresholds, recovery time, and time for root-cause work protect against overload and alert fatigue.
Where this building block is located in the topic model.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.