How can I show data rigour when I can’t share raw transcripts?
The short answer is that you can demonstrate the quality of your analysis by providing de‑identified excerpts, summary tables, and a clear data‑access protocol that respects the consent limits. Your examiner needs evidence that the coding, theme development, or statistical procedures were applied correctly, not the identifiable text itself. Start by extracting a handful of short, non‑identifying quotes that illustrate each major theme. Pair those with the coding frame you used, and attach a concise audit trail that links the excerpt to the code without revealing participant names or any personal details. If you worked with quantitative data, include descriptive statistics, reliability coefficients, and a screenshot of the analysis output that has been stripped of any ID columns. Finally, write a brief data‑management statement that explains why the full raw set cannot be shared, cites the consent wording, and offers a controlled‑access option (for example, a secure university repository that only authorised reviewers can log into). This combination satisfies most reviewers’ demand for transparency while keeping you within ethical boundaries.
What terminology do examiners expect for data‑access documentation?
Examiner rubrics often list specific terms such as “data provenance,” “audit trail,” “de‑identification protocol,” and “restricted‑access repository.” When you label each component with those exact phrases, the grader can quickly see that you have addressed the required criteria. For instance, under the heading “Data Provenance” you would describe the original collection method, the consent clause that limits sharing, and the date the data were archived. Under “Audit Trail” you list the coding software, version number, and any automated logs that record changes. The phrase “Restricted‑Access Repository” should appear in the section where you outline how a reviewer could request temporary access, including the institutional review board (IRB) approval number and the secure login procedure. Using the exact terminology from the module guide eliminates the need for the examiner to interpret vague language and reduces the chance of a “requires clarification” comment.
Which technical safeguards keep the data confidential yet verifiable?
First, strip all personally identifying information (PII) from any file you plan to share. In qualitative software this usually means removing the “Participant ID” column and any metadata that contains location or demographic details. Second, generate a checksum (e.g., MD5 hash) of the original file before you redact it; include the checksum value in your audit trail so the examiner can verify that the de‑identified version is derived from the original. Third, store the redacted files in a university‑approved secure folder that requires two‑factor authentication. When you provide a screenshot of statistical output, blur or crop out any column that could lead back to an individual record. Finally, attach a short “Data‑Access Request Form” that outlines the steps a reviewer must follow to obtain the full set under a confidentiality agreement. This layered approach shows that you have thought through both the ethical and technical dimensions of data sharing.
How do I address integrity concerns about missing raw data?
Examiners sometimes worry that withholding raw data could hide selective reporting. Counter that worry by supplying a “triangulation matrix” that maps each research question to the specific data source, the analytic method, and the resulting finding. In the matrix, mark each cell with a check‑mark to indicate that the link has been verified. Also, include a brief “limitations” paragraph that acknowledges the consent restriction and explains how it might affect reproducibility, but stresses that the analytical decisions were pre‑registered or documented in a research log. If you used software that automatically records version history (e.g., NVivo, ATLAS.ti, or SPSS), export the log file and attach it as evidence of no post‑hoc manipulation. By providing these artefacts you give the examiner a transparent view of your workflow without breaching participant confidentiality.
What immediate actions should I take to satisfy the examiner?
Below is a quick checklist you can start on tonight. Follow each step in order, and you’ll have a complete package ready for the next review cycle.
- Identify three representative quotes for each major theme, remove any names or IDs, and save them in a separate Word document.
- Export the coding schema from your qualitative software, include version number, and add a column that links each code to the anonymised quote.
- Run a descriptive statistics summary (means, SDs, frequencies) on the quantitative dataset after deleting ID columns; capture the output as a PDF.
- Generate an MD5 checksum of the original raw file and paste the value into the audit‑trail section.
- Draft a one‑page data‑access protocol that cites the consent clause, lists the secure repository location, and outlines the reviewer request process.
- Populate the triangulation matrix (see table) with research questions, data sources, methods, and findings; mark each verified link.
- Attach the software log file that records all analysis steps.
- Send the compiled package to your examiner with a brief note that the raw data remain confidential per consent, but all verification material is included.
| Action | What to Provide | How to Document | Risk Level |
|---|---|---|---|
| De‑identified excerpts | 3–5 short quotes per theme | Label with code and theme; remove IDs | Low |
| Statistical summary | Descriptive tables, reliability scores | Screenshot with file name hidden | Low |
| Audit trail | Software version, checksum, log file | Include in methods appendix | Very low |
| Data‑access protocol | Request form, repository link | Signed by IRB number | Medium |
| Triangulation matrix | Question‑source‑method‑finding links | Mark each cell with ✔ | Low |
You cannot share identifiable data under any circumstance. If the examiner insists on seeing the full set, forward the request to your supervisor or the ethics committee and let them handle the negotiation. Most institutions have a formal process for “data‑access exceptions,” and they will either grant a limited‑view permission or advise you to submit a confidentiality‑agreement addendum. By preparing the de‑identified evidence, the technical safeguards, and the clear protocol outlined above, you protect participants, uphold research integrity, and give the examiner the proof they need to judge your work fairly.