The single most effective scope-creep prevention tool at Cornelia Rasco isn't a contract clause. It's a specific set of questions asked on the discovery call, before a single wireframe gets drawn or a proposal gets written. A good discovery call doesn't just gather information; it surfaces the assumptions and ambiguities that, left unaddressed, turn into "wait, I thought that was included" conversations three weeks into a project.
Why discovery calls fail to prevent scope creep
Most scope creep doesn't come from clients acting in bad faith. It comes from genuine misunderstandings that existed from day one but never got surfaced, because the discovery call focused on generic questions like "tell me about your business" and "what's your timeline" instead of the specific, sometimes uncomfortable questions that reveal where expectations might diverge.
A discovery call that only covers timeline, budget, and a general project description leaves enormous room for a client to reasonably assume things that were never actually discussed. The fix isn't a longer contract. It's a more specific conversation upfront.
The questions that actually prevent scope creep
A handful of specific questions, asked directly and documented in writing afterward, catch the majority of scope ambiguity before a contract is signed:
"Who besides you needs to approve this design before it's considered final?" This single question has prevented more scope creep than any other, since an unnamed stakeholder who appears in week four with a completely different opinion is one of the most common sources of unplanned revision rounds.
"What does this project need to include for you to consider it a success, separate from what you'd like it to include if budget allowed?" This separates true requirements from nice-to-haves early, before they get treated as equally essential later.
"Has anyone else worked on this project before me, and is there existing work I should know about?" Prior work, whether a half-finished brand guide or a previous designer's abandoned files, often carries expectations about continuity that never get mentioned unless directly asked.
"What would make this project feel like a failure to you, even if everything we agreed on gets delivered?" This question surfaces unstated priorities, like a specific competitor's product the client is quietly benchmarking against, that a standard project brief would never capture.
"How many rounds of revisions do you expect, and what happens if we need more than that?" Naming a specific number upfront, rather than leaving "revisions" undefined, removes one of the most common sources of scope disputes later.
What happens after the call matters just as much
Asking good questions only helps if the answers get documented and referenced later. Every discovery call is followed by a written summary sent to the client within 24 hours, covering exactly what was discussed, what's included in the proposed scope, and what's explicitly excluded. This isn't a formality. It creates a shared, referenceable record that both sides can point back to if a disagreement about scope comes up mid-project.
Clients occasionally push back on specific line items in that summary, which is exactly the point. Catching a disagreement about scope during the discovery follow-up costs five minutes of clarifying email. Catching the same disagreement during week three of development costs a difficult conversation and possibly unpaid rework.
Handling the client who resists specificity
Some clients respond to detailed discovery questions with vague answers, either because they haven't thought through the details yet or because they're not used to being asked this directly. That's a useful signal in itself, not a problem to route around. A few approaches work well in that situation:
Offering examples rather than open-ended questions, such as "would this be closer to a full rebrand, or refreshing colors and typography within your current identity?"
Explicitly naming that vague scope now typically leads to a change order process later, so there's no surprise about why specificity matters
Building a short paid discovery phase into the engagement when a client's needs are genuinely still in flux, rather than trying to force premature specificity into a free consultation
The underlying principle
Scope creep prevention isn't really about contracts, change orders, or firm boundaries after the fact, though all of those matter. It's about asking the right questions early enough that ambiguity gets resolved before it becomes expensive. The best time to have an uncomfortable conversation about expectations is before any work has started, when it's still just a conversation and not a dispute.
Bringing this discipline to your own project
If you're planning a design engagement and want a discovery process that surfaces the right questions upfront, reach out to Cornelia Rasco to start with a call built around exactly this framework.
Photo: eekim (CC BY 2.0)
