Skip to content
PlagiatScanner.de
Higher education practice · action · HSP-08

Introduce a dissertation process portfolio

In brief: A process portfolio collects a small number of purposeful dissertation releases from proposal to submission. Before work begins, define milestones, acceptable evidence, assessment relationship, feedback, access and deletion. Useful entries can include a search decision, method release, analysis log, reviewed draft and reflection. The portfolio complements the final work; it is neither total surveillance nor automatic proof of authorship. Regulations and institutional data processes govern whether and how it can be introduced.

Milestones and evidence typesSources reviewed 4 September 2026

Make scholarly decisions visible without recording everything

A dissertation mainly displays an end product. A portfolio can show how the question, literature, method, analysis and revision developed. It supports feedback and reflection when every entry has a disciplinary function. An indiscriminate file collection creates workload and privacy risk without clearer assessment.

The record does not prove who typed every sentence. Timestamps move and files may be collaborative. The stronger evidence is a coherent connection between content, decision, feedback and subsequent change. Marking should reflect the declared learning outcome rather than reward a neat, artificially linear working style.

A new portfolio can alter assessment form, workload and weighting. The programme should therefore follow its actual approval, quality, privacy, accessibility and student-consultation routes. No single implementation rule applies to every institution.

Authority asset: milestone and evidence plan

Example requiring adaptation to programme and regulations
Milestone Scholarly evidence Reflection prompt Feedback focus
Question and plan Proposal, boundary and provisional sequence Which alternative was rejected? Feasibility and coherence
Search Search record and two source notes Which gap changes the question? Selection and source evaluation
Methods/data Method decision, ethics and data plan Which limit remains? Fit and protection
Analysis Data release, procedure, result and error log Which decision shapes the outcome? Traceability
Revision Draft, selected feedback and response What was not adopted, and why? Scholarly judgement
Closure Final reflection mapped to submission What remains uncertain? Limitations and transfer

Allow functional and accessible formats

Evidence may be prose, a table, code, audio, a sketch or an annotated figure where it reveals the learning outcome and remains reviewable. Offer equivalent routes. Handwriting, polished design or use of a commercial platform must not become unintended criteria.

Define minimum and maximum scope. A search entry can record question, service, query, selection reason and unresolved gap. An analysis log names data version, procedure, parameters, exclusions and outcome. Full browsing histories, screen capture and private chats are disproportionate defaults.

Record AI use under the module's stated rule. A compact entry may cover purpose, service, broad input type, retained function and disciplinary verification. Protected data and confidential feedback should not be uploaded to external services without authorisation.

Assess judgement rather than an attractive chronology

Mark reasons, source evaluation, method fit, response to error, use of feedback and reflection on limitations. A discarded approach can display strong judgement. Number of saved versions and early completion are not learning outcomes by themselves.

Publish rubric, weighting and consequences of missing entries in advance. Keep formative feedback distinct from summative decisions where required. Staff record feedback consistently. A later integrity concern cannot create new retrospective portfolio requirements.

A sampled discussion or interim viva can open selected evidence. Questions remain tied to the work and use comparable criteria. Accent, anxiety and technical polish must not substitute for subject understanding.

Collect only necessary information

Create a data inventory before launch: content, purpose, authority, location, access roles, retention and deletion. Do not copy participant data, health information and confidential comments into one broad system. A controlled reference may be enough.

Students should know who can view entries and whether they serve marking, support, quality assurance or integrity review. Do not change purpose silently. Provide an export and access route that survives a platform change.

Use external platforms only through institutional approval. Credentials, unauthorised full texts and third-party personal information do not belong in a generally readable portfolio. Delete or archive under the declared schedule.

Start with a bounded, reviewable implementation

  1. Confirm learning outcomes and formal approval needs.
  2. Choose six or fewer necessary milestones.
  3. Review rubric, examples, privacy and accessibility.
  4. Calibrate staff feedback and marking.
  5. Brief students before work and answer questions through one route.
  6. Review workload, clarity and technical issues without inventing effectiveness figures.

The assessment redesign matrix connects evidence and outcome. The interim viva opens selected entries. More models sit in the higher education practice hub. The sole foundation route is the guide to verifiable academic evidence.

Define a route for departures from plan. A late entry, platform failure or necessary method change is not automatically an integrity concern. Students can record cause, substitute evidence and consequences. Staff apply the published rule and document exceptions, preserving both learning purpose and meaningful deadlines.

Give feedback an explicit status: considered, adopted, partly adopted or rejected with reasons. The aim is scholarly response, not obedience. Link staff comments to the release reviewed. Where advice conflicts, the student records the evidence used to decide.

Design the handover with an index, stable entry IDs and a map to the final dissertation. Test external links and export central evidence durably. A reviewer should be able to trace a sampled claim to its portfolio record without searching private folders.

Official and scholarly foundations

  1. QAA Quality Code – transparent, fair and reliable assessment.
  2. Advance HE: Assessment and feedback – institutional practice for learning-oriented assessment.
  3. German Research Foundation: Handling of Research Data – documentation and responsible data practice.

Sources reviewed 4 September 2026. The institution's approved rules govern implementation.