When is a CMS worth including?

Include a content management system when your team needs to publish regularly, several people contribute or updates need an approval process. Developer-managed changes can suit a small site with occasional edits and a dependable support arrangement. Choose by the actual publishing workflow, then ask the agency to demonstrate that workflow before agreeing on the platform.

A website brief should say who changes prices, adds services, replaces images and publishes articles. For a US company with a marketing team, waiting for an engineering release to correct an office hour may be impractical. For an owner who updates a short site twice a year, maintaining an editing interface can create work they would prefer to delegate.

How do the options compare?

The table below describes starting points for a proposal. A platform name alone does not tell you how easy the delivered website will be to edit. Templates, permissions and training determine much of the day-to-day experience.

How do the options compare?
OptionGood fitAsk the agency to demonstrate
Developer-managed contentInfrequent updates with an agreed support contactRequesting an edit, reviewing it and recovering an earlier version
CMS with structured templatesA team regularly updates defined content typesEditing a service, previewing mobile layout and publishing with the correct role
CMS connected to a custom frontendContent feeds a tailored website or several interfacesPreview, publication delay, media handling and responsibility for both systems

What should an editor be able to change?

Write an editing inventory. Separate routine content fields from layout decisions and business logic. Your team may need to edit a headline and photograph while keeping spacing, form behavior and navigation consistent. Structured fields can make those boundaries easier to understand.

For example, a real estate business may need property records with an address, gallery, availability status and enquiry destination. Decide whether an editor can publish a listing before all required fields are complete. The workflow should match the property platform being commissioned.

Ask what happens when content exceeds the example used in the design. Test a longer service title, a missing image and a page with several sections. An editing system should help the team produce a usable page with realistic material.

How should drafts and approvals work?

Define who drafts, who approves and who can publish. WordPress documents roles with different capabilities, including editing and publishing permissions. Its roles guidance gives one concrete example of how those responsibilities can be assigned.

WordPress also documents draft, pending review, scheduled and published states in its post status guidance. When comparing a custom CMS or another platform, ask which equivalent states are included in the estimate. Check the implemented permissions with real editor accounts.

Specify the scheduling time zone when your team works across US regions or international offices. Preview should show the content that will go live, including links and images. Decide who receives failed-publication alerts and how urgent corrections are handled.

What maintenance belongs in the budget?

Ask for the recurring responsibilities alongside the build cost. Name the person handling software updates, hosting, backups, restore checks and access changes. For a CMS with a separate frontend, include both components and their connection in that conversation.

List paid plugins, themes, media services and editor-seat charges where applicable. Confirm who owns each account and what happens when the development arrangement ends. A lower initial build quote can be difficult to compare when ongoing responsibilities are left undefined.

For developer-managed content, agree how edits are requested, approved and charged. Include the expected response arrangement for a routine change and an urgent correction. The business needs a reliable path to maintain its own information.

Which editing tasks should you test before launch?

Give a future editor a short set of tasks using their normal account. Watch the workflow on the devices they will use and record any step that requires agency intervention.

  • Update a service description and preview the result on a narrow screen.
  • Replace a photograph and add its appropriate alternative text.
  • Save a draft and have another person review it before publishing.
  • Schedule an update and confirm the displayed time zone.
  • Recover an earlier version through the agreed process.
  • Try publishing with a role that should lack permission.
  • Check that a changed URL follows the approved redirect workflow.

What should you include in your website brief?

Provide the pages you expect to update, the people involved and how often each type changes. Include approval requirements and any content that must appear in more than one place. Ask the agency to quote the editing experience and training along with the public design.

Use our website handover checklist to review ownership and the redesign checklist when replacing an existing site. For website development, send Resoltives your current content workflow so we can scope a practical editing setup.

Sources and further reading

These official resources support the technical guidance in this article.

Put the thinking
into your project.

Tell us what you are planning. We can help turn the requirements into a clear scope.