Guest posting depends on handing work to someone else: a writer, an editor, an outreach assistant. The quality of that work depends heavily on the instructions you give, yet many teams treat the instructions as an afterthought. Six beliefs about briefs keep surfacing in conversations with marketers and site owners. Each sounds reasonable. Each is wrong in a way that costs time. Here is what actually happens.
The common thread is simple: a written brief states the result you want, the date, the constraints and what “finished” means. Writers, editors and reviewers all perform better against that, and you will be able to judge the work against criteria set in advance.
Myth 1: “A good writer does not need a brief”
Skilled writers are not mind readers. They are skilled at structure, tone and clarity, but they do not know which pages you want to support, which claims your organisation cannot make, or what the host site’s editor dislikes. An experienced writer often asks more questions than a novice precisely because they know what is missing. A brief answers those questions in advance. The strongest writers tend to welcome one, because it removes the guesswork from the part of the job that is least about writing.
Myth 2: “The more detail, the better”
Length is not the measure. A six-page document of preferences will be skimmed, and the important parts lost. A good brief is short enough to read in a couple of minutes and specific enough to act on. Aim for a single page: the purpose of the piece, the reader, the length range, the date, the budget basis, the deal-breakers and the finish line. If something does not change what the writer will do, leave it out. Precision beats volume.
Myth 3: “Keywords are the brief”
A list of phrases is not a brief; it is one ingredient. Handing over keywords with no purpose produces text that mentions them awkwardly. Instead describe the question the reader is trying to answer, then name one main phrase and where it should naturally appear. Our own pieces on pitching and writing for niche publications show how fitting the host site’s audience matters far more than repeating a term.
Myth 4: “A brief slows everything down”
Writing a brief takes perhaps twenty minutes. A missed expectation takes a revision round, and a revision round takes days. The arithmetic favours the brief nearly every time. Teams that adopt a standard template also find that the second brief takes half the time of the first. If you use content templates already, our write-up on speeding up article structure with standard formats can be adapted into a brief template with little effort.
Myth 5: “Budget talk should wait until the draft is in”
Many people avoid discussing money early, hoping to see the work first. This produces misunderstandings in both directions. The writer may have assumed one scope and priced for it; you may have wanted another. State your basis early: per piece, per word or per project, how many revision rounds are covered, and a range in words if you prefer not to give a number. None of this commits you. It prevents the awkward moment when expectations collide after the work is done.
Myth 6: “If the draft is wrong, the writer failed”
Sometimes the writer did fail. Often the brief did. A fair way to find out is to hold the draft against the page you wrote. If the draft ignored an explicit instruction, that is a writer issue. If it fell short of something you assumed but never wrote, that is a brief issue, and the remedy is to add a line so it does not recur. Treating each miss as a source of one more line in the template steadily improves results, whoever you work with.
What a short, effective brief contains
Replace the myths with a working structure. Six items cover nearly everything:
- Purpose: one sentence on what the piece should help the reader do.
- Reader: who they are and what they already know.
- Shape: length range, headings, and any must-cover points.
- Dates: first draft due, feedback due, final due.
- Limits: budget basis, banned claims, link rules, spelling convention.
- Finish line: what you will receive, in what format, and how revisions are handled.
Put your own name and a contact method at the top so the recipient can ask a question without searching for you.
Applying it to people outside your usual network
Not every helper in a guest posting workflow comes from your existing circle. You may need a subject expert to review a technical draft, a proofreader or a designer for graphics. For those searches, ProfessNow is a marketplace where you start from a profession, pick your city, read the listings and submit a booking request. Because your brief is already written, it can travel inside that request without changes.
A short worked example
Suppose a small software company wants one article for a partner blog about backing up a database. The vague version reads: “Write a guest post about database backups, one thousand words, include our keyword.” The written version says the piece should help a junior administrator understand why restore tests matter, runs nine hundred to eleven hundred words, is due as a draft on the fifth with feedback by the eighth, pays per piece with one revision round, must avoid unsourced statistics, and is finished when a clean document arrives together with a proposed headline and a two-line summary. The second version takes about fifteen extra minutes to write, and in our experience it removes several rounds of email that would otherwise follow.
How to tell whether the brief worked
After each commission, ask three questions. Did the first draft need fewer than two substantial changes? Were there questions from the writer that the brief should have answered? Did both sides agree on whether the job was done? Record the answers next to the brief. After a few rounds you will see exactly which lines earn their place and which can go. That feedback loop is worth more than any generic template.
It is also worth separating two things people confuse: judging whether a guest post is valuable and writing a request for one. The first concerns outcomes after publication; our discussion of weighing the lasting value of a placement addresses it. The second, the subject here, concerns the clarity of what you ask for before work begins. Both matter, and neither substitutes for the other.
Summary
Good writers benefit from briefs. Short briefs beat long ones. Keywords alone are not a brief. A brief saves time overall. Discussing money early prevents conflict. And a poor draft deserves a look at your own page before blame is assigned. Write the page, send the same page to everyone, and keep it with the finished piece. The next brief will be quicker, and the work that returns will look more like what you had in mind.