How to Write a One Page Project Brief That a Freelancer Can Act On

Quick answer

A one-page project brief works when a freelancer who has never spoken to you can read it once and restate three things: the goal, the audience, and the definition of done. Everything else on the page exists to support those three.

That means the page needs a measurable goal sentence, one audience line with one desired action, a short list of must-haves, an explicit out-of-scope line, a definition of done, and a single review checkpoint date. References go in as links, not pasted text. If a section doesn't help someone decide what to make or when it's finished, cut it.

This guide walks through a six-step workflow, a copyable example for a 30-second bakery opening announcement, a review checklist, and the mistakes that most often turn a brief into either a one-line guess or a five-page document nobody reads.

Why briefs fail in both directions

Small teams tend to produce one of two briefs.

The one-sentence brief — "We need a 30-second video for our bakery opening" — leaves scope, audience, and success criteria implicit. The freelancer fills the gaps with reasonable assumptions. Those assumptions are usually not yours. You get a polished video aimed at the wrong people, or one that spends its runtime on the storefront instead of the product.

The five-page brief has the opposite problem. It contains background, brand history, competitor notes, and pasted paragraphs from a strategy deck. The actual instructions are buried somewhere on page three. Freelancers skim it, extract the parts that look actionable, and miss the rest — not out of carelessness, but because the document doesn't signal what matters.

A one-page brief is not a shorter version of the five-page document. It's a different document: a decision sheet. It answers the questions a freelancer would otherwise have to ask you, in the order they'd ask them.

The six-step workflow

Step 1: Write the goal as one measurable sentence

The goal is not a topic. It's a change you want to cause. Write it as a single sentence with a verb, a subject, and something you could check afterward.

Weak: "Promote the bakery opening." Workable: "Get 150 local residents to save the opening date and visit during opening week."

You don't need a perfect number. You need a sentence where a reasonable person could say "yes, this deliverable serves that" or "no, it doesn't." If you can't attach any measure, describe the observable behavior instead: "Get people who walk past the shop to come in and ask about the opening."

Keep it to one sentence. A second goal sentence usually means you have two projects.

Step 2: Name the audience and the single action

One line for who, one line for what you want them to do after seeing the work.

Audience: People who live or work within a 10-minute walk of the shop and already buy bread weekly. Action: Save the opening date and come in during the first week.

The "single action" constraint matters. If the brief asks the audience to follow, share, subscribe, and visit, the freelancer has to guess which one the creative should be built around. Pick one primary action. Secondary asks can be mentioned as optional.

Be specific enough that the freelancer can picture a real person. "Everyone" is not an audience; it's a reason the work will feel generic.

Step 3: Separate three must-haves from three nice-to-haves

List exactly three must-haves. These are the elements whose absence makes the deliverable wrong. Then list up to three nice-to-haves — elements that would improve it but can be dropped if time or budget runs short.

For the bakery example:

Must-haves

1. The opening date and street name appear on screen and are readable without sound.
2. At least one shot of bread being taken out of the oven.
3. The final frame shows the shop's name and the opening hours.

Nice-to-haves

1. A short clip of the owner speaking to camera.
2. Ambient sound from the shop floor.
3. A version sized for a vertical feed.

The three-and-three limit is doing real work. It forces you to rank. A list of eleven must-haves is a wish list, and a freelancer will treat all eleven as equally optional because they can't tell which ones you'd defend.

Step 4: State what is explicitly out of scope

This is the line most briefs skip, and it's the one that prevents the most rework. Write down what you are not asking for, especially the things a freelancer might reasonably assume are included.

Out of scope: No paid ad versions, no captions in languages other than English, no photography of the interior beyond what's in the linked folder, no revisions to the logo or brand colors.

Out-of-scope lines do two things. They protect the freelancer from doing unpaid extra work, and they protect you from paying for work you didn't want. If you're unsure whether something belongs, put it out of scope and note that it can be quoted separately.

Step 5: Add a definition of done and one review checkpoint

"Done" is not "looks good." Define it as a checklist the freelancer can verify before sending anything.

Definition of done:

• 30 seconds, plus or minus 2 seconds
• Opening date and street name legible on a phone screen at arm's length
• Final frame holds for at least 3 seconds
• Delivered as an MP4 plus a still frame for the shop window
• All three must-haves present; any dropped nice-to-have noted in the delivery message

Then add one review checkpoint date — the date you will give consolidated feedback, not a running conversation. One checkpoint keeps the project moving. Multiple informal check-ins tend to produce contradictory notes that the freelancer has to reconcile alone.

Step 6: Keep it to one page and link your references

If the brief spills onto a second page, the problem is usually pasted material. Move it out.

• Brand colors, fonts, and logo files: link to a shared folder.
• Past work you like: link to two or three examples with one line each on what you like about them.
• Location details, hours, and address: link to the listing or a single reference doc.

A link with a one-line note ("this one for the pacing, not the music") is more useful than three paragraphs of description. It also keeps the page scannable, which is the whole point.

Copyable example: 30-second bakery opening announcement

This is an illustrative brief, not a record of a completed project. Adapt the specifics to your own situation.

Notice what isn't there: no brand history, no competitor analysis, no paragraph about "our passion for sourdough." Those can live in a linked document. The page itself is a set of instructions.

Sample prompt for drafting the brief

If you want help turning scattered notes into a one-page draft, you can use a prompt like this in a document workspace. Treat the output as a draft to edit, not as a finished brief.

The [NEEDS INPUT] instruction is the important part. A draft that silently fills gaps is harder to review than one that shows you where you were vague.

You can draft and revise this kind of structured page in Vife's AI document creator, which is built for working through documents alongside the rest of a project. If you're weighing workspace options, the pricing page lists what's available.

Review checklist before you send

Run this against your draft. Each item is a yes/no, not a judgment call.

• The goal is one sentence and contains something checkable.
• The audience is a describable group, not "everyone."
• Exactly one primary action is named.
• There are exactly three must-haves, and each is verifiable.
• Nice-to-haves are clearly marked as droppable.
• At least one out-of-scope line exists.
• The definition of done lists conditions, not adjectives.
• There is one review checkpoint date, not a vague "as we go."
• All references are links with a one-line note.
• The whole thing fits on one page.

Then do the real test: hand it to someone who hasn't spoken to you and ask them to restate the goal, the audience, and the definition of done. If they can, the brief is ready. If they hesitate, the section they hesitated on is the one to rewrite.

Common mistakes

Mixing must-haves and nice-to-haves. If everything is a must-have, nothing is. The freelancer will either over-deliver and blow the budget or quietly drop items and hope you don't notice.

Writing the definition of done as taste. "Feels warm and authentic" is a direction, not a completion criterion. Pair subjective direction with something observable — a duration, a legibility check, a required frame.

Skipping out-of-scope. Without it, the freelancer guesses where the edges are, and guesses tend to be generous in one direction or the other.

Pasting instead of linking. Long pasted references push the actual instructions off the first screen. Link them and annotate.

Setting multiple review checkpoints without a consolidation rule. If three people can each send notes directly, the freelancer receives conflicting feedback. Name one person who consolidates.

Treating the brief as final. A brief is a working document. If the goal changes mid-project, update the page and tell the freelancer which line changed.

FAQ

How long should a one-page project brief be?

One page, as the name says — roughly 300 to 500 words including the example block. If you need more room, the extra material is usually reference content that belongs in a linked document.

What if I don't have a number for the goal?

Use an observable behavior instead: "get walk-ins to ask about the opening," "get replies to the email," "get three people to request a quote." A checkable behavior is more useful than a vague aspiration, and you can add a number later.

Can I include more than three must-haves?

You can, but each addition weakens the ranking. If a fourth item is genuinely non-negotiable, remove one of the first three rather than extending the list.

Who should write the brief — me or the freelancer?

You should own the goal, audience, and out-of-scope lines, because those are business decisions. A freelancer can help draft the definition of done and suggest realistic checkpoints, since they know what's verifiable in the deliverable.

How do I handle revisions?

State the number of revision rounds and what counts as a revision in the definition of done or a short line beneath it. "Two rounds of consolidated feedback" is clearer than "revisions as needed," and it pairs naturally with a single checkpoint date.

Does a one-page brief work for bigger projects?

It works as the top layer. For a larger project, keep the one-page brief as the decision sheet and link to separate documents for research, brand assets, and technical specs. The freelancer reads the page first and follows links only where needed.

The takeaway

The test of a brief isn't length or polish. It's whether a stranger can act on it after one read. Write the goal as one measurable sentence, name one audience and one action, rank three must-haves above three nice-to-haves, draw the out-of-scope line, define done in checkable terms, and set one checkpoint. Link everything else. That page will save more rework than any amount of added detail.