Label the project accurately
Begin with the true context: university assignment, training project, assessed simulation, independent project or group coursework. Do not place it under Employment unless it genuinely was employment. A Projects or Practical Training section gives the work room to be evaluated on its merits. Include the course or provider, dates and a concise project title. Accurate labelling prevents confusion while still allowing you to demonstrate tools, analysis and outputs that match a vacancy. It also prepares you to answer questions about supervision, assessment and whether the task involved a real organisation.
Recover the original brief
Find the instructions, marking criteria, dataset and permitted feedback. Summarise the problem, audience, constraints and expected deliverable. Employers need this context to judge difficulty. If the brief contains protected or licensed material, create a private summary instead of publishing it. State whether data was real, fictional or anonymised. The brief defines the starting point and stops the final output being mistaken for work completed in another setting. Keep the original securely where permitted so later CV versions can be checked against the same source.
Identify decisions, not only software
List the choices you made: how you structured the task, checked information, selected an approach and responded to limitations. “Used Excel” is weak evidence. Explaining that you reconciled records, investigated exceptions and documented corrections demonstrates applied judgement. Choose two or three decisions relevant to the target role. Keep deeper technical detail available for interviews, but make the CV bullet understandable to a recruiter who may not use the tool daily. Tools matter because of what you accomplished and checked with them, not because their names appear in a skills list.
Use feedback and revision as proof
Record the feedback, change made and resulting improvement. Grades can provide context, but rarely explain capability alone. Revision demonstrates that you can receive direction and improve quality. Do not reproduce a tutor's private comments without permission. Summarise the principle, such as clearer assumptions, stronger checking or better communication. If no feedback was supplied, perform a structured self-review against the brief and document corrections honestly. Showing that an early approach changed for a reason often provides better interview evidence than presenting the final file as if it appeared perfectly on the first attempt.
Create a safe portfolio version
Remove names, student numbers, licensed material, hidden metadata and any data you cannot share. Check course rules before publishing assessed work, especially where future learners could copy it. A private interview version may be more appropriate than a public webpage. When the original cannot be used, rebuild a demonstration with invented data and explain its relationship to the course project. Protecting assessment integrity and information is part of professional judgement. Test every link and file as an external reader so private comments or inaccessible permissions do not undermine the sample.
Write evidence-based CV bullets
Combine action, tool, output, purpose and a supported result. For example: analysed a fictional transaction dataset in Excel, investigated reconciliation exceptions and produced an audit-ready summary against an assessment brief. Avoid commercial outcomes that did not occur. A high mark may be stated if accurate and relevant, but it should not replace the work description. Tailor emphasis to each vacancy without changing facts. Keep a longer private version so a concise CV bullet can always be traced back to the original project, files and feedback.
Prepare the interview story
Build a private situation, task, action, result and learning record. Be ready to explain what was difficult, what you would change and which elements were individual or shared. Connect the project to the employer's requirements while preserving the distinction between learning and employment. Review the evidence before applying and test every claim against retained files. A course project becomes credible career evidence when context is clear, contribution is specific, information is handled responsibly and limits are honestly stated. The goal is not to make coursework sound like a job, but to reveal relevant capability.
Evidence principle
Use a claim only when you can explain it clearly, label its context accurately and support it without exposing confidential information.