An evidence register connects a career claim with its source, scope, ownership and sharing status. Keep it private and record uncertainty instead of smoothing it away. The register does not need to contain every source document; a safe reference to an authorized record can be enough to support later checking and careful reuse.
Start with claims rather than a document collection
A folder of certificates and old presentations does not automatically show which statement each item supports. Begin with claims you may use in a CV, portfolio or interview. Write one claim per row in ordinary language, then identify the question a reviewer could reasonably ask. For a project claim, that might be your contribution; for a qualification, it might be the exact award and issuing institution.
Use a small set of practical fields: claim, context, your role, source location, date checked, confidence and sharing status. Add a limitation where needed, such as a team result or an outcome observed only during a pilot. This keeps the register useful as a decision tool. A complicated database that you never update is less helpful than a short, maintained record.
Record what the evidence actually establishes
One source may support a date but not a result. A meeting note can show that a proposal was discussed without proving it was adopted. A course certificate can show completion without establishing professional competence in every topic covered. Write the supported fact beside the source so that a later application does not inherit a stronger claim simply because a document exists.
Add a short note about who can clarify an unresolved question. Use status labels that prompt action: checked, needs clarification, superseded or do not share. Avoid treating confidence as a decorative score. If a figure lacks a denominator, note that specific gap and decide whether to remove it. When sources disagree, preserve the discrepancy until resolved rather than choosing the version that makes the strongest application sentence.
Keep the register private and maintainable
Only retain material you are authorized to keep. A register can refer to an approved record without copying customer data, employer files or identity documents into a new location. Store sensitive notes with appropriate access controls, and keep the public portfolio separate. A sharing-status field should distinguish public, permitted on request, private reference only and permission unresolved where those distinctions are useful.
Link application wording back to register entries. When you discover a correction, you can then identify which CV versions or portfolio pages need review. Record the exact application sentence when its interpretation matters, because a short rewrite can change attribution or implied scope even if the underlying facts remain the same.
Review the register after a substantial project or before an important application. Confirm that links still work, permissions still apply and old estimates have not become accepted facts through repetition. Retire unsupported claims rather than leaving them available for accidental reuse. The goal is to make accurate selection easier, not to build a dossier containing every detail of your employment.
Fictional example: three sources with different jobs
A fictional operations specialist creates entries for a job date, a handover project and a training course. An employment letter supports the role and dates. A permitted project summary confirms that a checklist was adopted by one team, while the specialist’s notes identify the sections they drafted. A course certificate confirms completion of a spreadsheet course but says nothing about advanced professional analysis experience.
The register marks the employment letter private, the project summary available only with permission and the course title suitable for a training section. An old claim that the checklist “transformed operations” is marked unsupported and replaced with the narrower adoption statement. When preparing a CV, the specialist selects facts from these entries without attaching private documents or presenting the course as a professional qualification.
A checklist for your next step
- Create one row for each reusable career claim.
- Record what each source actually supports.
- Separate confidence from permission to share.
- Keep sensitive documents out of public folders.
- Link corrections to the application versions affected.
Common questions
Do I need documentary proof for every sentence?
Not every routine statement needs a formal document, but important dates, credentials, metrics and ownership claims should have a defensible basis. Record uncertainty and avoid presenting assumptions as verified facts.
Should an employer receive the register?
Usually no. It is a private preparation tool. Share only the requested, appropriate evidence through the recipient’s stated process, with necessary permissions and personal information controls.
Further reading
These primary resources provide related background. They do not validate the illustrative example or endorse AliveCV.
AI-assisted drafting and automated technical checks. Examples are illustrative; no independent expert review or real-world outcome validation is claimed. Read our editorial policy.