Opens in a new tab

STATISTICAL SOFTWARE

Delve Qualitative Analysis
Coding Decisions That Outlast the Workspace

Our Delve qualitative analysis service carries out coding and theme development in Delve, working from your project, and returns the coded data and memos linked to supporting excerpts as agreed, with the codebook where the method uses one, so the analysis is not tied to one browser workspace.

No Commitment Required

Strictly Confidential

In-House PhD-Level Statisticians

Fixed Project Fee

Same-Day Response

What Is Delve Used For in Research?

Delve is a web-based qualitative coding tool, hosted in the cloud, in which researchers upload transcripts, build a codebook with nested codes and code excerpts alone or as a team. Researchers choose it for how readily a project starts and for shared access to the same transcripts, and it can support several qualitative approaches, such as thematic analysis, grounded theory and content analysis. Because codes can be created and renamed at any point, their names tend to drift, so definitions and rules for what a code includes have to be written alongside the coding. OnlineSPSS, a specialist statistical consultancy for academic, clinical and professional research, provides a Delve qualitative analysis service in which an in-house PhD-level statistician carries out the agreed analysis in Delve, working from your project and recording the codebook at each stage.

WHEN TO ENGAGE

How Delve Projects Reach Us

A web-based workspace lets a team begin coding at once, and requests usually follow when codes have drifted, a theme cannot be traced, a milestone is due, or the work must exist as files.

Code Names Drifting Codes were renamed and reused as the project grew, so Delve qualitative coding needs a codebook with inclusion and exclusion rules before it can be relied on.

Team Coding Without a Shared Process Several people code the same transcripts with no agreed procedure, so collaborative qualitative coding needs shared rules and, where the method uses one, a consistency check.

Themes Without Their Excerpts Theme names appear in a document, but the memos and decisions behind them are not linked to excerpts, so the Delve thematic analysis cannot yet be traced.

A Milestone to Export A thesis chapter, report or handover is due, and the codebook and coded data have to be exported as they stand so that the work is not held by a single workspace.

ANALYSES IN DELVE

Approaches Carried Out in Delve for Transcript Data

Transcript projects in Delve follow different traditions, and each card links to the method page on how that tradition uses a codebook, if it uses one at all.

Thematic Analysis

Codes are grouped into candidate themes inside the nested codebook, and the parent and child structure is revised as themes are reviewed, so the hierarchy records how each theme formed.

Explore Thematic Analysis
Grounded Theory

Open codes are compared across transcripts and gathered into higher-level categories in the nested codebook, with a memo recording each comparison as the theory forms.

Explore Grounded Theory
Content Analysis

Categories with clear inclusion rules are applied across transcripts, with dual coding used as a consistency check where the design requires it.

Explore Content Analysis
Framework Analysis

Excerpts exported from Delve are arranged into a case-by-theme chart, and each summary keeps a reference to the transcript it came from.

Explore Framework Analysis
Narrative Analysis

Each story is coded first as a whole account, for its turning points and its ending, before smaller excerpts are coded, so fragments never replace the narrative.

Explore Narrative Analysis
Interpretative Phenomenological Analysis (IPA)

Each participant's transcript keeps its own experiential codes at first, and shared themes are built only after every account has been read on its own terms.

Explore Interpretative Phenomenological Analysis (IPA)

COMMON DELVE ISSUES

Where an Easy Start in Coding Goes Wrong

In Delve research analysis, coding that starts easily can drift as transcripts are added, so these checks are made before a theme is reported.

Code Names That Move A code renamed during coding may now cover different text, so names are fixed against written definitions and the earlier excerpts are rechecked.

No Inclusion or Exclusion Rules Rules state what belongs under a code and what does not. Without them, a code is applied by feel, so rules are written from examples taken from the transcripts.

Nesting Under the Wrong Parent A code placed under the wrong parent changes the meaning of the structure, so the hierarchy is read from the top and each placement is justified.

Memos Not Linked to Excerpts Theme decisions linked to supporting excerpts form an audit trail, and unlinked ones do not, so the links are checked before themes are written up.

Team Coding Without Comparison When two people code one transcript, differences show where a definition is unclear. They are discussed and settled, and agreement statistics are used only where the approach calls for them.

Codes Applied Automatically Where an AI feature has applied codes from their names and descriptions, each application is checked against the written definition, because a vague description produces broad, confident coding.

DELIVERABLES

What You Receive From a Delve Analysis

The files are agreed in the scope and provided where applicable, taken at milestones so that the analysis is not locked to one workspace.

Codebook Export The codebook with nested codes, definitions and rules, exported at the agreed milestones, where the method uses a codebook.

Coded Data Export Coded transcripts and excerpts exported by code and by theme, with the source of each excerpt identified.

Theme Development Record Memos and decisions linked to the supporting excerpts, showing how each theme was developed.

Reviewed Code Structure The final code structure after review, with merged, renamed and retired codes listed and the reasons recorded.

Team Coding Notes Notes on how differences between coders were settled, with a consistency check where the method uses one.

Interpretation and Reporting Themes written up with the excerpts behind them, and a methods paragraph naming the codebook stages and how differences between coders were settled.

OTHER PLATFORMS

When Another Platform May Be More Appropriate

When a study adds media, survey data or many cases, or needs its themes laid out visually, another environment may suit it better than one built around transcripts.

ILLUSTRATIVE EXAMPLE

How a Delve Analysis May Look in Practice

An illustration of how drifting code names in a team project become a documented codebook with traceable themes.

ILLUSTRATIVE EXAMPLE · ONLINE BANKING USABILITY RESEARCH · UNITED STATES

A product research team at a financial technology company interviewed users of a mobile banking app about how they manage money, and coded the transcripts in Delve with an inductive thematic approach.

Several team members had coded in parallel as transcripts arrived. By the time the project was reviewed, a code called trust stood for data security in some transcripts and for brand reputation in others, and nearby codes overlapped. A codebook was written from the excerpts, with a definition and inclusion and exclusion rules for every code, the codes were renamed or split accordingly, and the earlier transcripts were recoded under the revised rules. Memos recording how each theme was developed were linked to its supporting excerpts, and the codebook and coded data were exported at the end of each coding stage so that the team could continue in its own workspace.

Outcome: The team received the exported codebook and coded data, the reviewed code structure with its change record, and theme memos linked to their excerpts, ready to extend as new interviews arrived.

View Case Examples

This example does not describe a real client or project. We never share details of actual client work, in line with the confidentiality we promise every researcher. This illustrative example is included to show the type, scope, and standard of work involved in this kind of analysis.

RESEARCH DISCIPLINES

Research Fields Where Delve Is Common

Delve is used for interview and transcript analysis in academic and applied settings, and the field shapes which approach and which reporting standard apply.

Explore All Research Disciplines

HOW WE ASSESS YOUR PROJECT

We Review Your Actual Research

Your assessment is based on a review of your actual research materials and analytical requirements, not a generic project category.

1

You Submit Your Project Details

Share whatever is available at the current stage, such as the research aim, protocol or proposal, dataset, variable list, manuscript or statistical requirements.

2

We Review Your Research and Define the Scope

Your statistically trained Research Coordinator reviews the materials to understand the study design, research questions, data structure, analytical requirements and expected deliverables. If clarification is needed, additional documents or information can be requested before the assessment is finalized.

Delve ProjectTranscriptsCodebook ExportMemosReviewer Comments
3

Your Analysis Is Completed and Delivered

Once the scope and fixed project fee are agreed, the in-house statistician completes the work and the Research Coordinator remains the communication point through delivery, with the analysis, deliverables and timeline as agreed.

RESEARCHER VOICE

What Researchers Say

Feedback from a user research lead on keeping the work in the team's own platform while code names and definitions were put in order.

“I needed the work kept in Delve because that is what our team uses internally. The main problem was code names and definitions drifting as the project grew. OnlineSPSS corrected the setup and returned the project files with clear reporting, which made later changes much easier.”

Independent reviews

4.5/5.0

Excellent rating

Read All Reviews

Statistical Support Within Your Research OnlineSPSS provides the agreed methodological, analytical and statistical reporting support, including the Delve exports and project files described in the scope. The researcher or research team retains the scientific question, substantive interpretation, conclusions and overall responsibility for the research.

FREQUENTLY ASKED QUESTIONS

Questions About Delve Analysis for Research

Short answers to what researchers ask before sharing a Delve project, from the approaches we carry out and reviewer acceptance to code drift, suggested codes and confidentiality.

Delve analysis at OnlineSPSS covers thematic, content, framework and narrative analysis, grounded theory and interpretative phenomenological analysis of transcript data. The approach follows your research question and is confirmed during the assessment.

Reviewers judge the analysis, not the program. They ask how codes were defined, how themes were reached and whether the report follows a standard such as COREQ or SRQR, so a Delve study is as defensible as its code definitions, its theme memos and its methods description. The methods section names Delve as the tool and then describes the procedure, which is what reviewers assess.

By separating a code’s name from its meaning. A rename is allowed only when the definition stays the same; when the meaning shifts, a new code is created and the excerpts under the old one are reread and reassigned, so one label never covers two ideas. Each change and its reason are listed in the reviewed code structure.

A suggestion is a prompt, not a finding. Where such a feature has been used, each suggested code is checked against the text and kept, changed or dropped by the researcher’s own judgment, and the final codebook records what the codes mean. Responsibility for the interpretation remains with the research team.

Your Delve project, transcripts and exports are handled confidentially, and project information is not published. An NDA is available where required and can be arranged before sensitive materials are shared. Read more about confidentiality and data security.

You share your research question, design and relevant materials, such as the Delve project or your transcripts, and a statistically trained Research Coordinator reviews the request and responds the same day. The analysis, deliverables, timeline and one fixed project fee are then confirmed before any work begins, so the timeline follows from the agreed scope.

Still have a question? Find more answers in our full FAQ.

View All FAQs →

NEXT STEP

Discuss Your
Delve Project With Us

Share your research question, the approach you intend to follow and the Delve project or transcripts you hold. We check the code names against their excerpts and confirm the scope before any work begins.

No Commitment Required

Strictly Confidential

Fixed Project Fee

In-House PhD-Level Statisticians

Same-Day Response

Serving Researchers Since 2014