Guide a reviewer through a researched vendor questionnaire

Why use this

1. A reviewer facing a long vendor questionnaire may spend effort locating basic capability evidence before they can judge any answer. A prefilled yes/no response can hide that the evidence describes a different product tier or an aspirational claim.

2. This job could prepare answer candidates with source pointers and unresolved questions, then keep each answer pending reviewer confirmation. That turns the questionnaire into a reviewable evidence exercise rather than an automatic endorsement of the vendor.

Why an agent / simpler alternative

Useful judgment

Interpret question scope, map evidence to the relevant capability and distinguish verified support from partial or marketing-only claims.

Simpler alternative

Ask the vendor to complete its standard questionnaire when little independent research is needed.

Unsuitable when

The output would certify security, compliance or contractual capability without qualified review.

Proposed inputs

1. Name

   Questionnaire

   Owner

   Evaluation owner

   Minimum scope

   Required questions, definitions and response format

   Quality check

   Identify mandatory evidence and ambiguous terms

2. Name

   Vendor evidence pack

   Owner

   Reviewer or researcher

   Minimum scope

   Permitted documentation with product/tier/version context

   Quality check

   Record source dates and distinguish claims from demonstrations

Access and setup — proposed or unknown

Proposed minimum

1. Read supplied evidence and draft answer candidates privately; no vendor portal submission or account connection.

Compatibility unknowns

1. Current source access, product-tier coverage, tool support and exact runtime compatibility are unknown.

External actions requiring approval

1. Contacting vendors, sharing internal evaluation needs or submitting approved answers requires authorization.

Expected deliverable and review checks

Proposed artifact

Question-by-question draft with evidence pointers, confidence limits and individual approval state.

Critical checks

1. Check answer scope against product/tier; preserve unknowns; require reviewer approval for each answer rather than a blanket inferred sign-off.

Missing output evidence

This overlay adds no new output inspection, execution or validation; consult the referenced canonical source outcome limits.

Failure signals and proposed responses

1. Signal

   Enterprise-only functionality becomes a general yes

   Why it matters

   The evaluation overstates the proposed purchase

   Proposed response

   Qualify the answer with the relevant tier.

2. Signal

   A vendor assertion is treated as independent proof

   Why it matters

   Confidence exceeds available evidence

   Proposed response

   Label attribution and request stronger evidence where required.

Effort and cost — unknown

Setup work

1. Define response standards and evidence requirements.

Ongoing review

1. Reviewer confirms answers and resolves material gaps.

Unknowns

1. Vendor responsiveness, documentation freshness, review effort and research costs are unknown.

First check — proposed, unexecuted

Status

proposed_unexecuted

Synthetic fixture

Invent four questions and three evidence snippets, including a tier restriction and an unanswered requirement; prepare candidate answers only.

Acceptance checks

1. Qualify the restricted feature; leave the gap unknown; mark every answer pending review; submit nothing.

Stop conditions

1. Stop if evidence is insufficient for a consequential certification or disclosure permission is missing.

Limits

1. A researched questionnaire does not establish vendor performance, contractual commitments or independent compliance assurance.