Skip to main content

Verified archive ·  Programmes, funding, departments, datasets, events, topics, and research prompts with direct routes back to the source.

Move from transcript to theme

Qualitative Coding and Theme Builder

Build a defensible qualitative coding strategy for interviews, focus groups, fieldnotes, or documents.

Analysis
Planner
Advanced
Qualitative
Open Coding
Memo Writing

Request a prompt

PROMPT: Qualitative Coding and Theme Builder
Move from transcript to theme
Analysis · Qualitative Analysis · Analysis

When to use this

  • Use this when you have qualitative material but need a disciplined analysis plan.
  • Use this before opening NVivo, Atlas.ti, MAXQDA, or a spreadsheet.
  • Use this when you need stronger logic between evidence and final argument.

What you should prepare first

  • Data type: [interviews, focus groups, ethnographic notes, documents, online posts, policy texts, etc.]
  • Research question or analytic aim: [state clearly]
  • Sample size and complexity: [approximate number of interviews, pages, cases, sites]
  • Analytic style: [inductive, deductive, abductive, theory-informed, reflexive thematic analysis, grounded theory inspired, discourse analysis, etc.]
  • Any concepts or theories that must remain visible in the coding process: [optional]

Paste this prompt

You are an elite sociology research and writing partner with strong expertise in sociological theory, research design, data analysis, academic communication, and publication standards.

Primary task:
Design a qualitative coding strategy for my sociology project and show how to move from raw material to robust themes without flattening the data.

Project details I will provide or you should ask me to clarify:
- Data type: [interviews, focus groups, ethnographic notes, documents, online posts, policy texts, etc.]
- Research question or analytic aim: [state clearly]
- Sample size and complexity: [approximate number of interviews, pages, cases, sites]
- Analytic style: [inductive, deductive, abductive, theory-informed, reflexive thematic analysis, grounded theory inspired, discourse analysis, etc.]
- Any concepts or theories that must remain visible in the coding process: [optional]

How you should work:
1. Recommend a coding strategy that fits the question and analytic tradition.
2. Build a starter codebook with parent codes, child codes, definitions, and inclusion or exclusion notes.
3. Explain how to write analytic memos and when to merge, split, or retire codes.
4. Show how to move from codes to categories to themes or arguments.
5. Flag common weak points such as descriptive coding overload, premature theory imposition, or overclaiming from thin data.

Output requirements:
- A starter codebook.
- A memo-writing workflow.
- A theme-development pathway tied to the research question.

Quality guardrails:
- Do not confuse frequent topics with analytically important themes.
- Keep contradictory or marginal cases visible instead of coding them away.
- If theory is used, explain whether it guides coding, interpretation, or both.

If crucial information is missing, make the minimum reasonable assumptions, label them clearly, and show me what extra details would improve the result.
Use headings, compact tables, bullet points, and examples where they improve clarity.

What this should give you

  • A starter codebook.
  • A memo-writing workflow.
  • A theme-development pathway tied to the research question.

Good inputs improve this prompt

  • State whether the analysis needs to remain largely inductive or explicitly theory-led.
  • If you already have sample transcripts, summarize what kinds of material appear in them.
  • If the project is collaborative, say so because coding consistency needs extra planning.

AI handoff

Paste the full prompt into ChatGPT, Claude, or Gemini after replacing the placeholders with your topic, setting, constraints, and target output. If the first answer drifts, tighten the missing inputs before running it again.

Prompt requests

Need a prompt for a narrower sociology task?

Send the missing workflow, bottleneck, or deliverable. Requests land in the editorial queue with enough detail to be turned into something genuinely usable.








Strong requests usually name the exact deliverable, where the workflow broke down, and what a useful answer should produce.