Practise interview role-plays by agreeing a scenario, taking a short turn and reviewing observable actions. The aim is to make your thinking clear under realistic constraints, not to memorise a speech that works for every employer.

Use fictional details and keep each round manageable. One person plays the applicant, one plays the customer or colleague, and an optional observer records what happened. All scenarios below are hypothetical practice exercises, not real employer assessments or universal company procedures.

1. Clarify an unclear request

Scenario: a colleague asks you to “sort out the report urgently” but gives no deadline or required output. The applicant must clarify the task before beginning. The partner should know the intended audience and deadline, but reveal them only when asked.

Practise identifying the result needed, the information available and the decision owner. A useful opening is: “Which part needs updating, and when will you use it?” Avoid asking a long series of unrelated questions.

The observer checks whether the applicant can summarise the agreed task. Experienced candidates can use a fictional workplace report; first-time applicants can use a project summary. The skill being practised is focused clarification, not technical expertise.

2. Explain an unfamiliar process simply

Scenario: someone cannot understand the next step in a fictional registration process. Give the applicant a short process card with three steps. The partner misunderstands one step and asks for help.

The applicant should find the confusing point, explain it in plain language and check understanding. They should not simply read the whole card faster. A possible check is: “Which step will you do next?”

The observer notes whether the explanation matches the process card and whether the applicant notices the misunderstanding. Do not reward invented exceptions or exaggerated friendliness over accuracy. Repeat the exercise with a different point of confusion to test adaptability.

3. Handle a request outside your authority

Scenario: a customer asks for an exception that the fictional process says needs supervisor approval. The applicant may collect relevant information and refer the request, but cannot promise the outcome.

Practise acknowledging the concern, explaining the approval route and giving a clear next step. Hypothetical wording: “I can pass the request to the person authorised to review it. I cannot confirm the outcome before that review.”

The observer checks for respectful language, a named route and realistic expectations. The partner should not become more aggressive merely to force a dramatic performance. The purpose is to practise boundaries, not to test tolerance of abuse.

4. Give a concise handover

Scenario: a task is still unresolved at the end of a shift or meeting. Provide the applicant with a fictional note containing the issue, completed checks, open question and next owner. Ask them to brief another person.

A useful sequence is: current issue, verified action, remaining decision, owner and next update. The receiving partner should repeat what they will do next. If they cannot, the handover needs clarification.

Experienced applicants can practise an operational case. Those without employment experience can hand over an event-planning task. Avoid private customer details, real account information or a long story that hides the action required.

5. Prioritise two competing tasks

Scenario: two people request work for the same deadline, and the applicant cannot complete both as requested. Give enough information to identify the conflict, but leave the final business priority to a fictional manager.

Practise explaining capacity, dependencies and possible options. The applicant should ask the right person to agree the trade-off rather than silently choosing a favourite requester.

The observer checks whether the answer makes the conflict visible and communicates the effect of a decision. “I will do everything” is not a solution when the scenario explicitly rules it out. Discuss what further information would change the proposed order.

6. Respond to corrective feedback

Scenario: a reviewer says a draft is difficult to use because the action points are buried. The applicant needs to understand the feedback and propose a revision, not defend every sentence.

A useful response asks which decision the reader needs to make, confirms the change and explains how the revised version will be checked. Hypothetical wording: “I will move the open actions to the top and keep the background below. Could we check that the action owners are clear?”

The observer looks for a concrete revision rather than repeated agreement. First-time applicants can use a class assignment; experienced candidates can use a fictional work update. No one needs to invent praise or an improvement percentage.

7. Explain a mistake and the next action

Scenario: an applicant discovers an incorrect date in a document already shared with a small team. The exercise is to inform the appropriate person and propose the correction through the agreed process.

Practise stating the error, the possible impact, the immediate check and the prevention step. Avoid minimising the issue before knowing who relied on the date. Equally, do not turn a correctable error into an unsupported catastrophe.

The observer checks whether the applicant accepts their part and keeps the response useful. A credible outcome may be that the corrected information reaches the team; it does not require a dramatic claim that the whole project was rescued.

Use a simple observer checklist

After each round, discuss five questions: Was the issue understood? Were facts separated from assumptions? Was the action within the stated authority? Was the next step clear? Did the applicant check understanding?

Record one strength and one change to practise. Do not score personality, accent or similarity to a memorised model answer. Repeat the same scenario once with the agreed improvement, then change a detail. This shows whether the applicant understands the principle rather than merely recalling wording.

Turn practice into an honest interview answer

A role-play is practice, not work experience. If asked about a real event, use something that actually happened. If asked what you would do, explain your intended steps and assumptions. You can say you practised a scenario, but cannot claim that a fictional customer praised you.

For a worked STAR rehearsal, choose the incorrect-date scenario: situation, a shared draft contained an error; task, correct the information; action, notify the owner and circulate the approved correction; result, the team has the correct date. Label the entire example hypothetical.

Frequently asked questions

Do I need someone from the same industry?

Not for basic communication practice. Technical or regulated scenarios require appropriate expertise; a friend should not invent professional rules.

Should I record the session?

Only with everyone’s agreement. Written observer notes are enough for many exercises.

How can I practise alone?

Read a scenario, speak your response and compare it with the checklist. A partner adds unpredictability, but you can still identify unclear assumptions yourself.

Prepare truthful examples

Use your OpenDoor profile to organise real experience separately from these practice exercises.