Business Continuity Planning NZ: A Practical Starting Point

If your usual workplace, internet connection or key business system became unavailable, which activities would you need to protect first? Business continuity planning starts with that question, rather than a shopping list of technology.

A useful plan records priorities, responsibilities and unresolved questions. It does not guarantee uninterrupted operations or replace professional advice about your particular risks.

Start with business priorities

Business.govt.nz’s continuity guide distinguishes continuity planning from emergency planning. Emergency arrangements address the immediate situation; continuity planning considers how essential business activities can continue or resume.

List the services or products your customers rely on. For each, note the people, premises, equipment, information and suppliers involved. Identify activities that could be paused while the team concentrates on essentials.

Use a simple worksheet with four columns: activity, dependency, responsible person and unanswered question. For example, a dependency might be access to the booking system. The question might be who can confirm the available options if that system cannot be used.

Keep assumptions visible. An alternative has not been confirmed merely because someone has suggested it.

Agree who makes decisions

The Wellington Region Emergency Management Office’s business continuity checklist includes essential roles, delegation of authority, contact information and practising the plan.

For your business, identify who coordinates decisions and who can act when that person is unavailable. Record who communicates with staff, customers and service providers. Check contact details rather than assuming an old supplier list is still accurate.

Decide how authorised people will find the plan when usual access is unavailable. Consider the sensitivity of information in it: a widely shared planning document is not an appropriate place for passwords or private customer records.

A short, understandable document with named responsibilities is a practical starting point. Leave unresolved responsibilities clearly marked rather than assigning them to a supplier without agreement.

Map technology dependencies

Use your worksheet to connect each priority activity with its technology dependencies. These may include internet access, phones, email, identity accounts, business applications and devices.

These are planning questions to discuss with the relevant provider:

• Which services depend on the same connection, location or account?
• What alternatives are actually included in the current service?
• Who is authorised to request a change or raise an incident?
• Which supplier dependencies could affect an alternative?
• What evidence would confirm that an agreed option works?

Avoid treating a second connection or a cloud subscription as proof of continuity. Ask your provider to assess the proposed arrangement and explain its limitations before relying on it.

Ask for backup and recovery evidence

NCSC’s backup guidance emphasises understanding business data, assigning ownership, setting recovery objectives and testing backups.

Ask your IT provider which important systems and data are covered, what is excluded, who reviews failures and when recovery was last tested. Request a plain-language summary of what the test demonstrated and any unresolved issues.

Discuss the business impact of unavailable or missing information before agreeing recovery objectives. A preferred recovery time is not a tested capability or contractual promise.

Technical recovery procedures need competent review for the actual environment. This article is a discussion guide, not instructions to restore systems, switch networks or change backup settings.

Rehearse decisions, then update the plan

Start with a discussion exercise, not an unapproved live outage. Choose a scenario, such as the usual workplace being unavailable, and ask the responsible people to explain their decisions.

Record missing information, unclear responsibilities and dependencies needing assessment. Give each follow-up an owner and review date. Distinguish discussion findings from evidence obtained through an authorised technical test.

Prepare your next conversation

Bring your priority worksheet and unresolved technology questions to a Bestcomm consultation. Discuss connectivity, communications and IT requirements, then confirm the proposed scope before agreeing any work.

Bestcomm’s emergency fibre/network response scope is Greater Auckland only. No response or recovery time is promised here.

Cover image is illustrative, not a Bestcomm customer project or recovery exercise.