The six weeks

Six weeks. Four moves. One signature.

Six weeks when the data call comes back on time; eight when it does not. Each move has the sessions it needs, the people who must be in the room, and a checkpoint at its end; three of the four checkpoints are decision reviews with the sponsor in the room. The engagement ends with your signature on the plan and the record handed over.

1 2 3 4 YOU ARE HERE A PLAN YOU CAN RUN SIX WEEKS
Before week one

The data call

Issued to your project manager or data steward two weeks before week one: inventories, diagrams, procedures, existing security material, the contracts and plans you already have. Answering it is what makes six weeks possible instead of eight.

Data-call check-in
Move 1

Entry and authority

What the engagement is, what it produces, who signs. The authority path named, the boundary drawn, the system categorized.

Decision review · path and scope
Move 2

Operating model and assessment

Where you stand, read from evidence and confirmed with the people who own it. The read-out names what can be reused and what could block.

Checkpoint · assessment read-out
Move 3

Services, crossings, and the foundation design

What the provider or the enterprise delivers, what stays yours, the cadence and the evidence it produces, the onboarding gate, and the general support system decided.

Decision review · foundation package readiness
Move 4

Rehearsal, signature, handover

A table-top rehearsal of a normal change and a failed connection with both teams. Then the plan is signed, every deliverable accepted or declined against its criteria, and the record handed over.

Decision review · first-workload launch posture
Day two

Your team runs it

The record is yours. A retainer of checkpoints that read the record against the last one is available, never required. We do not prime multiyear operations.

Optional retainer
What we ask of you

Enough of your people, at the right moments, to make the plan yours.

The data call

Two weeks, through your approved channels, before week one.

Four named contacts

The mission owner who decides, a technical lead, a security or evidence owner, an operations or service owner.

Time in the room

Interviews and working sessions in each move; three decision reviews.

Decisions

Confirm the facts, resolve disagreements, accept or decline each deliverable against its criteria, sign at the end. Missing information stays visible; it is never painted over.

Handling

Protected material stays in your approved environment. Nothing on this site takes evidence.

Three decision reviews

The moments the sponsor is in the room.

Path and scope

The first move is a decision you can sustain: a chosen cloud path and a bounded start. Staying put, modernizing in place, or a smaller step can all be sound decisions.

Foundation package readiness

The boundary, categorization, inheritance, and evidence set are ready for the chain that decides them. Readiness, not a promised date.

First-workload launch posture

What can proceed, what must wait, and who decides, with the receiving team named before the move.

Every deliverable names the client role that owns it after handover. That is a scoping rule, applied when the work is designed, not a test applied months later.