Proof of work is a compact, inspectable record of something you did. It can support a statement about your contribution, process or learning, but it is not a promise that a reader will accept the claim. A useful pack lets that reader see the evidence, understand its context and notice what remains unverified.
Start with one precise claim
Write the claim before collecting files. “Built the reporting dashboard” is too broad when several people contributed. “Designed the filter interaction and implemented the front-end view shown in the dated release” is easier to evidence. Separate direct work from team work, and record the period covered.
| Part | Question to answer | Useful record |
|---|---|---|
| Claim | What exactly did you do? | One scoped sentence |
| Context | Why did the work exist? | Brief, requirement or problem note |
| Artefact | What can a reader inspect? | Output, extract, screenshot or repository record |
| Verification | How can its origin or date be checked? | Version history, public link or issuer record |
| Limit | What does it not establish? | Clear boundary or missing evidence |
Collect the smallest sufficient set
A strong pack does not need every working file. Consider a short brief, one representative output, a decision or change log, relevant test or review evidence, and a reflection written after delivery. Keep original dates where they are meaningful. Explain whether a screenshot shows a live result, a prototype or a recreated example.
For team projects, include a contribution statement. Name the part you handled and the parts you did not. If a result was measured, record the metric, period, baseline and method. If no reliable outcome measure exists, describe the delivered output and what you learned instead of inventing impact.
Make verification proportionate
A public link can show that an output exists, but it may not prove who created it. A repository history can add authorship and timing context, but shared accounts or imported commits may limit that inference. An issuer-generated credential is different again: it is a record issued by an organisation, not something to recreate yourself.
The official Europass overview describes a profile where people can record work, education and training, skills, projects, volunteering and achievements, and store supporting documents. That makes it one possible organising tool. The underlying claims still need accurate descriptions and appropriate evidence.
Protect people and confidential material
- Remove personal data, access keys, internal URLs and customer records.
- Check contractual and organisational rules before sharing work.
- Use a labelled extract or recreation when the original cannot be disclosed.
- Keep an unshared source copy so redactions do not destroy the record.
- Ask whether each detail helps verify the claim; omit it if it only adds risk.
Use a one-page cover note
Put the claim, your role, the date range, a two-sentence context summary and a numbered evidence list on the first page. Add a verification note beside each item and finish with limitations. A reader should be able to understand the pack without guessing why each file is present.
Next step
Use the project case study template to turn one evidence pack into a readable narrative, or build a wider career evidence map without publishing every record.