What Vestigia Is¶
A Complete Orientation to the Framework¶
The Problem Vestigia Addresses¶
Most final-year projects leave behind two things: a submission and a gap.
The submission is assessed, archived, and filed. The gap is everything that led to it — the decisions made under uncertainty, the approaches that failed, the moments where the work shifted direction, the thinking that happened between the commits and the meetings and the drafts. That gap is where most of the actual learning lived. For most students, it disappears entirely by the time the project ends.
This is not a new observation. It is the reason the engineering log book, the lab notebook, and the project diary exist. Professional and academic traditions in engineering, science, and research have long recognised that the record of how work happened is as important as the work itself — for traceability, for professional development, and for the kind of explanation that interviews and presentations require.
The problem is that contemporary student projects — digital, distributed, often collaborative — have largely outgrown the formats designed to support that tradition. Log books designed for a single researcher working in a single lab do not map well onto a group of four students working across GitHub, group chat, a shared document, and a series of supervision meetings. The tradition remains in expectations; the practice has broken down.
Vestigia is a framework that responds to this mismatch directly.
What Vestigia Is¶
Vestigia is a structured, discipline-agnostic framework that supports students in three connected activities:
◆ recording project work as it happens — honestly, briefly, and in real time
◇ interpreting that record when the project ends — extracting what is significant and understanding what it means
◆ presenting the result professionally — in portfolios, showcases, CVs, and interviews
It is built around two sequential phases and an optional collective layer.
Guide A — During the Project¶
Guide A runs while the student is actively working on their project. It draws on the log book and engineering journal tradition, adapted for contemporary student projects.
Its core argument is simple: brief, honest records made at the time of a decision or event are worth far more than detailed reconstructions made weeks later from memory. It does not ask students to write more — it asks them to write earlier, lighter, and more honestly.
Guide A identifies five categories of meaningful entry:
◆ Direction and intention — what the student is trying to do and why
◇ Decisions and trade-offs — choices made, alternatives considered, risks accepted
◆ Work performed — individual contribution within sessions and within the group
◇ Problems and failure — what went wrong, why, and what it produced
◆ Reflection in motion — how understanding changed during the project, not only at the end
The emphasis on individual records within group projects is intentional and mirrors professional practice. In industry, engineers keep personal notebooks; teams produce shared deliverables. Both exist simultaneously. Vestigia supports the individual layer.
Guide B — After the Project¶
Guide B begins when the project ends. It is the phase most students never encounter — not because they lack the material, but because no one helps them know what to do with it.
It asks students to move from raw records to professional evidence: to extract what matters, connect it to their project artefacts, and present it in a form that is simultaneously honest and credible — suitable for portfolios, CV entries, LinkedIn, and the kind of professional conversations that interviews involve.
Guide B teaches four extraction filters — decisions, learning, problems and resolutions, and individual contribution — and then addresses how to organise extracted material into a coherent narrative, how to scale that material across different professional purposes, and how to maintain integrity when presenting collaborative work individually.
The connection to Itan — Vestigia's companion framework for broader portfolio development — is introduced in Guide B, at the point where students are ready to place their capstone work in the larger context of their professional development.
Shared Presence — Optional¶
The Shared Presence section addresses groups who want to build a collective, outward-facing presence for their project — a group website, a shared portfolio page, or another form of collective visibility.
Participation is entirely optional. The guidance covers what makes a shared presence meaningful rather than decorative, platform options for technical and non-technical groups, and the discipline of maintaining liveness throughout the project rather than only at the end.
The Intellectual Basis¶
Vestigia is not a new idea. It is a refinement of a long-established tradition.
The engineering notebook and the lab book have been foundational professional and academic artefacts for over a century. They exist because thinking that is not recorded disappears — and disappeared thinking cannot be traced, evaluated, reproduced, or learned from. These records served legal, professional, and educational functions simultaneously: they documented intellectual ownership, demonstrated professional practice, and provided material for reflection and improvement.
Vestigia preserves what these records were designed to do while removing the format assumptions that have made them feel irrelevant to modern students:
◆ what remains — dated, sequential entries; documented decisions and reasoning; honest capture of failure; individual ownership of the record
◇ what changes — the medium is the student's choice; entries cover meaningful moments rather than everything indiscriminately; the record serves two audiences (the student now, and readers later); the record feeds directly into professional presentation
The result is a practice that is lighter, more honest, and more useful than the log books it modernises — and one that addresses the gap between what final-year projects ask students to demonstrate and what students are typically equipped to produce.
What Vestigia Is Not¶
Being precise about this matters.
Vestigia is not a replacement for your module handbook, assessment rubrics, or submission requirements. It does not prescribe how projects should be managed, what tools students should use, or what deliverables they should produce.
It does not add compulsory work. Students may engage with it privately, selectively, or not at all. There is no expectation that staff will monitor, assess, or enforce engagement.
It is not in competition with WIL (Work Integrated Learning) frameworks, institutional reflective practice requirements, or existing supervision practices. In most cases it complements them — students who use Guide A tend to arrive at supervision meetings with more specific material to discuss, and students who use Guide B tend to produce more grounded and specific reflective writing for existing assessments.
It is not discipline-specific. The framework is written with CS, IT, and Engineering students primarily in mind — the disciplines where the log book tradition is most deeply rooted — but its structure and principles transfer across any project that involves decisions, iteration, and learning over time.
The Relationship to Itan¶
Vestigia is part of the same open educational ecosystem as Itan, a broader portfolio development framework for students and professionals across all disciplines.
Itan addresses the full arc of professional portfolio development — how students across eight domains of practice build, curate, and present a professional identity over time. Vestigia addresses one specific, high-stakes moment within that arc: the final-year project.
Guide B of Vestigia connects directly to Itan. Students who complete Guide B have developed the most substantive, evidenced piece of professional material they are likely to have at the point of graduation. Itan provides the framework for placing that piece in the larger context of their skills, experience, and professional development.
The two frameworks are designed to work together, but neither requires the other. Vestigia stands alone as a project documentation framework. Itan stands alone as a portfolio framework. Together, they support a more complete professional development arc than either does in isolation.
In Summary¶
Vestigia addresses a real and persistent gap in how students experience and present their final-year project work.
It is grounded in a long-standing professional tradition. It is practically oriented — students who use it do specific things, at specific moments, for reasons that connect directly to existing expectations. It does not add institutional complexity.
What it offers — to students who engage with it, and indirectly to the supervision conversations and assessment submissions that result — is something the tradition has always valued and that contemporary project structures rarely manage to preserve:
A traceable record of how the thinking happened.
Continue to How It Works in Practice for a ground-level view of the student experience.