The short answer
A usable brief names the reader, the problem, the proposed answer and the evidence available. Give the editor a clear scope with room for editorial judgment. A list of keywords alone does not explain what the article should help someone do or why the publication should carry it.
A worked example
For a fictional accounting audience, 'remote work productivity' is too broad. 'How a small accounting team can hand off unfinished client work across time zones' specifies a workflow. The writer can now request a handoff example, explain responsibility fields and distinguish a practical process from a generic productivity opinion.
A practical checklist
- Write the audience and outcome in plain language. State what the reader should be able to decide or complete after finishing the article.
- Provide a short outline with evidence required for each section. Identify missing interviews, examples or product facts before assigning the draft.
- Add publication-specific requirements, image permissions, link context and revision ownership. Keep promotional requests separate from the editorial answer.
What to avoid
Avoid asking the writer to repeat a phrase a fixed number of times or to manufacture expertise. If the brief requires customer outcomes, supply real approved evidence; otherwise use a clearly fictional working example. This keeps the article useful without implying an experience the author did not have.
A useful follow-up
How detailed should the first brief be?
Detailed enough to align audience, answer, evidence and scope. Resolve the important unknowns before drafting, then let the editor improve the structure.
