Qualitative Coding and Theme Builder
Build a defensible qualitative coding strategy for interviews, focus groups, fieldnotes, or documents.
Structure the paper before reviewers do it for you
Plan a sociology journal article that is structured for high-quality submission rather than a generic essay.
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: Build a high-quality sociology journal article blueprint for my project, including argument, structure, contribution, evidence strategy, and target-journal fit. Project details I will provide or you should ask me to clarify: - Paper topic or research question: [state clearly] - Data or evidence base: [what material supports the article] - Type of paper: [empirical qualitative, empirical quantitative, mixed methods, theory-driven, review, methodological, comparative] - Likely journal family or audience: [general sociology, subfield journal, interdisciplinary, methods-oriented] - Current draft stage: [idea, notes, findings memo, rough draft, revise and resubmit] How you should work: 1. Clarify the central claim, contribution type, and intended audience. 2. Map the article into sections with a clear rhetorical job for each one. 3. Explain how to position the paper within existing literature without overclaiming novelty. 4. Show what evidence needs to appear in the findings or analysis section and in what order. 5. Recommend how to tighten the article for journal expectations and likely reviewer concerns. Output requirements: - A section-by-section article blueprint. - A contribution and positioning statement. - A likely reviewer concern list with preemptive fixes. Quality guardrails: - Do not promise a top-journal contribution if the evidence does not support it. - Keep the article focused on one central intervention. - Make the structure publication-oriented rather than thesis-chapter oriented. 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.
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
Send the missing workflow, bottleneck, or deliverable. Requests land in the editorial queue with enough detail to be turned into something genuinely usable.
Shortlist and compare
0 shortlisted · 0 in compare
Compare mode