Transition Planning

How to Design a Small Work Sample for a Career Change

Write a focused practice brief for one task in a target role, with clear inputs, an honest finished output and questions that help you evaluate what you learned.

A small career-change work sample starts with one task, one intended reader and one finished output. Write those down before choosing tools. The purpose is to learn what the task involves and show what you actually did, not to imply that a personal exercise is professional employment or proof that you can already perform an entire role.

This guide provides an original practice-brief format and a fictional operations example. It suits tasks you can explore independently, such as organising information or drafting a process note. It is not a substitute for required qualifications, supervised practice or professional authorisation in work that needs them.

Choose a task instead of a job title

“Try project management” is too broad for a small sample. “Turn a fictional set of event requirements into a task list with dependencies” describes something you can attempt and inspect. The narrower task also makes it easier to ask for useful feedback.

Look at a target job description and identify an activity rather than a personality label. Phrases such as preparing reports, updating records or explaining a process give you more to work with than “dynamic self-starter.” Verify your interpretation through other descriptions or an appropriate conversation rather than assuming that one advert represents the whole occupation.

The National Careers Service’s guidance on identifying and developing skills suggests using job descriptions, job profiles and conversations to understand needed skills. It also recommends realistic goals that account for your time and circumstances. The practice brief below applies those limited ideas to a single self-directed exercise.

Write the question you want to answer. It might be “Can I organise incomplete information into a useful checklist?” or “Do I enjoy explaining a process clearly enough to want more practice?” Neither question requires you to recreate a company’s entire operation.

Define the reader and the decision they need to make

A sample becomes easier to judge when you know who would use it. A report for a manager choosing between options differs from a checklist for someone carrying out a routine task, even if both use the same information.

Describe the reader in one sentence. Then state what they should be able to do after looking at the output. For example: “A fictional event coordinator should be able to see which preparations depend on a room booking being confirmed.”

This creates a practical test for your work. If the dependencies are buried in a paragraph of background, the output may not meet the purpose even if it looks polished. You have something more specific to improve than whether the document feels professional.

Avoid choosing a reader you cannot realistically understand at all. If the task requires specialist judgement you have not learned, reduce the scope or seek suitable instruction. A useful beginner sample can expose a knowledge gap without pretending to resolve it.

Use inputs you can explain and share appropriately

For a first exercise, fictional inputs are often sufficient. You can invent a small event, a set of non-sensitive requests or a list of imaginary stock items. Label them as invented so nobody mistakes the resulting output for a real client’s work.

If you use published data or other material, record where it came from and check the permitted use before redistributing it. Publicly visible does not automatically mean unrestricted reuse. Keep your sample within the source’s terms and avoid copying large amounts of material simply to make the project look substantial.

Do not borrow confidential records from a current or former employer. Removing a name may not make a detailed record appropriate to share. A made-up case can let you practise the organisational task without needing anyone else’s operational information.

List assumptions separately from supplied inputs. “Assume the room holds 20 people” is not the same as a confirmed capacity. Keeping the distinction visible lets a reviewer see how you handled uncertainty instead of mistaking invented details for facts you verified.

Write the brief before opening the software

Use the following fields to define a manageable exercise. The suggested structure is a planning aid, not an industry certification standard.

Brief field Example question
Task What single activity am I practising?
Reader Who is the output intended to help?
Inputs What information do I have, and what is invented?
Output What file or explanation will I finish?
Boundaries What is explicitly outside this exercise?
Completion check How will I know the output answers the reader’s need?
Time limit How much time can I reasonably give it?
Review questions What feedback would help me improve?

Choose a time limit that fits your situation and record it as your limit, not a claim about how quickly a competent worker should finish. Beginners may spend time learning a tool that someone experienced already knows. That difference is information about your learning needs, not a verdict on your suitability.

State what you will leave out. A task-list exercise might exclude supplier selection, budgeting and live event delivery. Explicit exclusions help you finish a useful sample rather than keep expanding it whenever you discover another part of the job.

Worked brief: a fictional workshop preparation list

Imagine someone exploring operations coordination. Their sample task is to organise preparation for a fictional workshop with 12 attendees. All requirements are invented for practice, and there is no real booking or customer.

The inputs say that the room must be confirmed before invitations are sent, equipment must be checked before the session and the facilitator needs a final attendee list. One question remains open: whether the venue supplies a projector. The learner must leave that uncertainty visible rather than invent an answer.

The finished output is a one-page task list with owners expressed as fictional roles, dependencies and open questions. The reader is a fictional coordinator who needs to know what can proceed now and what is waiting on information.

Completion checks might be: every supplied requirement appears somewhere; no task assumes the projector is available; the invitation depends on room confirmation; and the reader can locate unresolved questions without reading all the notes. These checks assess this exercise, not all the competencies of an operations professional.

The learner produces the list, notices that the equipment task lacks a named role and revises it. In the accompanying note, they explain that change and why it matters. Showing the reasoning is more informative than presenting a polished page without any account of how it was made.

Keep a small process note while you work

Record the main choices, uncertainties and revisions. A few dated lines are enough. You might note that you changed the grouping because dependencies were hard to follow, or that you needed help with a spreadsheet function.

If you use a template, tutorial or AI tool, record what it contributed and what you checked yourself. Do not claim to have independently designed a method that you copied from a tutorial. Honest attribution makes it easier to distinguish your current capability from support you still need.

Save an intermediate version if it helps explain an improvement. You do not need to preserve every keystroke. The useful evidence is the change in your reasoning: what you noticed, what you tried and whether the final output addressed the original need.

For help describing existing strengths alongside new learning, use the guide to identifying transferable skills. Keep the claim attached to the work you can explain rather than adding broad skill labels unsupported by the sample.

Ask for feedback about the task, not your whole future

If an appropriate person is willing to review the sample, give them the brief and two focused questions. For the workshop example, ask whether the dependencies are clear and whether an important uncertainty has been hidden.

Avoid sending unsolicited large files or expecting free professional coaching. A short description lets the person decide whether they have the time and relevant experience to help. Respect a refusal or a narrower offer of feedback.

Separate comments about your output from information about the occupation. A reviewer may identify a missing column in your task list, but that does not establish whether the role’s working hours, entry requirements or broader responsibilities suit you. The guide to testing a career change covers that larger decision.

Keep feedback in its original context. “The task list is clear” is encouraging, but it is not a qualification or a hiring recommendation unless the reviewer explicitly provides one. Do not turn a helpful comment into a testimonial with a broader meaning.

Finish with an honest account of what the sample shows

Write a short description: the task, the invented or published inputs, the tools used, your contribution and what you would improve next. Label the work clearly as a self-directed practice project if you choose to include it in a portfolio.

Then decide the next step from the evidence you have. You might repeat the task with a more complex scenario, learn a missing technique or explore a different activity in the role. The guide to upskilling versus repositioning can help place that choice in your wider plan.

A completed sample need not prove that the career is right for you. It can show that you enjoyed one task, found a specific difficulty or discovered that your initial picture of the work was incomplete. Those are useful findings when they lead to a clearer next question rather than a larger claim than the exercise supports.