When several people contribute to your company website, giving everyone WordPress access is only the beginning. You also need to know who prepares the content, who checks the facts and who decides that an article is ready to go live. Without that clarity, unfinished copy can appear too soon while completed articles sit forgotten in drafts.
A straightforward editorial workflow connects technical permissions with practical responsibilities. Here is how Contributor, Author and Editor roles differ, and how to organise content handovers in a small team.
1. What each WordPress role can do
The descriptions below cover the standard WordPress roles. Plugins and custom configurations can change permissions, so check the actual capabilities on your site before defining your team’s process.
Contributor: writes but cannot publish
A Contributor can create and edit their own unpublished posts and submit them for review. They cannot publish posts or, in a standard configuration, upload files to the media library. Once their post is published, they cannot edit it themselves.
This role suits occasional contributors and subject specialists whose work needs approval. If their article requires images, they should hand those over separately to someone with permission to upload them.
Author: manages their own posts
An Author can write posts, upload media, publish their own posts and edit them after publication. They can also delete their own posts. The role does not allow them to edit other people’s posts or manage the site’s pages.
Choose this role for someone with genuine editorial independence. An internal rule requiring approval does not remove an Author’s technical ability to publish directly.
Editor: coordinates content across the team
An Editor can edit, publish and delete their own posts and those written by other users. They can also manage pages, categories, tags and comments. The role does not include plugin or theme administration by default.
The Editor role is a natural fit for your editorial lead. However, permission to publish does not automatically qualify someone to approve every commercial, legal or technical claim.
2. Assign responsibilities before handing out access
In a small team, one person may cover several responsibilities. What matters is that each article has a named owner, rather than an assumption that someone will deal with it. Separate these tasks:
- The writer prepares the copy and gathers sources, images and supporting information.
- The subject reviewer checks facts about products, services or procedures.
- The editorial lead reviews structure, clarity, tone and relevance to the reader.
- The publisher performs the final checks and publishes or schedules the article.
The same Editor can handle the last two tasks. A specialist checking the facts does not necessarily need WordPress access: they can review the material in a shared document.
If every article must go through approval, the standard Author role does not enforce that requirement. You can use Contributors and an Editor, or assess a dedicated editorial configuration, checking its resulting permissions separately.
3. Create a clear route from idea to publication
Standard post statuses are useful, but they do not describe your entire process. A draft could be an initial outline or an almost finished article. Support WordPress with a shared task list that records the owner, current stage and next action.
- Topic accepted: agree on the audience, the main question and the article’s purpose.
- Being drafted: the writer works in a draft post or an agreed shared document.
- Under review: the writer explicitly hands over the text, highlighting anything that needs confirmation.
- Changes requested: the writer receives feedback with a clear next action.
- Approved for publication: the editorial lead confirms the final version.
- Scheduled or published: the designated person completes the final checks and records the outcome.
In WordPress, Pending Review can indicate that a post has been submitted for checking. That status is not approval in itself, and it does not automatically send every notification your process might require. Agree separately on how a handover is announced.
When scheduling a post, check the date, time and site time zone. Use the same convention across the team so a deadline such as “tomorrow morning” does not mean different things to different people.
4. Hand over a complete package, not just the copy
A good handover reduces follow-up questions and helps prevent the wrong version from being published. Use a short template for every writer, whether they work directly in WordPress or elsewhere.
- Identification: the working title and a link to the draft or document.
- Context: the intended audience, purpose and action you want the reader to take.
- Validation: the sources used, the person responsible for factual approval and any unresolved questions.
- Media: the files, usage rights, captions and suggested alternative text.
- Publication: the proposed category, relevant links and any conditions affecting the publication date.
Make it clear where the authoritative version lives. If you move the copy from a shared document into WordPress, announce when further changes should be made only in the draft post. Editing two versions in parallel makes it easy to lose corrections.
Keep feedback in an agreed place: a shared document, a task management tool or an available editorial feature. Public comments on the article are not an internal review channel.
5. Separate editorial review from publication checks
When reviewing articles, start with meaning and accuracy rather than punctuation. Does the text answer the question promised by the title? Are its claims supported? Is the information about your offering current? Once those points are settled, refine the language and formatting.
Before publication, use a separate checklist:
- The title, subheadings and paragraphs are easy to read in the preview.
- Links lead to the intended destinations.
- Images are appropriate and have relevant alternative text where needed.
- The displayed author, category and date are correct.
- No internal notes, placeholder copy or unconfirmed information remain.
Depending on your site’s configuration, WordPress revisions can help you compare and recover versions, but they do not replace editorial approval. When an Author or Editor updates an already published post, those changes can become visible immediately. Prepare and approve substantial amendments before updating the live article.
Keep editorial and technical issues separate, too. If you are assessing your website’s infrastructure, you can explore WordPress hosting. Your hosting choice does not decide who approves content or replace an internal publishing procedure.
6. Start with a few explicit rules
Begin by naming an editorial lead, giving the Contributor role to people whose work requires approval and reserving the Author role for those trusted to publish independently. Choose one place for the current version and a clear handover message: “complete and ready for review”.
Test the process with one article and adjust any stages that cause confusion. For questions about hosting services, use the contact page; keep editorial approvals and deadlines within your team. A useful workflow makes the next person’s responsibility visible without turning every article into a complicated project.
