The right content workflow depends on the changes you make. Before replacing a CMS or buying another tool, list the updates from the last few months and who handled each one.
## Use the existing editor when it already works
If the site has suitable fields and the responsible person can use them, improving the instructions may be enough. Check their actual account permissions. Being able to view a dashboard does not necessarily mean they can edit or publish.
Ask the editor to perform a realistic update without coaching. Note where they hesitate: finding the right page, locating the field, knowing whether saving publishes, or checking the public result. Those are specific problems you can address.
## Use structured content for repeated records
Locations, team members, events and product records often need consistent fields and a way to add or remove entries. A CMS can be appropriate when content has that structure.
A headless CMS separates content management from the presentation layer, but that separation introduces integration work. Decide who will maintain previews, publishing, authentication and delivery to each destination. An API does not automatically keep every channel synchronized.
## Consider in-place editing for existing wording
An in-place editing layer can suit a site where the layout is settled and authorized editors need to change existing words. ReCopyFast follows that model after a developer installs its script.
Its changes do not rewrite the source files. The developer still needs to consider how source changes and published copy interact during future releases. It is not a replacement for creating new pages or managing structured collections.
## Offer a service when the owner prefers delegation
Some owners do not want another login. A maintenance service can be a better fit if the work is infrequent, involves several systems or needs technical review.
Specify whether the service includes requests, proactive checking or reserved capacity. Agree response windows and how out-of-scope work is estimated. The [maintenance cost tool](/tools/website-maintenance-cost) can support a conversation; its estimates are not a binding quote.
## Run a small acceptance test
Choose one authorized change and test the full path: request, approval, edit, publication, public verification and recovery. Include the person who will actually use the workflow.
Compare options against that task, including setup and ongoing maintenance. The simplest system that handles real updates reliably is usually easier to hand over than a collection of tools with overlapping responsibilities.
## Use the existing editor when it already works
If the site has suitable fields and the responsible person can use them, improving the instructions may be enough. Check their actual account permissions. Being able to view a dashboard does not necessarily mean they can edit or publish.
Ask the editor to perform a realistic update without coaching. Note where they hesitate: finding the right page, locating the field, knowing whether saving publishes, or checking the public result. Those are specific problems you can address.
## Use structured content for repeated records
Locations, team members, events and product records often need consistent fields and a way to add or remove entries. A CMS can be appropriate when content has that structure.
A headless CMS separates content management from the presentation layer, but that separation introduces integration work. Decide who will maintain previews, publishing, authentication and delivery to each destination. An API does not automatically keep every channel synchronized.
## Consider in-place editing for existing wording
An in-place editing layer can suit a site where the layout is settled and authorized editors need to change existing words. ReCopyFast follows that model after a developer installs its script.
Its changes do not rewrite the source files. The developer still needs to consider how source changes and published copy interact during future releases. It is not a replacement for creating new pages or managing structured collections.
## Offer a service when the owner prefers delegation
Some owners do not want another login. A maintenance service can be a better fit if the work is infrequent, involves several systems or needs technical review.
Specify whether the service includes requests, proactive checking or reserved capacity. Agree response windows and how out-of-scope work is estimated. The [maintenance cost tool](/tools/website-maintenance-cost) can support a conversation; its estimates are not a binding quote.
## Run a small acceptance test
Choose one authorized change and test the full path: request, approval, edit, publication, public verification and recovery. Include the person who will actually use the workflow.
Compare options against that task, including setup and ongoing maintenance. The simplest system that handles real updates reliably is usually easier to hand over than a collection of tools with overlapping responsibilities.