Build your evaluation evidence before the questionnaire arrives

An analyst questionnaire should organise your evidence. It should not be the moment your company starts looking for it.

The familiar scramble begins with a simple question: can we prove this? Product has a release note. Sales has a promising customer story. Marketing has a slide with an impressive claim. Each describes a slightly different version of the business. The deadline turns those differences into an urgent project.

An evidence register gives the team a shared starting point. Its purpose is practical: connect a claim to something verifiable, give someone responsibility for keeping it accurate, and make the gaps visible early.

Start with claims you already make

Take the claims in your standard company presentation. For each, ask what a sceptical reader would need to see. “Enterprise scale” needs a defined workload and operating conditions. “Fast implementation” needs a starting point, an endpoint and a representative example. “Global support” needs an explanation of what is available, where and when.

Avoid building the register around a questionnaire you have not received. Begin with your business and product evidence. Map it to the actual evaluation criteria when those are available, preserving the wording and scope of the request.

Use a register people can maintain

For each claim, record exactly what you are asserting and where it applies: the product, version, geography and use case. Link to evidence another person can inspect, and distinguish what is available now from a limited release or a roadmap commitment.

Name the person responsible for accuracy and record when they last checked the evidence. Note what can be shared, with whom, and any missing proof or clarification still needed. These details make the register useful when the person who assembled it is unavailable.

Once an evaluation begins, add the relevant criterion, submission deadline and approval owner. Keep the original evidence accessible rather than copying fragments into multiple documents that quickly diverge.

Keep ambition separate from delivery

A roadmap can explain direction. It cannot establish that a customer can use a capability today. Label the difference clearly, including any limits on availability. Apply the same discipline to customer examples: a pilot, a production deployment and a company-wide rollout support different claims.

For an illustrative example, consider a claim that a product supports multi-region deployment. A useful record would identify the supported configuration, documentation, release version and a validated deployment example. If automated failover is planned but unavailable, record it separately. Do not let a broad slide headline merge the two.

Agree who can approve the answer

AR can coordinate the register, but product owners need to validate capability claims and the appropriate commercial owner needs to verify company figures. Customer teams should confirm what a reference can substantiate and whether the proposed use has been agreed. A senior sponsor resolves contested priorities when evidence work competes with other commitments.

This division prevents a common failure: AR becoming the author, verifier and approver of information it does not own. Give every material answer a named validator. Where two sources disagree, settle the discrepancy before submitting the answer.

Keep a dated copy of what was submitted. The working register will continue to change; the submission record needs to show exactly which evidence supported the response at that time.

Prepare for the actual process

The register is an internal working method, not a research firm's scoring model. Forrester, for example, specifies questionnaire, strategy and product demonstration, and customer-reference inputs. Its methodology evaluates products generally available by the questionnaire due date and restricts same-market client engagements with the evaluating analyst from kickoff through publication. Those details affect what you prepare and how you seek clarification. Forrester Wave methodology.

Do not turn a historic engagement timetable into a promise that particular meetings will be available during an evaluation. Record the actual submission instructions, dates and permitted communication routes for the research you are participating in.

Make gaps useful

An empty evidence field is an early warning. It may reveal a documentation problem, an unapproved customer reference or a genuine capability gap. Each needs a different owner and response. Rewriting the sentence will not resolve all three.

Review the register when material releases, deployments or claims change. During an evaluation, reconcile it against the specific instructions you receive. A shared evidence process helps preparation; each research firm's requirements still need their own review.

The immediate test is simple: select five important claims from your presentation. Can the team trace each to current proof without asking around? Start with the ones it cannot.

Share this article