University projects can provide useful evidence for a first CV when you explain what you personally did, how you did it and why it matters to the opportunity. Start with the job’s requirements, select a genuine project and describe a relevant contribution. Do not turn a classroom activity into invented employment or claim the whole team’s work as your own.
The National Careers Service CV guidance recommends tailoring a CV to the opportunity and notes that first-time applicants can draw on projects, work experience or volunteering. The workflow here develops an optional way to select and describe academic evidence. It cannot guarantee an interview.
Read the requirement before selecting the project
Identify what the application actually asks for. “Communication” might mean explaining technical information, responding to customers or producing clear written records. A project example becomes stronger when it demonstrates the relevant kind of communication rather than merely repeating the word.
Separate required qualifications from skills you can illustrate through experience. A project can show practice with a method or tool; it does not automatically replace a qualification or professional requirement. Check the advert and ask the recruiter where a requirement is unclear.
Choose a small number of requirements to investigate first. For each, write a possible experience and the action that might demonstrate it. This creates a working evidence map. You can discard weak matches before spending time polishing the wording.
Avoid selecting a project only because it received your highest mark. The most relevant example may be a modest task in which you can explain a clear contribution. If you mention a grade, use the accurate result and make sure its inclusion serves a useful purpose.
Reconstruct what you actually contributed
Return to permitted project records: your own notes, the final output, task allocations and feedback. Identify the part you completed and the decisions you made. Do not rely on a vague memory that the group “did some research” if you need to explain your own work.
Separate the context from the action. The context might be a group report on a fictional organisation; your action might be comparing source material, checking conflicting figures or organising a review meeting. The report’s broad topic is not itself evidence of your skill.
Then identify the output or result you can honestly describe. It may be a completed comparison, a tested prototype or a presentation delivered to the class. You do not need an impressive percentage if no valid measurement was made. A precise qualitative outcome is preferable to an invented number.
Keep limits visible. Using a tool in one supervised assignment is different from applying it independently in a professional setting. Describe the level you can discuss and demonstrate. An exaggerated proficiency claim can create difficulties when the recruiter asks a practical follow-up question.
If a project contains confidential or restricted material, describe it at an appropriate general level. Check the relevant rules before sharing files or linking to a portfolio. Being able to discuss a contribution does not automatically mean you can publish the underlying material.
Build the bullet around an observable action
A useful project statement often connects an action, its purpose and an output. This is an organising suggestion, not a mandatory sentence formula. The reader should be able to understand what you did without needing a long explanation of your module.
For example, “Worked in a team” identifies the setting but says little about the contribution. A fictional replacement might be: “Coordinated the review of four draft sections and recorded agreed changes so the group could assemble a consistent report.” This gives the reader an action to evaluate.
Another weak description is “Good research skills”. In a fictional source-comparison assignment, a more informative statement could explain that the student compared the definitions used in several assigned readings and documented differences for the discussion. The claim now refers to visible work.
A technical example might begin as “Used spreadsheet software”. A clearer fictional description would identify the task: “Checked an imported practice dataset for inconsistent category labels and documented the corrections before producing summary tables.” Only use such wording if you actually performed the described work.
These are invented examples, not claims about a real applicant. They show how specificity can replace unsupported self-praise. Adapt the reasoning to your own experience rather than copying activities that never happened.
Distinguish your work from the team’s outcome
Group projects require careful attribution. You can explain the shared task and final product while specifying your responsibility. A statement should not imply that you designed, analysed and delivered everything if those tasks were divided between members.
Suppose a fictional team created a short audio guide. One student researched source material and checked the script’s factual claims; another recorded the narration. The first student can describe research and verification, but should not claim voice recording merely because the final guide contains it.
If you helped resolve a difficulty, describe the difficulty and your response accurately. “Led the team” can be ambiguous. Did you chair meetings, assign tasks with agreement, organise the final review or take responsibility for a particular stage? Use the description that reflects what happened.
Be ready to explain what others contributed. Acknowledging their work does not weaken your account. It shows that your claim has a clear boundary and gives the interviewer a more credible picture of how you operated within the project.
Also distinguish the outcome from your interpretation of its significance. Completing a submission on time is an observable event if your records support it. Claiming that your coordination alone caused the success may be harder to justify. Describe the contribution without overstating causation.
Place the evidence where readers can find it
Use a section arrangement that fits your experience and the application instructions. A project may sit under education, selected projects or relevant experience. Label it clearly as academic work so the reader can distinguish it from paid employment.
Give enough context to identify the activity, such as the project type and your course, without crowding the CV with module descriptions. Select the details that explain relevance. A list of every topic studied can hide the evidence the recruiter needs.
Keep the wording consistent with your application form and portfolio. Dates, project titles and responsibility descriptions should not contradict one another. If an employer requests a particular format, length or anonymised application, follow those instructions rather than a generic template.
Check any portfolio link from the perspective of someone who has not seen the course. Explain the task, your contribution and the status of the work. If access requires permission, do not assume the recruiter can open it. Remove unrelated personal information from shareable material.
Test the entry with a follow-up question
Read each statement and ask, “Could I explain this with a concrete example?” You should be able to describe the task, your action, a difficulty and the resulting output. If you cannot, investigate the record or narrow the wording.
Ask a careers adviser or trusted reviewer whether the entry makes your contribution clear. Give them the relevant job requirement so they can judge the connection. General praise for an attractive CV layout will not tell you whether the evidence answers the employer’s need.
Finally, keep a private evidence bank with fuller notes than the CV contains. Add genuine projects as they happen, including what you did and where the records are. Future applications can then draw on accurate material, while each CV remains selective and suited to the specific opportunity.
To explore what graduates do after university, see the UK graduate outcomes guide.
