Identify what the business needs to keep operating.

A considered approach to business continuity.

Understand the services, information, people and premises on which critical work depends. Use that view to agree recovery priorities and practical alternatives.

A connected solution should begin with a defined business outcome. Explain what is difficult today, what needs to work differently and which teams will be affected. This makes it easier to distinguish a technology requirement from an administrative or workplace task.

An initial conversation is also a chance to identify existing arrangements that should be retained. The business may already have an internal team, a software provider, an accountant or a facilities contact. The proposed work should fit around those responsibilities rather than assume they do not exist.

Define the boundaries before delivery.

Agree the scope, the people who can authorise decisions and the practical information needed to begin. Explain any important deadlines, access restrictions or dependencies on other providers. If an assumption is uncertain, make it visible so it can be resolved before it affects delivery.

• What specific activity or outcome does the requirement concern?
• Who owns the information, premises or systems involved?
• Which decisions need approval, and who can provide it?
• What documents, access arrangements or specialist advice are needed?
• How will completion, exceptions and follow-up be discussed?

The proposal should explain which division is involved in each part of the work. An integrated engagement is easier to manage when deliverables and handovers are explicit. Any additional service should be discussed before the scope changes.

Keep the result reviewable.

Use the agreed scope as the basis for reviewing the work. Discuss what has been completed, what information is being handed over and who takes responsibility for any continuing activity. If further work is useful, describe it as a new or revised requirement.

Before sending documents, ask how information should be shared. An initial enquiry should explain the requirement without including passwords, identity documents or confidential employee and financial records. Appropriate handling can be discussed once the scope is understood.