← Back to stories

Original articles

I would put responsibility for urgent website fixes in writing

I believe small and mid-sized businesses should make responsibility for urgent website security updates explicit in their maintenance agreements. Paying for hosting is not enough to establish who maintains the software, how quickly they should act or whether the work is included in the price.

DevmojosAuthored 19 Nov 2026Written with AI

I believe one mistake worth avoiding is assuming that paying to keep a website online also means paying someone to keep its software maintained. Those responsibilities may sit with the same provider, but I would never treat that as a substitute for an agreement. For an owner or manager, the important question is not whether someone looks after the website in a general sense. It is whether someone has clearly accepted responsibility for urgent security updates.

Hosting and software maintenance are different jobs. Hosting provides the environment in which a website runs; maintenance concerns the software running within it. A provider can offer both, but the scope depends on what has been agreed. In my view, an invoice for hosting should not be read as a promise to carry out every update the website might need. I would want that promise stated plainly, rather than inferred from a service name.

I understand why an owner might assume otherwise. When I pay a specialist to handle something technical, I want to stop thinking about the details. That is a reasonable aim, but I believe delegation only works when the other party knows what I have delegated. A broad expectation that someone will take care of things is not the same as a shared understanding of the work. I would rather spend a little time clarifying that boundary than discover it during an urgent problem.

My starting point would be a direct request to the provider: please record who is responsible for applying urgent security fixes to the software our website uses. I would want the answer to identify a responsible party, not simply describe the availability of technical support. Being able to contact someone is useful, but I do not consider it equivalent to knowing that someone is expected to act. If responsibility is split, I would want those boundaries explained in ordinary language.

I would also ask the agreement to say how quickly that person or team will act. To me, urgent is too open to interpretation to carry the whole commitment. I would want clarity on what starts the response, whether approval is needed and what happens if the usual contact is unavailable. I am not arguing that every website needs the same arrangement. I am arguing that the arrangement should be understood before either side has to rely on it.

Cost deserves the same clarity. I would ask whether applying an urgent fix is included in the existing fee or charged separately. If additional approval is required, I would want a workable way to give it. In my view, neither the business nor the provider benefits from discovering different expectations about payment while deciding what to do. A clear agreement should protect both sides from promises that one side thought existed and the other never intended to make.

I do not think this requires a long technical document. My preference is for a short, readable commitment that an owner, manager and provider can all understand. It should make responsibility, timing and cost explicit without pretending that any agreement can remove every security risk. I would keep it simple, revisit it when services change and get it in writing rather than leave it in assumptions.

DevMojos helps businesses adopt AI, and I believe clear responsibility for urgent website security updates belongs in the maintenance agreement, not in assumptions.

← Back to stories