How to Operate a Website for Sales, Recruitment and Communications
A website is rarely only a sales, recruitment or communications tool. That is why it will not last if everyone can change anything at any time—or if all responsibility sits with one person. Separate what each team needs from the facts the whole organisation must keep accurate, then establish a workable operating model.
Do not begin with a publishing calendar
Begin by deciding which decision the site supports for each team. That reveals the pages needed, the triggers for an update, the reviewer and a suitable way to check whether the information remains useful.
1. Give sales, recruitment and communications distinct page roles
Sales may use service scope, cases and conditions before a conversation. Recruitment may need to explain the work, team, vacancies and application route. Communications may maintain news, initiatives and accurate core information. Separating shared company facts from audience-specific information makes priorities easier to discuss.
2. Assign an owner and reviewer to each important fact
List information that requires confirmation when it changes: service scope, prices or conditions, cases, roles, vacancies and contact details. The person writing need not be the person approving the fact. Match CMS roles and permissions to the real responsibilities, and revisit them when people change position.
| Role | Decision | Record |
|---|---|---|
| Page owner | Audience, purpose, next action and update trigger | Pages and next review date |
| Fact owner | Accuracy of service conditions, prices, people and cases | Source, approver and review date |
| Editor | Copy, images, links and CMS entry | Change and draft state |
| Publisher | Release condition, rendering, forms and related pages | Release date and check result |
| Operations owner | Priority, exceptions, retirement and handover | Decision reason and successor |
3. Connect publishing to work already happening
New offers, exhibitions, recruitment rounds, published cases and changed hours are existing business events. Use them as update triggers. Simply adding a recurring “blog day” does not ensure important information stays current. Place the required material, deadline, reviewer and post-publication communication within the work the team already does.
4. Use a small set of checks and a regular review
Different teams do not need the same metric. Sales can learn from the nature of enquiries, recruitment from how people reach vacancy information and questions they raise, and communications from whether accurate guidance stays available. A regular conversation about what to retain, revise, add or retire keeps the website from becoming a static storage place for old information.
5. Separate routine publishing from an urgent correction
An error in contact details, conditions or recruitment information may need review before the normal publishing schedule. Decide who receives it, confirms the fact, identifies affected pages and languages, publishes the correction and tells the relevant people. Where the issue requires technical, security, legal or privacy judgement, the content team should escalate it to the appropriate owner rather than make that decision alone.
Content operation and technical maintenance are connected, but not the same job
This article owns content responsibility, review and publication. For updates, backups, permissions and performance, read the performance, security and updating guide. Use the first-90-days review to turn post-launch observations into the next decision.
MAKE THE SITE USEFUL
Could sales, recruitment and communications use the same website without creating more burden?
We can start with current content, owners and update difficulties to establish a sustainable operating point.
Review and source
Reviewed 20 August 2026. For the basic model of aligning CMS actions with responsibility, see the WordPress Developer Handbook on user roles and capabilities.
