Globalstrandtres Business Continuity Planning

Bălți · Republica Moldova

Engagement

How a continuity engagement proceeds from the first message to a plan you can maintain.

The path is the same whether the commissioned work is a business impact analysis, a full plan, or an exercise. Only the depth of each stage changes. There is no software onboarding and no obligation created by a briefing.

Initial contact

You write. We reply with fit, not a generic brochure.

Use the contact form or email info@globalstrandtres.com. Include the organization name, approximate size, sites if relevant, and the interruption that worries you most. If you already have a policy, IT recovery plan, or previous BCP, say so. The reply states whether Globalstrandtres can help, what information is needed next, and whether a short briefing call is useful.

We do not ask for payment at this stage. We do not add you to a marketing list. The enquiry is used to understand the work, as described in the Privacy Policy.

Discovery

The briefing establishes whether the work is a BIA, a plan, an exercise, or a program.

Discovery is a conversation with the person who will sponsor the work, sometimes joined by operations or IT. We ask how the organization makes money or delivers its mandate, which processes cannot pause, and what already exists on paper. You receive a written outline of recommended scope. You decide whether to proceed.

Preparation

Scope, access, and a working calendar are fixed before interviews start.

Preparation produces a short engagement note: functions and sites in scope, people to be interviewed, documents to share, expected deliverables, and a timetable. A single client counterpart is named so questions do not scatter. Confidentiality expectations are confirmed. Interviews are scheduled in blocks that operations can actually attend.

Workflow

Analysis and drafting run in visible cycles, not a long silence.

Interviews and document review come first. Findings are checked with owners before they harden into objectives. Strategies are chosen with the people who would have to execute them. Procedures are drafted in the client’s vocabulary. Each cycle has a review point so corrections happen while the work is still cheap to change. Remote workshops are the default; site time is used when premises and physical fallback matter.

Delivery

Handover is a working session, not a file transfer.

You receive the agreed documents in editable form, a walkthrough with owners, and a residual-risk note. If an exercise is in scope, it is run against the delivered plan rather than against an abstract scenario. Questions from the walkthrough are written back into the files before the engagement closes.

Communication

During the work there is one channel and a predictable rhythm.

Updates go to the named counterpart. Interview notes that contain operational detail stay within the engagement. We do not contact your staff without the counterpart’s agreement. If a workshop needs to move, it is moved; the calendar is a tool, not a performance target. English is the working language of this website and of the professional documents unless another language is agreed in writing.

Next steps

After delivery the organization owns the files. Further work is optional.

Typical next steps are an exercise if one was not included, a maintenance cadence, or an extension of scope to a site that was deliberately left out. None of these start automatically. If you want no further contact after handover, that instruction is respected.

See how the work is offered commercially and questions clients ask before commissioning.

The first useful artefact is a scoped briefing, not a finished plan.

Send the organization context and the interruption you want to be able to survive. We will answer with a proportionate path.

Start with contact