Assessment and Integration¶
How Vestigia Connects to Existing Assessment Structures¶
The Default Position¶
Vestigia is designed to sit alongside existing assessment structures without requiring changes to them.
This is a deliberate design choice, not a limitation. A framework that requires curriculum changes to implement will only be adopted by departments willing to make those changes. A framework that works within existing structures can be used by any individual supervisor, immediately and without institutional permission.
The default engagement model is therefore simple: a supervisor mentions Vestigia to students, students engage with it or do not, and the benefit — if it materialises — shows up in the quality of work they produce within existing assessment components. No submission of Vestigia records. No new marking criteria. No administrative overhead.
This document describes where that benefit tends to appear, and then addresses the question of more formal integration for departments that choose to pursue it.
Where Vestigia Benefit Appears in Existing Assessments¶
Students who engage consistently with Vestigia typically produce stronger work in several specific assessment areas. Understanding where to look for this is useful both for setting realistic expectations and for recognising the practice when it is working.
Decision justification in project proposals and technical reports¶
Many final-year project reports include sections requiring students to justify architectural, methodological, or design choices — why a particular technology was selected, why a particular research approach was taken, why a scope decision was made.
Students who kept Guide A records during the project typically write these sections with more precision and more honesty than students who did not. The reasoning was documented at the time of the decision, while the alternatives were fresh and the uncertainty was real. Reconstructed justification tends to be cleaner and more confident — because it is written from the position of knowing how things turned out. Live reasoning is more specific, more evidenced, and more credible.
This is not about being charitable to Vestigia users. It is about recognising where the friction in these sections comes from: for most students, it is that the justification was never captured at the time, and reconstruction is both harder and less accurate.
Individual reflective assessments¶
Reflection is among the most consistently weak categories in final-year project assessment across disciplines and institutions. The pattern is familiar: students produce generic statements about communication, time management, and teamwork — reflections that are technically responsive but not grounded in anything specific.
The core problem is that genuine reflection requires a specific moment to reflect on. Students who did not record specific moments during the project cannot reflect specifically after it — they can only generalise from an impression of the project as a whole.
Guide A's fifth category — reflection in motion — exists precisely to produce specific moments for later reflection. A student who recorded "I expected the mobile and web clients to synchronise token expiry automatically and discovered they do not — I now handle expiry independently on each surface" has something specific to reflect on in a formal submission. A student who did not record this is left with a vague sense that authentication was complicated.
The effect on assessment is measurable once you know what to look for: reflection submissions from consistent Guide A users tend to contain specific decisions, specific failures, specific changes in understanding. They read as genuine. This is the material that distinguishes the top of a reflection rubric from the middle.
On authenticity in reflection
One advantage of Vestigia-sourced reflection that is not always obvious is its resistance to fabrication. A reflection entry written in week four of a project — with a date, in the student's own words, about a specific technical or methodological experience — is implausible to have been invented at submission time. This does not mean fabrication is the concern being addressed; it means that authentic, time-stamped reflection is simply more credible, and that credibility is a component of quality.
Individual contribution statements in group assessments¶
In group projects with individual assessment components, students are often required to document their specific contribution — what they personally built, decided, or led. This is consistently one of the harder sections to complete well.
The problem is structural: in the moment of collaboration, contributions are fluid, overlapping, and not neatly delineated. By the time of submission, the memory of who initiated what and who led which part is partially reconstructed. Contribution statements written from this position tend to be either generic ("I contributed to the backend development") or slightly inflated, not necessarily from dishonesty but from the impossibility of accurate reconstruction.
Students who used Guide A and were explicit about individual contribution in their work-performed entries — "I implemented the token refresh logic while [name] worked on the login UI" — have accurate, specific material to draw from at submission time. The contribution statement becomes a summarising task rather than a reconstructing one.
WIL and professional practice documentation¶
For programmes with Work-Integrated Learning or professional practice documentation requirements, Vestigia records can serve as source material for reflection and evidence requirements. The five categories map reasonably well onto typical WIL documentation components: professional decisions, ethical considerations, client interactions, skill development, and reflection on practice.
Students will need to adapt and contextualise material from their Vestigia records for formal WIL documentation — Vestigia does not produce WIL artefacts directly. But the source material it generates tends to be considerably richer than what students produce without it.
Supervision Conversations¶
The benefit here is informal but consistent enough to be worth naming.
Supervision meetings with students who have been keeping Guide A records tend to be more productive than those without. The student arrives with specific material — a decision made, a problem encountered, a question that arose from the work — rather than a general update. The supervisor can engage with the actual state of the project rather than working to extract specifics from a broad summary.
This is not a dramatic change, and it is not uniform. Some students use Guide A actively, some partially, and some not at all. But among those who use it consistently, supervision conversations tend to be more substantive, more diagnostic, and more useful to both parties.
No change to supervision practice is required to benefit from this. It is a natural effect of students arriving more prepared.
Formal Integration — Considerations for Departments¶
Some departments may wish to integrate Vestigia more formally — referencing it in subject documentation, aligning marking criteria, or building it into project module structures. This is possible and the framework is designed to support it, but it involves trade-offs worth considering.
What formal integration can add¶
◆ clarity for students — explicit mention in a subject guide or handbook removes ambiguity about what the framework is and how it connects to the subject
◇ legitimacy signal — students are more likely to engage with something that appears in official documentation than with something mentioned informally in a supervision meeting
◆ assessment alignment — marking criteria that explicitly reward specific, evidenced reflection and justified decision-making create a direct incentive for the kind of practice Vestigia supports, without necessarily naming Vestigia at all
What formal integration risks¶
◆ compliance rather than engagement — if Vestigia records are required or assessed directly, some students will produce them performatively rather than genuinely. The practice works because it is honest and private; assessment pressure can compromise both qualities
◇ administrative overhead — collecting, reviewing, or assessing records adds workload for staff without necessarily improving student outcomes. The evidence base for reflective journal assessment is mixed; the evidence for private reflective practice is stronger
◆ reduced flexibility — a prescribed format or submission requirement limits the tool adaptability that makes Vestigia work across different project types and disciplines
A middle path¶
The most effective formal integration is usually indirect: adjust or supplement assessment criteria to reward the qualities that Vestigia supports — specific, evidenced reflection; justified decision-making; honest individual contribution — without assessing the records themselves.
A criterion that asks for "specific, grounded reflection on a named decision or failure, with clear account of what changed as a result" rewards Guide A users without disadvantaging students who produced equally genuine reflection through other means. The behaviour is incentivised; the tool is not mandated.
This approach requires no new administrative infrastructure and no formal adoption process. It is simply better assessment design for the reflective and professional components that most project modules already contain.
A Note on Academic Integrity¶
One question that occasionally arises when project documentation and professional showcases are discussed together is the relationship between private records and submitted work.
To be clear: Vestigia records are private working documents. They are not submitted, assessed, or claimed as academic work in themselves. When students draw on their Vestigia material to write formal submissions, those submissions are their own work, produced in their own words, from their own recorded experience. This is no different from a student using personal notes to write an essay.
Guide B's integrity and attribution document is explicit about this — it covers the ethics of presenting work honestly, attributing collaboration appropriately, and representing individual contribution accurately. It does not address academic misconduct because Vestigia use does not create academic misconduct risks. It creates source material, and source material in students' own words is the appropriate basis for their own formal writing.
In Summary¶
Vestigia requires no structural change to be useful. Its benefit appears naturally in the quality of work that students who engage with it produce within your existing assessment framework.
For departments that choose to go further, indirect integration — through assessment criteria that reward the qualities Vestigia supports — is likely to be more effective than direct assessment of records.
The framework is shared as an open educational resource. Adaptation, partial adoption, and collegial discussion are all welcome and expected.
This completes the For Lecturers section. The full Vestigia site — including all student-facing content — is accessible from the navigation above.