Query Architecture Review (Onboarding)
A checklist with 7 steps: Inventory every brand term the client wants tracked, then split the list into owned names, product SKUs, executive names, and misspellings.
By InnovaAI ResearchPublished
What are the steps?
Query Architecture Review (Onboarding)
- 01
Inventory every brand term the client wants tracked, then split the list into owned names, product SKUs, executive names, and misspellings
A single keyword list hides the difference between a trademark you can defend and a generic phrase that returns noise. Separate them so each gets its own query logic and its own review owner.
- 02
Test each candidate query against a 30-day historical window before it goes live
Pull the back window and count how many mentions a human would actually act on. If fewer than roughly one actionable mention per week surfaces, the query is too narrow for a retainer deliverable.
- 03
Set exclusion terms for the client's own handles, internal job postings, and unrelated homonyms
Brand names that double as common words (or as another company's name) will dominate volume until exclusions are written. Document each exclusion with the reason so a reviewer can reverse it later.
- 04
Define the sentiment and intent taxonomy in writing, with two worked examples per label
Labels like 'negative' mean different things to a support team and a PR lead. Two examples per label let a new analyst reproduce the client's classification without a call.
- 05
Confirm language and regional coverage against where the client actually sells
A platform that indexes 25 million sources may still miss the client's primary market language. Map coverage to revenue geography, not to the vendor's headline source count.
- 06
Agree the escalation threshold and the named human who receives it
State the volume, velocity, or severity level that triggers an out-of-hours alert, and name the person on both sides. An alert with no owner is a dashboard nobody reads.
- 07
Record the sampling and retention limits of the chosen plan in the client-facing scope note
Historical depth and query caps vary widely by tier. Writing them into scope now prevents a mid-quarter dispute about why a mention from eight months ago is unavailable.