Being available for work answers one question: whether you want an opportunity. A work sample answers another: what someone can inspect before deciding to interview you. Neither replaces the other, and neither guarantees an offer.
You do not need to settle the argument over a profile badge to improve the evidence behind your application. Start with one piece of work that connects to the role, explains your contribution and can be shared legitimately. The goal is to make a claim assessable without asking the reader to accept a string of adjectives.
Choose an artifact for a particular question
CareerOneStop’s portfolio guidance, sponsored by the U.S. Department of Labor, describes portfolios as collections of work samples. It recommends describing the project, your contribution and its results. Its examples extend beyond design: reports, spreadsheets, teaching materials and training presentations can also show work.
That guidance is practical rather than a study measuring hiring outcomes. The exercise below is an original way to apply it. It does not establish how a platform ranks candidates or whether a badge helps or hurts in a particular hiring process.
Imagine a fictional applicant, Maya, looking for an operations coordinator position. The role involves keeping customer handoffs organized. Her strongest relevant artifact may be a handoff checklist she developed, rather than an attractive presentation about an unrelated project.
Before choosing the sample, write the question it should answer: “Can this person turn an unclear handoff into an understandable process?” That gives the page a purpose. A folder containing every document Maya has ever made gives the reader much more sorting to do.
For a teaching role, the question might instead be whether a lesson anticipates where learners get stuck. For an analyst, it might be how they explain an ambiguous result. The artifact should let the reader examine the work involved in the question, not merely announce that the applicant has the right trait.
Write a small case around the sample
Maya’s fictional case could have five parts:
- The handoff problem and the people who needed the information.
- Her assigned responsibility within the team.
- The relevant constraint, such as different teams using different terms.
- The checklist and one decision it embodies.
- What she can substantiate about its use, plus what she cannot.
These are prompts, not facts to fill with impressive inventions. If Maya cannot substantiate a reduction in delays, she should not attach a percentage. She can explain the scope of the work and distinguish a delivered checklist from a measured improvement.
A weak description would be “I transformed operations through strategic excellence.” A more informative fictional version is: “I drafted the handoff checklist, compared the fields used by the two teams and revised the wording after their review.” The second version leaves room for follow-up questions. What differed? Which fields stayed? What did the reviewers challenge?
Show a short extract beside the explanation. An invented demonstration entry could read:
Request owner: Alex. Missing information: the customer’s preferred delivery date. Next agreed action: Alex will request the date before confirming the handoff.
This lets the reader inspect how ownership and the unanswered question stay visible. It is a fictional illustration, not evidence of a historical customer interaction. Label recreated examples beside the extract so they cannot be mistaken for the original delivered work.
Make your decisions visible
A finished artifact can hide the most useful part of a project: why its author chose that form. Add one decision you can defend.
In Maya’s hypothetical case, she might explain why the checklist uses a named owner rather than “the relevant team.” That wording makes responsibility explicit. She could also explain why she left out a field whose purpose duplicated another. These examples illustrate judgment without claiming to have discovered a universal operations method.
Keep the explanation proportional. An application sample does not need a diary of every meeting. It needs enough context for someone to assess what you did and ask an informed question about it.
Include a limitation. Perhaps the work covered one team and was never tested across the company. Perhaps the sample demonstrates a process proposal that was not adopted. Stating that boundary helps the reader interpret the evidence correctly. Hiding it makes the artifact look more conclusive than it is.
Sharing permission comes before presentation
Being proud of a document does not establish that you can publish it. Check what you are permitted to share before building the case around it. Removing a customer name may leave other identifying details, commercial information or internal processes visible.
If sharing is not permitted, choose another sample or create a clearly labeled fictional demonstration. Do not imply that the demonstration is the original delivered work. You can still explain your method without releasing material that belongs to someone else.
References also need a practical boundary. Ask before sharing another person’s contact details, and use the application process the employer requests. A public portfolio does not need to expose a former manager’s email address merely to look complete.
Make the sample easy to use in a conversation
After preparing the case, write one sentence that connects it to the vacancy. Maya’s could be: “This sample shows how I clarified ownership in a customer handoff, which relates to the coordination work described in your role.” The sentence earns its specificity from the sample, rather than from flattery about the employer.
Then check three things. Can the reader open the file? Does the first page explain its relevance? Can you discuss the contribution without overstating it? CareerOneStop recommends proofreading portfolios and checking links and appearance; apply that check on a phone as well as on the device you used to create the sample.
A sample complements the evidence in your resume. The resume establishes the relevant history; the case gives selected evidence more room. Keep dates, responsibility and results consistent between them.
If the work needs special software, provide an accessible extract when permitted. If it contains a chart, explain its question and limits. The reader should not have to reconstruct the purpose from a filename or a screenshot with unreadable text.
Your first version can be one relevant sample with an honest explanation. If you later add projects, the one-page portfolio guide shows how to organize the overview. Add a sample because it answers another question about the role, rather than because the page looks short.
