How to write a content brief a freelancer can deliver against

A usable content brief makes the important decisions before the freelancer starts. It explains who the piece serves, what that person needs to understand and what a finished assignment must contain. The goal is to give the writer or creator enough direction to exercise judgment without having to guess what the buyer meant.

Start with the reader's task. “Create an article about onboarding” leaves the freelancer to choose the audience and angle. “Help a new operations manager prepare the first customer onboarding call” gives the assignment a practical center. You can then decide what information, examples and format would help that reader.

Copy this field-by-field template

Keep the brief in one shared document. Link supporting material rather than pasting an entire research folder into it. Use the following fields as prompts for decisions, and leave a visible question wherever the answer still needs agreement.

1. Goal

Write the intended change in the reader's understanding or behavior. Name one primary outcome: prepare for a call, compare options, complete a task or recognize a problem. If there is a business objective, state it separately. A request to generate leads does not tell a writer what the article should teach.

2. Audience

Describe the reader's role, immediate situation and existing knowledge. Include a constraint that affects the advice, such as limited time or lack of specialist support. Avoid a broad demographic description when the practical distinction is experience. A first-time team lead needs different explanations from a person redesigning an established process.

3. Angle

State the central answer or proposition in a sentence. Explain what this piece will focus on and which adjacent questions belong elsewhere. The angle should help the freelancer decide what to leave out. If the brief contains several competing angles, select one before production or commission separate pieces.

4. Sources

List the documents, interviews and other evidence available to support the piece. Explain what each source can establish, who owns it and whether it can be quoted publicly. Mark outdated or provisional material. Ask the freelancer to flag an unsupported claim rather than fill the gap with a plausible number.

5. Must-include points

Specify the information the reader needs to complete the task. Keep these points concrete enough to check. “Be actionable” is not a required point; “include the questions to ask before assigning an onboarding owner” is. Mark priorities so a creator can resolve a space constraint without treating every suggestion as mandatory.

6. Format

Name the deliverable and its structure. An article may need descriptive headings and a copyable checklist. A video may need a shot list, spoken script and on-screen text. Say whether the assignment includes the supporting assets, such as a thumbnail or social caption, and which file formats the recipient can use.

7. Length

Set an editorial range or duration that fits the planned destination and the depth of the task. Explain whether it is flexible. Length should help with scope, not serve as a substitute for usefulness. Google Search Central's helpful-content guidance explicitly says Google has no preferred word count. Choose enough space to answer the question you have actually assigned.

8. Examples

Link one or two relevant examples and explain the feature to borrow: perhaps the clarity of a diagram or the way an introduction identifies the reader's problem. Also identify anything that should not carry over. A sample can be useful for structure while being entirely wrong for tone, level of detail or subject matter.

9. Acceptance criteria

Describe the observable conditions for completion. These could include a worked example, source links attached to factual claims and a checklist that can be used without reading another document. Include the reviewer and submission method. Avoid criteria such as “make it engaging” unless you can explain what a reviewer will actually look for.

A weak brief and an improved version

The following worked example is hypothetical. It concerns an article for a small software company's customer success team; the company and assignment are invented to show how the template works.

Weak brief

“Write 1,200 words about customer onboarding. The audience is businesses. Make it authoritative, friendly and useful. Mention our platform and include best practices. Use a style like our competitors. Send it next week.”

The freelancer must now choose the reader, decide what onboarding means and invent a standard for “best practices.” The platform mention could become a passing reference or dominate the piece. Even the deadline leaves the delivery day and review expectations unresolved.

Improved brief

• Goal: Help the reader prepare and run a first onboarding call that ends with an agreed next action.
• Audience: A newly appointed customer success manager at a small B2B software company, handling onboarding without a dedicated implementation team.
• Angle: Organize the first call around the customer's intended outcome and the information needed to assign the next task.
• Sources: Use the approved sample call agenda and interview the customer success lead. Treat internal customer notes as background only; ask before quoting anything from them.
• Must-include points: Preparation questions, a suggested call sequence, how to assign an action owner and a sample follow-up message. Explain what to do when the customer cannot answer a question.
• Format: An article with descriptive headings, a copyable agenda and one clearly labeled hypothetical call example. Supply an editable document.
• Length: Aim for 1,100 to 1,400 words. Ask before expanding the assignment if the example needs more space.
• Examples: Use the supplied help article as a model for short explanations. Do not copy its product-specific instructions.
• Acceptance criteria: A reader can prepare an agenda and write a follow-up using the included material. Source factual claims, label the invented example and avoid promises about retention. Submit Thursday for review by the customer success lead.

The improved version still leaves room for editorial judgment. The freelancer can choose an opening scene or a clearer heading. The decisions that would otherwise trigger a rewrite are now visible: the audience, the task, the required example and the role of the product.

Resolve questions before the draft

Ask the freelancer to read the brief and send back a short interpretation of the assignment. Have them identify missing sources and any conflict between the angle and required points. For a complex piece, approve a short outline before asking for a full draft.

If two stakeholders want different outcomes, settle that disagreement internally. A freelancer cannot reliably reconcile a product team's feature list with an editor's practical tutorial unless someone decides which takes priority. Record the decision in the brief so later reviewers see the same agreement.

Review against the agreed assignment

Read the first draft once as the intended reader, then compare it with the acceptance criteria. Group feedback into factual corrections, missing requirements and optional improvements. Explain the problem before prescribing a rewrite; the freelancer may have a better way to fix it.

When the business direction changes, update the brief and agree on the new scope. Keep a short note about which instructions caused confusion so the next commission starts with a better template. Use the template on the next commissioned piece, and make the first improvement based on a real question from its writer or creator.