Frame a community data sharing request carefully

Community partners often want learner information so they can coordinate support or report progress to a funder. A partnership director can acknowledge that goal while requiring clarity about purpose, data fields, consent, and authorized review. Helpful collaboration does not require casual disclosure of individual records.

Nonprofit director Celia says, "We referred thirty residents to your certificate. Please send us their attendance and grades every month so we can report to our board." Director Marcus responds, "I understand why your board wants to know whether the partnership is reaching people. Before discussing records, can we define the reporting question and whether aggregate information would answer it?" Celia says the board wants to see participation and completion. Marcus continues, "Learner level information has privacy and consent requirements, so I cannot agree to share it on this call. Our privacy and institutional research teams can review a proposed reporting plan. Let us list the measures, audience, and reason for each one, then ask those owners what can be reported." Celia agrees to bring her grant reporting template.

Marcus keeps the partnership moving by asking what decision the data supports. The answer may reveal that counts or a summarized report are more useful than a spreadsheet of names. Privacy review then has a concrete proposal to evaluate.

Take a fictional funder report and mark each requested data field as aggregate, learner level, or unclear. Roleplay a request for a roster. End by naming the review owners and the document they need, rather than making a disclosure commitment.