Inter-Institutional Research Consortium Email Protocol Spec
Standardize cross-university research communications, governance dispatches, and milestone alerts into an actionable operational specification.
Use this template when coordinating high-stakes communication across multiple universities, labs, and funding bodies. It establishes a formal email architecture to keep co-principal investigators aligned on deliverables and ethics compliance.
Role: Senior Academic Consortium Director and Research Governance Lead
Context
- Consortium Identity: {{consortium_name}}
- Sponsoring Lead Institution: {{lead_institution}}
- Participating Partner Sites: {{partner_institutions}}
- Sponsoring Funding Body: {{grant_funder}}
- Regulatory and Ethics Framework: {{compliance_framework}}
- Reporting and Milestone Cadence: {{milestone_cadence}}
Task
Produce an operational email communication specification that establishes standardized broadcast templates, escalation triggers, and compliance reporting messages across all participating research institutions for {{consortium_name}}.
Method
- Audit the governance hierarchy between {{lead_institution}} and {{partner_institutions}} to map tier-specific email distribution vectors.
- Draft three core email archetypes: Quarterly Milestone Reminder, Urgent Ethics/Compliance Alert, and Funder Review Dispatch.
- Specify standard header parameters, mandatory archival tags, and version-tracking subject line conventions for each archetype under {{compliance_framework}}.
- Define pre-approved copy blocks for grant attribution acknowledging {{grant_funder}} and data-sharing mandates.
- Design escalation paths within body copy for flagging schedule slips relative to {{milestone_cadence}}.
- Embed confidentiality disclaimers, data-retention notices, and secure file transfer protocol (SFTP) links into structural footers.
- Establish response-time SLAs and auto-routing rules for principal investigators and institutional review boards.
Constraints
- MUST maintain strict adherence to academic protocols dictated by {{compliance_framework}}.
- MUST NOT include informal conversational idioms or ambiguous action items in broadcast templates.
- All subject lines MUST incorporate standardized bracketed identifiers.
- Output must clearly separate administrative metadata from email message blueprints.
Output format
Provide a technical specification structured as:
- Email Architecture Matrix (Table: Trigger, Sender Persona, Audience, SLA)
- Standard Subject Line Taxonomy (List of 4 mandatory formats)
- Three Complete Email Blueprint Specs (Components: Header, Body Blueprint, Variable Tokens, Footer Requirement)
- Governance & Escalation Rules (Numbered protocol, max 300 words)
Self-review
- Verify that every partner institution tier in {{partner_institutions}} is accounted for in distribution rules.
- Confirm that {{grant_funder}} compliance clauses appear in all external dispatch blueprints.
- Check that all variable tokens use clear bracketed syntax.
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.