Scope Creep Examples — Web development
Extra technical training, beyond what onboarding included
The engagement included one technical handoff session for the client's engineering team. New engineers keep joining and each wants their own walkthrough.
The SOW included one technical handoff session covering the codebase, architecture decisions, and deployment process, delivered to the client's engineering team at project close. Months later, as the client's engineering team grows, new engineers each ask for their own walkthrough of the same material — understandable individually, but a request that would have the original agency re-delivering the same handoff repeatedly, indefinitely, for free.
Clause typically implicated
Clause typically implicated
Deliverables clause→ — The single handoff session is the scoped deliverable — repeat sessions for a growing team are a different, recurring ask.
Suggested change-order wording
Suggested change-order wording (illustrative, not legal advice)
The original handoff session covered architecture and deployment for [original team] at project close. For new engineers, I'd recommend we record a documentation walkthrough now that your team can reuse for onboarding going forward, at no extra cost. If a live Q&A session with our team is still useful for a specific new hire, that would be billed at [rate] per session.
How this usually resolves
Pairing a recorded walkthrough with good written documentation (if it doesn't already exist) usually solves this well enough that live sessions stop being requested at all — engineers especially tend to prefer being able to reference material on their own timeline anyway.
Related reading