Content Creation Request

Content creation requests submitted through email or informal Slack messages give writers and content teams an inconsistent brief to work from. The objective of the piece is not separated from a general description. Target audience and key messages are described vaguely. Tone of voice is not specified, leading to content that requires revision before it aligns with the brand's voice. SEO keywords are communicated in a follow-up rather than captured upfront. Without a centralized, structured content brief process, delivering content that meets the requester's expectations without multiple revision cycles requires the writer to ask for information that should have been in the original request.

The Content Creation Request template for SharePoint, built with Infowise Ultimate Forms, provides a brief form that captures the requester's contact details, the content title, content type, objective, target audience, key messages, tone of voice, content length, SEO keywords, requested deadline, special instructions, and supporting attachments. Every brief is stored as a complete, searchable record in SharePoint.

How it works

Requester details

The form captures the requester's full name, email address, phone number, and department. Capturing the department alongside contact details gives the content team the organizational context needed to understand the purpose of the request and follow up with the correct person without additional search.

Content type and objective

The form captures the content title and a structured content type column — blog post, social media copy, email, whitepaper, case study, or another format. A required objective column captures what the piece is designed to achieve. Capturing content type and objective in structured columns at the brief stage allows the content team to assess the appropriate format, length, and approach before a word is written, rather than discovering misalignment after the first draft is delivered.

Target audience and key messages

A target audience column captures who the content is written for. A key messages column captures the specific points the content must communicate. Capturing both in structured columns within the brief ensures the writer has a documented mandate for what the content should say and to whom, providing a clear basis for quality review once the content is drafted.

Tone of voice and content length

A tone of voice column captures the register and style the content should adopt — authoritative, conversational, educational, promotional, or another defined tone. A content length column captures the expected word count or format length. Capturing both removes two of the most common sources of first-draft misalignment, allowing the writer to deliver content that is already pitched correctly for the channel and audience without a separate style conversation.

SEO keywords, deadline, and supporting materials

An SEO keywords column captures the search terms the content should be optimized for, enabling the writer to incorporate them from the outset rather than retrofitting them after the draft is complete. A required deadline column captures when the content is needed. A special instructions column and a file attachment column allow the requester to provide additional context, reference materials, or brand assets alongside the brief.

What you get

• A content creation brief capturing requester details, content title, content type, and objective
• Target audience and key messages in dedicated columns for clear creative direction
• Tone of voice and content length eliminating the most common sources of first-draft misalignment
• SEO keywords, requested deadline, special instructions, and supporting attachments
• Every brief stored as a complete, searchable record in a standard SharePoint list
• Extendable with automated submission notifications and content review workflows using Ultimate Forms
• Free for all Ultimate Forms customers, installed automatically with a single click

Built on standard SharePoint lists

The Content Creation Request system is built entirely on standard SharePoint lists. There is no external data storage and no custom interface. All brief records stay inside your SharePoint environment, governed by your existing permissions and data policies. The system can be extended or adapted at any time in the browser by the administrator who manages the site.