Monitoring and Evaluation

Use these five templates to define monitoring cases, preserve answers, assess representation, calculate interpretable measures, and select tools. Connect C.1 to Part B’s question map and C.4 to the evaluation commitments in A.1 and A.6.

Replace brackets with actual decisions. The scoring rules are proposed internal conventions; approve and version them before use. All numerical examples are hypothetical. NIST’s AI Risk Management Framework supports documenting test sets, metrics, tools, and evaluation limits; it does not prescribe the GEO scores below.

C.1 Prompt registry

A case is a versioned prompt and its specified context. An observation slot is one scheduled collection of that case in a defined AI experience. Several attempts may be needed to complete one slot.

Registry template

Field

Entry to complete

Identity and purpose

[Case ID/version; B.4 question ID; prompt family; buying/referral decision; owner]

Audience and scope

[Client/referrer role; service; industry; market; jurisdiction; language]

Exact input

[Complete prompt with placeholders resolved; supplied files; full preceding conversation; target answer/turn to score]

Origin and group

[Observed/recalled/researcher-designed; source reference; unbranded discovery/named-firm check/other diagnostic]

Target identity

[Firm/entity; accepted aliases; excluded namesakes or network members; owned domains]

AI experience

[Product; interface; mode; model/version if observable; collection route; supplier]

Conditions

[Location; language; account/subscription; personalization or memory state; search setting; session context; unknown conditions]

Collection plan

[Dates/timezone; frequency; repetitions; ordering; retry rule/deadline; collection-specification version]

Evaluation

[Applicable dimensions; reference-fact version; rubric/dictionary versions; case weight; review method; minimum coverage]

Lifecycle

[Approval; baseline period; effective date; amendment reason; retirement date; replacement case]

Maintain a reference-fact record with the practice owner: [Entity; service boundaries; professionals; markets; qualifications; evidence URLs/files; effective dates; reviewer]. Record uncertainties and verify consequential claims against appropriate evidence.

Use fresh conversations for standalone cases. Preserve all prior turns when evaluating a sequence. Record settings that cannot be controlled instead of assuming equivalence.

Changes and comparability

Approve the case set, repetitions, weights, and reporting rules before collection. Retain the original panel when adding practices or markets; report additions separately.

Change record: [Case/specification; old/new version; reason; effective date; effect on comparison; owner].

Annotate material changes in prompts, product experience, conditions, collection, or scoring. Where feasible, compare methods during an overlap period. If continuity cannot be supported, start a new baseline and retain the history.

A retry completes an existing slot under the agreed rule. Use the first valid capture within the agreed window unless another selection rule was approved in advance. Preserve all attempts; do not keep rerunning until the firm appears. Additional research runs receive separate IDs and stay outside the original panel.

C.2 Answer evidence log

Create one slot record and link every attempt to it. A valid capture preserves the complete target answer from the specified case and conditions.

Evidence template

Field

Entry to complete

Traceability

[Slot ID; case/version; scheduled time; attempt IDs; actual timestamps; collector/tool]

Actual conditions

[Observed product/mode/model; account and location context; deviations from specification]

Raw evidence

[Full answer; prompt/conversation; screenshot or export where useful; storage location; collection time]

Citation inventory

[Displayed links; final destinations; owned/external classification; access-check date/status]

Entity and presentation

[Resolved identity; exact mentions; substantive passages; candidate/exclusion language; explicit list position and list length]

Claim checks

[Claim ID/excerpt; reference evidence; finding; missing qualification; materiality; reviewer/date]

Scores and review

[C.3 codes; reasons; human/automated method; provisional/final status; disagreements and adjudication]

Follow-through

[Issue ID; correction/research action; responsible owner; due date; recheck slot]

Keep raw evidence unchanged. Store annotations and later corrections alongside it. If a cited page changes, distinguish the retained source evidence from its current version.

Collection and review statuses

Status

Treatment

Not attempted

Planned slot remains visible with the reason.

Failed

Technical collection produced no usable answer; retain error and attempt records.

Invalid

Wrong case/conditions or incomplete capture; retain evidence and explain exclusion.

Captured

Valid answer retained, including a refusal, abstention, or answer proposing no providers.

Awaiting review

Captured evidence has no final assessment.

Reviewed

Applicable dimensions assessed; unresolved and inapplicable items explicitly coded.

The first four are mutually exclusive final slot statuses at the reporting cutoff. Without a valid capture, use the last attempt’s failed/invalid status, or not attempted if none occurred. Review status applies separately to captured slots. Failures and invalid captures are missing observations, not zero visibility scores. A valid refusal is an observed answer; score its actual content.

Using a planned review sample when reviewing every answer is impractical. Record the selection procedure and sampling weights. Use random or predefined stratified selection for panel estimates; otherwise describe only the reviewed set. Keep targeted investigations outside headline calculations unless they follow the same selection method.

C.3 Scoring rubric

Score the saved answer against the case and reference facts. Keep dimensions separate; increased visibility can accompany inaccurate or unsuitable representation.

Use U for unresolved assessment and NA where a dimension does not apply. Neither means zero. Record automated labels as provisional until the agreed validation and review requirements are met; identify human-reviewed and automated results separately.

Rubric template

Dimension

Codes and decision rules

Visibility V

0: Firm absent from answer body. 1: Incidental naming. 2: Substantive discussion of services, experience, or fit. Use U for unresolved identity. A citation alone does not establish a body mention.

Candidate consideration K

Yes: Answer proposes or recommends the firm for the stated need. No: It does not. Score only cases designated for provider selection; otherwise NA. Use U for unresolved interpretation.

Accuracy A

2: Required firm-claim checks are complete, claims supported, and necessary qualifications retained. 1: Minor defect without material misrepresentation. 0: Material falsehood or misleading omission. U: Verification insufficient. NA: No assessable firm claim.

Suitability S

2: Evidence supports the stated fit within approved service/market boundaries. 1: Potential fit depends on a material unresolved requirement that the answer accurately identifies. 0: Incompatible or misleadingly asserted fit. U: Evidence insufficient. NA: No positive suitability claim.

Citation presence L

Record links separately as owned or external, with Yes/No/U for owned-link presence. A working link does not establish support for a claim.

Citation support C

For each cited firm-related claim, assess attached sources together. 2: Full support. 1: Partial support. 0: No support or contradiction. U: Unavailable evidence prevents judgment. NA: No applicable cited claim.

Visibility captures prominence, including negative discussion. Preserve whether the firm is recommended, criticized, or excluded. Record numerical position only when the answer provides an explicitly ordered list; paragraph order alone does not establish rank.

Materiality and scoring examples

A material defect could change a reasonable assessment of the firm’s capability or suitability. Examples include invented credentials, fabricated or demonstrably misstated results, incorrect service availability, or misleading jurisdictional coverage.

A known material error produces A0, even if other claims remain unresolved. Otherwise, use U when a required factual check remains incomplete, rather than A1 or A2. An unsupported citation can receive C0 even when independent evidence establishes that the claim is true.

A truthful exclusion receives K No in eligible cases and S NA. Normal engagement acceptance checks alone do not lower supported fit to S1. Missing evidence about capability receives U. Use L U for unresolved ownership; an inaccessible page is not automatically an absent citation.

  • Consulting: An answer describes the firm extensively but invents implementation services: V2 and A0; assess K and S separately.
  • Accounting: Only an owned resource appears in the sources: V0 and owned-link Yes; assess any actual claims separately.
  • Law: A firm is proposed for a jurisdiction it does not serve: K Yes, with A0/S0 where verified evidence establishes the misrepresentation.
  • Engineering consulting: The answer identifies potentially relevant capability but correctly states that a material project-phase requirement needs confirmation: S1.

Reviewer calibration

Have reviewers independently score the same initial answers. Resolve disagreements with reference evidence and record [Original codes; reason; adjudicator; final codes; date]. Include absent firms, ambiguous names, refusals, unsupported citations, and material errors.

Check a continuing sample and professionally review consequential findings. Version rubric changes; rescore earlier evidence consistently or mark the resulting break in the series. These ordinal codes should not be added into a single GEO score.

C.4 Metric dictionary

For each measure, complete:

[Metric ID/version; purpose; unit; eligible case group; formula; evidence source; cutoff; exclusions; aggregation; owner; cadence; baseline; decision threshold and rationale].

Report numerator and denominator, unresolved counts, exclusions, collection coverage, and review coverage. A zero denominator means not calculable.

Core measures

Metric

Definition

Capture coverage

Valid captured slots / planned slots. Show failed, invalid, and unattempted counts separately.

Review coverage

Captured slots with final review / valid captured slots. State the review selection method.

Mention rate

Answers with V1 or V2 / answers scored V0, V1, or V2. Report unbranded and named-firm groups separately.

Substantive visibility

Answers with V2 / answers scored V0, V1, or V2.

Candidate consideration

K Yes / answers scored K Yes or No within eligible provider-selection cases.

Accuracy pass rate

Answers with A2 / answers scored A0, A1, or A2. Show A1, A0, U, and NA counts.

Material error rate

Answers with A0 / answers scored A0, A1, or A2. Report severity and affected cases alongside the rate.

Suitability distribution

Counts of S0, S1, S2, U, and NA; percentages, if used, identify their denominator.

Owned citation incidence

Answers with owned-link Yes / answers with owned-link Yes or No. Include citation-only occurrences.

Full citation support

Cited claims with C2 / cited claims scored C0, C1, or C2. Count each claim once; show U separately.

Qualified inquiries

Distinct inquiries meeting the agreed fit definition in the period. Retain qualification evidence and reported discovery/evaluation influences.

Commercial progression

Distinct opportunities by agreed CRM stage, accepted engagements, and revenue under the firm’s stated recognition convention. Identify the cohort and reporting date.

Accuracy and suitability measures are conditional on assessable claims. Citation-support results exclude uncited claims; they do not establish how much of the answer is evidenced overall. Report cited and uncited claim counts alongside support.

Keep observed AI referrals, self-reported influence, and inferred influence identifiable. Deduplicate inquiries and opportunities; do not add successive stages as separate opportunities. Monitoring movements and commercial outcomes alone do not establish that GEO work caused an engagement.

Worked example

For an unbranded panel, 40 slots were planned. Thirty-six valid answers were captured; three slots failed and one was not attempted. Thirty answers received final review, leaving six awaiting review.

Measure

Result

Capture coverage

36/40 = 90%

Review coverage

30/36 = 83.3%

Mention rate, with identity resolved in all reviewed answers

12/30 = 40%

Substantive visibility

9/30 = 30%

Ten reviewed answers contain firm claims requiring assessment: six score A2, one A1, one A0, and two remain U. The other twenty are NA. Accuracy pass rate is 6/8 = 75%; material error rate is 1/8 = 12.5%, with two unresolved assessments.

These are reviewed-run results. They do not describe all planned slots or establish the frequency of outcomes across real client queries.

Aggregation and decisions

Calculate results within each case before an equal-case or predefined weighted aggregate. Extra repetitions must not silently increase a case’s importance. Preserve approved weights for the comparable headline. If missing cases prevent calculation, withhold it or publish a clearly labeled partial-panel result identifying included cases and revised weights. Withhold the headline when agreed coverage is unmet.

Distinguish missing observations from cases without applicable claims. A case-level accuracy denominator of zero is not calculable; identify whether the cause is NA, unresolved assessment, or missing review.

Keep platforms, modes, markets, languages, and question families identifiable. Compare the same panel and review method; label targeted reviews as diagnostics. Show counts and variation across repetitions, and avoid treating repeated answers as independent clients.

Close each report with [Finding; evidence/limits; correction or experiment; owner; due date; next decision]. Track verified delivery separately from subsequent answer changes.

C.5 Tool assessment

Assess tools against the actual collection and evaluation requirements. Include manual sampling and existing reporting capabilities as alternatives.

Assessment record: [Tool/version; proposed use; assessor; pilot dates; required capabilities; spending/capacity limit; renewal/cancellation deadline].

Assessment worksheet

Criterion

Evidence to request or test

Collection fidelity

What product, interface, or API is observed? Are proxies or generated approximations labeled? Are prompts altered? Which conditions are controllable?

Coverage

Demonstrated support for the required modes, locations, languages, frequencies, and case volumes; documented gaps.

Evidence retention

Full answers, context, sources, timestamps, stable IDs, and usable exports. Test export and confirm retention/access terms after cancellation.

Scoring transparency

Published definitions, entity-matching rules, treatment of missing data, human overrides, and traceable score changes.

Reliability

Scheduled versus completed slots; errors, retries, duplicates, sampling changes, and notification of method changes.

Review workload

Time to verify claims, resolve mismatches, inspect citations, and produce the required report.

Data handling

Authorized access, retention/deletion controls, subcontractor handling, and permitted use of supplied information.

Integration and exit

Export compatibility, account custody, CRM linkage definitions, handover, cancellation terms, and retained records.

Whole-period cost

Setup, subscriptions, usage, storage/export charges, minimum contract commitment, and internal review/administration hours.

For each criterion, record [Essential/desirable; acceptance requirement; evidence; meets/partial/fails/untested; limitation; owner/date]. An essential requirement must be evidenced before relying on that capability.

Pilot and selection

Test collection on a small, predefined case panel under documented conditions. Inspect raw outputs and verify failure handling. A separate manual rerun may produce a different answer; it is not a reliable reference for the vendor’s classification of its earlier answer.

Evaluate scoring against human-adjudicated labels for the same saved answers. If a tool cannot import examples, review its exports and compare those answers with its labels. Include namesakes, negative mentions, citation-only appearances, refusals, and material errors. Record disagreement counts by type and their operational consequences.

Pilot result: [Cases/slots; capture coverage; reviewed answers; classification disagreements; export test; hours used; unresolved limitations].

Decision: [Adopt / limited use / extend pilot / decline]; [purpose; evidence; restrictions; accountable owner; budget; next review].

Prefer the option whose usable evidence and saved effort justify its full cost. Reassess when the firm’s scope, available reporting, or supplier method changes. Record whether to renew, narrow, replace, or stop the tool, while preserving required evidence and maintenance responsibilities.

How to get started

1

arrow-down-blue

Tell us about your project

2

arrow-down-blue

Interview candidates

(We’ll provide bios within 48 hours on average)

3

Select your consultant and start work

Find a Consultant

or email us at: [email protected]