Define the information learners need, obtain approval from its owner and choose a safer substitute when possible. Set access, storage, sharing and closure arrangements before work starts. A confidentiality statement supports these controls but cannot compensate for giving participants unnecessary or unapproved business information.
Start with the learning question and minimum information
A realistic project does not always require real customer records. Ask which features of the business problem matter educationally. Learners studying incomplete inventory fields may need examples of missing values and inconsistent units, not supplier names, prices and transaction histories. An approved synthetic table can preserve the analytical challenge while avoiding unnecessary exposure. Check that the substitute still supports the intended learning rather than becoming an unrelated exercise.
Identify who has authority to approve the material. A mentor who uses a report daily may not own the decision to share it externally. Make the approval request specific: which fields or documents, which participants, what purpose and what period. Review screenshots, embedded comments, revision histories and file metadata as well as visible pages. Removing an obvious name from a document does not automatically remove all sensitive context.
Make handling instructions practical
Tell learners where the approved files will be stored and which tools may process them. A restriction against public sharing is incomplete if participants do not know whether they can use personal email, generative AI services or public repositories. Agree permitted tools through the relevant institutional and employer process before the task begins. Where approval is uncertain, hold the material back and provide a safe alternative rather than asking learners to make the judgement themselves.
Keep access proportional to the activity. A learner who needs one approved sample should not receive a production account with broad permissions for convenience. State who grants and withdraws access, how questions are raised and what to do if an unexpected file appears. Encourage prompt reporting of accidental exposure. Learners should not investigate a suspected disclosure by copying it to more people or testing how much additional access is possible.
Plan publication and closure from the beginning
Discuss the final presentation and portfolio before learners invest in a particular format. Agree whether an employer representative will review outputs for restricted information and how long that review will take. The academic assessor may need a secure submission route different from the public showcase. Offer a non-confidential summary option so learning can be demonstrated without making sensitive business detail the centre of a learner’s portfolio.
At the end, follow the approved return, deletion and record-retention arrangements. Separate the institution’s necessary assessment records from temporary working copies and employer system access. Document who confirms closure and what remains legitimately retained. Confidentiality, intellectual property and personal-data questions can require specialised institutional advice and applicable local requirements. A short project document should point to that process instead of claiming that one generic agreement settles every possible issue.
Illustrative case: a synthetic returns dataset
Fictional Alder Appliances wants learners to explore why returned products receive inconsistent reason codes. Its first proposed export contains customer contact details, free-text complaints and commercial pricing. The tutor asks which features are needed for the learning question. The authorised data owner creates a synthetic table containing product categories, dates, reason-code inconsistencies and deliberately incomplete records, with no actual customers.
Learners use the institution’s approved workspace and receive a written rule against uploading the sample or employer documents to unapproved external tools. Their public presentation explains the validation method through invented records rather than business screenshots. Before closure, the mentor checks the summary for restricted process details, and the tutor confirms the assessment copy follows institutional arrangements. The case illustrates information planning; it does not establish legal compliance or claim the employer’s returns process improved.
A checklist for your next step
- Identify the minimum information required for the question.
- Obtain approval from the authorised information owner.
- Specify permitted storage, tools and access boundaries.
- Agree output review, portfolio permissions and closure arrangements.
Common questions
Is anonymisation always enough?
No. Combinations of detail, free text or contextual clues may still be sensitive. Ask the authorised information owner to assess the proposed material and consider synthetic alternatives.
Can a mentor approve public portfolio use?
Only if that decision is within their authority. Confirm the approval route and the exact material allowed before learners publish it.
Further reading
These primary resources provide related background. They do not validate the illustrative example or endorse AcadNexus.
AI-assisted drafting and automated technical checks. Examples are illustrative; no independent expert review or real-world outcome validation is claimed. Read our editorial policy.