Most briefing problems come not from a lack of information but from an assumption that the other person shares your context. You know your business inside out. You know what your emails usually sound like, what your documents typically look like, what tone you take with different types of clients. Your support specialist does not — at least not yet. A good brief bridges that gap.
The four things every brief must contain
What the task is
This sounds obvious but is often where briefs fail. "Can you sort out my inbox?" is not a task brief. "Please monitor my inbox daily, respond to any general enquiries using the templates in the shared folder, flag anything from existing clients for my attention, and archive anything that does not need a response" is a task brief. Be specific about what you want done, not just the general category it falls into.
What a good outcome looks like
The clearest way to brief any task is to describe the finished state. What will be true when the task is complete? "The inbox will have no unread emails, any that require my personal response will be in a folder called 'Needs Rosanna', and I'll have a short daily summary of what came in." This gives your support specialist a target to aim at rather than a process to guess at.
The context they need
Context is everything. The same task might need to be done completely differently depending on who it is for, what the relationship is, or what is happening in your business at the time. "This client has been with me for three years and prefers very informal communication" is context that transforms how an email gets written. "This document is going to a prospective client we have been pursuing for six months" changes how carefully a proposal gets formatted. Share the context that changes how the work should be done.
The deadline
Every brief needs a clear deadline. Not "when you get a chance" or "sometime this week" but a specific day and time. Without a deadline, tasks get prioritised by default according to the support specialist's judgement — which might be different from yours. A deadline is not a sign of distrust. It is the minimum information needed to manage a workload sensibly.
Before sending any task: What exactly needs to be done? What does done look like? What context matters? When does it need to be ready? If you can answer all four in two minutes, you have a good brief.
Building your reference library
The briefing investment pays the biggest dividends when you build up a library of reusable briefs, templates, and SOPs. The first time you brief someone on how to handle your inbox, it takes twenty minutes. Once that brief is documented and refined, the second time takes two minutes. Over time, the operational knowledge of your business lives in a shared document rather than in your head — which makes everything more efficient and much less dependent on you personally.
Good support specialists will help you build this library as a matter of course. After each new type of task, ask: can we document this process so it does not need explaining again? Most recurring tasks can be captured in a one-page SOP that makes future execution faster, more consistent, and less dependent on your involvement.
The brief you should not skip
The most important brief of all is the onboarding brief — the conversation that happens before any tasks are assigned, in which you share the context of your business, your working style, your non-negotiables, and your preferences. This is the brief that prevents the most mistakes, establishes the right working relationship from the start, and saves the most time over the life of the engagement.
Do not skip it in the interest of getting started quickly. An hour spent on a thorough onboarding brief at the beginning is worth weeks of gradual course-correction later.
We make the onboarding easy
Every new client starts with a thorough onboarding call. We ask the right questions, document your preferences and standards, and then get to work. From £140/month.
See support packages