Checkpoint 1
Fit and boundary
Confirm the workflow, plan capacity, decision owners, accepted fields, excluded data, retention, and written acceptance checks.
Written scopeImplementation
Four checkpoints from fit to a dependable operating rhythm.
Published plans start without a software migration. We still treat definitions, ownership, safe input, module mapping, and acceptance as real implementation work.
Checkpoint 2
Field mapping
Map normalized project, task, and dependency CSVs to the published data profile. Resolve definitions before processing a live cycle.
Approved field mapCheckpoint 3
Dry run
Use a limited, buyer-reviewed sample to test rejects, rule explanations, output structure, and handoff responsibilities.
Accepted dry runCheckpoint 4
Operating cadence
Deliver the onboarding dependency control pack on the plan cadence, review exceptions, record corrections, and improve the mapping without changing scope silently.
Scheduled deliveryResponsibility matrix
No vague handoffs.
These roles may be held by the same person in a smaller team, but the decisions stay explicit.
Onboarding lead
Defines the standard journey and reviews cross-team blockers.
Workstream owner
Confirms task state and owns resolution.
Data owner
Provides the five-project normalized export.
Acceptance criteria
Done means reviewable, not merely delivered.
- All five projects use the same approved task and dependency mapping.
- Every blocker shows the supplied state and dependency rule.
- Missing data stays separate from inferred risk.
- The buyer reviews and sends every message or escalation.
A useful first conversation
Bring the current export and the person who owns the definitions.
Describe it in general terms. We will tell you which plan fits, what we would need, and where we would draw the line.