Quick answer: Create two or three self-directed samples that demonstrate tasks relevant to your target job. Give each sample a brief, a finished deliverable, and a short explanation of your decisions and checks. Clearly label simulated work, use fictional information, and claim only results you can demonstrate—not imagined business outcomes.
A portfolio is a collection of work samples showing your skills and qualifications; it does not have to be a complicated website. CareerOneStop describes both online and paper formats. (cloudfront.careeronestop.org)
1. Choose one target skill before making anything
For this starter portfolio, choose one kind of role and one central skill. Avoid trying to demonstrate everything you could possibly do.
If you are unsure where to start, CareerOneStop’s Skills Matcher asks you to rate yourself on 40 workplace skills and suggests careers matching those ratings. Use it to generate ideas, then compare those ideas with actual job descriptions. Treat a self-rating as a starting point, not proof of proficiency. (cloudfront.careeronestop.org)
Try this selection process:
- Read a few descriptions for the type of job you want.
- Note recurring tasks, such as maintaining records or drafting customer communications.
- Choose a task you can demonstrate without access to a real employer’s systems.
- Define what someone should be able to inspect in your finished sample.
For example, replace “show that I am organized” with “create a request tracker that makes ownership, deadlines, and missing information clear.”
Write a selection sentence:
“For an entry-level administrative role, I will demonstrate accurate recordkeeping through a fictional request tracker.”
For a marketing role, you might demonstrate audience-focused writing through an email and matching landing-page draft. Keep the task narrow enough to finish and explain.
2. Plan two or three complementary samples
Use two or three samples as a manageable starting target—not an employer rule. Give each a distinct purpose rather than producing several versions of the same thing.
For an administrative portfolio, consider:
| Sample | What you would make | Skill you intend to demonstrate |
|---|---|---|
| Request tracker | Spreadsheet with fictional requests, owners, deadlines, and statuses | Record organization and accuracy |
| Handoff guide | One-page instructions for updating the tracker | Clear procedural writing |
| Status update | Short email summarizing outstanding items | Prioritization and concise communication |
These choices fit CareerOneStop’s examples for office-support portfolios, which include reports, newsletters, and spreadsheets. (cloudfront.careeronestop.org)
For a marketing alternative, create a fictional campaign brief, an email draft, and a content schedule. Label the audience and campaign assumptions; do not imply that the campaign ran.
Before starting, answer four questions for each sample:
- Who is supposed to use it?
- What task should it help them complete?
- What constraints will you follow?
- How will you check whether it meets the brief?
You can connect the samples through one fictional scenario. Just make sure each adds evidence of a different skill.
3. Build a fictional administrative sample from a clear brief
The following project is a hypothetical exercise. Its setting, records, and requirements are invented for practice. It is not client work or evidence of business results.
Project brief
Project: Shared office request tracker
Intended user: An office coordinator handing work to a colleague
Problem: Requests need clear ownership and follow-up information
Deliverables: A spreadsheet, a one-page handoff guide, and a short status email
Constraints: Use only invented records; make the information understandable without a spoken explanation
Completion standard: A reviewer can identify open requests, find missing information, and understand how to update the tracker
Create a small fictional dataset, perhaps 12 requests. Include enough variation to test your choices: a completed request, an approaching deadline, an overdue item, and a request with missing information.
Suggested fields:
- Request ID
- Request type
- Date received
- Due date
- Assigned role
- Status
- Next action
- Information still needed
Use role labels such as “Office coordinator” rather than real names. Choose a reference date for the exercise and display it prominently so that “overdue” has a clear meaning.
Work through one decision
Suppose a request is waiting for someone to confirm a delivery date. You could leave its status as “Open,” but that does not explain the obstacle.
Instead, define a status called “Waiting for information” and add a next action:
Confirm the delivery date before arranging room access.
In your project notes, explain:
“I separated the status from the next action so that the person taking over can see both the current position and the task still required.”
That is an explanation of your reasoning—not an unsupported claim that the tracker improved productivity.
Test what happens when you change the request to “Complete.” Does it disappear from the outstanding-items view? If you add a new record, does it appear where expected? Record what you checked and what you corrected.
4. Document your decisions, contribution, and limits
Give every sample a short case note. Do not make the reviewer reconstruct the project from an unexplained attachment.
Use this structure:
- Context: What fictional problem did you set?
- Your contribution: What did you personally create?
- Decisions: Why did you choose this structure, wording, or approach?
- Checks: What did you test or review?
- Limitations: What has not been tested?
- Next step: What would you investigate before real-world use?
This emphasis on reasoning has an employer-backed basis. Atlassian’s design interview guidance asks candidates to explain their approach, the problems addressed, lessons learned, and specific contributions. Those instructions apply to Atlassian design roles; they are a useful model for explanation, not a universal requirement for administrative applicants. (atlassian.com)
For the fictional tracker, a suitable limitation is:
“This is a self-directed simulation using invented records. I checked the sample entries and status changes, but the tracker has not been tested in a live office.”
If you used a template, identify it and explain your changes. If another person reviewed the draft, describe their contribution accurately. Distinguish your work from tools, templates, or assistance.
For a resume, use a heading such as Selected Projects rather than presenting the exercise as employment.
Avoid: “Managed office requests and improved team efficiency.”
Use, if accurate: “Created a fictional office request tracker and handoff guide; checked status changes and documented update instructions.”
5. Evaluate the sample against a practical rubric
Use the following suggested rubric before publishing. It is a self-review tool, not a hiring score or certification.
Mark each item ready, needs revision, or not yet checked.
| Criterion | Practical check |
|---|---|
| Relevance | Can you connect the sample to a task in your target job descriptions? |
| Accuracy | Do the entries, calculations, dates, and summaries agree? |
| Usability | Can someone identify what to do next without your explanation? |
| Reasoning | Have you explained a meaningful choice and its trade-off? |
| Honesty | Are the simulation, your contribution, and limitations explicit? |
| Presentation | Is the finished version readable and free of drafting debris? |
For the tracker, manually compare the outstanding-items summary with the underlying records. If you used formulas, test them with deliberately changed inputs.
For the handoff guide, ask someone to follow the instructions without coaching. Ask specific questions:
- Which step was unclear?
- Where did you expect to find the status definitions?
- Could you identify the next action?
- What information seemed unnecessary?
Record the feedback and any revision you actually made. Do not turn one person’s comments into a claim that the sample is “proven” or that employers will prefer it.
Keep a brief revision note, such as: “Added status definitions after the reviewer could not distinguish ‘Open’ from ‘Waiting for information.’” Use that wording only if it describes a real review.
6. Label simulations and keep confidential material out
For this exercise, use invented information from the beginning. Do not start with a former employer’s spreadsheet and assume that replacing names makes it suitable to publish.
Put a visible label on both the portfolio description and the downloadable sample:
Self-directed practice project. All records are fictional. Not commissioned by or affiliated with an employer or client.
As a conservative publishing rule, leave out:
- Customer, employee, patient, student, or applicant records
- Internal emails, screenshots, pricing, or financial information
- Passwords, access tokens, private links, or account details
- Material whose publication permission is uncertain
Inspect hidden sheets, comments, document properties, filenames, and screenshot backgrounds as part of your review. Do not rely only on what appears on the first page.
If ownership or permission is unclear, omit the material and build a fresh example with invented content instead. Do not present this checklist as a legal determination that a document is safe to disclose.
Common mistakes to correct include calling a fictional organization a “client,” inventing performance gains, and using an employer’s branding in a way that suggests endorsement. Describe what you made and tested, not what you hope it might achieve.
7. Publish a small, usable version and test the handoff
For your first version, choose one simple container: a PDF with a contents page, a view-only folder, or a basic webpage. Keep the sample descriptions close to the files they explain.
CareerOneStop recommends clear organization, proofreading, checking links, and making digital portfolios mobile-friendly. (cloudfront.careeronestop.org)
Use this final checklist:
- Each sample has a title, purpose, and visible simulation label.
- My contribution is distinguished from templates and outside help.
- Claims describe completed work and checks, not invented outcomes.
- Files contain no confidential or unnecessary personal information.
- Text, tables, and screenshots are readable.
- Links work when tested while signed out.
- Sharing permissions match my intention.
- The application’s requested file type and submission method are followed.
- I can explain one decision, one correction, and one limitation.
If the employer does not request a portfolio, do not substitute it for required application materials. Ask whether an optional sample would be useful when you have an appropriate opportunity.
Start with one finished project before adding the next. The immediate goal is straightforward: produce something relevant, inspectable, and honestly described that you can discuss with confidence.