Build an example bank from events you can explain accurately. Record the situation, your responsibility, decisions, evidence and what remains uncertain. Tag examples by the questions they can genuinely answer, then practise selecting one rather than memorising a script. Keep confidential material outside the bank.
Collect events before assigning competencies
Start with a timeline of work, study, volunteering or independent projects. Look for moments when something changed: an unclear request became a plan, a handover exposed a risk, or a first approach failed. An event is easier to examine than a claim such as good communicator. Write its date, setting and the problem in ordinary language. Do not exclude modest examples if your actions are clear. A small scheduling decision may reveal more judgment than a large project where you only observed the outcome. Separate what you remember from what a record confirms. You can consult your own permitted notes, but copying private employer files into a personal preparation document creates a different problem. A short evidence pointer is often enough to refresh your memory. Note the question you could answer with the event, and leave room to correct the record after rehearsal.
Give every example a usable record
Use a consistent set of fields for retrieval: prompt, context, responsibility, options, action, observed result and limitation. Consistent fields help you compare events; they should not flatten the stories into identical answers. Explain why you selected an option, who else contributed and who had approval authority. If the result was a completed draft, name that result rather than suggesting commercial impact. Add a note about questions the example cannot answer. Coordinating peers does not automatically demonstrate formal line management. Keep a separate correction field for uncertain dates or numbers. Resolve those uncertainties before using them aloud, or choose language that accurately reflects the uncertainty. The bank should make your memory more accountable, not make an incomplete recollection sound more precise.
Test retrieval instead of perfecting scripts
Tag each record with a few defensible themes such as prioritisation, learning or disagreement. Then practise with unfamiliar questions and choose an example that addresses the actual request. Say the answer aloud, listen for a long introduction and ensure your own decisions are audible. A trusted listener can ask what changed because of your action and what you would do differently. Keep useful follow-up details below the main record so that you can expand without reciting everything at once. Retire examples that depend on confidential facts or cannot survive basic questioning. Revisit the bank after new projects, adding corrections rather than polishing old claims indefinitely. Preparation works when it helps you explain a real event flexibly, including its ordinary constraints and unfinished parts.
Fictional example: sorting a handover story
In this fictional exercise, Leena is preparing for a project assistant interview. Her first note says she improved team communication, but it contains no event a listener could examine. She returns to her permitted personal diary and identifies a student exhibition handover. Two volunteers used different versions of the setup checklist. Leena compared the versions, marked conflicting instructions and asked the exhibition coordinator to confirm the final sequence. She did not approve the exhibition budget or supervise the volunteers.
Her bank entry records the conflict, her comparison sheet, the coordinator's decision and the resulting agreed checklist. She tags it for clarifying ambiguity and coordinating a handover. She explicitly avoids tagging it as staff management. When a practice question asks about missing a deadline, she selects another example because this event did not involve a missed deadline. The improved artifact is a searchable, bounded account with an evidence pointer and a limitation. No interview outcome is claimed; the exercise shows how selection becomes more accurate before any employer conversation occurs.
A checklist for your next step
- List real events before broad strengths.
- Record your decisions and authority.
- Distinguish evidence from recollection.
- Tag only defensible interview themes.
- Practise selection with unfamiliar questions.
Common questions
How many examples should I collect?
Collect enough to cover the role’s main tasks with distinct events. A smaller bank you understand is more useful than numerous shallow or repetitive stories.
Can one event answer several questions?
Yes, when each question fits a real part of the event. Change the emphasis while keeping the facts and contribution consistent.
Further reading
These primary resources provide related background. They do not validate the illustrative example or endorse AliveCV.
AI-assisted drafting and automated technical checks. Examples are illustrative; no independent expert review or real-world outcome validation is claimed. Read our editorial policy.