Make office IT visible
Inventory devices and users, critical shares, responsible contacts and maintenance priorities.
Identify your critical service, acceptable downtime and recovery responsibilities together.

List the applications, files, users and connections that keep work moving. Two copies on the same storage may be affected by the same failure. Review not only job status but data-loss objectives, recovery time, access to backups and responsibility for testing.
These are illustrative scopes for an initial discussion, rather than claims about completed customer projects.
Inventory devices and users, critical shares, responsible contacts and maintenance priorities.
A test scope separated from production, selected data, acceptance criteria and outcome records.
Dependencies, version compatibility, a maintenance window, backup and rollback options.
RPO describes acceptable data loss; RTO describes a target time to restore a service. A package does not automatically guarantee either objective. They need consideration alongside dependencies, budget and testing.
Mark the information you have ready, then prepare the gaps as a WhatsApp enquiry summary.
Open the infrastructure checklistBring the job result, affected objects and last usable recovery point into one incident record.
Read the guideAssess backup success against the business targets for recovering data and usable applications.
Read the guideAssess temporary rollback points separately from independent protection and capacity planning.
Read the guideConnect the device list to ownership, business dependencies and maintenance decisions.
Read the guideFirst, clarify the issue, the data and the scope.
The draft includes the summary and recent messages. Download and attach the transcript for the complete long conversation.