Skip to main content
Out of Scope

is content entry out of scope?

Yes — typing the client's content into the system you built is a distinct, time-consuming task that's separate from designing or building the container for it. The exception is a contract that listed content population or migration as a deliverable.

Why this answer

There's a clean line between building the vessel and filling it. Your contract scopes the structure — the templates, the layouts, the components, the CMS — and assumes the client provides finished content to go in. Content entry is the labor of placing every paragraph, uploading and naming every image, formatting every table, and proofing it all into place. On a real project that's hours or days of work, and it scales with the client's content volume, not with your build. Clients often don't see this as separate because to them the site 'isn't done' until it has their words in it. But populating it requires content they often haven't finished writing, and the act of entry is production labor distinct from the design and engineering you were hired for. Building the empty system and filling it with someone else's material are two different jobs.

When the answer flips

The verdict flips to In Scope when your proposal listed content entry, population, or migration as a deliverable, or when you quoted a 'launch-ready' site that implies finished content in place. It also flips if you only built a handful of demo pages and the contract's page count already accounts for populated examples. A small amount of placeholder-to-final swapping on a few key pages is often a reasonable courtesy. And if the project is a content migration from an old system — moving existing content rather than entering newly written material — that migration is sometimes assumed in the build scope, so the contract language matters more than the general rule here.

What to do next

Clarify what 'done' meant in your agreement: 'The build covers the site structure and templates; entering your content into it is a separate task I can take on.' Then give the client a choice. Option one: they populate it — many CMSs are built for exactly that, and you provide a short guide. Option two: you do the content entry at a stated rate, priced per page or per hour, since the time scales with their content volume. Ask for all final content in one organized batch before you start, because piecemeal content arriving over weeks turns a bounded task into open-ended babysitting. Add a content-readiness clause to your next contract.

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

Frequently asked questions

Isn't the site incomplete until my content is in it?+

It's complete as the deliverable you contracted for — a built, functional structure ready to receive content. Whether that structure is empty or full is a separate question from whether the build is done. Most contracts scope the container and assume the client supplies and places the content, unless population was explicitly named as part of the job.

How should I price content entry?+

Price it per page or per hour, because the effort scales with content volume, not with the build. A simple page with one block of text is fast; a dense page with tables, galleries, and formatting is not. A per-page rate with a note that complex pages may cost more keeps it fair and predictable for both sides.

What if the client hasn't finished writing their content yet?+

Then content entry can't even begin, which is the clearest sign it's a separate task from the build. Make clear you need final, organized content before you start, ideally in one batch. Entering content that's still being written turns a bounded job into endless revisions and is itself a form of scope creep worth pricing in.

Can I just teach the client to enter their own content?+

Often that's the best outcome. Most modern CMS and site builders are designed for clients to manage their own content. A short walkthrough or a one-page guide hands them ownership and saves you the repetitive entry work. Offer this as the default option, with paid content entry as the alternative for clients who'd rather not.

Does content migration from an old site count as content entry?+

It's related but distinct, and the contract language matters. Migrating existing content from an old platform is sometimes assumed inside a rebuild scope, whereas entering newly written content usually isn't. If migration is involved, check whether your proposal named it, because clients frequently expect their existing content to carry over as part of the move.

How do I scope this cleanly upfront?+

Add a content-readiness clause stating that the client provides final, organized content by a set date, and that content entry or population, if you're doing it, is a separate line item priced per page. Name who's responsible for placing content into the build. That one paragraph prevents the most common launch-week scope fight.

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