Checking the risk register for a prepared response to a resource being suddenly unavailable is a proactive action that the project manager should take to deal with the situation. The risk register is a document that records the identified risks, their causes, impacts, probabilities, and responses. By consulting the risk register, the project manager can see if there is a contingency plan or a fallback plan for the loss of a key resource, and implement it accordingly. Checking if the team member's activities are sufficiently documented to facilitate handover is another important action that the project manager should take to ensure the continuity and quality of the project work. The team member's activities may include tasks, deliverables, dependencies, assumptions, constraints, and other information that are relevant to the project scope, schedule, and cost. By reviewing the documentation, the project manager can identify the gaps, risks, and issues that may arise from the absence of the team member, and take appropriate measures to address them. References: (Professional in Business Analysis Reference Materials source and documents)
* PMBOK Guide, Seventh Edition, Section 11.4.3, "Risk Register"
* PMBOK Guide, Seventh Edition, Section 4.3.3, "Project Management Plan"
* Professional in Business Analysis (PMI-PBA) Guide, Section 4.2.2, "Documentation"