Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

When you submit a brief to the content team, it is important that we are provided with a complete brief that covers all the important information. This ensures that we can progress your brief efficiently.

Before you submit a new brief, please run through the checklist below and ensure that your brief has covered all of the relevant points.  

Tip
titleA brief must contain all the below details before the team can progress your request.


Explain the brief


Create a new ticket in JIRA and then add in the following details:

  •  What kind of content needs to be published - is it a publication, a consultation, a news item or a set of statistics.
  •  Who will be using this content
  •  Why do they need access to the content, and how will it help them
  •  When does the content need to be published
  •  Where should the content be published when it has been signed off
  •  In your own words, what do we need to know about this new content? (Please explain in 140 characters maximum)

Add important links and contacts


At the bottom of the JIRA ticket, please include these details:

  •  Lead point of contact for this content
  •  Required publication date
  •  Embargo time and date, if this is applicable
  •  Existing location of the content (please include the web link, or URL)
  •  Intended location of the new content (please include URL, or if the new location is unknown, please write 'TBC')

Review and approvals


When the new content is ready, we will need you to provide these approvals:

  •  Review the final content
  •  Give your approval via the JIRA comments section
  •  Notify the relevant press officer that the content is being published
  •  Ensure sign-off from your manager, or the subject lead



Info

Content by Label
showLabelsfalse
max5
spacescom.atlassian.confluence.content.render.xhtml.model.resource.identifiers.SpaceResourceIdentifier@2265b8
showSpacefalse
sortmodified
reversetrue
typepage
cqllabel in ("content","request","brief") and type = "page" and space = "IPSD"
labelsbrief request content


Page properties
hiddentrue


Related issues