Updating a CV that has not changed in years, when your job title has not changed either, means looking past the title for what has actually changed inside the role: the scope of what you own, the size of what you work on, tools that did not exist when the CV was last touched, and the people who now depend on your work. A title staying the same does not mean the job stayed the same, and the update is mostly a matter of surfacing that growth in specific terms instead of leaving the same three bullet points sitting under an unchanged heading. The goal is not a rewrite from scratch, just an honest look at what changed since the last time anyone read it closely.
Why "nothing changed" is rarely true
A role that keeps the same title for several years still tends to accumulate scope: more systems to look after, a bigger team relying on the work, ownership of something that used to sit with someone else, or a longer track record that earns more trust with less oversight. None of that shows up automatically on a CV that has not been touched since the role began, because a CV only reflects what was written down at the time, not what happened afterward. Before rewriting a single bullet, it helps to do a plain stock-take: list what is different about the day-to-day job now compared with when the CV was last updated, including details that feel too ordinary to mention. Ordinary, gradual change is usually exactly what a static title fails to capture, and it is the raw material the rest of the update draws from.
Find where your scope actually grew
A few places are worth checking specifically. Who reports to you or relies on your sign-off now that did not before. Which systems, accounts, budgets or projects fall under your responsibility that used to sit elsewhere. What decisions you now make without asking someone else first, compared with the early version of the role. Which tools, processes or technologies you picked up along the way that were not part of the job description when you started. None of this needs a title change to count as real growth worth describing, and a CV that only updates on a promotion misses years of change that happened without one. Read how to write a resume alongside this if the bullet structure itself, not just the content, also needs a refresh; the underlying advice on describing scope and outcome applies here even though the role has not formally changed.
It also helps to think in terms of who used to make a given decision and who makes it now. A long-tenured employee often ends up as the person newer colleagues ask when something unusual happens, or the one trusted to handle an exception without checking first, and that kind of informal authority rarely gets written down anywhere except a CV that is actually kept current. Naming a specific instance, one exception handled, one process improved, one newer colleague mentored, reads as far more concrete than a general claim of being "experienced" in the role.
Illustrative example: the same title, a bigger job
Before: "Office Manager, manage day-to-day office operations and supplies."
After: "Office Manager, oversee facilities and vendor relationships for a 60-person office, up from 15 when the role started; manage an annual operating budget and now approve vendor contracts directly rather than routing them through finance."
The title did not change across those years, but the second version states the scope that did: headcount, budget ownership and a decision that used to require someone else's approval. That is the kind of detail an unchanged CV usually leaves out entirely, because none of it was true on day one, and it is exactly the sort of change that a long-tenured employee tends to stop noticing simply because it happened gradually rather than on a single memorable date.
Update the parts that decay even without a new title
A skills list ages even in a stable role, as tools get replaced and new ones get adopted; check it against what you actually use today rather than what you used when the CV was written. See turning duties into achievements on your CV for how to rewrite bullets that still describe a task rather than an outcome, which is common in a CV that has not been touched in years regardless of title. A summary line written for an earlier stage of the same role usually needs the biggest rewrite of all, since it is the one part most likely to describe who you were rather than who you are now.
Turn the update into a habit, not a one-off project
Once the update is done, treat it as the new baseline rather than the last one: a short note added every few months, whenever scope visibly changes, keeps the next update from turning into another multi-year backlog. A running list somewhere outside the CV itself, added to right after something noteworthy happens rather than reconstructed from memory months later, makes the next full update a short editing pass instead of a project. Start updating your CV with the stock-take above as a starting checklist, and revisit it again well before the next job search actually starts, since a CV read for the first time under time pressure is much harder to get right.