Project Brief Generator

Create a clear project brief with outcome, audience, deliverables, constraints, ownership, approval, and acceptance criteria.

Shape the result.

Convert a loose request into a brief the client, delivery team, and approver can review together.

Drafts save privately in this browser.

Use the output as a decision draft.

Start with the change

Describe the business or client outcome before listing outputs.

Make scope testable

A deliverable needs acceptance evidence, an owner, and a boundary.

Name decision authority

Contributors can advise, but the final approver must be explicit.

Record uncertainty

Assumptions and missing information belong in the brief before they become schedule risk.

What to know before using it.

What is the difference between a project brief and a creative brief?

A project brief governs the wider outcome, scope, ownership, timing, and acceptance. A creative brief goes deeper on audience, message, brand, format, and creative direction.

Who should approve the brief?

Use the person authorized to accept scope, priorities, timing, and commercial consequences for the client or sponsoring team.

Should assumptions be included?

Yes. Mark them as assumptions, name who must verify them, and avoid treating them as agreed facts.

Turn the draft into live work.

Continue in Stelaah when the result needs owners, client context, decisions, files, dates, and progress.

Continue in Stelaah