If you're afraid to talk about scope creep, read this.

Your team is working weekends. The client keeps asking for more. No one wants to push back. You tell yourself it’ll balance out later—but the hours keep piling up.

This is scope creep. And in most architecture studios, it isn’t just common—it’s cultural. We’re taught to serve, to say yes, to keep the peace.

But here’s the truth: saying yes without clarity erodes trust. It drains profit. And eventually, it burns out your team.

You don’t need to become rigid or corporate. You just need a simple, clear way to catch changes early and respond with confidence.

Here’s how to do it:

Step 1: Make scope visible

Before you can spot scope creep, everyone needs to know what “in scope” means.

• Have one page that defines what was agreed (milestones, drawings, key deliverables)

• Make it visible to the whole team—pinned in your project folder or management board

Step 2: Spot changes early

Every week, ask your team:

• Are we doing anything not in the scope document?

• Has the client asked for anything new (even small)?

Don’t wait for a crisis. Ask early, often, and make it normal.

Step 3: Respond with structure

When you spot a scope change:

• Pause and acknowledge it: “Thanks for that request.”

• Respond in writing with: “We’re happy to do this. Here’s what it would involve…”

• Include time, fees, and any adjustments to timeline

Most clients aren’t trying to overreach—they just don’t know what’s involved. Your job isn’t to say no. It’s to shine a light on the impact.

---

🏗️ HTCH ("hatch"): All your building data, always ready.
📂 Designs, plans, & models–never lost.
🔗 Try HTCH free: https://www.htch.app/