Cross-Institutional Research Data Sharing Proposal

Role: Principal Research Scientist and Academic Consortium Director with 18 years leading multi-institutional longitudinal studies.

Context

• Sponsoring Lead Institution: {{lead_institution}}
• Target Partner Institution: {{partner_institution}}
• Study Initiative: {{research_project_title}}
• Data Compliance Standard: {{data_governance_framework}}
• Scope of Requested Cohort Data: {{requested_dataset_scope}}
• Grant or Filing Deadline: {{submission_deadline}}

Task

Draft a high-stakes, collaborative formal research email to senior institutional review board chairs and principal investigators at {{partner_institution}}, securing formal authorization and data transfer terms for {{research_project_title}} ahead of {{submission_deadline}}.

Method

1. Establish the overarching scientific merit and collective grant-funding relevance of {{research_project_title}}.
2. Articulate the exact boundary of {{requested_dataset_scope}}, explaining why partner data is indispensable for statistical validity.
3. Address data security, IRB compliance, and pseudonymization methods under {{data_governance_framework}}.
4. Define explicit co-authorship, intellectual property, and publication attribution frameworks for contributing researchers.
5. Outline a structured data transfer, escrow, and storage architecture at {{lead_institution}} to eliminate audit friction.
6. Provide a linear milestone timeline driving toward the hard cutoff of {{submission_deadline}}.
7. Conclude with clear procedural next steps, offering a technical alignment briefing with data governance officers.

Constraints

• MUST adhere strictly to academic peer etiquette and institutional legal clarity.
• MUST NOT use informal phrasing or vague definitions of data custody.
• Keep email body within 350 to 500 words across three distinct message components.
• Emphasize mutual institutional benefit rather than a one-sided extraction request.

Output format

• Subject line: 1 high-clarity academic subject line with grant or project reference.
• Executive Opening: Context, shared academic mission, and formal proposal context.
• Collaborative Terms & Security: 3 structured bullet points addressing data scope, {{data_governance_framework}} safeguards, and co-authorship.
• Operational Timeline & Call to Action: Hard milestones leading to {{submission_deadline}} and a direct scheduling request.

Self-review

• Did I specifically reference {{data_governance_framework}} compliance mechanisms?
• Are data security, intellectual property, and attribution unambiguously protected?
• Is the tone authoritative yet collegial toward {{partner_institution}} peers?