The Undocumented Step Up: Turning Extra Duties Into a Recognised UK Role

It often begins quietly. A colleague leaves, and you cover their project. A new starter needs mentoring, so you step in. A manager asks you to chair the weekly meeting, approve a supplier, or represent the team at a regional forum. None of these requests seems unreasonable in isolation. Together, they can amount to a job that has grown well beyond its title.

In UK organisations, this pattern is rarely malicious. Lean teams, restructuring, and cautious hiring can create gaps that capable people fill. The difficulty is that informal contribution is not the same as a documented role change. Without a clear record, employees can find themselves explaining at appraisal why their grade feels outdated, or at interview why their CV claims responsibilities that their job title does not reflect. The answer is not to become defensive. It is to make the gap visible, specific, and business-relevant.

Start with the employer's own map

Before assembling a case, locate the organisation's job architecture. Most medium and large UK employers have role profiles, grade descriptors, competency frameworks, or banding criteria. These may sit with HR, on an intranet, or in a departmental handbook. Ask your line manager or an HR business partner for the current profile for your role and, where available, the level above.

Compare duties against criteria rather than job titles. A grade descriptor might refer to autonomy, budget responsibility, people leadership, risk management, or stakeholder influence. Use those categories to organise your evidence. Instead of saying that you are doing more, say that the role now includes decisions previously reserved for the next grade, such as signing off expenditure up to a defined limit, managing a temporary project team, or representing the department to external partners.

This approach keeps the conversation anchored in the employer's language. It also avoids the trap of comparing yourself to a named individual. The question is not why a colleague holds a particular title. The question is whether the duties you now perform consistently meet the criteria for a different level.

Build an evidence trail without becoming a diarist

A useful record is selective rather than exhaustive. Keep a fortnightly log of significant duties that sit outside your current profile. For each entry, note the date, the task, the outcome, who benefited, and roughly how much time it took. Save examples of work that demonstrate judgement: a project summary, a client email thanking you for resolving an issue, a paper you drafted for a senior meeting, or a note confirming that you chaired a forum.

Quantify carefully. Figures are persuasive when they are accurate and modest. Rather than claiming that you transformed a process, record that you reduced approval turnaround from ten working days to six over a three-month period. Rather than saying that you mentor the team, note that you have supported two new starters through probation and delivered four internal training sessions.

Distinguish between a temporary surge and a sustained change. Covering for someone during annual leave is not a role change. Repeatedly carrying the same higher-level duties over eight to twelve weeks is a pattern worth examining. A simple one-page table can be effective: current profile requirement, what you actually do, evidence, and frequency. Keep it factual and free of grievance language.

Choose the moment and the audience

Timing matters. A role-review conversation is unlikely to land well during a crisis, a major restructure, or the final week of a financial quarter. Use a regular one-to-one to ask for a dedicated discussion, and explain the purpose in advance. A short message can be enough: 'I would like to review how my role has developed against the current profile. Could we set aside thirty minutes in the next fortnight?'

In the first instance, speak to your line manager. HR may need to join later, particularly where grading, pay, or job evaluation is involved. Avoid turning the meeting into an ambush or an ultimatum. The aim is to establish shared facts and agree a process.

The conversation: calm, specific, forward-looking

Open with the business context. Explain that your responsibilities have evolved and that you want to ensure the role is documented accurately. Then move to evidence. A script such as the following can help: 'Over the past six months I have taken on responsibility for the supplier review process and line management of two temporary staff. I have mapped these duties against the grade descriptors, and I would like to discuss whether the role should be reviewed.'

Be ready for questions about why this has happened and what you are seeking. You may be asked whether you want a new title, a pay review, or both. It is reasonable to say that you are seeking clarity on the role and a documented outcome, whether that is a regrade, a phased title change, or a development plan with a review date. Avoid demanding an immediate decision. Ask instead what process applies, who will be involved, and what timeline is realistic.

If the answer is 'not yet', do not leave the meeting without detail. Ask what would need to be true for the role to be reviewed again, and by when. A useful response might be: 'I understand that budget approval is not available this quarter. Could we agree the specific criteria that would demonstrate the role has changed, and diarise a review for the next appraisal cycle?' Record the agreed actions in a short email after the meeting.

Realistic timelines and what to expect

Role reviews in UK employers can take weeks or months. Job evaluation, HR sign-off, and budget approval rarely move at the pace of the individual request. A six to twelve week process is not unusual, and pay changes may align with a quarterly or annual cycle. Retrospective pay is possible in some organisations but should not be assumed. Ask about policy rather than relying on hope.

Documentation matters throughout. Keep a copy of your evidence table, the role profile, and any written summary of the discussion. If the process stalls, a polite follow-up referencing the agreed date is more effective than a fresh complaint.

If the answer remains no

A refusal is not always final, but it should not leave you as permanent unpaid extra capacity. If the organisation cannot recognise the role now, propose a boundary and a development route. Ask which duties should be prioritised, which could be handed back, and what formal development might bridge the gap. A secondment, project allowance, or sponsored training may be more achievable than an immediate regrade.

Keep your own record of achievements regardless of the outcome. Those examples will serve you in internal applications and future interviews. And if the gap between responsibility and recognition persists without a credible review date, consider whether a sideways move or external search is the more honest route for your career.

A quiet promotion does not have to remain invisible. With the employer's criteria, a concise evidence trail, and a calm conversation, extra responsibility can become a documented role change rather than an enduring assumption.