Your creative workspace

Workspace guide

Writing a brief that survives handover

A brief is not a message to a person who already knows the context. It is the only thing that travels from you to whoever makes the asset. Most rework does not come from bad design work — it comes from a brief that left out one of the four fields below.

Brand / product

Write the name as it appears on packaging, plus the category in plain words. "Suanli Chuhai" alone tells nobody what you sell; "GPU rental brokerage, B2B, English" does. If the product has a regulation-sensitive category, say it here rather than in the notes — it changes what can legally be shown.

Target language

This is a production setting, not a preference. English and Japanese assets are not the same asset with different subtitles: text length, reading direction of the layout, and whether a voiceover is expected all change. Pick one language per brief. If you need three, submit three briefs — a single brief covering six languages produces six half-finished assets.

Scene requirements and selling points

Separate what must be visible from what must be said. "Must be visible: the cable connector, the 8 heat zones" is checkable. "Should feel premium" is not. Three selling points is the practical ceiling for a 15-second asset; five means the viewer remembers none.

Visual / voice style

Name a reference that exists. "Like the Apple Watch product page" is usable; "modern and clean" describes every page on the internet. For voice, state accent and pace, because those two are the most common mismatch between what was ordered and what was delivered.

What happens to a draft

The "Save brief on this device" button writes to this browser's local storage only. Nothing is submitted, nothing is synced to an account, and clearing site data removes it permanently. This is intentional for the drafting stage: a brief often contains an unreleased product name or a price that has not been announced, and those should not sit on a server before you have decided to order.

When you are ready to order, the brief is submitted with the order and becomes part of the project record. From that point it is stored with the order, not with your browser, so it survives a device change.

Uploads, allowances and delivery

File uploads are disabled in the draft stage and unlock for paid projects. The reason is storage cost: a product photo set can run into hundreds of megabytes, and holding that for every abandoned draft is not a cost worth paying. Once an order is placed, the upload slot opens and the assets you provide are attached to that order only.

Project allowances are counted per package, not per file. One AI Product Photos order covers one product with a set number of output images; a second colourway is a second order unless the package states otherwise. The allowance is shown next to each package in the list, before you submit, so the count is never a surprise afterwards.

Delivery arrives as a link, not as an attachment, because video files routinely exceed what email providers accept. The link is tied to the order and to the delivery email you provide at checkout — the same address you use on the delivery page.

Order of operations that avoids rework

1. Write the brief and save it locally. Do not upload anything yet.
2. Read the three selling points back. If two of them could apply to a competitor's product, rewrite them.
3. Pick one target language. Duplicate the brief for a second language instead of widening this one.
4. Only then open the package list and match the package to the deliverable you actually need — photos, video, or voiceover.