Free editorial brief desk

Writing brief generator for reader and promise

Free writing brief generator: settle the reader, promise, claim, evidence, scope, reader action, channel, and a channel-specific definition of done.

A useful brief shows unresolved decisions.Required fields stop an empty brief. Optional gaps remain visible as decisions for the writer or editor. Nothing is uploaded.
EDITORIAL DESK / 02

Make the decisions before the draft

A useful brief exposes uncertainty. Empty optional fields return as named decisions, not invented answers.

Reader and outcome
Argument and proof
Boundaries and delivery
BRIEF PREVIEWDecisions before sentences
Your brief will show what is settled and what is not.

Required decisions stop the form. Optional gaps stay visible so a writer or editor can resolve them.

Agreement before drafting

The writing brief builder assembles eight editorial decisions instead of returning a half-complete form. Topic, reader, promise, and central claim are required. Evidence, scope, and reader action can stay open, but the finished brief names each gap clearly. The definition of done changes with the intended channel.

Use it before you commission work, before you open a blank document, or when review keeps circling. It does not generate a strategy. It makes the current strategy legible enough for a writer, editor, or client to challenge before prose becomes expensive.

A complete artifact

What a resolved editorial brief looks like

Source decisions
Working topic
onboarding emails that survive a product rename
Primary reader
lifecycle marketers at small B2B software companies
Reader promise
they can audit and rewrite a six-email sequence in one afternoon
Central claim
a product rename is incomplete until every lifecycle message reflects the new identity
Evidence or examples
the support-ticket spike after the March rename; twelve emails that still name the old product; last quarter's audit spreadsheet
Scope and non-goals
the six-email onboarding sequence; not sales emails, in-app copy, or the rename strategy itself
Desired action
schedule the audit and assign one owner for the sequence
Channel
Website article
Brief ready for handoff
EDITORIAL BRIEF
Channel: Website article
Readiness: 8 of 8 decisions settled

Working topic
onboarding emails that survive a product rename

Primary reader
lifecycle marketers at small B2B software companies

Reader promise
they can audit and rewrite a six-email sequence in one afternoon

Central claim
a product rename is incomplete until every lifecycle message reflects the new identity

Evidence and examples
the support-ticket spike after the March rename; twelve emails that still name the old product; last quarter's audit spreadsheet

Scope and non-goals
the six-email onboarding sequence; not sales emails, in-app copy, or the rename strategy itself

Desired reader action
schedule the audit and assign one owner for the sequence

Definition of done
Claim checked; sources linked; headings answer reader questions; metadata and accessibility reviewed.

The claim and promise do different work. Read them together before drafting: one says what the reader gains, and the other says what the piece must prove. If either could fit a different article unchanged, narrow it.

The decisions the brief must settle

Reader

Who has the problem and enough context to use the answer?

Promise

What can that reader understand, decide, or do afterward?

Claim

Which central idea is the writer prepared to defend?

Proof

What evidence exists, and which research gap remains?

Boundary

What tempting adjacent subject stays outside this piece?

Delivery

Where will it appear, and what should happen next?

Fill the brief without hiding uncertainty

  1. Fill the working topic loosely

    This field is a placeholder for the subject, not a headline. Write it as you would describe the piece to a colleague. It appears verbatim under the first heading, so a phrase is enough; you will retitle later.

  2. Pick the reader who has the problem

    This field accepts one line. Choose the person with the problem, not the person who approves the budget. If two audiences genuinely need the piece, write the harder one here and note the other under scope.

  3. Separate the promise from the claim

    The promise describes the reader's after-state. The claim states the idea the piece will defend. A reader may be promised a way to audit six emails while the claim argues that naming consistency is part of product trust.

  4. List proof without hiding the gap

    Record facts, sources, observations, interviews, and screenshots already available. The builder copies them unchanged. If this field remains empty, the result labels evidence as a decision still needed rather than pretending the claim is supported.

  5. Set the boundary and the next action

    Use non-goals to remove adjacent subjects the piece cannot cover well. Then name what the reader should do after reading and select the delivery channel. The tool uses that channel to set a relevant quality check.

Best moment

Use it before prose becomes expensive

  • Handing a piece to a freelancer who was not in the room where it was decided - See working with an editor.
  • A draft came back wrong twice and nobody can say precisely what wrong means.
  • You have a folder of research and no agreement on what the piece is arguing.
Honest limit

A brief cannot make the decisions for you

  • It writes no prose and makes no strategic choice. Open optional fields remain marked as decisions, so the handoff cannot hide what nobody has settled.
  • Long documents with several audiences - A book, a report with an executive summary - Usually need a brief per section.

Writing brief questions

What is the difference between a brief and an outline?

+

A brief decides what the piece must achieve and for whom. An outline decides the order it happens in. Write the brief first; an outline built on an undecided promise tends to look reasonable and read hollow.

Do my entries leave the page?

+

Your entries never leave the page. The brief is assembled locally by the script already loaded in the tab, with no request to any server and no record kept between visits. Copy it somewhere durable before you close it.

What goes in scope and non-goals?

+

Name the adjacent subjects the piece will deliberately skip. Non-goals stop the slow expansion that turns a focused guide into a survey nobody finishes, and they give a reviewer fair grounds to refuse an addition.

How strict is the definition of done?

+

The definition changes with the selected channel. A website article checks sources, headings, metadata, and accessibility; documentation checks prerequisites, tested steps, product names, and verification. Treat it as a floor and add specialist review where the risk requires it.

Can one brief cover a series?

+

Yes, if the reader and the promise hold across every part. Write the shared brief once, then add a one-line finish condition per instalment. When the reader changes between parts, you have two series, not one.

Move from the brief to structure and a session

Outline generator

Free outline generator for articles and essays: shape your topic, reader, promise, evidence, and constraint into a guide, comparison, tutorial, or case study.

Focus sprint planner

Free focus sprint planner and timer for writers: calculate setup, protected work, and closing time around one finish line, distraction, and restart cue.

Free to start - No card required

Projects, notes, versioned drafts, imported sources, and careful AI assistance in one private workspace.