Who does what: sharing website responsibilities
When something goes wrong, nobody should wonder whose job it is. Here is a simple way to share website responsibilities clearly.

Most website problems are not caused by missing skills. They are caused by missing clarity. Everyone assumes someone else was looking after the updates, the renewals or the backups.
The usual gaps
- Who updates the software?
- Who renews the domain and the certificate?
- Who owns the logins?
- Who fixes it when a page breaks at 5 p.m. on a Friday?
- Who decides what content is published?
Three groups, three roles
In most arrangements, responsibilities sit with three parties:
| Area | Your organisation | Your provider | Your web developer (if any) |
|---|---|---|---|
| Content and messages | Owns and approves | Supports on request | Supports on request |
| Server and infrastructure | Informed | Looks after | Informed |
| Software updates | Depends on plan | Depends on plan | Depends on agreement |
| Backups | Informed | Looks after | Informed |
| Logins and access | Approves who gets access | Sets up and removes | Follows agreed rules |
| Domains and renewals | Owns | Can manage on your behalf | Informed |
The exact split varies, and that is fine. What matters is that it is written down.
Why it matters
Where we look after something for you, we say so. Where it stays with you or your own team, we say that too. Neither is better in general; what matters is that it is chosen knowingly and clearly shown on your client page.
Make it practical
- Write a one-page responsibility list and share it.
- Name a main contact in your organisation and a backup.
- Agree how requests are made and how quickly you expect a response.
- Review it once a year or whenever people change roles.
Remember handovers
When staff or agencies change, make sure access, documents and knowledge stay with the organisation.
Want a clear responsibility map for your website? Ask our team to draw one up with you.
