Career change guide
A practical transferable-skills worksheet for your career change
Most people can list their skills.
Few can prove them.
A transferable skills worksheet closes that gap. It forces you to move from a title, through a task, to a capability, and finally to evidence someone else can check.
This is not a theory exercise.
It is a method you complete once, on paper or in a document, and reuse in every CV, application and interview from then on.
Helpino GuideUpdated 20269 min read
What should a transferable skills worksheet actually contain?
A useful worksheet has five columns: the experience you drew it from, the task you performed, the underlying capability, the evidence that proves it, and the language your target role uses for it.
Working through these columns, in order, stops you from describing your old job and forces you to describe a transferable capability instead.
- Experience: where did this happen?
- Task: what did you actually do?
- Capability: what underlying skill did the task require?
- Evidence: what result or detail proves you have it?
- Target-role language: how would the new field describe it?
Complete one row at a time. Do not move to the next experience until the row is honest and specific.
Why job titles hide transferable value
A job title is a summary written for people already inside your industry.
It compresses years of decisions, problems and relationships into two or three words.
Outside that industry, the compression works against you.
A hiring manager reading “Retail Store Manager” or “Claims Handler” sees a category, not a capability. They do not automatically translate your daily reality into something relevant to their team.
That translation is your job, not theirs.
A worksheet exists to do that translation deliberately, rather than hoping it happens by accident in an interview.
Task versus capability
The first mistake in most self-assessments is stopping at the task.
A task is what you did. A capability is why it transferred.
Task (what you did)
Reconciled monthly supplier invoices against purchase orders.
Capability (why it transfers)
- Attention to detail under time pressure
- Working accurately with structured data
Task (what you did)
Handled escalated customer complaints by phone.
Capability (why it transfers)
- De-escalating conflict
- Making judgment calls with incomplete information
Task (what you did)
Trained new starters on the till and stock system.
Capability (why it transfers)
- Breaking down a process for a new learner
- Checking understanding through practice
Task (what you did)
Rearranged shift rotas around last-minute absence.
Capability (why it transfers)
- Constraint-based planning
- Balancing competing priorities quickly
Notice that the capability column never mentions the industry. That is the point. A capability should survive the move even when the task disappears.
Capability versus evidence
A capability without evidence is a claim. A capability with evidence is a fact a stranger can weigh up.
“I am good at de-escalating conflict” is a claim. “I handled around fifteen escalated complaints a week, and my manager began routing the most difficult callers to me” is evidence.
The evidence is what a sceptical reader believes. The capability is only what you say.
When you write your worksheet, resist the urge to leave the evidence column vague. If you cannot fill it in yet, that is useful information. It tells you where you need a sharper example, not where you need a better adjective.
A practical mapping table
Use these five columns for every significant role or project in your history.
Experience
Name the role, project or period. Be specific about dates and context, not just a job title.
Task
Describe one concrete thing you did regularly, in plain language. Avoid job-advert phrasing at this stage.
Capability
Name the underlying skill the task required, stripped of any industry-specific detail.
Evidence
Give a detail, scale or outcome that supports the capability. A number, a comparison or a specific consequence.
Target-role language
Rewrite the capability using the words your target field uses in its own job descriptions.
Work through this table for four to six of your strongest experiences before you write a single line of a CV or cover letter. The rows become your raw material.
Worked example: finance analyst moving into product operations
Consider someone who has spent six years as a finance analyst and wants to move into product operations, a field they have never formally worked in.
Monthly close process for a 40-person business unit, three years.
Chased five department heads for numbers, reconciled discrepancies, presented a summary by the third working day.
Running a recurring cross-functional process to a fixed deadline, with several stakeholders who do not report to you.
That capability, running a recurring cross-functional process without formal authority, is close to what a product operations role actually needs. The industry changes. The mechanism does not.
The evidence: “I reduced the close cycle from five working days to three by moving the reminder and reconciliation steps earlier in the calendar, and by agreeing a single submission template with department heads.”
The target-role language: a product operations job description might ask for someone who can “own a recurring operating cadence across cross-functional teams” or “drive process improvements that reduce cycle time.” The analyst's worksheet row now maps directly onto that phrase, because the underlying work is genuinely the same shape.
This is the difference between saying “I have finance experience” and saying “I have run a five-stakeholder operating cadence and cut its cycle time by 40 per cent.” Only one of those sentences gives a hiring manager something to trust.
Questions for identifying underestimated skills
Some of your strongest transferable capabilities are the ones you no longer notice, because they have become ordinary to you.
Turn any honest answer into a worksheet row.
- Ask a former manager or colleague what they would say you were reliably good at.
- Reread your last three appraisals for tasks you have stopped mentioning because they feel routine.
- List the questions people came to you with, not just the tasks on your job description.
Translating skills into target-role language
Once the capability and evidence columns are solid, the last step is language. The same capability can sound irrelevant or highly relevant depending on the words around it.
Current field
Underlying capability
Target field
- Finance analyst chasing month-end submissionsRuns a recurring cross-functional process to a deadlineProduct operations coordinator owning a release cadence
- Retail manager covering last-minute absenceConstraint-based planning under time pressureResource planner in a logistics or operations team
- Customer service handling escalated complaintsDe-escalation and judgment with incomplete informationTrust and safety analyst or account management lead
Do not invent vocabulary you cannot back up in an interview. Read genuine job descriptions in your target field and note which words repeat. Use those words only where your evidence genuinely supports them.
Where this fits in Career OS
Doing this worksheet by hand once is valuable. Doing it as a living record is more valuable, because a career change usually needs the same evidence reshaped for several different applications.
Inside Career OS, the Career Builder holds your experience in structured form, and the Evidence Bank stores the specific proof points, numbers, outcomes and examples, so you are not rewriting your worksheet from memory every time a new job description appears.
You complete the mapping once. Career OS then helps you pull the right rows into a CV, a cover letter or interview preparation for a specific role, in that role's own language.
Common questions
How many rows should my worksheet have?
Aim for four to six strong rows rather than a long list of weak ones. A handful of well-evidenced capabilities will do more work in an application than twenty vague claims.
What if I cannot think of a number for the evidence column?
Not every proof point needs a percentage. A specific comparison, a named outcome or a change in how others treated your judgment can be just as convincing as a statistic.
Should I do a separate worksheet for each job I apply to?
No. Build one master worksheet covering your whole history, then select and reword the relevant rows for each application. Rebuilding it from scratch each time wastes the work you have already done.
Is this different from the transferable skills guide on this site?
Yes. The other guide explains which meta-skills tend to matter most in a career change. This worksheet is the practical method for finding and proving your own version of those skills from your actual history.
Can I use this worksheet before I have chosen a target role?
You can complete the experience, task, capability and evidence columns without a target in mind. The language column needs a direction, even a tentative one, because it depends on how a specific field talks about the work.
Written by Benonica Mirea Angelova, Founder, Helpino.
Keep exploring
Transferable skills
Transferable skills for a career change
Identify transferable skills for a career change and turn them into evidence. Includes meta-skills, examples and a practical mapping method.
Read guide9 min readCareer change CV
Career change CV
Write a career-change CV that translates your experience into relevant evidence. Includes structure, personal-statement guidance and examples.
Read guide9 min readTransition planning
Career transition plan template
Use a 13-week career transition plan template to move from uncertainty to a credible new direction, covering clarity, evidence, market testing and positioning.
Read guide10 min read