Back to all articlesCustomer onboarding

Reset an onboarding plan after a milestone is missed

Alactic Editorial9 min read

Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.

The onboarding milestone is late, so the project owner moves the completion date. But the same specialist is still overbooked, the same approval is unresolved, and the remaining work is unchanged. The revised date describes a hope, not a different plan.

A useful reset establishes what is genuinely complete, rebuilds the dependency chain, reserves realistic capacity, and makes the scope trade-off explicit. The replacement date follows those decisions; it cannot substitute for them.

This guide starts after the delay's cause is known. It covers rebuilding the remaining plan, not root-cause diagnosis, initial estimation, or contractual remedies. The filled worksheet is also a reusable meeting structure: replace its entries with evidence from your own project.

1. Preserve the baseline before changing it

Keep the original milestones, scope, capacity assumptions, and acceptance criteria visible. Otherwise, the team cannot distinguish recovered progress from silently removed work.

Separate three things that often get mixed together:

  • Established cause: what prevented the missed milestone from being completed.
  • Current constraint: what limits recovery now, even if it did not cause the delay.
  • Recovery choice: what the team proposes to change.

For example, an unresolved data ownership decision might explain the missed milestone. Reduced specialist availability might constrain recovery. Deferring historical records might be the response. Changing the date without addressing all three leaves the plan fragile.

Keep the missed milestone's original due point and outstanding evidence visible. A draft awaiting approval is not an approved deliverable, even when most production work is finished.

2. Reconcile actual progress, not completion percentages

For each deliverable, ask what exists, who checked it, and whether downstream work can use it. Classify it as accepted, awaiting acceptance, unfinished, or requiring rework.

Accepted work stays complete unless the scope change invalidates it. Work awaiting acceptance needs a decision slot, not necessarily more production time. Unfinished work needs an owner and effort allowance. Rework needs its own allowance rather than disappearing inside an optimistic percentage.

Use observable completion conditions. “Import preparation complete” is ambiguous. “The operations owner approved the field map, and the test file matches it” gives both teams something to inspect.

Check whether completed supporting work survives the scope change. An export may remain reusable; training materials for two teams may need revision when only one team launches. Neither restarting everything nor treating everything as reusable produces a reliable remaining-work estimate.

3. Filled worksheet: original plan and current position

Fictional worked example: All roles, quantities, dates, and effort allowances below are hypothetical, not Alactic customer results. Days are project working days. This is a recommended operating practice, not a claim about software capabilities or automatic execution.

Worksheet A: baseline and delay

  • Outcome: operations staff can manage new enquiries in the agreed workflow, using checked records and a named support contact.
  • Original scope: two teams, 24 months of records, and a custom management report.
  • Original milestones: export accepted Day 5; mapping approved Day 10; import complete Day 12; validation and training complete Day 14; launch Day 15.
  • Original specialist capacity: four focused hours per working day.
  • Missed milestone: Day 10 mapping approval. Several source fields lacked an agreed business owner, preventing decisions about their treatment.
  • Recovery constraint: specialist availability is now two focused hours per day.
  • Reset meeting: Day 11, attended by the sponsor, operations owner, onboarding lead, and specialist.

Worksheet B: evidence at the reset

  • Accepted: readable source export; project-team workspace access checked.
  • Awaiting acceptance: draft mapping exists, but disputed fields remain unresolved. Mapping is not complete.
  • Not started: production import, final configuration, report preparation, validation, and training.
  • Rework: training agenda must reflect the proposed smaller release.
  • Decision authority: operations owner can resolve disputed fields. Required review slots have been requested but are not yet confirmed.

This separates useful progress from usable dependencies. The export can support recovery, but the unapproved mapping cannot yet support the production import.

4. Choose the outcome before promising the date

If capacity has fallen, preserving every deliverable and the deadline may be impossible. Present choices in terms of customer outcomes, not just internal tasks.

Worksheet C: options and approval state

  • Option A—retain full scope: keep both teams, all history, and the custom report. Estimate the additional work and confirm resources before offering a date. Day 20 is not supported for this option.
  • Option B—protect a usable first release: one team, 90 days of records, and a standard report. Defer the second team, older history, and custom report.
  • Option C—add help: assess whether an authorised additional specialist is available and whether tasks can be divided without excessive handover. No additional person is confirmed.
  • Recommendation: Option B, proposed at the Day 11 meeting. Sponsor approval and customer review-slot commitments remain outstanding.
  • Schedule status: Day 20 is provisional until written scope approval and review-slot confirmation arrive by the end of Day 11. It then remains conditional on the execution gates below.
  • Deferred work: onboarding lead prepares a separate phase proposal after first-release acceptance; no completion date is promised now.

Correct field handling, appropriate access, and acceptance remain required. Reducing historical coverage changes scope; skipping validation merely hides risk. If the sponsor rejects the smaller outcome, return to the alternatives rather than treating the recommendation as an agreed baseline.

5. Reconcile every deliverable with capacity

Build the schedule from prerequisites, including customer decisions. Explicitly budget apparently small deliverables: a standard report still needs preparation and verification.

Worksheet D: proposed remaining-work schedule

  • Days 12–13: mapping, four specialist hours. Operations owner provides two one-hour review sessions. Exit: approved reduced-scope mapping, including disputed fields.
  • Days 14–15: import, four specialist hours. Depends on mapping approval. Exit: agreed 90-day records imported and exceptions recorded.
  • Day 16: configuration and standard report, two specialist hours. Depends on the imported record structure. Allow one hour for first-team configuration and one hour to prepare the standard report against agreed fields, filters, and totals. Exit: workflow and report ready for validation.
  • Days 17–18: validation, four specialist hours. Allow three hours for records, access, and workflow tests, plus one hour for report verification. Exit: recorded test results, defect dispositions, and a training-readiness decision.
  • Day 19: bounded corrections and rechecks, two specialist hours. Reserved for defects that fit this allowance. It is not unlimited contingency.
  • Day 19: training, one hour. Onboarding lead teaches only if the readiness gate below passes. Customer team and operations owner attend.
  • Day 20: acceptance and launch decision. Operations owner reserves two hours before noon; onboarding lead coordinates. Launch requires the acceptance conditions to be met.

The specialist total is 4 + 4 + 2 + 4 + 2 = 16 hours, matching eight days at two hours per day. Report preparation and verification are included, not additional hidden work. The estimate has no spare specialist capacity beyond the bounded correction allowance.

The onboarding lead separately reserves one hour on Day 16 to revise training materials, one hour after the Day 18 readiness review to finalise them, one hour for Day 19 training, and two hours for Day 20 acceptance coordination. Routine status communication uses a separately protected coordination slot, not specialist time.

The operations owner needs six hours: two for mapping, one for the Day 18 readiness and defect review, one for training, and two for acceptance. Other trainees need the training hour. All commitments remain requested until confirmed.

Worksheet E: assumptions and acceptance conditions

  • Inputs: source structure stays stable after mapping approval; replacements require impact assessment.
  • Capacity: named specialist and lead slots remain protected.
  • Records and workflow: agreed sample records match approved mappings; test cases pass; assigned users can perform their tasks with appropriate access.
  • Standard report: agreed fields and filters are present, and totals reconcile to the agreed validation dataset. A mismatch is recorded as a defect, not ignored because the report is standard.
  • Release: no unresolved issue blocks the agreed first-team workflow or required report use; customer acceptance is recorded.

6. Gate training on a stable workflow

Training beside defect correction is safe only when corrections cannot invalidate what people are being taught. Hold the readiness review at the end of Day 18, after validation, before finalising materials.

  • Pass: the taught workflow and required report behaviour have passed validation. Remaining corrections do not change steps, permissions, field meanings, or report interpretation. The specialist and operations owner record that assessment; Day 19 training may proceed alongside those bounded corrections.
  • Fail: a correction changes the taught workflow, report behaviour, or training materials. Do not run the original session. The onboarding lead notifies the sponsor and trainees that Day 19 training and Day 20 acceptance are no longer supported.

On failure, use the Day 19 specialist allowance for correction and revalidation only if sufficient. The lead then estimates material revisions and secures fresh preparation, training, and customer acceptance slots in that order. Publish replacement dates only after those slots are confirmed. If correction exceeds two hours, secure additional specialist capacity too.

This fallback deliberately withdraws the unsupported date. The fully allocated schedule cannot absorb workflow-changing fixes, extra preparation, and unchanged acceptance timing by declaration.

7. Send a decision request that matches the approval state

The customer message must distinguish a recommended plan from an approved baseline. In this example, both scope approval and review commitments remain pending.

Worksheet F: reset message brief

  • Sender: onboarding lead.
  • Recipients: sponsor and operations owner; specialist copied.
  • Decision: approve Option B and confirm named review slots by the end of Day 11.
  • Next evidence update: mapping approval status at the end of Day 13.

Hypothetical customer message:

We missed Day 10 mapping approval because several field-ownership decisions were unresolved. The mapping remains unapproved, and the original Day 15 launch is no longer supported.

We recommend a first release for one team, covering 90 days of records and the standard report. The second team, older history, and custom report would move to a separately planned phase.

Day 20 is provisional. Please approve this scope and confirm the requested mapping, readiness-review, training, and acceptance slots by the end of Day 11. Our plan includes report preparation and verification within the reserved specialist capacity.

Training depends on the Day 18 readiness gate. If corrections change the workflow being taught, we will reschedule training and acceptance rather than teach an unstable process.

We will report mapping approval status at the end of Day 13. If a dependency or capacity assumption fails, we will present the impact and choices before confirming replacement dates.

8. Manage the recovery through evidence and triggers

At each update, report accepted outputs, unresolved decisions, remaining work, and capacity changes. A completion percentage cannot show which dependency is blocked.

  • No Day 11 approval or slot confirmation: keep the proposal unapproved and reassess resource reservations; do not announce Day 20 as committed.
  • No mapping approval by Day 13: mark import blocked and show the affected sequence before assuming downstream slots remain usable.
  • Capacity withdrawn: identify displaced tasks; do not assume overtime or substitute staff.
  • Defects exceed allowance: assess the unmet acceptance conditions and obtain a revised plan. Do not rename a blocker to preserve the date.
  • Acceptance withheld: record the unmet criterion, owner, and next review point. Training attendance is not acceptance.

The immediate next step is concrete: obtain the Day 11 decisions, then publish either the approved mapping or unresolved decisions with schedule impact by Day 13. That gives both teams evidence to act on, rather than another date to hope for.

Customer onboardingProject recoveryCapacity planning

Put the next conversation to work.

Explore Alactic Communications for WhatsApp conversations, campaigns and AI-assisted workflows. Choose the product and plan that fit your team.

Explore Communications