Brief Validation Gate Before Writer Release (QA)

Brief Validation Gate Before Writer Release (QA)

1. 01

   Confirm the target keyphrase maps to a single dominant search intent

   Pull the top five ranking URLs and label each as informational, commercial, transactional, or navigational. If the set splits across two intents, split the brief into two deliverables rather than forcing one outline to serve both.

2. 02

   Cross-check the brief's recommended headings against at least three competitor pages

   Flag any heading that appears in the brief but has no supporting coverage in the ranking set. Those are usually model inventions, not gaps the client can win.

3. 03

   Verify every semantic term carries a real search or entity signal

   Terms with no volume, no SERP presence, and no entity match get cut. A brief padded with 40 low-signal terms trains writers to keyword-stuff and lengthens the revision cycle.

4. 04

   Read the outline aloud against the client's brand voice guide

   Tone drift is the most common reason a client rejects a draft that is technically optimized. Catch it at the brief stage, when the fix costs minutes instead of a full rewrite.

5. 05

   Check that the brief names a primary conversion action and its placement

   State where the CTA sits, what it asks for, and which page it points to. Writers without this instruction default to a generic end-of-post link that rarely converts.

6. 06

   Log the brief's source data date and re-validation window

   SERP composition shifts. A brief built on a snapshot older than 90 days should be re-run before a writer starts, especially for competitive commercial terms.

7. 07

   Get one named approver to sign off before the brief leaves the queue

   Ambiguous ownership is why briefs sit untouched for a week. Assign a single approver per client account and record the sign-off date in the brief header.