PLANNING & MAINTENANCE · 3 MIN READ

Website Maintenance or New Development: What Should Be Included?

Define website maintenance around routine checks, updates, recovery, and response expectations while separating new features and compatibility projects.

“Maintenance included” can mean very different things. One agreement may cover updates and routine checks; another may include a defined amount of development time. Neither phrase tells you how incidents, feature requests, or obsolete custom code will be handled.

A useful maintenance agreement names the work, the limits, and the person responsible for decisions.

01

Separate recurring work from change requests

Recurring work may include dependency reviews, scheduled updates, backup checks, and a short verification of important journeys. New workflows, design changes, and integrations are development tasks unless explicitly included.

An update can also reveal a compatibility problem requiring development. That does not make the update process wrong, but the response should be defined. Explain how additional work is assessed, estimated, and approved.

02

Establish an onboarding baseline

Before taking responsibility for an existing site, inspect access, hosting, installed components, customizations, and known issues. Identify unsupported dependencies and undocumented integrations.

A hypothetical store with an obsolete payment customization may need stabilization before routine maintenance is realistic. Calling it covered without reviewing it creates expectations that neither side can assess.

WordPress's upgrade guidance provides a technical reference for update preparation. A service agreement must add the site-specific responsibilities and checks around that work.

03

Define response expectations

Distinguish acknowledgement, investigation, workaround, and resolution. A promised response time should not be mistaken for a guarantee that every incident can be fixed within that period.

State working hours, contact channels, and what happens outside them. Do not assume continuous monitoring or round-the-clock support unless those are explicitly part of the arrangement.

Classify what constitutes an urgent incident. A checkout outage and a request to adjust a heading should not enter the same queue with the same expectations.

04

Clarify third-party ownership

List who pays for and controls hosting, domains, plugin licences, email delivery, and connected services. Identify how expired subscriptions or unavailable vendors affect support.

Keep administrative access appropriate and recoverable. The business should not lose control of essential accounts because a maintenance relationship ends.

05

Ask for useful reporting

A concise report can list changes, checks performed, issues discovered, and recommended next work. It should help the owner make decisions rather than merely display a count of updates.

Review the scope when the site gains a store, customer portal, or important integration. Maintenance requirements change as the business becomes more dependent on the system.

A clear agreement makes routine work predictable and larger changes easier to discuss. Its purpose is shared understanding, not the broadest possible promise for the smallest monthly fee.

06

Discuss the implementation

Explore website maintenance and custom WordPress development.

KEEP EXPLORING

Sources & further reading

Official documentation for the topics discussed. Check implementation details against the versions and services used by your project.

WRITTEN BY MARKO ARNAUTOVIC

Practical thinking.
Hands-on engineering.

I build AI automation, web platforms, and mobile applications for businesses. These notes share the decisions behind that work.

Meet the engineer behind ArnautCode

PUT THE IDEAS TO WORK

Need help with
the implementation?

Explore the approach and scope for website maintenance.

Explore the service
Chat on WhatsApp