社区参与式研究合作方案规划
围绕社区共同决策提出分工、报酬、伦理及成果回馈方案,相关法律事项交由机构确认。
完整提示词
<context>
Community-based participatory research shares power across the whole project: community partners help set the question, choose methods, interpret results and decide how findings are used. It fails when it is participatory in name only: researchers arrive with a funded question, ask for "input" once, pay community members in gift vouchers for skilled work, publish before the community has seen the results, and leave when the grant ends. Communities that have been studied many times without benefit are rightly wary. Good partnerships start from relationships and the community's priorities, write down how decisions are made and who owns the data, pay people fairly and on time, and plan from the start how findings return to the community and what happens after the project.
</context>
<task>
Plan a participatory research partnership on: {{question}}
<community>
{{community}}
</community>
{{#resources}}
<resources>
{{resources}}
</resources>
{{/resources}}
1. Readiness check: is there evidence the community wants this research, what relationships exist, what history of research the community may have, and what the researcher should do before proposing anything (listen, attend community events, meet existing organisations). Say plainly if the plan should begin with relationship-building rather than research.
2. Partnership structure: a steering or advisory group with community majority or parity, how members are chosen, how decisions are made (consensus, voting, which decisions belong to whom), how disagreements are resolved, and the items for a written partnership agreement (purpose, decision-making, data ownership and access, publication and authorship, credit, conflict resolution, exit).
3. Roles: a table of who does what - community partners, community researchers or peer researchers, academic team, partner organisations - including who can speak publicly about the project.
4. Compensation: pay community researchers as staff or at a fair hourly rate for skilled work, pay advisory members for meetings and preparation, cover costs (travel, childcare, food, data), pay promptly and in a form that suits people (and flag checking whether payments affect benefits or immigration status, as a question for the institution's finance and legal teams).
5. Co-designing the question and methods: how partners refine the question, choose methods that fit the community (including language and literacy), and help design instruments and recruitment.
6. Ethics and data governance: institutional ethics review plus any community review process, consent that is genuinely voluntary in close-knit communities, confidentiality where people know each other, risks of stigma for the community as a whole, data ownership and control (including Indigenous data sovereignty principles where they apply), storage, and who approves secondary use.
7. Capacity building: what community partners gain (training, credentials, paid roles) and what the academic team must learn from them.
8. Timeline: phases from relationship-building to after the project, with decision points that partners approve.
9. Returning findings: community-first sharing before publication, partners reviewing interpretations, accessible formats (events, short reports in the community's languages, visual summaries), and how findings feed into action.
10. Ending well: what happens to data, relationships and any services or tools after funding ends.
11. Questions to take to partners: open questions to decide together, not to answer for them.
12. Before you answer, check that no decision in the plan has been made for the community that the partnership should make together; mark any such item as a proposal.
</task>
<constraints>
- Do not invent facts about the community, its leaders or its history; mark assumptions.
- Write proposals as options for partners to decide, not as settled terms.
- Do not state legal rules on payments, benefits or data protection as fact; list them for the institution to confirm.
- If the community has not raised the issue and no relationship exists, say that the first phase is building one, and keep later phases provisional.
</constraints>
<output_format>
Markdown with the sections in the output contract. Roles and the timeline as tables, the partnership agreement items as a checklist, and the rest as short bullets.
</output_format>可替换内容
- {{question}}
- {{community}}
- {{#resources}}
- {{resources}}
- {{/resources}}
分类与标签
学习教育、社区参与研究、合作治理、研究伦理、成果回馈