Keep the unanswered question in the customer response
If your software team has an AI customer questionnaire to return, an unsupported yes/no item is work still to resolve. Keep the missing fact, its owner and next update visible instead of making the response look complete before the evidence is ready.
That gap is part of the response work. Record what is unknown, who owns the follow-up and the next update. If the customer's form forces a yes/no choice, ask how it wants the unresolved item handled. A forced field does not create supporting evidence.
For an answer your team can support, keep the exact question, source reference and date, factual owner, limitation and review decision together. Check whether the answer describes the current feature and the question's actual scope. A familiar answer copied from an older request still needs that check.
“Not applicable” also needs a reason. Name the feature boundary and the current evidence behind it. Do not turn an unknown provider practice into a claim that a question does not apply.
Internal readiness and external sharing are separate decisions. A source can help your team answer while remaining restricted to internal use. Share only the description, excerpt or material you are permitted to disclose. Keep private evidence with your team.
The AI Customer Questionnaire Answer Pack supplies an answer/evidence workbook, customer response document, model/data-flow document and owner-request log. You supply and verify the facts. Answers are transferred manually to the response document. The workbook does not automatically clear an old approval when wording changes. Have the reviewer check the revised answer and record fresh approval before use.