In this guide
Explain what you can do with fresh synthetic examples, clear contribution boundaries and evidence you are authorized to share.
Demonstrate the method, not the private file
A portfolio can help a reader explain their skills, but a workplace document is not automatically theirs to publish. Research, personnel, student, financial and patient-related material can carry obligations that are not removed by cropping a screenshot. The safest preparation exercise is often to create a new example from scratch, using invented non-sensitive data and a clearly stated purpose.
This article offers an editorial method for career preparation, not a legal determination about ownership or permission. The public UTSW application-administrator and administrative-associate postings illustrate different kinds of work a candidate might want to explain. They do not authorize anyone to disclose employer records. If a recruiter requests a work sample, clarify the requested format and follow applicable permissions rather than assuming that a request makes every existing document shareable.
A synthetic example should be unmistakably synthetic. Label it as a demonstration. Use fictional project names, ordinary placeholder tasks and invented dates that do not encode a real person's situation. Do not borrow a confidential case and merely change the name. The purpose is to show how you structure work, not to prove that you have access to impressive information.
Choose an artifact small enough to inspect
For coordination work, a one-page dependency plan may be more useful than a large project folder. For application support, a fictional issue report with clear reproduction steps and a stated boundary can show careful communication. For research administration, a generic document-completeness checklist can illustrate attention to requirements without claiming to reproduce a sponsor's actual rules.
The artifact needs a reader task. A reviewer should be able to answer a question after looking at it: what is missing, who owns the next action or which assumption remains unverified? If the example is visually elaborate but the answer is unclear, simplify it. A useful sample makes your reasoning inspectable without requiring the reviewer to imagine what the work was supposed to accomplish.
Avoid creating clinical protocols, laboratory procedures or contract templates merely to look relevant to a health organization. Those can imply expertise or authority that the exercise does not establish. There are many lower-risk ways to demonstrate organizing information: a fictional seminar plan, a version register, a meeting-decision log or a public-source comparison. Choose the example that matches your genuine experience.
Write the contribution statement beside it
Every artifact should have a short explanation of its purpose, what you personally created and what it does not demonstrate. A synthetic source register might show that you can preserve titles, dates and unresolved questions. It does not prove you have administered grants, managed regulated data or used a particular enterprise application in production.
For work completed by a team, separate your contribution from the team's outcome. You can say that you maintained a schedule or prepared review material if that is true. Do not turn participation into sole authorship. A clear boundary is not a weakness: it allows a reviewer to understand exactly what evidence the example supplies.
Use numbers only when they are real, relevant and shareable. A made-up performance improvement is not rescued by being placed in an otherwise fictional exercise. If a demonstration uses invented figures, label them as sample data and do not present the figures as your achieved results. If your actual result was qualitative, explain it in ordinary terms instead of manufacturing a metric.
Review the sample as an outsider would
Before sharing, ask someone who does not know the project to identify the purpose and the next action. If they need a long verbal explanation, the artifact may contain too much assumed context. Revise the labels or reduce the scope. This is a communication test, not a substitute for verifying permission to share.
Then run a separate disclosure check. Does the file contain hidden comments, metadata, real names, internal addresses, screenshots or copied fragments from an employer system? Creating the example in a clean document from the start reduces this risk. Keep the source of any public information visible, and do not imply the institution commissioned or approved the sample.
Finally, decide whether the sample is needed at all. A concise written account may answer the application question better than an unsolicited attachment. Follow the actual recruitment instructions. Keep an editable private preparation version and share only the material that is requested and appropriate. The portfolio should make your work easier to understand, not create a new burden for a reviewer or a new exposure for someone whose records were never part of the application.
Continue reading: A shared research core is a service relationship as well as a facility, Administrative writing is useful when it carries the next decision, Put the benefit year next to the claim.