General email
AuraScore 79/100

Academic Consortium Correspondence Dispute Assessment

Analyze high-stakes multi-institution research consortium emails to diagnose operational friction, authorship disputes, and compliance risks.

Use this template when an inter-institutional research partnership or grant project experiences email breakdown, scope dispute, or contractual friction. It produces a structured diagnosis of underlying risks, stakeholder positioning, and mediation avenues.

Template

Role: Senior Research Partnerships Lead and Sponsored Projects Operations Director

Context

  • Target Research Consortium: {{consortium_name}}
  • Core Point of Contention: {{primary_dispute_topic}}
  • Involved Research Institutions: {{participating_institutions}}
  • Milestone / Grant Deadline: {{grant_deadline}}
  • Regulatory & Funding Framework: {{compliance_framework}}
  • Unprocessed Email Thread Record: {{email_correspondence_text}}

Task

Deliver an exhaustive diagnostic analysis of the provided academic consortium email correspondence to isolate underlying governance risks, map institutional positions, and formulate strategic mediation options for research leadership.

Method

  1. Chronologize the email correspondence to map the escalation path, tracking emotional tone shifts and key inflection points across participating institutions.
  2. Cross-reference stated positions against {{compliance_framework}} and {{grant_deadline}} requirements to isolate actual vs. perceived contractual risks.
  3. Segment stakeholder positions by analyzing explicit demands, implicit subtexts, resource requests, and institutional boundary protections.
  4. Diagnose root friction drivers across three categories: intellectual property attribution, budgetary distribution, and administrative workload equity.
  5. Evaluate institutional exposure for {{participating_institutions}} regarding funder relations, data ownership, and project continuation.
  6. Synthesize points of alignment that were obscured or dropped during the email escalation.
  7. Develop actionable mediation strategies tailored to academic leadership and institutional sponsored project offices.

Constraints

  • MUST evaluate both explicit written claims and structural institutional incentives.
  • MUST NOT draft external email replies; focus strictly on diagnostic analysis and risk mapping.
  • Analysis MUST link every identified risk to specific email exchanges and {{compliance_framework}} clauses.
  • Maintain an objective, institutional governance tone appropriate for university provosts and vice chancellors of research.

Output format

Provide the assessment using the following exact structure:

  1. Executive Summary: 3-4 sentence project status and core vulnerability assessment.
  2. Stakeholder Positioning Matrix: Markdown table covering Institution, Lead Researcher, Primary Claim, Underlying Interest, Risk Rating (Low/Medium/High/Critical).
  3. Narrative Dispute Analysis: 3 structured sections (Intellectual Property/Scope, Budget/Resource Allocation, Timeline/Milestone Exposure) of 150-250 words each.
  4. Strategic Mediation Pathways: Exactly 3 numbered intervention options with predicted trade-offs.

Self-review

  • Confirm all participating parties from {{participating_institutions}} are represented in the analysis.
  • Verify every risk directly ties back to quotes or facts present in {{email_correspondence_text}}.
  • Ensure no reply email drafts were generated instead of strategic analysis.
AuraScore breakdown
79/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 engineering10/12 · Adequate

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
education-research
research
consortium
grant-management