For UK teams

PHP and WordPress estate maintenance for UK organisations

Establish a UK website estate baseline across PHP, WordPress, hosting and licences. Prioritise upkeep, recovery checks and named release responsibilities.

Let’s talk

Make the estate understandable

Application code displayed on a desktop monitor.
Illustrative photography · Karl Pawlowicz / Unsplash

If your organisation has accumulated several websites and PHP applications, even a routine change can raise awkward questions. Who holds the hosting account? Does a former supplier still renew a plugin licence? Which site sends enquiries into the sales system? We start by making those relationships understandable before proposing ongoing maintenance.

Webvelopment can scope an initial review of a UK business or agency estate, covering WordPress sites, PHP applications and the connections between them. Bring the site list and the problems your team already knows about. Together, we can separate routine upkeep, technical risks that need attention and improvements better handled as a project. Incident cover and new development need their own agreed scope.

Build a useful maintenance plan

We look at the information behind each site: hosting access, backups, dependency versions, paid licences, forms, integrations and release procedures. Tell us which services your business relies on and where another supplier needs to participate. If a dependency cannot be changed safely with the available access or information, the plan should explain what is missing and who can help resolve it.

The schedule should reflect what happens when something fails. A form that brings in sales enquiries may need different checks from an archive that rarely changes. Agree which tasks will be checked, who can confirm the result and how findings reach the person who can act on them. That gives the maintenance work a practical purpose beyond reporting that updates were installed.

Separate upkeep from new development

Fixing a defect, updating a dependency and building a new workflow take different preparation. Describe the result you need, and we can discuss which category fits. For example, correcting a broken recipient address is different from adding a new set of enquiry-routing rules. Both matter, but they should not enter the same allowance without considering the work involved.

Changes need an appropriate test environment and an agreed recovery approach before release. We also agree what happens if a live problem interrupts planned work. Emergency availability, monitoring and response commitments require specific terms; they are not automatically included with routine maintenance or round-the-clock cover.

Start with evidence

Send the site list, known issues and an explanation of which accounts your business controls. Leave credentials out of an initial enquiry; authorised access can be arranged once the review scope is clear. A recent example of a failed form, difficult update or supplier handover can help us understand where to begin.

We can use those details to discuss a first review and the information needed before recommending an ongoing arrangement. See our PHP outsourcing approach and WordPress capability. Discuss your estate.

Establish a serviceable baseline before an allowance

For each site, establish its business role, account ownership, hosting, important dependencies and recovery route. Ask who receives its forms, which integrations staff rely on and who renews paid licences. Those answers may reveal a more immediate problem than an outdated component: an enquiry might be reaching a mailbox nobody now checks.

Your team supplies the inventory, known incidents and access it is authorised to provide. If an incumbent supplier controls an account, we need to understand that dependency and how their cooperation can be arranged. Commissioning a review does not itself authorise a hosting move or a live-system change. Keep those approvals explicit so assessment work can proceed without creating unintended disruption.

Prioritise by consequence and readiness

A proposed first phase might establish a usable test environment and check an important enquiry path before routine updates begin. In an illustrative check, a clearly marked sample request would be submitted and followed through to the agreed recipient. The reviewer would confirm the information arrived and was useful, while the technical notes would explain the relevant recovery approach.

The output could include a risk list, recovery notes and an ordered maintenance plan. Agree what evidence you need to approve that phase, including how restoration of the relevant build would be demonstrated. Then separate urgent risks, scheduled upkeep, desirable improvements and findings that still need investigation. You can see both why an item matters and whether the team has enough information to act on it.

Define what the ongoing relationship includes

The schedule should tell your team what happens during an ordinary maintenance cycle: which checks are performed, which changes may proceed under existing approval and who receives the report. A new website, application feature or larger replacement needs its own discussion. Monitoring, incident response and guaranteed availability also require explicit terms.

Keep the estate record current as work proceeds. Handover notes should explain unresolved constraints, licence ownership, important accounts and the decisions still waiting for an answer. If a platform cannot support the required changes, compare replacement options and their business case separately. That lets you consider a rebuild when it serves a clear need, without treating the age of a site alone as a reason to replace it.

Use the estate record to resolve fragmented ownership

For each site or application, identify the hosting account holder, source-code location, paid dependencies, business contact route and person responsible for recovery. An inaccessible domain account or former supplier’s licence needs a named person to resolve it. Put that action beside the technical finding so it can be followed up.

After the first maintenance cycle, your team should be able to see what changed, what was checked and what remains open. For example, a form check might confirm delivery to the agreed mailbox while leaving a separate CRM connection unverified. The report should preserve that distinction. Agree who checks the important enquiry or transaction steps and who authorises release, then keep those notes available for the next cycle or a future supplier handover.

Questions to help you choose this approach

A few useful answers before you decide.

Can we buy routine maintenance without an initial review?
We need enough information about access, recovery and dependencies to agree what we would maintain. The review can fit the size of your estate. Bring any existing inventory and operating notes so we can identify useful evidence you already have and the gaps that still need checking before an allowance is agreed.
Does an update report prove the whole site works?
No. The report should say which components changed, which workflows were checked and what could not be verified. Agree the important tasks in advance, such as sending an enquiry or completing a transaction. A successful component update does not establish that every connected system or business process has also been checked.
What if a licence belongs to a former supplier?
First establish who owns it and what use is permitted. Your business may need the supplier’s cooperation or a replacement licence. We can explain how that dependency affects the proposed work and identify the options to resolve it. The plan must use access and rights that have actually been established.
Are backups enough to make changes safe?
A backup is one part of recovery. The plan also needs to explain what it contains, who can restore it and how the restored service would be checked. Ask for the recovery approach to be verified for the relevant environment; a backup setting in a hosting panel does not by itself demonstrate restoration.
Can new features use the same maintenance budget?
That depends on the agreed priorities and commercial terms. A feature may need further discovery, its own review examples and time that would otherwise go to upkeep. We should show you that effect before reallocating work, so you can decide whether to change priorities or commission the feature separately.
Who receives the maintenance findings?
Choose someone who can decide priorities and bring in the relevant specialist or supplier. The report should show completed work, remaining risks and questions that need an answer. Where a finding belongs to someone else, identify who will contact them and what response is needed before work can continue.
What happens when a live incident occurs?
Use the support and escalation process agreed for your engagement. Routine maintenance does not automatically provide emergency response or continuous monitoring. Before work begins, clarify who receives an incident, what response has been contracted and where additional cover needs to be arranged. Keep those instructions accessible to the people operating the sites.
How do we move maintenance elsewhere later?
Keep the inventory, access record and operating notes current throughout the relationship. An exit handover should explain outstanding issues and transfer the agreed material through authorised routes. Identify accounts or licences requiring separate action as well, so your team and the next supplier understand what they can use and what still needs arranging.
Let’s move things forward

Start a conversation

Tell us what you are working towards. We’ll help you find a practical next step.

Let’s talk