Handle new onboarding requests without silently changing the plan
Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.
A customer asks for another report during training. Someone agrees to clean an extra data file. A new team joins the implementation chat and requests its own workflow. Each request sounds reasonable, but the original completion date stays unchanged—even as the definition of finished expands.
To manage scope changes during customer onboarding, compare each request with the agreed outcome before accepting the work. Choose one of four dispositions: include it, substitute it for something else, defer it, or decline it. Then record the effect on milestones, the customer's decision, and the revised completion expectations in one visible log.
The goal is not to reject small requests. It is to stop a friendly acknowledgement from becoming an invisible commitment. A useful decision makes clear both what the team will do and what will no longer be true about the previous plan.
1. Establish the outcome against which requests will be judged
A task list alone is a weak scope boundary. It may say that configuration, import, and training are included without explaining which users, which data, or what those activities must accomplish. When a new request arrives, both sides can interpret the same list differently.
Before evaluating changes, write a short operational baseline containing:
- The onboarding outcome: what the customer should be able to do when implementation ends.
- The initial users and work: which team, workflow, and data set are included.
- Completion evidence: what observable demonstration or review establishes readiness.
- Milestones and dependencies: what happens when, and what each side must provide.
- Known exclusions: adjacent work that is not part of this onboarding phase.
A request to fix a configuration that prevents the agreed demonstration is different from a request to add another department. The first may be necessary to deliver the existing outcome; the second may create a new outcome.
If the baseline is missing, reconstruct it with the customer before making further promises. Mark unresolved assumptions explicitly. Do not retrospectively present an internal interpretation as something the customer already accepted.
2. Acknowledge the request without accepting it
Separate receipt from commitment. Anyone working with the customer can capture a request, but an acknowledgement should not imply that the team has accepted its effort, deadline, or completion criteria.
We have recorded the request. Before adding it to the onboarding plan, we will check what it changes and return with a recommendation. The current milestone remains the working plan until we agree an update.
Capture the requested result, not just the proposed feature. Ask what the customer cannot do today, who needs the change, and what would happen if it waited until after onboarding. A requested dashboard may actually be a need to verify ownership before training; a simpler review could meet that need.
Also distinguish a new request from a defect or a missed commitment. If the agreed workflow does not work as specified, do not automatically label the correction an enhancement. Investigate against the baseline and record the classification. That prevents scope control from becoming a way to avoid delivering the original outcome.
When the answer depends on an investigation, define a bounded assessment rather than accepting the whole change. Record who will investigate, what question they will answer, and when the decision will return to the customer.
3. Evaluate the consequences before choosing a disposition
For each request, test its relationship to the outcome and its effect on the remaining work. Effort matters, but it is not the only constraint. A short configuration change may require new test cases, another training audience, or a revised handover document.
- Outcome: Is this necessary for the agreed result, helpful to it, or a separate result?
- Dependencies: What data, decisions, access, or specialist input must arrive first?
- Downstream work: What must be retested, rewritten, demonstrated, or taught?
- Milestones: Can the work fit without moving readiness checks or consuming time reserved for corrections?
- Completion: Will the evidence required to finish onboarding change?
Use those answers to select a disposition:
- Include: add the request and state its effect, even when the milestone does not move. Identify any capacity or contingency consumed.
- Substitute: add the request while explicitly removing or reducing named work. Check that the remaining plan still delivers the agreed outcome.
- Defer: keep the current onboarding boundary and place the request in a separate review path with an owner and a review trigger. Deferral is not a promise of future delivery.
- Decline: explain why the request does not belong in this implementation or cannot be responsibly supported. Offer an alternative only if one is genuinely available.
If including a request changes a date, present that changed date before work begins. If the impact is uncertain, say what remains unknown rather than disguising uncertainty as a firm estimate. Any commercial or contractual questions should follow the organisation's separate approval process; this operational log does not replace it.
4. Fictional worked example: a filled request decision log
All organisations, roles, dates, quantities, and outcomes in this worked example are hypothetical. The log illustrates a recommended operating practice, not a product feature or a customer result.
Hypothetical baseline: a customer is onboarding one service team. Completion means the team can assign incoming enquiries, update their status, and demonstrate a handover using an agreed sample. The plan includes one approved contact file, one team workflow, a basic operating guide, and one training session. Historical activity migration and a second department are excluded.
Hypothetical milestones: configuration review on 8 June, data validation on 10 June, training on 12 June, and completion review on 15 June. The customer operations lead confirms operational priorities; the implementation lead assesses effects and updates the plan.
R-01: Add a preferred-contact-time field
- Requested change: the customer operations lead asks for a field to help the initial team choose when to follow up.
- Assessment: it supports the existing workflow. The implementation lead estimates two additional hours covering configuration, sample checks, and guide updates.
- Disposition: include.
- Milestone effect: the configuration review stays on 8 June, using two hours of reserved contingency. Remaining contingency falls from four hours to two.
- Customer decision: the operations lead confirms inclusion on 5 June and agrees to provide the field definition that day.
- Updated expectation: the field will be demonstrated in the existing sample workflow. This does not include a broader redesign of contact data.
R-02: Replace a summary report with an unassigned-enquiry view
- Requested change: the team supervisor wants to find enquiries without an owner before each handover.
- Assessment: the need is closer to the agreed handover outcome than the planned summary report. The implementation lead assesses the replacement as comparable effort.
- Disposition: substitute.
- Milestone effect: no date change. The summary report is removed from the configuration review and training agenda.
- Customer decision: the operations lead confirms the swap on 6 June after checking with the report's original requester.
- Updated expectation: completion includes demonstrating how the supervisor identifies unassigned enquiries. The removed report is not an outstanding onboarding task.
R-03: Import historical activity from several files
- Requested change: a manager asks to add historical activity from six files alongside the approved contact file.
- Assessment: the files need mapping and quality assessment. Their effort and effect on validation cannot yet be stated reliably, and historical activity is outside the baseline.
- Disposition: defer.
- Milestone effect: data validation remains on 10 June for the approved contact file only.
- Customer decision: the operations lead confirms deferral on 6 June. The customer data owner will inventory the files for a separate review after the completion meeting.
- Updated expectation: historical activity is not required for onboarding completion. The later review will assess feasibility and priority; no import date is committed.
R-04: Add a second department before training
- Requested change: another department asks to join with its own assignment rules, examples, and training needs.
- Assessment: this adds a new workflow and audience rather than extending the initial team's setup. It requires separate discovery and readiness checks.
- Disposition: decline for this onboarding phase.
- Milestone effect: training remains on 12 June for the initial service team; no second-department readiness claim will be made.
- Customer decision: the operations lead confirms the phase boundary on 7 June and will explain it to the second department's manager.
- Updated expectation: completion on 15 June is assessed only against the initial team's outcome. Any second-department proposal requires separate planning.
The log makes the cumulative effect visible: dates remain unchanged, but contingency has reduced, one deliverable has been replaced, and two requests are outside completion. Without those details, an unchanged completion date could misleadingly suggest that every request had been absorbed.
5. Turn each decision into an updated working plan
A decision log is useful only if delivery and customer communication reflect it. After agreement, update the affected task, milestone, training agenda, and completion checklist. Link or reference the request identifier so the reason for the change remains traceable.
For substitutions, remove the displaced work from active delivery lists. Leaving both items visible as unfinished creates a predictable dispute at handover. For deferrals, move the request out of the onboarding completion checklist and record its separate review owner and trigger.
Send a concise confirmation that covers three points: the decision, its consequence, and what now counts as finished. Avoid a message that says only that the request is approved.
Where a decision needs customer confirmation, ask for a specific response. Do not treat silence as agreement to a changed milestone. Keep the existing agreed plan as the baseline, unless a newly discovered dependency makes it infeasible; in that case, flag the milestone as at risk rather than continuing to present it as secure.
6. Recover when informal promises have already accumulated
If extra work has already started, stop adding further commitments long enough to reconcile the plan. Do not erase the informal promises or blame the customer for relying on them.
- Inventory the commitments: collect requests from meeting notes, messages, and delivery tasks. Distinguish requested, acknowledged, accepted, started, and completed work.
- Assess the remaining impact: include unfinished tests, documentation, and training—not just build effort.
- Identify conflicts: show where the current workload, milestone, and completion criteria cannot all hold together.
- Offer a revised choice: present a smaller completion boundary, a substitution, or a changed milestone with explicit consequences.
- Confirm and reconcile: record the customer's decision and update every active version of the plan.
Work already completed does not automatically justify adding its full expansion to the remaining phase. Equally, time already spent should not be hidden. Explain what is done, what remains, and which decisions are still open.
A common failure is to preserve the date by quietly reducing validation or training. That changes readiness without making the trade-off visible. If a readiness check must change, name the resulting limitation and resolve it explicitly rather than treating it as an internal scheduling adjustment.
7. Use the next milestone to test whether the log works
Before the next customer checkpoint, review every request received since the previous milestone. Each should have a disposition or a named person and date for returning an assessment. Each accepted change should appear in the working plan, and each substitution should identify the work it removed.
Track observable gaps rather than collecting metrics for their own sake:
- Accepted requests missing an impact assessment.
- Unresolved decisions blocking a milestone.
- Differences between the delivery plan and customer-facing completion checklist.
- Remaining contingency after accepted additions.
For tomorrow's working session, take the requests from the latest customer conversation and enter them into the log. Ask the customer decision owner to confirm the proposed dispositions, then restate the current milestone and completion evidence. The immediate test is simple: can both sides explain what changed, what did not, and what will count as finished?
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