A student can finish a valuable project and still need clarification before putting its code, images or client material in a public portfolio. Academic completion, ownership and permission to disclose are separate questions. A course with industry projects should make those questions understandable before a student relies on the work as public evidence of their skills.

The government's knowledge-asset guidance says student-created intellectual property can be affected by university policy, funding and project agreements. This article uses that limited point to build a practical evidence map. It does not determine ownership, interpret an individual's contract or offer a legal conclusion about a particular project.

List the project's different inputs and outputs

Consider a fictional team project using a sponsor's dataset, an existing software library, students' new analysis code and a final presentation. Different materials can have different rules. Treating the whole folder as a single object called “my coursework” can hide the permissions that need checking.

Material or action Question for the actual agreement or responsible service
Sponsor-supplied data What use and disclosure are permitted?
Existing software or images Which licences or permissions apply?
Newly created team code Who has rights, and what can each member reuse?
Final report or screenshots Does confidentiality restrict public display?
Portfolio publication Who can authorize this specific disclosure?

This table identifies questions rather than supplying default answers. A student contributing most of the coding has not, by that fact alone, established every right needed to publish the dataset, teammates' work or sponsor branding. Likewise, receiving a mark does not necessarily change a confidentiality condition.

Ask about the intended portfolio use early

Describe what would actually be shown: source code, a live demonstration, selected images, a written account or a private interview presentation. Permission for one use may not cover another. A generic assurance that the project is “good for employability” is not a precise answer about publication.

Read the relevant university policy and the project-specific terms together through the appropriate support route. Ask who handles ownership, confidentiality, licensing and any sponsor approval. If documents appear inconsistent or difficult to understand, obtain qualified guidance before signing or disclosing material.

Keep a record of any written permission, including the version of the material it covers and any conditions. Do not assume a teammate can authorize release on behalf of the sponsor or university. A verbal comment in a meeting should be clarified when the decision affects public disclosure.

Consider an approved demonstration alternative

If the actual project cannot be shown publicly, ask whether a separate demonstration using synthetic data or independently created assets would be acceptable. That may help explain a technique, but changing the data does not automatically remove every restriction on the code or project design. The revised material still needs the relevant checks.

A portfolio description should also represent the student's contribution accurately. Distinguish individual tasks from team achievements and avoid inventing client results, commercial deployment or permissions that were never granted. An approved high-level account can be more credible than an impressive-looking repository with unresolved rights.

Do not confuse public availability of a file with permission to reuse it. A sponsor's website, an accessible repository and a library download can each have conditions. Record the actual licence or authorization rather than assuming that anything downloadable belongs in a new project.

Include the issue in course comparisons

When evaluating project-heavy courses, ask how students are told about agreements and what support exists when portfolio aims conflict with sponsor restrictions. This is a practical question about the learning arrangement, not a reason to presume every sponsored project is unsuitable.

The group-project marking guide addresses how work is assessed. This map addresses what happens when the student wants to show or reuse it afterwards. A useful record separates contribution, ownership, confidentiality and the specific proposed use. That makes the eventual portfolio more honest and easier to support with evidence, while leaving individual rights questions with the institution and appropriately qualified advisers.