A demo often reveals useful new requirements. The delivery problem begins when those requirements are treated as small wording edits despite changing integrations, authority, or operating responsibility.
Keep an approved baseline with supported scenarios, actions, assumptions, exclusions, and acceptance cases. Evaluate each requested change against that baseline rather than the amount of text needed to describe it.
Classify the behavioral impact
A greeting edit may be low impact. Adding cancellation changes authority, remote operations, recovery, and customer commitments. A new location adds identity mapping and local policy even when the conversation sounds identical.
Record the requested behavior, business reason, affected dependencies, implementation effort, acceptance changes, recurring costs, and operational owner. Mark unverified capabilities before estimating them as known work.
Work through a fictional demo follow-up
After seeing appointment intake, a client asks the agent to reschedule existing visits. The initial scope only creates requests for staff. Rescheduling requires patient or customer matching, appointment selection, authority checks, supported updates, and stale-notification handling.
The change record explains those additions and proposes a bounded rescheduling scenario or a separate discovery check. It does not simply add “you may reschedule” to the prompt and inherit every edge case.
| Requested change | Impact to review |
|---|---|
| Greeting wording | Approved facts and regression scope |
| New remote action | Permission, validation, and recovery |
| New branch | Local configuration and isolation |
| New price promise | Approved data and authority |
| New support expectation | Staffing and incident responsibility |
Keep delivery decisions reviewable
Offer concrete options when useful: replace an existing deliverable, add scope and adjust terms, or defer the request. The client should review a specific resulting scope, not a vague warning that changes cost more.
A formal process can feel heavy for small edits. Use a lightweight log for routine revisions and a clear threshold for consequential changes. The goal is accurate commitments and acceptance, not paperwork for every punctuation mark.
Rerun affected tests after approved changes and update operating notes. Review acceptance criteria to keep the final scope measurable.
Questions about scope changes
Is every prompt edit a paid change?
That depends on the agreement and actual impact. Distinguish included refinement from new behavior using the approved baseline.
Can the client approve a change verbally?
Use the agreed process and preserve a concrete record of behavior, terms, and acceptance impact.
What should happen to the demo?
Update or label it so reviewers understand which behavior represents the current scope. A stale demonstration should not become an accidental promise.