Protocol
Keep one portfolio artifact that does not belong to your employer
A portfolio should not require leaking the work that created the skill.
When it fits
- All proof of capability is trapped inside confidential systems you may lose access to.
When to avoid it
- Public artifacts are optional signals, not a requirement for every profession; confidentiality and employment agreements come first.
Why it matters
Create independent, lawful artifacts that demonstrate the mechanism: public sample, synthetic case, open-source contribution, article, diagram, benchmark or tutorial. Use invented or public data and clearly separate it from client work.
Steps
- Artifact is legally yours to share.
- No confidential data or screenshots used.
- Task resembles a real capability.
- Quality is reviewable.
- Context and limitations are explained.
An example
A consultant builds a public synthetic master-data validation example that demonstrates modelling and test design without reproducing client configuration.
Check your result
At least one important capability can be inspected without employer access.
Keep this limit in mind
- Public artifacts are optional signals, not a requirement for every profession; confidentiality and employment agreements come first.
Evidence and sources
Supports
OECD 2025 and 2026 skills work supports transparent recognition of skills and more portable ways to signal learning and capability across jobs.
Skills-first hiring does not remove the importance of experience, regulated qualifications or occupation-specific requirements.
A Skills-First Labour Market · Skills-first labour market summary