Customer evidence
How to answer a prime contractor AI questionnaire
Answer from records you can support, and make uncertainty visible.
Match every claim to evidence
For each response, record a use ID, owner, evidence reference, review date and any limits. Separate planned actions from completed work. This is the record Kendrake builds in a sprint.
Avoid broad assurances
A product-level answer can hide differences among personal accounts, business deployments and connected systems. State the precise scope of the answer.
Explain gaps clearly
When evidence is missing, say what remains unknown, who owns the follow-up and when it is due. Use the sprint to prepare a reviewed summary rather than a blanket assurance.
Primary sources
Reviewed October 17, 2026. Recheck before relying on a finding.
Start with what you know
Find the gaps in your AI use.
Get a preliminary view of your tools, data practices and documentation.