books, library, jrr tolkien, library books, education, learn, literature, read, study, knowledge, stack, research, hardcover, textbook, indoor, books, books, books, books, books, library, education, study, research
Photo by AnnieSpratt on Pixabay

Operations

Part of What keyword research operations means for content delivery

Why keyword research service standards need a written brief

How to set keyword research service standards in a written brief: scope, evidence, quality checks, sign-off, and a before and after table for deliverables.

What to take away

  • A service standard is a written brief that fixes deliverables, formats, owners and dates. It makes no promise about rankings.
  • Every figure in the output carries a named source and the date it was pulled.
  • Three checks run inside the workflowsource, duplication and compliance. A final read-through is not a check.
  • One named approver, one named rejecter, and a sign-off date written into the brief.
  • A misleading commercial claim can breach the Consumer Protection from Unfair Trading Regulations 2008 (legislation.gov.uk).

What the brief must specify

Scope is the first field. Write the deliverable in countable terms: 200 keyword phrases with intent labels in a spreadsheet, or a 12-month content calendar built from those phrases. Each is a separate deliverable with its own price and owner. When scope stays verbal, the review becomes an argument about memory.

Format comes second. A spreadsheet with columns for phrase, intent, source, pull date and owner survives a handover. A slide deck rarely does, because the reasoning stays with the person who presented it.

Scope: what is in and out

In scope

Deliverable
200 keyword phrases
Format
Spreadsheet with columns
Owner
Named in brief
Price
Set per deliverable

Out of scope

Deliverable
Content calendar
Format
Slide deck
Owner
Unassigned
Price
Separate quote

Boundaries belong in the same section. List what sits out of scope as plainly as what sits in: link building, technical fixes, ad copy, translations. If you need the full sequence from intake to archive, the operations and delivery guide for 2027 shows where each deliverable sits.

Example: a one-page brief skeleton

Seven fields cover most England clients. Copy the list and fill it in before work starts.

One-page brief skeleton

  1. Deliverablename, count, format, file location, owner.
  2. Metric sourcesthe tool or property behind each number, with the pull date.
  3. Intent labelsthe set in use and the rule for assigning one.
  4. Checkswho runs the source, duplication and compliance checks, and when.
  5. Sign-offone approver, one rejecter, the date.
  6. Change requestsprice and turnaround for work outside scope.
  7. Reviewthe date and scope of the first review of the standard itself.

Evidence: naming the source and the date

Each number needs an origin a third party could open. If a volume figure comes from a tool, name the tool. If it comes from a client's Search Console property, name the property and the export date. Google documents the date range, filters and comparison settings in its performance report guidance.

Mixing tool data and client data without labels is how teams end up defending figures they cannot trace six months later. If a difficulty column comes from Ahrefs Keyword Difficulty, say so beside the number, so nobody reads a third-party score as a Google signal.

Three checks before delivery

Run these inside the workflow, not in a final read-through.

  • Source checkevery figure has a named origin and a pull date. A valid source is one a third party can open, such as a tool export, a Search Console report or a published dataset. A number recalled from a call is not a source.
  • Duplication checksort the phrase column, compare adjacent rows, then run one clustering pass so one intent maps to one cluster. Keyword clustering for UK content planning explains how to merge near-duplicates without losing a query.
  • Compliance checknothing in the output claims a result the team cannot evidence.

Three checks before delivery

  • Source checknamed origin and date
  • Duplication checkno phrase twice
  • Compliance checkno unevidenced claims
  • One sign-off owner per deliverable
  • One person who can reject
  • Sign-off date fixed in brief

A misleading commercial practice can breach the 2008 Regulations even when nobody intended to mislead. That is why the compliance line is written down rather than assumed.

Sign-off, change requests and review

Name one person who signs off each deliverable and one person who can reject it. Two approvers with no tie-breaker is a delay waiting to happen. Put the sign-off date in the brief so the review has a fixed point.

Before the brief

Scope
Verbal agreement, changes by email
Evidence
Mixed tool and client data, no dates
Checks
Final read-through by one person
Sign-off
Whoever replies first
Review
Ad hoc after launch

After the brief

Scope
Named deliverables, formats and owners
Evidence
Each figure has a source and a pull date
Checks
Source, duplication and compliance checks
Sign-off
One approver, one rejecter, dated
Review
Fixed review of the standard

Anything outside the brief becomes a written change request with a fixed fee or day rate, a stated turnaround and a revised delivery date. Before launch, test the standard against real pages with the launch review in England, which catches scope gaps and phrases that never reached the plan.

Common questions

How long should the standard be, and who owns it?

One or two pages is enough, short enough that the team reads it before starting work. The delivery lead owns it and the client contact signs it. Without an owner it describes how work used to be done.

What if the client asks for something outside the brief?

Treat it as a change request: written, priced at a fixed fee or day rate, with a stated turnaround and a revised date. That keeps the original standard intact and makes the extra work visible on both sides.

Which check catches a phrase labelled twice?

The duplication check. Sorting the phrase column and clustering once shows two intent labels on the same query, which is usually a scope problem rather than a data problem.

Does this apply outside England?

Scotland, Wales and Northern Ireland have their own arrangements across several areas of consumer and trading law. Check the position for the nation you are trading in before reusing an England brief.

More in Operations