Skip to main content
All CollectionsPractical tips and guides
Content governance: Example project workflows
Content governance: Example project workflows

View example content workflows for content governance such as maintaining website content or help centre documentation.

Bruno Wilson avatar
Written by Bruno Wilson
Updated over a week ago

In Content Workflow, workflow makes the status of your content crystal clear. Workflow is the set of statuses that can be applied to items in your project to communicate their progress.

The default workflow will depend upon the project type that was selected when the project was created.

The default workflow will depend upon the project type that was selected when the project was created.

Example workflows for content governance

Content Workflow is a great tool to manage the governance of content and ensure your content is up-to-date and accurate. In content governance, your project workflow will likely follow this essential process:

  1. To be updated

  2. Draft

  3. Review

  4. Edit

  5. Approved

  6. Live

We encourage you to customise your project workflow to match your team's content production process. Here are some example workflows by different types of content governance projects:

Maintaining website content workflow

You can use workflow in Content Workflow to keep track of what content is live and to send reminders when content should be reviewed for accuracy once it's been live for a set period of time:

  1. To be updated - Use this stage to notify contributors when content needs to be updated

  2. Draft

  3. Review

  4. Edit

  5. Approved

  6. Live - Use this stage to keep track of what content is live

  7. Accuracy check - Set deadlines with this stage to send reminders when content needs to be reviewed for accuracy. If there are no edits required, shift it back to 'Approved' or 'Live' or into 'To be updated' if edits need to be made. 

Maintaining help centre documentation workflow

Help centre content will need to change as often as changes are made to your product or services. Workflow for a project like this may look like this: 

  1. New brief - Use this stage when a new article/doc is required  

  2. Published and needs updating - Use this stage when a change means existing documentation needs to be updated

  3. Draft

  4. Review

  5. Edit

  6. Approved

  7. Live

You can customise your workflow as much or as little as suits for your project. We recommend that before content production begins you should agree on your content workflow with your team and then setup your Content Workflow project workflow to reflect this. This helps keep everybody clear on responsibilities and the review process.

Further Reading

Did this answer your question?
https://help.gathercontent.com/en/articles/2682565-content-governance-example-project-workflows
help.gathercontent.com
CC-MAIN-2024-38
62950
application/http; msgtype=response
sha1:RPHLJA6JPQPMMVOTBEZB3NEDVERAINKK
<urn:uuid:1430ff41-8fc8-4426-8ce7-ce8de196f965>
2024-09-09T10:35:14Z
172.67.168.3
text/html
sha1:BTVL7IW27I5AWO5U6Q27LIMXEJQQ7VZL
<urn:uuid:7d6e737e-6b72-45f7-9742-f5002c148a2b>
https://help.gathercontent.com/en/articles/2682565-content-governance-example-project-workflows
response
<urn:uuid:49233810-23d5-40df-8c26-e88355240ca7>
isPartOf: CC-MAIN-2024-38
publisher: Common Crawl
description: Wide crawl of the web for September 2024
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-163
software: Apache Nutch 1.20 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.5-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: https://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/