Sponsored Research Data Access Dispute Resolution Checklist
Provide a comprehensive compliance and escalation checklist for resolving grant-funded research repository access disputes.
Use this template when access to sensitive research datasets is revoked, blocked, or disputed between researchers and institutional data stewards. It establishes clear protocols to safeguard grant compliance and intellectual property.
Role: Principal Research Data Compliance Specialist with deep expertise in university grant governance and sponsor data use agreements.
Context
- Host academic/research institution: {{research_institution}}
- Federal or corporate funding agency: {{funding_agency_name}}
- Lead Investigator: {{principal_investigator}}
- Repository security tier: {{data_repository_tier}}
- Core dispute or breach nature: {{compliance_breach_type}}
- Current escalation status level: {{escalation_severity_level}}
Task
Create a standardized dispute resolution and compliance audit checklist that research operations and IT support can immediately execute to resolve repository access deadlocks while upholding {{funding_agency_name}} contractual obligations.
Method
- Analyze {{compliance_breach_type}} against standard governance guidelines applicable to {{data_repository_tier}}.
- Outline legal and compliance verification checks involving Data Use Agreements (DUAs) for {{principal_investigator}}.
- Establish emergency isolation protocols to protect research data integrity without destroying audit trails.
- Design identity and privilege verification checklists for all lab personnel requesting restored access.
- Detail mandatory documentation milestones required by {{funding_agency_name}} prior to restoring pipeline privileges.
- Structure a joint review checkpoint between IT data stewards and {{research_institution}} compliance officers.
- Formulate a final sign-off protocol for complete incident de-escalation and grant file archival.
Constraints
- MUST classify every checklist task by responsible stakeholder (e.g., Research IT, Compliance Officer, Principal Investigator).
- MUST NOT recommend manual data bypasses that violate federal or institutional security rules.
- Verification criteria MUST specify required written documentation or signed addenda.
- All recommendations must preserve data chain of custody.
Output format
Return a structured checklist organized as follows:
- Incident Classification Overview (2-3 sentences referencing severity and grant requirements)
- Stage 1: Legal & Compliance Verification Checklist (4 items with
[ ]) - Stage 2: Repository Security & Identity Audit Checklist (4 items with
[ ]) - Stage 3: Lab Remediation & Access Restoration Checklist (4 items with
[ ]) - Stage 4: Grant File Documentation & Institutional Sign-Off (3 items with
[ ])
Self-review
- Does the checklist directly mitigate the specific risk in {{compliance_breach_type}}?
- Are the regulatory mandates of {{funding_agency_name}} reflected in the audit items?
- Does every task provide an explicit completion criterion for {{research_institution}}?
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.