Fixing the RTO at which each prioritized activity comes back at agreed capacity lets the organization pick strategies that cut the length of disruption, limit harm and allow a timely restart. Guidance: to bring prioritized activities back within their RTOs, also set matching RTOs for their dependencies and supporting resources and decide at what capacity each must return, weighing the option of offering a different service until fully restored; mobilizing staff effectively; helping and encouraging staff back to work; workarounds (manual working, for example) that postpone the need to restore a supporting resource; backlog and the time needed to recover lost information; and how complex and large the recovery is, or whether specialist equipment with long lead times is needed. Strategies can include moving the activity elsewhere within the organization or out to a third party, on its own initiative, by mutual aid or by agreement, considering damaged and intact alternative sites; moving or reassigning resources, staff included, to another site or activity; alternative processes and capacity, including spare or duplicate capacity in processes or stock; and workarounds or other ways of working that give acceptable results for a while, usually slower or more labour-hungry and so fit only for short spells or to delay the return to normal. Examples are spare production capacity at another site and remote working for key staff.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.