How to brief a project so it runs smoothly

A brief is the short document that tells everyone what we are making, who it is for, and what done looks like. It does not need to be long or formal. It needs to be clear. A good brief turns a request into a shared plan, so the work starts in the right direction and stays there. A weak brief leaves gaps that get filled with guesses, and guesses cost time.

This guide covers what to put in a brief, the gaps that most often slow projects down, and how briefs travel with your order inside the Fortuna Media client portal.

What a good brief includes

Start with the goal. Say what outcome you want and why it matters, in one or two sentences. A goal like "more enquiries from the contact page" gives us something to aim at; "refresh the site" does not. Then set the scope. List what is included, and just as important, what is out. If a homepage redesign does not cover writing new product copy, say so now, before anyone assumes it does.

Next, name the audience. Who reads this, and what do they need to understand or do. Add examples and references: a few links or screenshots of work you like, and a note on what you like about each. Gather your assets in one place — logos, current copy, brand colours, and any logins or access we will need. Finally, give a realistic deadline and a budget range. Both shape the choices we make, and a real constraint is more useful than an optimistic one.

The brief checklist

• Goal: the outcome you want, in one or two plain sentences
• Scope: what is included, and what is deliberately left out
• Audience: who this is for and what they need from it
• Examples and references: links or screenshots, with a note on why
• Assets and access: logos, copy, brand details, and any logins
• Deadline and budget: a realistic date and a range to work within
• Decision-maker: the one person who can give final sign-off

Common gaps that slow projects down

A few patterns cause most delays. Vague goals are the first: when the aim is fuzzy, every draft is a guess, and feedback turns into a long back-and-forth. Missing assets are the second; work pauses while we wait for a logo file or a password that only one person holds. The third is having no single decision-maker. When three people send conflicting notes, someone has to reconcile them, and that someone is usually waiting on a reply.

The fourth is moving scope. Adding "one small thing" mid-project is normal and often worth doing, but each change has a cost in time and budget. The fix is not to freeze the work; it is to name changes as changes, so we can adjust the timeline and the estimate together rather than quietly absorbing them until the deadline slips.

How briefs work in the portal

In the Fortuna Media client portal, the brief lives with the work. You send it along when you place an order, and it stays attached to that project, so the team doing the work is reading the same instructions you wrote. There is no separate email thread to dig through and no version that drifts out of date.

From there, delivery is tracked end to end. You can see the project move through its stages, add notes or assets if something was missing, and review what comes back against the brief you set. Each charge for the work produces an invoice, drawn from the funds on account for the services you order. A clear brief at the start is the single thing most likely to make the rest of it run smoothly — spend twenty minutes on it, and you save hours later.