In this article
Wanting to show what you have learned does not mean you should collect copies of workplace material. Customer information, internal reports, colleague details and training documents may be private or restricted. A useful account of development can often be made without them. The first question is what the evidence needs to establish, followed by what you are allowed to share.
Match the evidence to the claim
If the claim is that you can explain a simple process clearly, an original fictional explanation may demonstrate your approach. If the claim is that you completed a recognized course, the appropriate completion record may be relevant. Those are different kinds of evidence. A self-made example cannot become a certification just because it is polished.
In an invented exercise, a learner creates a one-page guide to sorting blank event cards. Every label, card and instruction is original. The sample can show how the learner organizes information and makes exceptions visible. It cannot prove that they improved a real employer’s operation or trained actual colleagues.
Label a fictional sample where it will be seen
A small disclaimer hidden in a footer is not enough if the title implies a real business achievement. Use an explicit description such as “Original fictional practice sample.” Avoid a real employer’s logo, customer names, internal layouts or details that suggest the sample was commissioned or approved by the organization.
The same rule applies to examples from this publication. They are learning exercises, not templates for claiming work experience. Readers should not copy a fictional scenario into a résumé as though it happened. The value lies in practicing the reasoning and then describing their own genuine experience accurately.
Describe real experience at the right level
When a real example is appropriate to discuss, keep the account focused on your action and a supportable result. Remove unnecessary identifying detail. Do not assume that deleting names makes an internal screenshot safe to share; dates, locations, account fields or unusual events may still reveal private information.
Follow employer rules and any applicable obligations. If you are unsure whether an artifact can leave the workplace, do not export it merely to make a portfolio more convincing. Ask through the appropriate route or choose a different form of evidence. This publication does not grant permission to reuse internal materials.
Preserve the difference between practice and achievement
A practice sample can be revised until it is clear and complete. A real achievement should not be rewritten into a more impressive story than the facts support. It is acceptable to say that you contributed to a team task, received feedback or are still developing a skill. Accuracy is more durable than a claim that falls apart under a simple follow-up question.
O*NET’s occupational description supplies general vocabulary for service work. It does not verify an individual’s proficiency or endorse a portfolio. Use such references to name the capability, then supply evidence that genuinely belongs to your own experience or clearly labeled practice.
Keep the collection small and purposeful
A few carefully chosen examples can be easier to explain than a large archive. For each one, note the claim it supports, its source, whether it is fictional and whether sharing is permitted. Do not include passwords, employee identifiers, customer transactions, private messages or personal information about other people.
A development conversation may need only a concise description and a question about the next learning opportunity. The goal is not to gather the largest possible file of evidence. It is to make a credible, appropriately private account of what you know, what you have practiced and what you still need to learn. See translating a skill for the final step from example to clear language.
Sources and limits
O*NET OnLine: Baristas, 35-3023.01. Public material checked October 8, 2026. Fictional examples and practice structures are original editorial work. They are not employer training, an assessment credential or a promise of a career outcome.