UK

United Kingdom · Internal consulting · Mid-Level (2-5 years)

Requirements Management Advisor

Here is the whole job, in plain words. What it is, what you decide, how you're judged, how people get here and where they go next. Then the part no course gives you: twelve AI tutors who learn your work.

Start my Requirements Management Advisor plan, free

Free to start: a plan built for this role, and a Future Fluency module to try first. No card.

Keep this job description

Where should we send it?

One email: what AI is changing in this job, and where to start free. With a link back here. Nothing else follows unless you confirm your address.

Upskilling a team in this role? Talk to us

  • Experience bandMid-Level (2-5 years)
  • Direct reportsNo direct reports
  • Reports toSenior Requirements Management Advisor
  • UK framework levelUsually a coordinator, or early in a professional job

Also advertised as Business Analyst · Requirements Analyst · Solution Analyst

Built on 43,079 real UK job descriptions we analysed · grounded in qualifications employers recognise

Two short quizzes about you

1From this job to a course

The qualifications matched to this job

EAL Level 4 Diploma in Engineering and Advanced Manufacturing (Development Competence) Excellence, Achievement & Learning Limited · Level 4 · covers 1 of 7 standards
ETCAL Level 3 NVQ Diploma in Engineering Technical Support ETC Awards Limited · Level 3 · covers 1 of 7 standards
EAL Level 3 NVQ Extended Diploma in Engineering Technical Support Excellence, Achievement & Learning Limited · Level 3 · covers 1 of 7 standards
City & Guilds Level 3 Certificate in ICT Systems and Principles City & Guilds Limited · Level 3 · covers 1 of 7 standards
City & Guilds Level 3 Diploma in ICT Systems and Principles for IT Professionals City & Guilds Limited · Level 3 · covers 1 of 7 standards
City & Guilds Level 4 Diploma For ICT Professionals (Systems and Principles) City & Guilds Limited · Level 4 · covers 1 of 7 standards

Matched from the standards this job is measured against: a suggestion, not an official ruling.

The units you would start with

Establishing engineering software implementation EAL Level 4 Diploma in Engineering and Advanced Manufacturing (Development Competence)
Determining Engineering Software Requirements ETCAL Level 3 NVQ Diploma in Engineering Technical Support
Requirements analysis and systems specifications City & Guilds Level 3 Certificate in ICT Systems and Principles

The future skills this job leans on

AI Fluency working with AI as a thinking partner
Data Fluency turning numbers into a decision
Systems Fluency seeing the whole picture
Start my Requirements Management Advisor plan, free
Your Plan Illustration

Built for Requirements Management Advisor

3 units that map to this job, from the qualifications that cover it.

  1. Establishing engineering software implementation Excellence, Achievement & Learning Limited · covers 1 of 7 standards Level 4
  2. Determining Engineering Software Requirements ETC Awards Limited · covers 1 of 7 standards Level 3
  3. Requirements analysis and systems specifications City & Guilds Limited · covers 1 of 7 standards Level 3
These are the real units behind this job, in the order they rank for it. Nothing here is marked done, because this plan has not been started by anyone yet. Yours would fill in as you go.

2AI and this work

Will AI change your work as a Requirements Management Advisor?

Nobody can say exactly how. Here is what this job is being asked for next, and where to start.

The new skills this role is being asked for

  • Prompt Engineering & LLM Integration
  • Data Storytelling & Visualisation
Why each one is rising

The future skills this job leans on

We'll only ever tell you what we can actually back up. No hype, no scare tactics.

What happens when you start

Next, a free account. We build your Requirements Management Advisor plan as you set up, starting with a Future Fluency module on using AI in your job. No card.

Your first Future Fluency module is free. After that, your AI tutor is £70 a month.

Start my Requirements Management Advisor plan, free Ready to pay? Subscribe for £70 a month

3What this role really is

A requirements management advisor works out what internal clients actually need, then turns that into clear requirements for technical teams. The job involves digging into messy business problems and translating them into plans others can build against, keeping everyone aligned from start to finish.

4What you'd actually use

The tools this job runs on, and how well you'd need to know each one.

Jira (with Zephyr/Xray plugins) or Azure DevOps (ADO) Intermediate

You'll use this daily to document, link, and track requirements (user stories, epics, tasks). You'll navigate existing project structures, update issue statuses, and ensure traceability is maintained.

Lucidchart or MS Visio Intermediate

You'll use these to create 'as-is' and 'to-be' process maps, data flow diagrams, and other visual models to help stakeholders understand complex workflows. You'll be using standard BPMN symbols.

Confluence or SharePoint Intermediate

You'll create and maintain project spaces, structure pages, manage permissions, and draft clear documentation (e.g., meeting notes, project charters, non-functional requirements) from templates.

Microsoft Excel Intermediate

You'll use Excel for basic data validation, quick analyses (PivotTables, VLOOKUPs), and managing smaller lists of requirements or action items. It's still a workhorse, honestly.

SQL (Basic Querying) Basic

You'll execute pre-written SQL queries to extract data for validating stakeholder assumptions or for initial data discovery. You won't be writing complex queries from scratch, but you'll understand the basics.

5What you get to decide, and how that grows

Power in a job isn't your title. It's what you're allowed to decide. Here's how it grows as you move up.

The choiceComing in Where you are nowThe step above
Requirements Elicitation Approach Suggests approach to supervisor; executes under guidance. Independently selects and executes appropriate elicitation techniques (e.g., interviews, workshops, document analysis) for a given scenario. Consults Senior Advisor on complex or politically sensitive situations. Designs overall elicitation strategy for complex programmes, coaches others on techniques, and resolves conflicts on approach.
Requirements Prioritisation Contributes to prioritisation discussions based on input from supervisor. Facilitates prioritisation discussions with Product Owners/stakeholders for their assigned project, using techniques like MoSCoW. Escalates major disagreements or scope conflicts to Project Manager/Senior Advisor. Leads prioritisation across multiple projects within a programme, resolving significant conflicts and making recommendations to leadership.
Requirements Tool Usage & Configuration Uses existing tool configurations (e.g., Jira workflows) as directed. Configures basic aspects of requirements tools (e.g., custom fields in Jira, page structures in Confluence) for their project. Proposes minor improvements to existing tool usage. Designs and implements complex tool configurations and workflows (e.g., advanced Jira schemes, Jama Connect traceability rules) and mentors others on best practices.
Process Design Changes Documents 'as-is' and 'to-be' processes based on stakeholder input, reviewed by supervisor. Proposes and models 'to-be' process improvements based on identified inefficiencies. Seeks stakeholder agreement and consults Senior Advisor on significant changes to core business processes. Architects major business process transformations, assessing impact across multiple departments and influencing senior leadership on strategic process direction.

6How you'll be judged

The scoreboard, and what is not on it. The hard targets, how often each is actually looked at, and the quiet signals that never reach a dashboard.

Requirements Quality Score
Percentage of user stories and functional requirements that are clear, concise, unambiguous, and testable on their first pass by the development or QA team.
Target · >90% on average per project

For a recent project, 92% of your user stories met the 'INVEST' criteria (Independent, Negotiable, Valuable, Estimable, Small, Testable) after initial review, meaning less back-and-forth for the dev team.

Defect Rate Attributable to Requirements
Percentage of User Acceptance Testing (UAT) defects or production issues that can be directly traced back to incomplete, ambiguous, or incorrect requirements.
Target · <5% of total UAT defects

Out of 50 UAT defects reported, only 2 were due to a misunderstanding of the original requirements, hitting our target.

Documentation Timeliness
Adherence to agreed-upon deadlines for delivering key requirements artefacts, such as meeting notes, process maps, user stories, and specifications.
Target · 95% of artefacts delivered within 24 hours of agreement or by scheduled deadline

All your workshop summaries and initial user story drafts were shared with stakeholders within 24 hours, keeping the project moving without delays.

Stakeholder Feedback Score (Requirements Clarity)
Average score from internal clients and technical teams on the clarity and completeness of the requirements you've produced.
Target · >4.0 out of 5.0

Your last project's business sponsor rated the requirements documentation a 4.2 for clarity, noting it was 'easy to understand even for non-technical folk'.

Proactive Problem Identification
Your ability to spot potential issues or conflicts in requirements before they become blockers or cause rework.
  • You're often the first to flag an unstated assumption, a missing edge case, or a potential conflict between two different stakeholder requests. You bring these up in meetings with proposed solutions, rather than waiting for someone else to find them.
Effective Stakeholder Engagement
How well you engage with and manage expectations of business and technical stakeholders to get the information you need and keep them informed.
  • Stakeholders consistently feel heard and understood. They trust you to accurately represent their needs. You manage to get key decisions made without excessive delays or endless email chains, often by bringing the right people together at the right time.
Process Improvement Contributions
Your input into improving our internal consulting methodologies, templates, or tools for requirements management.
  • You'll suggest small tweaks to our Jira workflow, propose a new template for a specific type of user story, or share a more efficient way you found to run a virtual workshop. It's about making things better for everyone, not just your own work.
Mentorship and Knowledge Sharing (Informal)
Your willingness and ability to help out and guide newer or less experienced team members.
  • You're the person a new joiner asks for help with a tricky user story, or you'll offer to review a junior colleague's process map before they share it. You share useful articles or tips you've picked up, helping to lift the whole team's capability.

7Would you like it

Both sides. What people enjoy, and what grinds them down.

What people enjoy
Solving Puzzles

You love taking a tangled, unclear problem and breaking it down into logical pieces until you understand how it all fits together. The 'aha!' moment when you connect the dots is what gets you going.

You're given a vague brief about 'improving customer onboarding'. You'll dive into existing processes, interview different teams, and map out the entire journey, identifying bottlenecks and hidden dependencies, until you have a clear picture of what needs to change.

Making an Impact

You're not just happy to document things; you want to see your work actually lead to a tangible improvement. Knowing that your clear requirements helped build a better system or process is deeply satisfying.

After weeks of detailed requirements work, you see a new internal tool go live that genuinely makes a team's daily tasks quicker and easier. That direct link between your effort and their improved experience is a big win for you.

Learning and Growth

You're always keen to pick up new techniques, understand different business areas, or get better at your craft. You see every project as a chance to expand your knowledge and skills.

You proactively seek feedback on your process maps, ask senior colleagues about new elicitation techniques, or spend time understanding the nuances of a new business unit's operations, even if it's not directly for your current project.

What frustrates people
  • The Vague Stakeholder: Dealing with people who know they have a problem but can't articulate what they want, leading to endless revision cycles.
  • Scribe vs. Strategist: The constant battle to be seen as a strategic advisor who shapes the solution, rather than just a note-taker.
  • Unread Documentation: Spending ages on a meticulously detailed specification, only to realise the delivery team barely looked at it.
  • The Mid-Flight Change: Being handed a 'small, simple' change request halfway through a sprint that unravels a dozen hidden dependencies.
  • Assumption Whack-a-Mole: The exhausting process of identifying and documenting every unstated assumption before it becomes a project-derailing issue.
  • Political Crossfire: Being stuck between a business unit wanting a feature 'yesterday' and IT saying it's technically impossible or will take six months.
What this role does not give you
  • A perfectly stable, predictable workload with no last-minute changes.
  • The ability to make unilateral decisions without consulting multiple parties.
  • A role where you only interact with people who are always clear and concise.
  • A guarantee that every piece of your detailed work will be read cover-to-cover by everyone.

8Who you work with

Your work directly impacts project success rates, reducing rework and ensuring that the solutions we build actually solve the intended business problems. You help bridge the communication gap between business and technology, making our internal consulting practice more efficient and effective. Get it right, and we save time and money; get it wrong, and we waste both.

Inside the business
  • Project Managers
  • Product Owners
  • Technical Leads (e.g., Architects, Developers)
  • Business Unit Representatives (your internal clients)
  • Quality Assurance/Testing Teams

9What you need before you start

Not a wish list. The things you would be expected to already have.

  • At least 2 years of dedicated experience as a Business Analyst or Requirements Analyst, where you were responsible for the full requirements lifecycle on multiple projects.
  • Demonstrable experience in eliciting, documenting, and managing requirements for software development or business process improvement initiatives.
  • Proven ability to create clear user stories, acceptance criteria, and process maps.
  • Experience working in an Agile development environment.
  • A solid grasp of business analysis principles and methodologies (e.g., from BABOK or similar frameworks).

10What to practise next

Where the job is going, and what to do about it starting this week.

Advanced Process Automation Identification

Critical within 12-18 months. Businesses are constantly looking for ways to automate repetitive tasks. As a Requirements Advisor, you'll be expected to not just map processes, but to actively identify opportunities for Robotic Process Automation (RPA) or other digital automation, and then define the requirements for those solutions.

RPA suitability assessment · Process mining basics · Defining automation requirements · Impact analysis of automation

  • This week: Read an introductory article or watch a webinar on RPA and process mining.
  • This month: Shadow a colleague who's working on an automation project. Ask lots of questions.
  • Month 2: Identify one process in your current project that could be a candidate for automation. Map it out and highlight the automation points.
  • Month 3: Research common RPA platforms (e.g., UiPath, Automation Anywhere) and understand their capabilities from a requirements perspective.

Quick win: When mapping a process, add a 'robot' swimlane to visualise potential automation points. It's a simple way to start thinking differently.

11Staying current once you are in

What people here do to keep up
  • Actively participating in industry forums or communities (e.g., IIBA local chapters, LinkedIn groups) to stay current with best practices.
  • Attending webinars or online courses on new elicitation techniques, process modelling, or requirements management tools.
  • Reading relevant books or articles on business analysis, Agile methodologies, and internal consulting strategies.
  • Seeking out opportunities to shadow senior colleagues on complex projects to learn from their approach.

12The rising capability

The rising capability

Zavmo analysis

What's rising in its place

This is where the work is heading, and the higher pay with it. Get fluent here and the shift stops being a threat and starts being your edge.

Prompt Engineering & LLM Integration

This is critical within 6 months—it's already happening, not some distant future. Competitors are using tools like GPT to draft reports in 10 minutes that used to take 2 hours. Analysts who figure this out will outproduce peers 3:1.

  • Context windows and token limits
  • Temperature settings for different tasks
  • RAG architectures for proprietary data
  • Output validation and hallucination detection
  • Prompt chaining for complex analysis

Data Storytelling & Visualisation

Important within the next 12 months. We're collecting more data than ever, but raw numbers don't convince anyone. The ability to turn complex data insights into a compelling narrative that drives action is becoming a superpower for BAs.

  • Audience-centric communication
  • Narrative structure for data
  • Effective chart selection
  • Dashboard design principles
  • Explaining 'Why' behind the 'What'

13What you’ll use

What you’ll use

Skills this role draws on

Technical

  • BABOK® Framework Application
  • Agile Requirements Management
  • Business Process Modeling Notation (BPMN 2.0)
  • Stakeholder Analysis & Management
  • Requirements Traceability
  • Elicitation Techniques (Core)

14The pathway

The pathway

How you actually get there, here

How you become one varies far more by country than what one does. This is the UK route. Most people take one of these ways in; the right one depends on where you're starting from.

  1. 1

    Junior Business Analyst / Associate Requirements Analyst

    1-2 years

    Skills to master

    • Mastering core documentation (user stories, process maps), basic elicitation techniques (interviews), and understanding project lifecycles. Getting comfortable with our core tools like Jira and Confluence.

    You're ready to move on when

    • Consistently delivering accurate and complete requirements documentation under supervision.
    • Proactively identifying minor issues and suggesting solutions.
    • Receiving positive feedback from supervisors and immediate team members on collaboration and learning speed.
  2. 2

    Project Coordinator / Project Support Officer

    2-3 years

    Skills to master

    • Understanding project management methodologies, stakeholder communication, and basic risk/issue management. Learning how projects are structured and delivered.

    You're ready to move on when

    • Demonstrating a clear understanding of project phases and deliverables.
    • Effectively managing project logistics and communication with various teams.
    • Showing initiative in taking on tasks beyond administrative support, particularly related to project scope or documentation.
  3. 3

    Graduate Programme (with Business Analysis focus)

    2 years

    Skills to master

    • A broad exposure to different business functions and project types, with dedicated training in business analysis fundamentals. Building a network across the organisation.

    You're ready to move on when

    • Successful completion of all graduate programme modules and rotations.
    • Strong performance reviews from project leads and mentors.
    • Demonstrating a keen interest and aptitude for analytical and problem-solving roles, often seeking out BA-related tasks.

15Where this role leads

The long view: This work can lead to lead requirements advisor roles, or into principal requirements architect and business analysis leadership positions.

The ten Future Fluencies

Zavmo analysis

The credential is what you can do today. These are what keep you valuable.

A qualification proves you can do the job as it's defined today. These ten are what decide whether you're still the obvious person for it in five years. They're the capabilities employers are now writing into senior roles faster than people are learning them. Zavmo weaves them through whatever you study, so you come out with both: the credential and the fluency.

The highlighted ones are the Fluencies your role leans on hardest, from how Requirements Management Advisor is actually changing.

Where it leads

Roles this leads to

How you would learn this

One to one, on the work you already do

A tutor sets the task against your own job and marks the reasoning, at your pace. There is no cohort to fall behind.

A lesson from Establishing engineering software implementation, worked against Requirements Management Advisor.

Establishing engineering software implementation Level 4

Applied to your work in Requirements Management Advisor

This unit aims to equip learners with the skills to determine requirements, select, plan, implement, test, validate, and document the implementation of engineering software. Learners will analyse engineering needs, choose appropriate software, and manage the implementation process effectively.

How the thinking builds
  1. 1 Remember
  2. 2 Understand
  3. 3 Apply
  4. 4 Analyse
  5. 5 Evaluate
  6. 6 Create
An illustration of a Zavmo lesson, built from this role’s own route. The unit, its objective and every criterion above are the awarding body’s own words, not an example.

It is £70 a month, billed monthly. Your free first module is Future Fluency, and you can cancel any time.

Start my Requirements Management Advisor plan, free
See Your Progress Grow Illustration
Requirements Management Advisor
  • BABOK® Framework Application
  • Agile Requirements Management
  • Business Process Modeling Notation (BPMN 2.0)
  • Stakeholder Analysis & Management
  • Requirements Traceability
  • Elicitation Techniques (Core)
This is your Mind Palace on learn.zavmo.ai. Every skill above comes from this role's own record, not an example borrowed from another job. A node lights up when you evidence it, and what you build stays yours between jobs. That is the part a course cannot do.

16The detail, folded away

Everything else the record holds

The career branches in full, how AI is already showing up in the day-to-day, and the questions people ask about this job. Here when you want them, out of the way while you decide.

Where it leads next, rung by rung

Where it leads

The career path, and where it branches

Requirements Management Advisor is a start, not a ceiling. Each step below asks for new skills and hands back more autonomy.

  1. Senior Requirements Management Advisor

    3-5 years in current role

    Level 3 (Senior)

    • Leading requirements efforts for complex, cross-functional programmes
    • Designing and implementing new requirements methodologies or tools
    • Advanced stakeholder analysis and political navigation
    • Representing the requirements function in senior-level discussions
Working with AI on the job

Working with AI

Where AI is starting to help

Let's be honest, parts of requirements management can be a bit of a grind. Sifting through meeting notes, summarising feedback, drafting user stories... it all takes time. But what if you could cut down on the tedious stuff and focus more on the strategic thinking and stakeholder engagement that really moves the needle?

That's where AI comes in. We're actively exploring and integrating AI tools into our internal consulting practice to make your life easier and more productive. We're not talking about replacing your brain; we're talking about giving you a superpower. Imagine having an intelligent assistant that handles the heavy lifting of documentation and initial analysis, freeing you up to do what you do best: understand people and solve complex problems.

First-Draft Automation

Use AI to transcribe recorded stakeholder interviews or workshops and then generate a first draft of user stories, meeting summaries, and process steps. You'll then refine and validate this output, saving you hours of manual transcription and drafting.

Insight Synthesis

Feed hundreds of pieces of user feedback (from surveys, support tickets, emails) into an AI model. It'll instantly identify recurring themes, pain points, and conflicting requests, massively accelerating your discovery phase and helping you spot patterns you might have missed.

Accelerated Research

Point an AI tool at dense internal documentation (e.g., old project specs, technical architecture diagrams) or external regulations. Ask it to summarise key constraints, dependencies, and rules relevant to your current project, getting you up to speed much faster.

Acceptance Criteria Generation

Provide a well-written user story to an AI assistant and ask it to generate a comprehensive list of positive and negative acceptance criteria (the 'happy path' and 'edge cases'). This reduces the risk of missed scenarios and ensures your stories are truly testable.

Common questions

Common questions

How do you become a Requirements Management Advisor?

Common routes in include Junior Business Analyst / Associate Requirements Analyst (1-2 years), Project Coordinator / Project Support Officer (2-3 years) and Graduate Programme (with Business Analysis focus) (2 years). Times vary with prior experience.

Where can a Requirements Management Advisor progress to?

This role can lead on to Senior Requirements Management Advisor (3-5 years in current role), depending on the skills you build.

What new skills matter most for a Requirements Management Advisor?

Increasingly, Prompt Engineering & LLM Integration and Data Storytelling & Visualisation. These are the skills our record of this role lists as growing.

Free tools

Want a read on where you stand?

Three free tools, no account needed. Each one ends with a role, a level and a way in.

Read the Zavmo manifesto to understand how you will be taught Meet your tutors

Or try another one

17Where to go from here

Other roles at Level 3

Same depth of qualification, different job. Useful if the work appeals but this particular role does not.

 More jobs in internal consulting

Stay in the field you know and move sideways rather than up.
If you leave this industry

The skills built in this role transfer easily. They can lead to product management, project management, business process optimisation, or specialist roles in UX or data analysis. Translating business needs into actionable plans is a skill in demand across industries.

This role profile is © 2026 Growth Engineering Technologies Ltd. Built from UK occupational standards and regulated qualification data, and written for Zavmo.

You're not behind. You're right on time. The shift is only just beginning. Your role won't look the same in two years. Be the one who leads the change, not the one it happens to. Start my Requirements Management Advisor plan, free What happens next: a free account, then we build your plan as you set up. No card. Build your plan, see your roadmap and meet the twelve tutors matched to you. All free. When you're ready to start learning, it's £70 a month, billed monthly. Cancel any time and billing stops.