Academic Research Data Governance and IRB Pushback Script

Role: Principal Research Informatics Account Executive specializing in university compliance, data sovereignty, and sponsored research infrastructure.

Context

• Research Institution: {{research_institution}}
• Compliance Stakeholder Role: {{compliance_stakeholder_role}}
• Target Research Project: {{target_research_project}}
• Data Sensitivity Classification: {{data_sensitivity_level}}
• Specific Compliance Objection: {{specific_security_objection}}
• Applicable Governance Framework: {{regulatory_framework}}

Task

Author a rigorous, compliance-focused verbal script that allows a commercial research representative to systematically resolve data sovereignty, privacy, and regulatory roadblocks raised by {{compliance_stakeholder_role}} at {{research_institution}}.

Method

1. Analyze {{specific_security_objection}} through the legal and ethical lens of {{regulatory_framework}}.
2. Draft an authoritative opening response acknowledging the non-negotiable nature of {{data_sensitivity_level}} data protection.
3. Create three clarifying diagnostic questions to isolate whether the concern is encryption architecture, cloud tenancy, or IP ownership.
4. Develop precise technical rebuttal language assuring full institutional data ownership, auditability, and zero commercial data mining.
5. Construct a structured dialogue script showcasing a live negotiation with {{compliance_stakeholder_role}} regarding {{target_research_project}}.
6. Embed clear evidentiary pivots toward standard compliance documentation such as SOC2 Type II, HECVAT, and Data Use Agreements (DUA).
7. Formulate a collaborative next-step ask to initiate a direct security review with the institution's information security officer.

Constraints

• MUST directly reference compliance with {{regulatory_framework}} and handling standards for {{data_sensitivity_level}}.
• MUST NOT make unverified security claims or dismiss Institutional Review Board (IRB) oversight protocols.
• Representative speaker turns MUST maintain an authoritative, compliance-literate technical tone.
• The script MUST distinguish between data storage boundaries and algorithm processing permissions.

Output format

1. Compliance Alignment Brief

• Risk profile overview (2 sentences)
• Security positioning thesis (2 sentences)

2. Multi-Stage Objection Handling Script

• Stage 1: Regulatory Affirmation & Alignment (Representative script)
• Stage 2: Technical Isolation of Objection (Dialogue exchange)
• Stage 3: Data Sovereignty & Audit Architecture Defense (Representative script)
• Stage 4: InfoSec Review & Documentation Hand-off (Call-to-action script)

3. Rapid Compliance Rebuttal Snippets

• 2 succinct verbal responses for data residency and sub-processor inquiries

Self-review

• Does the dialogue demonstrate mastery of academic research security standards?
• Are all 6 input variables integrated into their appropriate technical contexts?
• Does the script establish immediate credibility with {{compliance_stakeholder_role}}?