General email
AuraScore 81/100

Multi-Institutional Grant Consortium Communication Checklist

Verify cross-institutional research communications for intellectual property, data governance, and milestone compliance.

Use this checklist when coordinating complex research deliverables across university or institutional consortiums. It ensures outbound emails protect intellectual property, clarify accountability, and meet strict grant deadlines.

Template

Role: Principal Research Operations Director specializing in cross-institutional academic consortia and federal grant administration.

Context

  • Participating institutional partners: {{consortium_partners}}
  • Applicable data governance charter: {{data_governance_protocol}}
  • Targeted grant milestone: {{grant_milestone_target}}
  • Working draft email: {{draft_email_content}}
  • Binding decision deadline: {{decision_deadline}}
  • Intellectual property terms: {{ip_sharing_terms}}

Task

Produce an exhaustive multi-institutional communication readiness checklist that evaluates {{draft_email_content}} to ensure unambiguous milestone alignment for {{grant_milestone_target}}, total compliance with {{data_governance_protocol}}, and complete protection of rights under {{ip_sharing_terms}}.

Method

  1. Cross-examine {{draft_email_content}} against {{grant_milestone_target}} deliverables to ensure all required technical obligations are specified.
  2. Review all data-sharing requests in the draft against {{data_governance_protocol}} for transfer compliance and security protocols.
  3. Audit collaborator attributions, authorship claims, and proprietary data disclosures against {{ip_sharing_terms}}.
  4. Evaluate {{consortium_partners}} representation to confirm appropriate institutional points of contact and signatory authorities are engaged.
  5. Verify that {{decision_deadline}} includes necessary timezone specifications, sign-off mechanics, and default contingency pathways.
  6. Generate an itemized checklist categorized by Governance, Technical Commitments, Data Security, and Action Items.
  7. Provide an annotated revision of the draft containing bracketed institutional flags and confirmation tags.

Constraints

  • The checklist MUST include explicit verification of institutional signatory authority for all {{consortium_partners}}.
  • You MUST NOT permit unencrypted transfer of restricted datasets in draft instructions.
  • Action items MUST specify a single institutional owner rather than shared multi-institutional ambiguity.
  • Technical milestone requirements MUST align strictly with published funding agency guidelines.

Output format

Structure the final response into these sections:

  1. Consortium Readiness Scorecard (table with Category, Audit Item, Status [Ready/Blocked/Needs Clarification], Impact Assessment)
  2. Actionable Pre-Send Verification Checklist (10-15 granular pass/fail checkpoints categorized by operational area)
  3. Optimized Email Blueprint (revised email text with clear callouts for milestone dependencies and {{decision_deadline}})
  4. Partner Sign-Off Tracking Grid (table listing partner, required response, and escalation timeline)

Self-review

  • Check that all institutions listed in {{consortium_partners}} have designated action items.
  • Confirm that data exchange language strictly adheres to {{data_governance_protocol}}.
  • Ensure the revision eliminates open-ended commitments that could cause grant default.
AuraScore breakdown
81/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering12/12 · Strong

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency5/10 · Thin

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness3/5 · Adequate

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

emails
emails-general
research-productivity-operations
research
grant management
consortium communication