How to Write a Content Brief: Field Provenance and the Limits of Writer Discretion

CONTENT BRIEFH1 AND SUMMARYH2 + FORMAT CODEANSWER FIRSTLINK + ANCHORFSPAADEFLSTEXA

A content brief in a semantic content network is the document that transfers structural decisions from the topical map to the writer so that no decision is made twice. Three documents are routinely mistaken for briefs: the outline, the keyword sheet, and the competitor summary, and none of them transfers a decision. The rule that separates a brief from those three is provenance: every field in a brief traces to an upstream artifact, and a field the briefer invented is a decision being made in the wrong place. Eleven fields carry the brief, and each has one source, which is either the topical map or the query network. Leaving a field empty has a specific and predictable cost rather than a general one, and the cost is paid by the network rather than by the article. The brief ends where the prose begins, and the writer holds full discretion over everything the brief does not name. A brief is checked before writing starts by verifying provenance on every field. A worked example then shows the brief fields behind one of Holistic Radar’s own service node pages. The closing questions cover whether a brief is required, whether it improves rankings, and brief length, AI drafting, and outer section briefs.

What a content brief is here

A content brief in a semantic content network is the document that transfers structural decisions from the topical map to the writer, so that no structural decision is made twice.

Topical maprows andclassesQuerynetworkclusters andsequenceContentbriefdecisionsfixedWriterprose onlyPublishedpageno decisionmade twice
Figure 1 · The brief moves decisions from map to writer

Structural decisions are the ones that affect other pages: which questions this URL answers, which angle it takes, which terms it uses, which pages it links to, and where it forwards the reader. Each of these is decided once, at map level, with the whole network visible. The brief carries those decisions to the person writing.

The definition here is a narrower definition than the industry’s. A brief here is not a set of instructions about how to write well. A brief is a transfer mechanism for decisions already made, and every field in it exists because that decision otherwise gets remade at the desk by someone who can see one page.

The three documents mistaken for briefs

Three documents are routinely delivered as content briefs, and none of them transfers a decision.

The outline. A heading structure with notes beneath each heading. An outline specifies what the article says and specifies nothing about how the article relates to the other four hundred. Two outlines produced independently for adjacent attributes overlap, because neither writer sees the other’s.

The keyword sheet. A primary term, a list of secondary terms, and a target word count. A keyword sheet is an instruction to include strings, which is the practice semantic SEO replaced. A keyword sheet cannot express page scope, link direction, or forward targets, because a list has no relationships in it.

The competitor summary. An analysis of the top three ranking pages with an instruction to cover what they cover and add more. This document guarantees the absence of information gain, because its explicit standard is the contents of the index. An article written to it is a better version of something the index already holds.

All three are useful documents. None is a brief, because a brief’s job is to prevent a decision from being made twice and these three make no decisions at all.

The provenance rule

Every field in a content brief traces to an upstream artifact, and a field the briefer invented is a decision being made in the wrong place.

WHERE THE ELEVEN BRIEF FIELDS COME FROMTopical map5 fieldsQuery network4 fieldsMap and network1 field: entity vectorPublisher’s own source1 field: information gainA field the briefer invented is a decision made in the wrong place
Figure 2 · Every brief field traces to one upstream source

The rule is checkable. Take any field in a brief and ask which document it came from. If the answer is the topical map or the query network, the field is valid. If the answer is that the briefer decided it while writing the brief, the decision has been made at page level and the network’s consistency depends on that person making the same judgment on every other brief.

Provenance is what makes briefs reproducible across writers and across months. Two briefers working from the same map produce compatible briefs. Two briefers working from their own judgment produce a network whose consistency degrades in proportion to how many people touched it.

The practical consequence is that a brief cannot be written before the map exists. A brief produced without a map is an outline with more fields.

The fields and their sources

Eleven fields carry a content brief, and each has exactly one upstream source.

FieldSourceWhat it fixes
Source attribute, with its classificationsTopical mapWhich map row this URL discharges
Contextual vectorTopical mapThe single angle, preventing drift and cannibalization
Predicate and sectionTopical mapWhether the page serves the informational or transactional predicate
Source query clusterQuery network, correlative signalPage scope: which queries share this URL
Question inventory, orderedQuery network, annotation layerWhich question types the page answers and in what order
Entity vector, orderedTopical map and query networkWhich entities appear and in what sequence
N-gram vocabulary, lockedQuery networkThe exact term forms, with synonym rotation forbidden
Sequential forward targetsQuery network, sequential signalWhich next queries the page answers or links to
Internal link targetsTopical map, link graphWhich pages this URL links to
Bridge target and justificationTopical map, path signalWhere the page forwards relevance
Information gain elementThe publisher’s own sourceWhat this page contains that the index does not

Ten of the eleven come from the map or the network. The eleventh, the information gain element, is the only field that originates with the publisher, and it is the field most often left blank.

What an empty field costs

Each empty field has a specific downstream cost, and the cost is paid by the network rather than by the article.

Field left emptyWhat happens
Contextual vectorThe writer picks an angle. Two URLs eventually pick the same one and compete for the same query
Source query clusterThe writer decides page scope. Scope creeps to fill the word count, absorbing tuples belonging to other URLs
Question inventoryThe article answers questions in the order they occurred to the writer, and the extractive summary contract has nothing to inherit from
N-gram vocabularySynonym rotation appears, because varying vocabulary is what good writing training teaches. One strong lexical signal becomes three weak ones
Sequential forward targetsLinks get placed by topical resemblance, and the reader returns to the search engine for the next question
Bridge targetThe page terminates. Earned relevance stops where it landed
Information gain elementThe article restates the index. This is the most expensive empty field and the least visible, because the resulting page reads perfectly well
COSTContextual vector emptyTwo URLs pick the same angle and competeCOSTQuery cluster emptyScope creeps and absorbs other URLs’tuplesCOSTBridge target emptyThe page terminates; earned relevancestopsHIGHEST COSTInformation gain emptyThe article restates the indexThe cost is paid by the network, not by the article
Figure 3 · Four empty fields and what each costs the network

The pattern is consistent: an empty field is not an omission, it is a delegation. The decision still gets made, by someone with less information, at a moment when the network is not visible.

Where the brief ends and the writer begins

A brief ends where the prose begins, and the writer holds full discretion over everything the brief does not name.

STRUCTUREThe brief fixesWhat the page coversIn what orderWith which termsLinking wherePROSEThe writer ownsThe sentences themselvesEverything the brief does not nameFull discretion inside thestructurevs
Figure 4 · What the brief fixes and what the writer owns

The brief fixes what the page covers, in what order, with which terms, linking where. The brief does not fix sentence construction, paragraph length, examples, analogies, tone, or how a section is opened. These choices are the writer’s, and a brief that specifies them has confused structural decisions with editorial ones.

This boundary matters commercially. Writers refuse rigid briefs when rigidity extends into prose, and they accept rigid briefs when the rigidity is confined to structure and the reason for each constraint is stated. A brief naming the n-gram lock and explaining that synonym rotation splits a lexical signal is followed. A brief listing forbidden words is resented and quietly violated.

One constraint sits on the boundary and belongs to the brief: the first sentence beneath every heading answers that heading with an extractable triple carrying an exact value. The constraint is a retrieval requirement rather than a style preference, and it is the single instruction most likely to be overridden by a writer’s training.

How to check a brief before writing starts

Check a brief in four passes before it reaches a writer.

Pass one: provenance. Name the source artifact for every populated field. Any field whose source is the briefer’s judgment is either corrected upstream or accepted knowingly as a local decision.

Pass two: completeness. Confirm no field is empty. An intentionally empty field is recorded as intentionally empty with a reason, so that its cost is chosen rather than incurred.

Pass three: the vector. Confirm exactly one contextual vector, and confirm the question inventory is consistent with it. A definitional vector with a question inventory full of procedural questions means the vector is wrong or the cluster is.

Pass four: uniqueness. Confirm the source query cluster does not overlap another brief in the same seed cluster. Overlap at brief stage becomes cannibalization at publication and is far cheaper to resolve here.

Four passes take a few minutes per brief and prevent the two failures that are most expensive to fix after publication: cannibalization and missing information gain.

A content brief from holisticradar.com

The brief for the query network research page on this site shows every field traced to a source.

Brief fieldValueSource
AttributeQuery network research: serviceTopical map row
Contextual vectorProceduralTopical map row
Phrase rootquery network researchN-gram vocabulary
Question inventoryWhat it produces, which signals, which data sources, how it compares to keyword researchAnnotated query network
Link targetsTopical map production; Semantic InstrumentsSequence data
ParentSemantic SEO servicesTopical map row
Information gainA worked example from this site’s own query networkUnique attribute

The live page is query network research. The toolkit that fills these fields is Semantic Instruments.

Content brief provenance with Semantic Instruments

Everything above describes one brief. The difficulty is not writing one, and any competent strategist produces a good brief given a good map and an afternoon.

SCALE400 briefsidentical provenance onevery onePEOPLESeveral briefersone standard across peopleTIME18 monthswhile the map is extended
Figure 5 · The scale problem a single brief hides

The difficulty is producing four hundred with identical provenance, across multiple briefers, over eighteen months, while the map is being extended and people are joining and leaving. At that scale the four checking passes stop being a habit and have to become a process, the n-gram vocabulary has to live in one place rather than in each brief, and the source query clusters have to be checked against every other brief rather than against the ones a briefer remembers.

The described setup is a content brief system rather than a brief template. The system holds the vocabulary centrally, derives every field from the map by rule rather than by recall, flags cluster overlap automatically, and refuses to emit a brief with an empty information gain field, so that building topical authority to rank survives the point where more than one person is producing the content.

The four pillars of a content brief

The four pillars of a content brief are contextual vector, contextual hierarchy, contextual structure and contextual connection, and a draft that breaks one returns to the brief stage.

PillarWhat the brief fixesRule
Contextual vectorThe heading sequence from H1 to the final H2One unbroken line of meaning per page, with no tangents
Contextual hierarchyHeading levels by intent weightH2 for primary sub-attributes, H3 for steps and criteria, H4 to H6 for boolean and voice sub-queries
Contextual structureThe answer format of every headingOne format per question: table, ordered list, unordered list or paragraph
Contextual connectionAnchors, link positions and PageRank routingLinks sit in main content, flow from nodes up to seeds, and match target title tags
H1H2H3Vector: one line of meaning from H1to the last H2Hierarchy: H2 primarysub-attributes, H3 steps andcriteriaStructure: one answer format perquestionConnection: links in main content,nodes up to seeds
Figure 6 · The four pillars located on one page

Table constraints inside a brief

A table request in a brief carries four constraints, so the writer cannot improvise the shape:

  1. The exact row and column count, such as 4 columns and 6 rows.
  2. The column headers, named in the brief.
  3. The row order, by prominence or by quantitative value.
  4. A full definition sentence placed directly before the table.
01Exact shapee.g. 4 columns, 6rows02Named headersset in the brief03Row orderby prominence orvalue04Definitionfirstone full sentencebefore
Figure 7 · Four constraints on every table request

IR zones: title tag, meta description, image URL and alt text

IR zones are the auxiliary places a search engine reads to confirm a page’s macro-context, and a brief sets the wording of each one.

Title tagentity and attributepairMeta descriptiontitle echo in first10 wordsImage URLunder 4 tokens, nostop wordsAlt textnames the centralobjectMacro-contextone page
Figure 8 · Four auxiliary zones that confirm macro-context
ZoneBrief rule
Title tagThe raw entity and attribute pair, verbalised with a conjunctive “and”, a plural set, or a hypernym and its hyponyms
Meta descriptionTitle echo in the first 10 words, then attribute expansion and instances, then the micro-context and a call to action
Image URLUnder 4 tokens, no stop words, inverted noun and modifier order, such as /images/topical-map-template.png
Alt textNames the central object of the image, aligned with the section heading, with EXIF data intact

The sentence rules each brief code enforces are set out in microsemantics. Image indexation is checked after publication with the src: search operator.

→ Semantic Instruments: the toolkit that gives every brief field its provenance

Whether semantic SEO works without a meta description

Yes, because Google builds snippets mainly from page content and uses the description only when it fits better. The brief still sets the field, and the semantic HTML for SEO article covers the title and description rules.

Whether semantic SEO works without an image

Yes, because headings and sentences state the entities and attributes, so an image adds a second reading, not the first. The brief sets the image URL and alt text when an image exists, and semantic HTML places it beside its text.

Content brief length, AI drafting, and outer section briefs

Whether a content brief is required

No search engine requires a content brief, and a page can rank without one. The production process requires it, because a writer without a brief decides the entity, the intent, the headings, and the links alone. A page written that way is often correct in prose and wrong in position, which is the failure the brief prevents.

Whether a content brief improves rankings

A brief does not raise rankings by itself. It raises the share of pages that arrive with the right entity, page type, and links, and a ranking depends on those properties.

How long a content brief should be

Length is the wrong measure, because a brief is complete when its eleven fields are populated from their sources and not before. A brief with eleven populated fields is often shorter than a detailed outline and carries considerably more decision.

Prose instructions are the part to cut. A brief that runs long is usually long because it contains writing advice, which belongs in an onboarding document read once rather than in every brief.

Whether AI can write content briefs

AI populates the derivable fields well: source query cluster from a correlation matrix, question inventory from annotated query types, entity vector from extraction, n-gram vocabulary from frequency analysis. The derivable fields are transformations of existing data and automation is more consistent at them than people are.

NOT DERIVABLEOnly thebusiness knowsThe information gain elementWhat the organization knows thatthe index does notDERIVABLEAI populates wellSource query clusterQuestion inventoryEntity vectorN-gram vocabularyvs
Figure 9 · What AI can and cannot populate in a brief

AI cannot populate the information gain field, because that field asks what your organization knows that the index does not, and the answer exists inside the business rather than inside the corpus. A fully generated brief is systematically empty in the one field that determines whether the article was worth writing.

Whether writers should see the topical map

Writers see their own row and its neighbours, not the whole map. The full map invites scope negotiation on every brief, and scope was decided upstream for reasons the writer cannot evaluate from one row.

The neighbouring rows matter, because they show the writer what the adjacent pages cover, which is the most reliable way to prevent overlap that survives the checking passes.

What changes in a brief for an outer section page

Outer section briefs carry the same eleven fields with two differences. The central search intent is not required in main content, because outer pages serve the informational predicate. The bridge target is required rather than optional, because an outer page without a bridge has no reason to exist in a commercial network.

→ Helpful Content: what Google Rewards and How It Is Judged

→ What is a query network: the three signals a keyword list cannot give you

→ How to build a topical map: nine steps, two halves, four failure modes

Frequently asked questions

What should a content brief include?

Eleven fields: the source attribute with its classifications, the contextual vector, the predicate and section, the source query cluster, the ordered question inventory, the ordered entity vector, the locked n-gram vocabulary, the sequential forward targets, the internal link targets, the bridge target with its justification, and the information gain element.

What is the difference between a content brief and an outline?

An outline specifies what one article says. A content brief transfers structural decisions from the topical map so that decisions affecting other pages are not remade at page level. An outline makes no decisions about how the article relates to the rest of the network.

Can AI write content briefs?

AI populates the derivable fields well, including the source query cluster, question inventory, entity vector, and n-gram vocabulary. AI cannot populate the information gain element, because that field asks what the organization knows that the index does not, and the answer exists inside the business rather than inside the corpus.

Should a content brief include a word count?

A content brief states the question inventory rather than a word count, because length follows from the questions the page must answer.

Who writes the content brief?

The strategist who owns the topical map writes the brief, because every field is derived from the map.

Can one brief cover two pages?

One brief covers exactly one URL, because each URL carries one contextual vector.

How to Write a Content Brief in the semantic SEO topical map

How to Write a Content Brief is the brief engineering attribute of semantic SEO, the central entity of the Holistic Radar topical map, and sits in the outer section under the Know predicate.

The outer section holds the page because the page teaches the concept without a direct sale, so internal link equity flows from it to Semantic Instruments, since field provenance leads to the toolkit that establishes it.

→ Microsemantics: the sentence rules a writer applies to every brief

→ Topical Map Template With a Real Worked Example: the rows each brief starts from

Get my free Radar ScanFree Radar Scan