RESEARCH SUPPORT
MAXQDA support
before coding starts
Support for qualitative researchers setting up or rescuing a MAXQDA project: document groups and variables, a team coding protocol and a rule for translated transcripts, settled early so that the analysis stays easy to account for.
No Commitment Required
Strictly Confidential
In-House PhD-Level Statisticians
Fixed Project Fee
Same-Day Response
What Is MAXQDA Project Setup?
MAXQDA support at OnlineSPSS is help with the research side of a project file: how documents are grouped, which document variables describe each participant, how a team will code together and how translated material is handled. It is research-analysis support, not licensing, installation or vendor support, which stay with the software publisher. Done early, MAXQDA project setup keeps a growing project retrievable, and later it lets tools such as the Code Matrix Browser and MAXMaps be read for what they display. Setting up and reviewing such projects is carried out in-house at OnlineSPSS, a specialist statistical consultancy for academic, clinical and professional research, by PhD-level statisticians, and what the accounts mean is decided by the researcher.
WHEN TO ENGAGE
Where Structure Pays Off in a MAXQDA Project
Using MAXQDA well depends on decisions taken before the first segment is coded, and the gap shows when coding grows faster than the structure behind it.
Before the First Transcript Is Coded Transcripts are arriving, and the document groups, participant variables and a starting code system are better settled now than after hundreds of segments have been coded.
Material From Several Sources Transcripts from a transcription service, field notes and a survey export arrive in different formats, so document names, import settings and the identifier that links them are fixed before anything is coded.
Team Protocol and Translated Material Coders work across sites or languages, so a protocol states who codes what, in which language, and how translated passages are recorded, before the first shared segment is coded.
Patterns to Show Across Cases Coding is finished and the findings must show how themes vary across participants or groups, which depends on variables being set and visual tools being used appropriately.
PROJECT ARCHITECTURE
Document Groups, Codes and Memos in MAXQDA
A MAXQDA file is easiest to analyze when its documents, variables, codes and memos were organized for the question before coding began, and each is set up deliberately.
Document Groups and Sets
Transcripts, field notes and documents are grouped by source or participant category, so that coding and retrieval can be limited to the material a question concerns.
Document Variables
Participant characteristics such as role, site or interview wave are stored as variables, which allows codes to be compared across groups later without recoding anything.
Code System Design
Codes are named, defined in a code memo and arranged in a hierarchy of manageable depth, in line with Thematic Analysis where themes are the aim.
Memos as an Audit Trail
Analytic memos record why a code was created, merged or dropped, and the trail supports the trustworthiness and reflexivity that a reviewer of qualitative work expects.
Visual Tools
The Code Matrix Browser, Code Relations Browser and MAXMaps show distributions and links among codes, and they are read as aids to interpretation, not as measures of importance.
Integration With Numbers
Where coded material is combined with survey or other numeric data, the integration follows the design set out for Mixed Methods Research.
STRUCTURAL WEAKNESSES
Setup Faults a Reviewer Notices Later
Most weaknesses in a coded project are introduced in its setup, and they surface only when a comparison is attempted or a reviewer asks how the analysis was built.
Documents Grouped by Convenience Files are sorted by date of import and not by the participant categories the question compares, so retrieving one group means selecting documents by hand each time.
Segments Stripped of Context Segments coded as a phrase or two lose the context that gives them meaning, so a segmentation rule is agreed and applied before codes are compared across documents.
Variables Typed In After Coding Participant characteristics are filled in from memory once coding is done, so values are inconsistent, and the variables are instead set from the interview records at the start.
Protocol Agreed Only in Conversation Rules for proposing codes and settling disagreements live in people's memory, so a new coder works differently, and a short written protocol is dated and kept with the project.
Reflexivity Left Out The researcher's assumptions and decisions are absent from the record, so the audit trail does not show how interpretation developed out of the data.
Speakers Marked Differently Transcripts arrive with interviewer and participant turns labeled differently from file to file, so a participant's words cannot be retrieved apart from the questions, and one transcription convention is fixed before import.
DELIVERABLES
Project File, Codebook and Audit Trail
Structure, definitions and decisions are documented alongside the project file, so the logic of the coding is visible without reopening every segment.
Structured Project File The MAXQDA project with document groups, variables and a code system arranged as agreed, ready for your own coding or for the coding already completed.
Codebook With Definitions Each code listed with its definition, its inclusion and exclusion rules and an example segment, consistent with the code memos held in the project.
Coding Protocol A short protocol for applying codes consistently, including how new codes are proposed and how disagreement between coders is resolved.
Agreement Check Report Where the approach calls for two coders, the result of an intercoder agreement check on a sample of documents, with a note on how disagreements were resolved.
Visual Tool Exports Matrices, maps and relation displays exported with notes on what each shows and what it does not, for use in a thesis or an article.
Analytic Audit Trail A dated summary of structural decisions, such as merged and renamed codes, in support of the transparency expected under Qualitative & Mixed Methods Analysis.
ILLUSTRATIVE EXAMPLE
A Bilingual Interview Project Set Up Before Coding
An illustration of how a project with two languages and two coders was organized so that sites could be compared later.
ILLUSTRATIVE EXAMPLE · HOSPICE VOLUNTEER INTERVIEW RESEARCH · UNITED STATES
A doctoral nursing researcher was about to code interviews with hospice volunteers at three sites, some in English and some in Spanish, and a second researcher would code part of the material.
The project was set up in document groups by site and by volunteer role, with document variables for site, language, tenure and interview date taken from the interview records. The complication was translation: a few Spanish transcripts had already been translated by different people, in different styles. The researchers decided to code Spanish interviews in the original language and translate only the quotations used in reporting, recorded the language as a variable, and wrote a short protocol covering who codes which documents and how disagreements are settled. After coding, the Code Matrix Browser compared sites, and the comparison was reported as a pattern in what volunteers said, with the passages shown beside each display.
Outcome: The researcher received the structured MAXQDA project, the document variable list, the coding protocol, a note on the handling of translation and guidance on reading the exported displays, ready for the methods section.
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.
SOFTWARE
MAXQDA With Other Qualitative Programs
A second program enters a MAXQDA study when collaborators already work in another package or the survey strand is analyzed in a statistics program.
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.
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.
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.
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.
RESEARCH RESPONSIBILITY
Interpretation Remains Your Analytical Work
A structured project organizes the evidence, whereas deciding what participants meant and which themes matter is interpretive work that belongs to the researcher.
Agreed Statistical Support OnlineSPSS provides the agreed methodological, analytical and statistical reporting support, defined in a scope that is confirmed before any work begins.
No Intellectual Contribution OnlineSPSS does not claim any intellectual contribution to your thesis, article or report. Authorship remains the researcher's.
Your Research Decisions The research question, the interpretation of participants' accounts, the choice of themes, the discussion and the conclusions remain yours, with overall responsibility.
Confidential Handling Research data and project details are handled confidentially, project information is not published, and an NDA is available where required.
FREQUENTLY ASKED QUESTIONS
Questions About Structuring a MAXQDA Project
A translated transcript, an undated memo or a matrix shown without its passages can each weaken a qualitative report under review.
What does setting up a MAXQDA project involve?
MAXQDA project setup at OnlineSPSS covers the structure of the project file: document groups and variables, a defined code system, memos for the audit trail, and the choice of visual tools for examining the coded material. Coding itself can remain with you or a team, and the structure can be agreed before the first transcript is imported or revised once coding is under way.
Should transcripts be coded in the original language or after translation?
Either can be defended, provided the choice is made once and recorded. Coding in the original language keeps nuance that translation can flatten, whereas coding a translation lets a team with different languages share one code system. Many projects code in the original and translate only the quotations used in reporting, with a second reader checking the translations. A document variable for language keeps the choice visible.
What belongs in a memo, and why do memos matter for rigor?
A memo records a decision and its reasoning: why a code was created, merged or dropped, what a pattern might mean, or what the researcher expected before reading. Dated and linked to the codes or documents concerned, memos form the audit trail that lets a reviewer follow how interpretation developed, and they are where notes on the researcher’s own position are kept.
Can a visual tool serve as evidence in a paper?
A visual can illustrate a pattern, but it does not stand as evidence. A matrix or map displays coding decisions, and its meaning depends on how the material was segmented and coded. The claim rests on the underlying segments, quotations and the argument that connects them, with the display placed beside them.
How do you protect my research data and confidentiality?
Your data and project details are handled confidentially, and project information is not published. Researcher names and institutions are not used publicly without permission. An NDA is available where required and can be arranged before sensitive materials are shared. Read more about confidentiality and data security.
What happens when I request an assessment, and how long does it take?
You share your research question, design and relevant materials, such as a sample of transcripts, the research aim, any draft codebook and the participant list, 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.
NEXT STEP
Give Your Coding a Structure
That Reviewers Can Follow
Describe the kind of material, the number of coders and the questions the study asks, and attach the project file or codebook if coding has already started.
No Commitment Required
Strictly Confidential
Fixed Project Fee
In-House PhD-Level Statisticians
Same-Day Response
Serving Researchers Since 2014