ResearchOps application visual walkthrough

Generated evidence of the current application build, covering registered pages and important interaction states.

Base URL: https://researchops.pages.dev/

Run started: 2026-05-04T20:11:35.957Z

17 pages 33 states 66 screenshots 0 failures

Core

Home

/

ResearchOps landing page.

Default state

captured · https://researchops.pages.dev/

Initial loaded page state.

Gherkin acceptance criteria for this state
Feature: Access the ResearchOps home page

  As a user researcher
  I want to access the ResearchOps home page
  So that I can choose the right ResearchOps journey for my work

  Background:
    Given I am a user researcher
    When I visit the ResearchOps home page

  Scenario: View the ResearchOps service identity
    Then I should see the service name "ResearchOps Demo Suite"
    And I should see the tagline "Objective orientated applied user research done well."
    And I should see the page heading "ResearchOps Demo Suite"
    And I should see introductory text explaining that the service supports applied user research with operations, governance and accessibility baked in

  Scenario: Understand that the service is a prototype
    Then I should see a prototype banner
    And the banner should warn me not to enter real participant personal data

  Scenario: Navigate using the primary navigation
    Then I should see primary navigation links for:
      | Home                   |
      | Start research project |
      | Projects               |
    And the "Home" navigation item should be shown as the current page

  Scenario: View the available research journeys
    Then I should see the section heading "Choose a journey to explore"
    And I should see journey cards for:
      | Journey title                                      | Category        |
      | Start a new research project                       | Getting started |
      | Set clear research objectives                      | Team alignment  |
      | Recruit participants for user research studies     | Recruitment     |

  Scenario: Start a new research project journey
    Given I can see the "Start a new research project" journey card
    Then I should see the question "How might we define the research project?"
    And I should see a description explaining that the project will be defined with its service phase and project status before adding stakeholders and objectives
    When I select "Go to start research project service"
    Then I should be taken to the start research project service

  Scenario: Open the research objectives journey
    Given I can see the "Set clear research objectives" journey card
    Then I should see the question "How might we overcome the impact of unclear objectives in user research?"
    And I should see a description explaining that misaligned objectives can affect research, design and delivery teams
    When I select "Go to objective definition service"
    Then I should be taken to the objective definition service

  Scenario: Open the participant recruitment journey
    Given I can see the "Recruit participants for user research studies" journey card
    Then I should see the question "How might we ensure that participant recruitment reflects the diversity and needs of the service's real users?"
    And I should see a description explaining the risk of biased, exclusionary or ineffective findings when recruitment is poorly planned
    When I select "Go to participant management service"
    Then I should be taken to the participant management service

  Scenario: Access the home page using a keyboard
    Given I am navigating with a keyboard
    Then I should be able to move focus through the primary navigation links
    And I should be able to move focus through each journey call-to-action
    And I should be able to activate each link using the keyboard

  Scenario: Understand the page structure with assistive technology
    Then the page should have one clear main heading
    And the journey section should have a meaningful heading
    And each journey card should expose its title, supporting text and call-to-action in a logical reading order

  Scenario: View footer information
    Then I should see the footer text "© 2026 Home Office Biometrics · ResearchOps v1.0.0"
Desktop

captured · https://researchops.pages.dev/

Home: Default state — Desktop
Mobile

captured · https://researchops.pages.dev/

Home: Default state — Mobile

Start research project

/pages/start/index.html

Start page for creating or beginning research project work.

Default state

captured · https://researchops.pages.dev/pages/start/index.html

Initial loaded page state.

Gherkin acceptance criteria for this state
Feature: Define a research project

  As a user researcher
  I want to define a research project with objectives, stakeholders and ownership
  So that my team can start research work with shared context and traceable intent

  Background:
    Given I am a user researcher
    When I visit the start research project service

  Scenario: Understand the page purpose
    Then I should see content that supports start page for creating or beginning research project work.
    And I should understand what ResearchOps task I can complete from this page

  Scenario: Work with the "Default state" state
    Given I am using the start research project service
    Then the interface should make it clear that this state is for initial loaded page state.
    And I should be given enough context to decide what to do next

  Scenario: Use the default view
    Then I should understand what ResearchOps task this page supports
    And I should be able to choose an appropriate next action

  Scenario: Use the state accessibly
    Then the page should have one clear main heading
    And headings, labels and controls should be exposed in a logical reading order
    And I should be able to move through the available controls using a keyboard
    And I should be able to activate links, buttons and form controls without a mouse
Desktop

captured · https://researchops.pages.dev/pages/start/index.html

Start research project: Default state — Desktop
Mobile

captured · https://researchops.pages.dev/pages/start/index.html

Start research project: Default state — Mobile

Step 1 completed with project definition

captured · https://researchops.pages.dev/pages/start/index.html

Project name, description, phase and status entered using believable discovery-stage dummy data.

Gherkin acceptance criteria for this state
Feature: Define a research project

  As a user researcher
  I want to define a research project with objectives, stakeholders and ownership
  So that my team can start research work with shared context and traceable intent

  Background:
    Given I am a user researcher
    When I visit the start research project service

  Scenario: Understand the page purpose
    Then I should see content that supports start page for creating or beginning research project work.
    And I should understand what ResearchOps task I can complete from this page

  Scenario: Work with the "Step 1 completed with project definition" state
    Given I am using the start research project service
    Then the interface should make it clear that this state is for project name, description, phase and status entered using believable discovery-stage dummy data.
    And I should be given enough context to decide what to do next

  Scenario: Complete the interaction needed for this state
    Given I am ready to work with this ResearchOps state
    When I enter "Assisted Digital Support Discovery" into the "Project name" field
    And I enter "This discovery examines how caseworkers and support staff help people who cannot complete a digital application without assistance. The research will focus on confidence, evidence…" into the "Project description" field
    And I choose "discovery" from the "Service phase" field
    And I choose "planning" from the "Project status" field
    Then I should be able to continue the ResearchOps journey with confidence

  Scenario: Use the state accessibly
    Then the page should have one clear main heading
    And headings, labels and controls should be exposed in a logical reading order
    And I should be able to move through the available controls using a keyboard
    And I should be able to activate links, buttons and form controls without a mouse
Desktop

captured · https://researchops.pages.dev/pages/start/index.html

Start research project: Step 1 completed with project definition — Desktop
Mobile

captured · https://researchops.pages.dev/pages/start/index.html

Start research project: Step 1 completed with project definition — Mobile

Step 2 default state

captured · https://researchops.pages.dev/pages/start/index.html

Second wizard step after a valid project definition has been entered on step 1.

Gherkin acceptance criteria for this state
Feature: Define a research project

  As a user researcher
  I want to define a research project with objectives, stakeholders and ownership
  So that my team can start research work with shared context and traceable intent

  Background:
    Given I am a user researcher
    When I visit the start research project service

  Scenario: Understand the page purpose
    Then I should see content that supports start page for creating or beginning research project work.
    And I should understand what ResearchOps task I can complete from this page

  Scenario: Work with the "Step 2 default state" state
    Given I am using the start research project service
    Then the interface should make it clear that this state is for second wizard step after a valid project definition has been entered on step 1.
    And I should be given enough context to decide what to do next

  Scenario: Complete the interaction needed for this state
    Given I am ready to work with this ResearchOps state
    When I enter "Assisted Digital Support Discovery" into the "Project name" field
    And I enter "This discovery examines how caseworkers and support staff help people who cannot complete a digital application without assistance. The research will focus on confidence, evidence…" into the "Project description" field
    And I choose "discovery" from the "Service phase" field
    And I choose "planning" from the "Project status" field
    And I select "Continue to stakeholders and objectives"
    Then the "Stakeholders, objectives and user groups step" section should be available
    Then I should be able to continue the ResearchOps journey with confidence

  Scenario: Use the state accessibly
    Then the page should have one clear main heading
    And headings, labels and controls should be exposed in a logical reading order
    And I should be able to move through the available controls using a keyboard
    And I should be able to activate links, buttons and form controls without a mouse
Desktop

captured · https://researchops.pages.dev/pages/start/index.html

Start research project: Step 2 default state — Desktop
Mobile

captured · https://researchops.pages.dev/pages/start/index.html

Start research project: Step 2 default state — Mobile

Step 2 completed without AI rewrite invoked

captured · https://researchops.pages.dev/pages/start/index.html

Stakeholders, objectives and user groups entered with realistic planning data before the AI rewrite is requested.

Gherkin acceptance criteria for this state
Feature: Define a research project

  As a user researcher
  I want to define a research project with objectives, stakeholders and ownership
  So that my team can start research work with shared context and traceable intent

  Background:
    Given I am a user researcher
    When I visit the start research project service

  Scenario: Understand the page purpose
    Then I should see content that supports start page for creating or beginning research project work.
    And I should understand what ResearchOps task I can complete from this page

  Scenario: Work with the "Step 2 completed without AI rewrite invoked" state
    Given I am using the start research project service
    Then the interface should make it clear that this state is for stakeholders, objectives and user groups entered with realistic planning data before the AI rewrite is requested.
    And I should be given enough context to decide what to do next

  Scenario: Complete the interaction needed for this state
    Given I am ready to work with this ResearchOps state
    When I enter "Assisted Digital Support Discovery" into the "Project name" field
    And I enter "This discovery examines how caseworkers and support staff help people who cannot complete a digital application without assistance. The research will focus on confidence, evidence…" into the "Project description" field
    And I choose "discovery" from the "Service phase" field
    And I choose "planning" from the "Project status" field
    And I select "Continue to stakeholders and objectives"
    Then the "Stakeholders, objectives and user groups step" section should be available
    And I enter "Priya Shah | Service owner | priya.shah@example.gov.uk Mark Evans | Operations lead | mark.evans@example.gov.uk Amelia Brown | Policy adviser | amelia.brown@example.gov.uk" into the "Stakeholders" field
    And I enter "Understand where users need assisted digital support before, during and after the application journey. Identify operational signals that help staff recognise accessibility, safegu…" into the "Research objectives" field
    And I enter "Applicants with low digital confidence, support workers, caseworkers, users with accessibility needs, users who need language support" into the "User groups" field
    Then I should be able to continue the ResearchOps journey with confidence

  Scenario: Use the state accessibly
    Then the page should have one clear main heading
    And headings, labels and controls should be exposed in a logical reading order
    And I should be able to move through the available controls using a keyboard
    And I should be able to activate links, buttons and form controls without a mouse
Desktop

captured · https://researchops.pages.dev/pages/start/index.html

Start research project: Step 2 completed without AI rewrite invoked — Desktop
Mobile

captured · https://researchops.pages.dev/pages/start/index.html

Start research project: Step 2 completed without AI rewrite invoked — Mobile

Step 2 AI rewrite shown

captured · https://researchops.pages.dev/pages/start/index.html

Objectives meet the AI assistance threshold and the objectives AI rewrite panel is shown using a deterministic mocked response.

Gherkin acceptance criteria for this state
Feature: Define a research project

  As a user researcher
  I want to define a research project with objectives, stakeholders and ownership
  So that my team can start research work with shared context and traceable intent

  Background:
    Given I am a user researcher
    When I visit the start research project service

  Scenario: Understand the page purpose
    Then I should see content that supports start page for creating or beginning research project work.
    And I should understand what ResearchOps task I can complete from this page

  Scenario: Work with the "Step 2 AI rewrite shown" state
    Given I am using the start research project service
    Then the interface should make it clear that this state is for objectives meet the AI assistance threshold and the objectives AI rewrite panel is shown using a deterministic mocked response.
    And I should be given enough context to decide what to do next

  Scenario: Complete the interaction needed for this state
    Given I am ready to work with this ResearchOps state
    When I enter "Assisted Digital Support Discovery" into the "Project name" field
    And I enter "This discovery examines how caseworkers and support staff help people who cannot complete a digital application without assistance. The research will focus on confidence, evidence…" into the "Project description" field
    And I choose "discovery" from the "Service phase" field
    And I choose "planning" from the "Project status" field
    And I select "Continue to stakeholders and objectives"
    Then the "Stakeholders, objectives and user groups step" section should be available
    And I enter "Priya Shah | Service owner | priya.shah@example.gov.uk Mark Evans | Operations lead | mark.evans@example.gov.uk Amelia Brown | Policy adviser | amelia.brown@example.gov.uk" into the "Stakeholders" field
    And I enter "Understand where users need assisted digital support before, during and after the application journey. Identify operational signals that help staff recognise accessibility, safegu…" into the "Research objectives" field
    And I enter "Applicants with low digital confidence, support workers, caseworkers, users with accessibility needs, users who need language support" into the "User groups" field
    Then the "AI objectives support panel" section should be available
    And I select "Improve objectives with AI"
    Then I should see "Concise rewrite (optional):"
    Then I should be able to continue the ResearchOps journey with confidence

  Scenario: Use the state accessibly
    Then the page should have one clear main heading
    And headings, labels and controls should be exposed in a logical reading order
    And I should be able to move through the available controls using a keyboard
    And I should be able to activate links, buttons and form controls without a mouse
Desktop

captured · https://researchops.pages.dev/pages/start/index.html

Start research project: Step 2 AI rewrite shown — Desktop
Mobile

captured · https://researchops.pages.dev/pages/start/index.html

Start research project: Step 2 AI rewrite shown — Mobile

Step 3 default state

captured · https://researchops.pages.dev/pages/start/index.html

Final wizard step after the project definition, stakeholders, objectives and user groups have been entered.

Gherkin acceptance criteria for this state
Feature: Define a research project

  As a user researcher
  I want to define a research project with objectives, stakeholders and ownership
  So that my team can start research work with shared context and traceable intent

  Background:
    Given I am a user researcher
    When I visit the start research project service

  Scenario: Understand the page purpose
    Then I should see content that supports start page for creating or beginning research project work.
    And I should understand what ResearchOps task I can complete from this page

  Scenario: Work with the "Step 3 default state" state
    Given I am using the start research project service
    Then the interface should make it clear that this state is for final wizard step after the project definition, stakeholders, objectives and user groups have been entered.
    And I should be given enough context to decide what to do next

  Scenario: Complete the interaction needed for this state
    Given I am ready to work with this ResearchOps state
    When I enter "Assisted Digital Support Discovery" into the "Project name" field
    And I enter "This discovery examines how caseworkers and support staff help people who cannot complete a digital application without assistance. The research will focus on confidence, evidence…" into the "Project description" field
    And I choose "discovery" from the "Service phase" field
    And I choose "planning" from the "Project status" field
    And I select "Continue to stakeholders and objectives"
    Then the "Stakeholders, objectives and user groups step" section should be available
    And I enter "Priya Shah | Service owner | priya.shah@example.gov.uk Mark Evans | Operations lead | mark.evans@example.gov.uk Amelia Brown | Policy adviser | amelia.brown@example.gov.uk" into the "Stakeholders" field
    And I enter "Understand where users need assisted digital support before, during and after the application journey. Identify operational signals that help staff recognise accessibility, safegu…" into the "Research objectives" field
    And I enter "Applicants with low digital confidence, support workers, caseworkers, users with accessibility needs, users who need language support" into the "User groups" field
    And I select "Continue to lead researcher and notes"
    Then the "Lead researcher and notes step" section should be available
    Then I should be able to continue the ResearchOps journey with confidence

  Scenario: Use the state accessibly
    Then the page should have one clear main heading
    And headings, labels and controls should be exposed in a logical reading order
    And I should be able to move through the available controls using a keyboard
    And I should be able to activate links, buttons and form controls without a mouse
Desktop

captured · https://researchops.pages.dev/pages/start/index.html

Start research project: Step 3 default state — Desktop
Mobile

captured · https://researchops.pages.dev/pages/start/index.html

Start research project: Step 3 default state — Mobile

Step 3 completed before create project

captured · https://researchops.pages.dev/pages/start/index.html

Lead researcher, email and project notes entered on the final wizard step before project creation is submitted.

Gherkin acceptance criteria for this state
Feature: Define a research project

  As a user researcher
  I want to define a research project with objectives, stakeholders and ownership
  So that my team can start research work with shared context and traceable intent

  Background:
    Given I am a user researcher
    When I visit the start research project service

  Scenario: Understand the page purpose
    Then I should see content that supports start page for creating or beginning research project work.
    And I should understand what ResearchOps task I can complete from this page

  Scenario: Work with the "Step 3 completed before create project" state
    Given I am using the start research project service
    Then the interface should make it clear that this state is for lead researcher, email and project notes entered on the final wizard step before project creation is submitted.
    And I should be given enough context to decide what to do next

  Scenario: Complete the interaction needed for this state
    Given I am ready to work with this ResearchOps state
    When I enter "Assisted Digital Support Discovery" into the "Project name" field
    And I enter "This discovery examines how caseworkers and support staff help people who cannot complete a digital application without assistance. The research will focus on confidence, evidence…" into the "Project description" field
    And I choose "discovery" from the "Service phase" field
    And I choose "planning" from the "Project status" field
    And I select "Continue to stakeholders and objectives"
    Then the "Stakeholders, objectives and user groups step" section should be available
    And I enter "Priya Shah | Service owner | priya.shah@example.gov.uk Mark Evans | Operations lead | mark.evans@example.gov.uk Amelia Brown | Policy adviser | amelia.brown@example.gov.uk" into the "Stakeholders" field
    And I enter "Understand where users need assisted digital support before, during and after the application journey. Identify operational signals that help staff recognise accessibility, safegu…" into the "Research objectives" field
    And I enter "Applicants with low digital confidence, support workers, caseworkers, users with accessibility needs, users who need language support" into the "User groups" field
    And I select "Continue to lead researcher and notes"
    Then the "Lead researcher and notes step" section should be available
    And I enter "Alex Morgan" into the "Lead researcher name" field
    And I enter "alex.morgan@example.gov.uk" into the "Lead researcher email" field
    And I enter "Initial recruitment should include users with different levels of digital confidence and staff who handle assisted digital requests." into the "Project notes" field
    Then I should be able to continue the ResearchOps journey with confidence

  Scenario: Use the state accessibly
    Then the page should have one clear main heading
    And headings, labels and controls should be exposed in a logical reading order
    And I should be able to move through the available controls using a keyboard
    And I should be able to activate links, buttons and form controls without a mouse
Desktop

captured · https://researchops.pages.dev/pages/start/index.html

Start research project: Step 3 completed before create project — Desktop
Mobile

captured · https://researchops.pages.dev/pages/start/index.html

Start research project: Step 3 completed before create project — Mobile

Projects

Projects

/pages/projects/index.html

Project list page.

Default state

captured · https://researchops.pages.dev/pages/projects/index.html

Initial loaded page state.

Gherkin acceptance criteria for this state
Feature: Review research projects

  As a user researcher
  I want to review existing research projects
  So that I can find the right project and continue the right ResearchOps task

  Background:
    Given I am a user researcher
    When I visit the projects page

  Scenario: Understand the page purpose
    Then I should see content that supports project list page.
    And I should understand what ResearchOps task I can complete from this page

  Scenario: Work with the "Default state" state
    Given I am using the projects page
    Then the interface should make it clear that this state is for initial loaded page state.
    And I should be given enough context to decide what to do next

  Scenario: Use the default view
    Then I should understand what ResearchOps task this page supports
    And I should be able to choose an appropriate next action

  Scenario: Use the state accessibly
    Then the page should have one clear main heading
    And headings, labels and controls should be exposed in a logical reading order
    And I should be able to move through the available controls using a keyboard
    And I should be able to activate links, buttons and form controls without a mouse
Desktop

captured · https://researchops.pages.dev/pages/projects/index.html

Projects: Default state — Desktop
Mobile

captured · https://researchops.pages.dev/pages/projects/index.html

Projects: Default state — Mobile

Project dashboard

/pages/project-dashboard/index.html

Project dashboard page.

Default state

captured · https://researchops.pages.dev/pages/project-dashboard/index.html

Initial loaded page state.

Gherkin acceptance criteria for this state
Feature: Review a research project dashboard

  As a user researcher
  I want to review the status, evidence and next actions for a research project
  So that I can coordinate research activity across the team

  Background:
    Given I am a user researcher
    When I visit the project dashboard

  Scenario: Understand the page purpose
    Then I should see content that supports project dashboard page.
    And I should understand what ResearchOps task I can complete from this page

  Scenario: Work with the "Default state" state
    Given I am using the project dashboard
    Then the interface should make it clear that this state is for initial loaded page state.
    And I should be given enough context to decide what to do next

  Scenario: Use the default view
    Then I should understand what ResearchOps task this page supports
    And I should be able to choose an appropriate next action

  Scenario: Use the state accessibly
    Then the page should have one clear main heading
    And headings, labels and controls should be exposed in a logical reading order
    And I should be able to move through the available controls using a keyboard
    And I should be able to activate links, buttons and form controls without a mouse
Desktop

captured · https://researchops.pages.dev/pages/project-dashboard/index.html

Project dashboard: Default state — Desktop
Mobile

captured · https://researchops.pages.dev/pages/project-dashboard/index.html

Project dashboard: Default state — Mobile

Project outcomes

/pages/projects/outcomes/index.html

Outcomes page for project-level findings and outputs.

Default state

captured · https://researchops.pages.dev/pages/projects/outcomes/index.html

Initial loaded page state.

Gherkin acceptance criteria for this state
Feature: Manage project outcomes

  As a user researcher
  I want to review findings, outputs and decisions for a project
  So that I can keep research outcomes traceable to evidence and recommendations

  Background:
    Given I am a user researcher
    When I visit the project outcomes page

  Scenario: Understand the page purpose
    Then I should see content that supports outcomes page for project-level findings and outputs.
    And I should understand what ResearchOps task I can complete from this page

  Scenario: Work with the "Default state" state
    Given I am using the project outcomes page
    Then the interface should make it clear that this state is for initial loaded page state.
    And I should be given enough context to decide what to do next

  Scenario: Use the default view
    Then I should understand what ResearchOps task this page supports
    And I should be able to choose an appropriate next action

  Scenario: Use the state accessibly
    Then the page should have one clear main heading
    And headings, labels and controls should be exposed in a logical reading order
    And I should be able to move through the available controls using a keyboard
    And I should be able to activate links, buttons and form controls without a mouse
Desktop

captured · https://researchops.pages.dev/pages/projects/outcomes/index.html

Project outcomes: Default state — Desktop
Mobile

captured · https://researchops.pages.dev/pages/projects/outcomes/index.html

Project outcomes: Default state — Mobile

Project journals

/pages/projects/journals/index.html

Reflexive journal page.

Default state

captured · https://researchops.pages.dev/pages/projects/journals/index.html

Initial loaded page state.

Gherkin acceptance criteria for this state
Feature: Capture reflexive journal entries

  As a user researcher
  I want to capture reflexive notes during a project
  So that I can make assumptions, decisions and researcher influence visible

  Background:
    Given I am a user researcher
    When I visit the project journals page

  Scenario: Understand the page purpose
    Then I should see content that supports reflexive journal page.
    And I should understand what ResearchOps task I can complete from this page

  Scenario: Work with the "Default state" state
    Given I am using the project journals page
    Then the interface should make it clear that this state is for initial loaded page state.
    And I should be given enough context to decide what to do next

  Scenario: Use the default view
    Then I should understand what ResearchOps task this page supports
    And I should be able to choose an appropriate next action

  Scenario: Use the state accessibly
    Then the page should have one clear main heading
    And headings, labels and controls should be exposed in a logical reading order
    And I should be able to move through the available controls using a keyboard
    And I should be able to activate links, buttons and form controls without a mouse
Desktop

captured · https://researchops.pages.dev/pages/projects/journals/index.html

Project journals: Default state — Desktop
Mobile

captured · https://researchops.pages.dev/pages/projects/journals/index.html

Project journals: Default state — Mobile

Study

Study overview

/pages/study/index.html

Study overview and readiness controls.

Default state

captured · https://researchops.pages.dev/pages/study/index.html

Initial loaded page state.

Gherkin acceptance criteria for this state
Feature: Review study readiness

  As a user researcher
  I want to review a study and its readiness controls
  So that I can prepare research activity before sessions begin

  Background:
    Given I am a user researcher
    When I visit the study overview page

  Scenario: Understand the page purpose
    Then I should see content that supports study overview and readiness controls.
    And I should understand what ResearchOps task I can complete from this page

  Scenario: Work with the "Default state" state
    Given I am using the study overview page
    Then the interface should make it clear that this state is for initial loaded page state.
    And I should be given enough context to decide what to do next

  Scenario: Use the default view
    Then I should understand what ResearchOps task this page supports
    And I should be able to choose an appropriate next action

  Scenario: Use the state accessibly
    Then the page should have one clear main heading
    And headings, labels and controls should be exposed in a logical reading order
    And I should be able to move through the available controls using a keyboard
    And I should be able to activate links, buttons and form controls without a mouse
Desktop

captured · https://researchops.pages.dev/pages/study/index.html

Study overview: Default state — Desktop
Mobile

captured · https://researchops.pages.dev/pages/study/index.html

Study overview: Default state — Mobile

Discussion guides

/pages/study/guides/index.html

Discussion guide list and editor page.

Default state

captured · https://researchops.pages.dev/pages/study/guides/index.html

Initial loaded page state.

Gherkin acceptance criteria for this state
Feature: Manage discussion guides

  As a user researcher
  I want to create, review and organise discussion guides for a study
  So that sessions are run with consistent and purposeful research prompts

  Background:
    Given I am a user researcher
    When I visit the discussion guides page

  Scenario: Understand the page purpose
    Then I should see content that supports discussion guide list and editor page.
    And I should understand what ResearchOps task I can complete from this page

  Scenario: Work with the "Default state" state
    Given I am using the discussion guides page
    Then the interface should make it clear that this state is for initial loaded page state.
    And I should be given enough context to decide what to do next

  Scenario: Use the default view
    Then I should understand what ResearchOps task this page supports
    And I should be able to choose an appropriate next action

  Scenario: Use the state accessibly
    Then the page should have one clear main heading
    And headings, labels and controls should be exposed in a logical reading order
    And I should be able to move through the available controls using a keyboard
    And I should be able to activate links, buttons and form controls without a mouse
Desktop

captured · https://researchops.pages.dev/pages/study/guides/index.html

Discussion guides: Default state — Desktop
Mobile

captured · https://researchops.pages.dev/pages/study/guides/index.html

Discussion guides: Default state — Mobile

Participants

/pages/study/participants/index.html

Participants page for a study.

Default state

captured · https://researchops.pages.dev/pages/study/participants/index.html

Initial loaded page state.

Gherkin acceptance criteria for this state
Feature: Manage study participants

  As a user researcher
  I want to review and manage participants for a study
  So that recruitment and session planning reflect the study needs

  Background:
    Given I am a user researcher
    When I visit the participants page

  Scenario: Understand the page purpose
    Then I should see content that supports participants page for a study.
    And I should understand what ResearchOps task I can complete from this page

  Scenario: Work with the "Default state" state
    Given I am using the participants page
    Then the interface should make it clear that this state is for initial loaded page state.
    And I should be given enough context to decide what to do next

  Scenario: Use the default view
    Then I should understand what ResearchOps task this page supports
    And I should be able to choose an appropriate next action

  Scenario: Use the state accessibly
    Then the page should have one clear main heading
    And headings, labels and controls should be exposed in a logical reading order
    And I should be able to move through the available controls using a keyboard
    And I should be able to activate links, buttons and form controls without a mouse
Desktop

captured · https://researchops.pages.dev/pages/study/participants/index.html

Participants: Default state — Desktop
Mobile

captured · https://researchops.pages.dev/pages/study/participants/index.html

Participants: Default state — Mobile

Study session

/pages/study/session/index.html

Session running and note capture page.

Default state

captured · https://researchops.pages.dev/pages/study/session/index.html

Initial loaded page state.

Gherkin acceptance criteria for this state
Feature: Run a research session

  As a user researcher
  I want to run a research session and capture notes
  So that session evidence is recorded consistently and safely

  Background:
    Given I am a user researcher
    When I visit the study session page

  Scenario: Understand the page purpose
    Then I should see content that supports session running and note capture page.
    And I should understand what ResearchOps task I can complete from this page

  Scenario: Work with the "Default state" state
    Given I am using the study session page
    Then the interface should make it clear that this state is for initial loaded page state.
    And I should be given enough context to decide what to do next

  Scenario: Use the default view
    Then I should understand what ResearchOps task this page supports
    And I should be able to choose an appropriate next action

  Scenario: Use the state accessibly
    Then the page should have one clear main heading
    And headings, labels and controls should be exposed in a logical reading order
    And I should be able to move through the available controls using a keyboard
    And I should be able to activate links, buttons and form controls without a mouse
Desktop

captured · https://researchops.pages.dev/pages/study/session/index.html

Study session: Default state — Desktop
Mobile

captured · https://researchops.pages.dev/pages/study/session/index.html

Study session: Default state — Mobile

Utilities

Notes

/pages/notes/index.html

Notes page.

Default state

captured · https://researchops.pages.dev/pages/notes/index.html

Initial loaded page state.

Gherkin acceptance criteria for this state
Feature: Capture research notes

  As a user researcher
  I want to capture and review research notes
  So that evidence can be used later for synthesis and decisions

  Background:
    Given I am a user researcher
    When I visit the notes page

  Scenario: Understand the page purpose
    Then I should see content that supports notes page.
    And I should understand what ResearchOps task I can complete from this page

  Scenario: Work with the "Default state" state
    Given I am using the notes page
    Then the interface should make it clear that this state is for initial loaded page state.
    And I should be given enough context to decide what to do next

  Scenario: Use the default view
    Then I should understand what ResearchOps task this page supports
    And I should be able to choose an appropriate next action

  Scenario: Use the state accessibly
    Then the page should have one clear main heading
    And headings, labels and controls should be exposed in a logical reading order
    And I should be able to move through the available controls using a keyboard
    And I should be able to activate links, buttons and form controls without a mouse
Desktop

captured · https://researchops.pages.dev/pages/notes/index.html

Notes: Default state — Desktop
Mobile

captured · https://researchops.pages.dev/pages/notes/index.html

Notes: Default state — Mobile

Sessions

/pages/sessions/index.html

Sessions list page.

Default state

captured · https://researchops.pages.dev/pages/sessions/index.html

Initial loaded page state.

Gherkin acceptance criteria for this state
Feature: Review research sessions

  As a user researcher
  I want to review scheduled and completed research sessions
  So that I can coordinate session delivery and follow-up activity

  Background:
    Given I am a user researcher
    When I visit the sessions page

  Scenario: Understand the page purpose
    Then I should see content that supports sessions list page.
    And I should understand what ResearchOps task I can complete from this page

  Scenario: Work with the "Default state" state
    Given I am using the sessions page
    Then the interface should make it clear that this state is for initial loaded page state.
    And I should be given enough context to decide what to do next

  Scenario: Use the default view
    Then I should understand what ResearchOps task this page supports
    And I should be able to choose an appropriate next action

  Scenario: Use the state accessibly
    Then the page should have one clear main heading
    And headings, labels and controls should be exposed in a logical reading order
    And I should be able to move through the available controls using a keyboard
    And I should be able to activate links, buttons and form controls without a mouse
Desktop

captured · https://researchops.pages.dev/pages/sessions/index.html

Sessions: Default state — Desktop
Mobile

captured · https://researchops.pages.dev/pages/sessions/index.html

Sessions: Default state — Mobile

Analysis

Study synthesis

/pages/synthesize/index.html

Study-scoped evidence grouping and theme creation page.

Missing study ID error state

captured · https://researchops.pages.dev/pages/synthesize/index.html

Synthesis loaded without a study ID; the page shows the blocking route-context error.

Gherkin acceptance criteria for this state
Feature: Synthesize research evidence

  As a user researcher
  I want to group evidence and create traceable themes
  So that insights and recommendations remain connected to source evidence

  Background:
    Given I am a user researcher
    When I visit the study synthesis page

  Scenario: Understand the page purpose
    Then I should see content that supports study-scoped evidence grouping and theme creation page.
    And I should understand what ResearchOps task I can complete from this page

  Scenario: Work with the "Missing study ID error state" state
    Given I am using the study synthesis page
    Then the interface should make it clear that this state is for synthesis loaded without a study ID; the page shows the blocking route-context error.
    And I should be given enough context to decide what to do next

  Scenario: Use the default view
    Then I should understand what ResearchOps task this page supports
    And I should be able to choose an appropriate next action

  Scenario: Use the state accessibly
    Then the page should have one clear main heading
    And headings, labels and controls should be exposed in a logical reading order
    And I should be able to move through the available controls using a keyboard
    And I should be able to activate links, buttons and form controls without a mouse
Desktop

captured · https://researchops.pages.dev/pages/synthesize/index.html

Study synthesis: Missing study ID error state — Desktop
Mobile

captured · https://researchops.pages.dev/pages/synthesize/index.html

Study synthesis: Missing study ID error state — Mobile

Empty evidence state

captured · https://researchops.pages.dev/pages/synthesize/?pid=recVisualProject001&sid=recVisualStudy001

Study synthesis loaded with valid study context but no captured evidence notes. The page routes the researcher to evidence capture rather than showing synthesis controls.

Gherkin acceptance criteria for this state
Feature: Synthesize research evidence

  As a user researcher
  I want to group evidence and create traceable themes
  So that insights and recommendations remain connected to source evidence

  Background:
    Given I am a user researcher
    When I visit the study synthesis page

  Scenario: Understand the page purpose
    Then I should see content that supports study-scoped evidence grouping and theme creation page.
    And I should understand what ResearchOps task I can complete from this page

  Scenario: Work with the "Empty evidence state" state
    Given I am using the study synthesis page
    Then the interface should make it clear that this state is for study synthesis loaded with valid study context but no captured evidence notes. The page routes the researcher to evidence capture rather than showing synthesis controls.
    And I should be given enough context to decide what to do next

  Scenario: Complete the interaction needed for this state
    Given I am ready to work with this ResearchOps state
    Then I should see "Capture evidence before starting synthesis"
    Then I should see "Capture evidence in a session"
    Then I should be able to continue the ResearchOps journey with confidence

  Scenario: Use the state accessibly
    Then the page should have one clear main heading
    And headings, labels and controls should be exposed in a logical reading order
    And I should be able to move through the available controls using a keyboard
    And I should be able to activate links, buttons and form controls without a mouse
Desktop

captured · https://researchops.pages.dev/pages/synthesize/?pid=recVisualProject001&sid=recVisualStudy001

Study synthesis: Empty evidence state — Desktop
Mobile

captured · https://researchops.pages.dev/pages/synthesize/?pid=recVisualProject001&sid=recVisualStudy001

Study synthesis: Empty evidence state — Mobile

Evidence available before working clusters

captured · https://researchops.pages.dev/pages/synthesize/?pid=recVisualProject001&sid=recVisualStudy001

Study synthesis with realistic evidence available. The first available task is creating a working cluster grouping; evidence selection remains hidden until a cluster exists.

Gherkin acceptance criteria for this state
Feature: Synthesize research evidence

  As a user researcher
  I want to group evidence and create traceable themes
  So that insights and recommendations remain connected to source evidence

  Background:
    Given I am a user researcher
    When I visit the study synthesis page

  Scenario: Understand the page purpose
    Then I should see content that supports study-scoped evidence grouping and theme creation page.
    And I should understand what ResearchOps task I can complete from this page

  Scenario: Work with the "Evidence available before working clusters" state
    Given I am using the study synthesis page
    Then the interface should make it clear that this state is for study synthesis with realistic evidence available. The first available task is creating a working cluster grouping; evidence selection remains hidden until a cluster exists.
    And I should be given enough context to decide what to do next

  Scenario: Complete the interaction needed for this state
    Given I am ready to work with this ResearchOps state
    Then I should see "Create a working cluster grouping before selecting evidence."
    Then I should be able to continue the ResearchOps journey with confidence

  Scenario: Use the state accessibly
    Then the page should have one clear main heading
    And headings, labels and controls should be exposed in a logical reading order
    And I should be able to move through the available controls using a keyboard
    And I should be able to activate links, buttons and form controls without a mouse
Desktop

captured · https://researchops.pages.dev/pages/synthesize/?pid=recVisualProject001&sid=recVisualStudy001

Study synthesis: Evidence available before working clusters — Desktop
Mobile

captured · https://researchops.pages.dev/pages/synthesize/?pid=recVisualProject001&sid=recVisualStudy001

Study synthesis: Evidence available before working clusters — Mobile

Working cluster grouping created

captured · https://researchops.pages.dev/pages/synthesize/?pid=recVisualProject001&sid=recVisualStudy001

A researcher creates a provisional working cluster grouping before adding evidence. Evidence selection becomes available only after the cluster exists.

Gherkin acceptance criteria for this state
Feature: Synthesize research evidence

  As a user researcher
  I want to group evidence and create traceable themes
  So that insights and recommendations remain connected to source evidence

  Background:
    Given I am a user researcher
    When I visit the study synthesis page

  Scenario: Understand the page purpose
    Then I should see content that supports study-scoped evidence grouping and theme creation page.
    And I should understand what ResearchOps task I can complete from this page

  Scenario: Work with the "Working cluster grouping created" state
    Given I am using the study synthesis page
    Then the interface should make it clear that this state is for a researcher creates a provisional working cluster grouping before adding evidence. Evidence selection becomes available only after the cluster exists.
    And I should be given enough context to decide what to do next

  Scenario: Complete the interaction needed for this state
    Given I am ready to work with this ResearchOps state
    When I enter "Confidence before the form starts" into the "Working cluster label" field
    And I enter "Evidence about how users judge whether they are ready to begin the service." into the "Working cluster description" field
    And I select "Create working cluster grouping"
    Then I should see "Created working cluster grouping Confidence before the form starts."
    Then I should see "I was not sure whether I had the right documents before I started, so I nearly called the helpline instead of continuing online."
    Then I should be able to continue the ResearchOps journey with confidence

  Scenario: Use the state accessibly
    Then the page should have one clear main heading
    And headings, labels and controls should be exposed in a logical reading order
    And I should be able to move through the available controls using a keyboard
    And I should be able to activate links, buttons and form controls without a mouse
Desktop

captured · https://researchops.pages.dev/pages/synthesize/?pid=recVisualProject001&sid=recVisualStudy001

Study synthesis: Working cluster grouping created — Desktop
Mobile

captured · https://researchops.pages.dev/pages/synthesize/?pid=recVisualProject001&sid=recVisualStudy001

Study synthesis: Working cluster grouping created — Mobile

Evidence added to working cluster grouping

captured · https://researchops.pages.dev/pages/synthesize/?pid=recVisualProject001&sid=recVisualStudy001

A researcher selects two evidence notes and adds them to an existing working cluster grouping. Theme creation becomes available after evidence is grouped.

Gherkin acceptance criteria for this state
Feature: Synthesize research evidence

  As a user researcher
  I want to group evidence and create traceable themes
  So that insights and recommendations remain connected to source evidence

  Background:
    Given I am a user researcher
    When I visit the study synthesis page

  Scenario: Understand the page purpose
    Then I should see content that supports study-scoped evidence grouping and theme creation page.
    And I should understand what ResearchOps task I can complete from this page

  Scenario: Work with the "Evidence added to working cluster grouping" state
    Given I am using the study synthesis page
    Then the interface should make it clear that this state is for a researcher selects two evidence notes and adds them to an existing working cluster grouping. Theme creation becomes available after evidence is grouped.
    And I should be given enough context to decide what to do next

  Scenario: Complete the interaction needed for this state
    Given I am ready to work with this ResearchOps state
    When I select the "evidence item" checkbox
    And I select the "evidence item" checkbox
    And I choose "cluster-confidence-start" from the "Target working cluster grouping" field
    And I select "Add selected evidence to the working cluster grouping"
    Then I should see "Added 2 evidence items to Confidence before the form starts."
    Then I should be able to continue the ResearchOps journey with confidence

  Scenario: Use the state accessibly
    Then the page should have one clear main heading
    And headings, labels and controls should be exposed in a logical reading order
    And I should be able to move through the available controls using a keyboard
    And I should be able to activate links, buttons and form controls without a mouse
Desktop

captured · https://researchops.pages.dev/pages/synthesize/?pid=recVisualProject001&sid=recVisualStudy001

Study synthesis: Evidence added to working cluster grouping — Desktop
Mobile

captured · https://researchops.pages.dev/pages/synthesize/?pid=recVisualProject001&sid=recVisualStudy001

Study synthesis: Evidence added to working cluster grouping — Mobile

Theme creation hidden before evidence is grouped

captured · https://researchops.pages.dev/pages/synthesize/?pid=recVisualProject001&sid=recVisualStudy001

Theme creation remains hidden until at least one working cluster grouping contains source evidence.

Gherkin acceptance criteria for this state
Feature: Synthesize research evidence

  As a user researcher
  I want to group evidence and create traceable themes
  So that insights and recommendations remain connected to source evidence

  Background:
    Given I am a user researcher
    When I visit the study synthesis page

  Scenario: Understand the page purpose
    Then I should see content that supports study-scoped evidence grouping and theme creation page.
    And I should understand what ResearchOps task I can complete from this page

  Scenario: Work with the "Theme creation hidden before evidence is grouped" state
    Given I am using the study synthesis page
    Then the interface should make it clear that this state is for theme creation remains hidden until at least one working cluster grouping contains source evidence.
    And I should be given enough context to decide what to do next

  Scenario: Complete the interaction needed for this state
    Given I am ready to work with this ResearchOps state
    Then the "working cluster grouping" section should be available
    Then I should see "Add evidence to a working cluster grouping before creating a theme."
    Then I should be able to continue the ResearchOps journey with confidence

  Scenario: Use the state accessibly
    Then the page should have one clear main heading
    And headings, labels and controls should be exposed in a logical reading order
    And I should be able to move through the available controls using a keyboard
    And I should be able to activate links, buttons and form controls without a mouse
Desktop

captured · https://researchops.pages.dev/pages/synthesize/?pid=recVisualProject001&sid=recVisualStudy001

Study synthesis: Theme creation hidden before evidence is grouped — Desktop
Mobile

captured · https://researchops.pages.dev/pages/synthesize/?pid=recVisualProject001&sid=recVisualStudy001

Study synthesis: Theme creation hidden before evidence is grouped — Mobile

Theme created with evidence traceability

captured · https://researchops.pages.dev/pages/synthesize/?pid=recVisualProject001&sid=recVisualStudy001

A theme is created from a populated cluster and the source evidence IDs remain inspectable.

Gherkin acceptance criteria for this state
Feature: Synthesize research evidence

  As a user researcher
  I want to group evidence and create traceable themes
  So that insights and recommendations remain connected to source evidence

  Background:
    Given I am a user researcher
    When I visit the study synthesis page

  Scenario: Understand the page purpose
    Then I should see content that supports study-scoped evidence grouping and theme creation page.
    And I should understand what ResearchOps task I can complete from this page

  Scenario: Work with the "Theme created with evidence traceability" state
    Given I am using the study synthesis page
    Then the interface should make it clear that this state is for a theme is created from a populated cluster and the source evidence IDs remain inspectable.
    And I should be given enough context to decide what to do next

  Scenario: Complete the interaction needed for this state
    Given I am ready to work with this ResearchOps state
    When I choose "cluster-confidence-start" from the "Working cluster grouping for the theme" field
    And I enter "Digital confidence is shaped before the form starts" into the "Theme label" field
    And I enter "Users decide whether to continue based on evidence expectations, support routes and confidence before they begin entering details." into the "Theme description" field
    And I select "Create theme"
    Then I should see "Created theme Digital confidence is shaped before the form starts."
    And I select "theme traceability details"
    Then I should be able to continue the ResearchOps journey with confidence

  Scenario: Use the state accessibly
    Then the page should have one clear main heading
    And headings, labels and controls should be exposed in a logical reading order
    And I should be able to move through the available controls using a keyboard
    And I should be able to activate links, buttons and form controls without a mouse
Desktop

captured · https://researchops.pages.dev/pages/synthesize/?pid=recVisualProject001&sid=recVisualStudy001

Study synthesis: Theme created with evidence traceability — Desktop
Mobile

captured · https://researchops.pages.dev/pages/synthesize/?pid=recVisualProject001&sid=recVisualStudy001

Study synthesis: Theme created with evidence traceability — Mobile