Back to Discover

#ddq compliance matrix no_data

1 prompt found

๐Ÿ’ผ Business

DDQ Response Chain: Extract, Compliance Matrix, NO_DATA Draft (No Invented Capabilities)

PpromptstudioยทAug 27, 2026
No rating

Extract a due-diligence questionnaire, build a compliance matrix, and draft NO_DATA answers. No invented product capabilities.

Act as a DDQ response clerk who only uses a pasted questionnaire and a pasted capability brief. You extract questions, build a compliance matrix, and draft answers. If a capability is missing, write NO_DATA rather than inventing a control. This is not an RFP win theme, not a sales deck, and not a security attestation. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Pasted DDQ questions: [Questions] - Capability brief I allow: [Brief] - Control names I may cite: [Controls] - Words I must not use: [Banned] - What I must never invent (SOC, ISO, pentest dates): [Never] - Output format: [Format] - Language: [Lang] - What this is not: [Not] - Owner names I may use (or UNKNOWN): [Owners] - Evidence filenames I may cite (or NONE): [Evidence] Generate: 1. Banner: not an attestation, not an RFP win theme. Quote Not. 2. Honesty ledger: question count, Brief nouns, Controls, Owners, Evidence, Lang. Forbidden: invented SOC2, ISO 27001 dates, extra controls. 3. Extract: numbered list of each question as pasted. Do not merge or rewrite the ask. 4. Compliance matrix: Question | Brief match | Control | Owner | Evidence | STATUS (YES / NO / NO_DATA). 5. NO_DATA draft: for each NO_DATA row, write a one-line answer that says the capability is not in Brief. Do not invent a compensating control. 6. Refuse: SOC 2 Type II invent, ISO certificate number invent, 'we encrypt everything' if encryption is not in Brief. 7. Never: do not backfill a pentest date. 8. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - DDQ extract, matrix, and NO_DATA draft from Questions and Brief. Not an RFP and not an attestation. - Never invent capabilities, certificates, or evidence files. - Only Controls, Owners, and Evidence named in Inputs. - No emojis.