Skip to main content
Out of Scope

is an extra page out of scope when the count was agreed?

Yes — if your agreement names a page count, anything beyond it is additional work, even when the client calls it small. The exception is when a page was clearly implied by the agreed structure (a required confirmation screen, say) and was simply never written down.

Why this answer

A page count is one of the cleanest scope boundaries in web work, which is exactly why it gets tested. When you priced a five-page site, you priced five pages worth of design, content integration, responsive testing, and review cycles. A sixth page isn't a rounding error on that estimate — it's a full unit of the same work: layout, copy placement, mobile checks, cross-browser passes, and its own slice of feedback. Clients reach for 'just one more page' because each page feels marginal from their seat, but from yours the additions stack into real hours. The count also anchors the rest of the project's economics: navigation structure, internal linking, and the testing matrix all scale with page volume. Letting the count drift means every downstream estimate drifts with it. Holding the line isn't about being rigid — it's about keeping the number you both agreed to from quietly becoming a different number.

When the answer flips

It tilts toward In Scope when the extra page was functionally implied by what you agreed to build. If you scoped a checkout flow, the order-confirmation page is part of that flow even if no one itemized it. The same goes for a required legal page like a privacy policy on a site that obviously needed one. It can also be In Scope if your contract used soft language — 'a small marketing site' — without a hard count, in which case one more page sits inside a reasonable reading of that brief. And if the new page is genuinely trivial and replaces a planned one rather than adding to the total, swapping it is usually fair. The decisive question is whether the page expands the agreed structure or merely completes it.

What to do next

Acknowledge the request and price it as a unit, not a favor. Quote a per-page rate that reflects your real cost for a page of that complexity — a content-only page differs from one with a custom layout or interactive element, so don't flatten them into one number. Send it as a short change order: the page, the fee, the added timeline, and a note that the rest of the project stays on its original schedule until the addition is approved. Useful framing: 'Happy to add it — each page is its own deliverable, so this is [fee] and pushes delivery by [days]. Want me to fold it in?' If the client balks, offer the swap alternative: replace a lower-priority planned page with this one at no extra cost. That gives them a free path while protecting your total.

Settled reads your contract and gives you the exact verdict for this situation — try it free →

Frequently asked questions

The client says one page is barely any work. Are they right?+

Rarely. A page that looks simple still needs layout, content placement, responsive behavior across breakpoints, browser testing, and at least one round of feedback. Even a 'plain' page consumes a real fraction of what you estimated for the whole site. The client sees the finished page; you carry the production work behind it. Quote what it actually costs, not what it appears to cost from the outside.

How do I price an additional page?+

Set a per-page rate tied to complexity tiers rather than a single flat number. A text-and-image page is one price; a page with a custom layout, form, or interactive component is another. Build a small menu so you can quote quickly and consistently. Pricing per page also makes the cost legible to the client — they can see precisely what each addition buys and decide accordingly.

What if the new page replaces one we already planned?+

Then it's usually a fair swap at no extra charge, because your total page count stays the same. Confirm the planned page is genuinely dropped, not just deprioritized to resurface later. Put the swap in writing so there's no ambiguity about which pages are in the final set. A one-for-one trade keeps the client happy without expanding your scope.

Is a page that's required for the site to function — like a thank-you page — out of scope?+

Generally no. If a page is structurally necessary for a flow you already agreed to build, it's part of that deliverable even if no one listed it. A confirmation screen after a form, an error page for a checkout, a privacy policy on a site collecting data — these complete the agreed structure rather than expanding it. New marketing or content pages are a different story.

Can I just add it for free to keep the client happy?+

You can once, but understand what it signals: that the page count was negotiable all along. The next 'one more page' arrives with the same expectation. If you want to be generous, do it visibly — note that you're including it as a one-time courtesy and that further pages will be quoted. Generosity you name reads as goodwill; generosity you hide reads as a precedent.

How do I scope page count so this doesn't come up?+

List the pages by name in the contract, not just a number, and add a line stating that pages beyond the named set are quoted separately at a per-page rate. Naming them prevents the 'I thought that was included' conversation, because there's an explicit list to point to. Pair it with the per-page rate so the answer to any addition is already priced before it's asked.

Related reading

Answer scope creep from your actual contract — not a template.

Settled reads your contract and the client's request, gives you a verdict (In Scope / Out of Scope / Ambiguous), and drafts the email grounded in your specific clause.

Try it free →Read the scope creep guide