Recovery scope follows the affected systems.

How much of the site is involved?

One affected installation, several sites sharing a hosting account and a custom application are different scopes. Identify the public sites and connected services that may be relevant, while keeping unverified assumptions separate from observed problems.

Which records and trusted copies are available?

Logs, version history, original software packages and known backup dates can help establish what changed. Missing information may require more investigation or limit what a reviewer can conclude.

Can a proposed backup be used?

The existence of an archive does not establish that it is suitable for restoration. Its contents, date and restore behavior need checking. Newer pages, accounts or orders also need consideration before an older version replaces the live one.

Who controls the surrounding systems?

The hosting provider, domain owner or software vendor may need to act on part of the recovery. An estimate should identify those dependencies and what can proceed while a decision is pending.

What does completion include?

Agree on the site checks, documentation and follow-up responsibility. A recovered website, an external provider review and longer-term monitoring are distinct pieces of work; the proposal should state which are included.

Describe the website and the incident to begin a scope discussion. No passwords or raw incident records are needed in the first inquiry.