Skip to main content

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

Write items you can actually analyse

Survey and Scale Builder

Design a sociology survey instrument with constructs, item wording, response scales, and validation logic.

Fieldwork
Planner
Advanced
Quantitative
Dataset
Survey Design
Codebook Construction

Request a prompt

PROMPT: Survey and Scale Builder
Write items you can actually analyse
Data Collection · Data Collection · Fieldwork

When to use this

  • Use this when you need to move from an abstract concept to measurable items.
  • Use this before survey piloting or field deployment.
  • Use this when you want an analysis-ready questionnaire instead of only descriptive questions.

What you should prepare first

  • Concepts or constructs I need to measure: [trust, stigma, social capital, belonging, precarity, burnout, polarization, etc.]
  • Population and context: [students, households, workers, online users, residents, faculty, etc.]
  • Survey mode: [online, in person, phone, classroom, panel, cross-sectional]
  • Any existing validated scales I may want to adapt: [optional]
  • Project goal: [exploratory survey, hypothesis test, index construction, descriptive profile, regression analysis]

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:
Build a sociology survey instrument or scale plan that turns my concepts into measurable items and a usable analysis strategy.

Project details I will provide or you should ask me to clarify:
- Concepts or constructs I need to measure: [trust, stigma, social capital, belonging, precarity, burnout, polarization, etc.]
- Population and context: [students, households, workers, online users, residents, faculty, etc.]
- Survey mode: [online, in person, phone, classroom, panel, cross-sectional]
- Any existing validated scales I may want to adapt: [optional]
- Project goal: [exploratory survey, hypothesis test, index construction, descriptive profile, regression analysis]

How you should work:
1. Translate each concept into dimensions and then into candidate survey items.
2. Recommend appropriate response formats and explain the logic behind them.
3. Distinguish items for background variables, key predictors, mediators, outcomes, and controls if relevant.
4. Flag wording problems such as ambiguity, double meaning, social desirability risk, and leading language.
5. Suggest piloting, reliability checks, construct validation steps, and a first-pass analysis plan.

Output requirements:
- A structured instrument outline.
- A construct-to-item map.
- A validation and analysis checklist.

Quality guardrails:
- Do not invent pseudo-scientific scales without conceptual logic.
- Keep the instrument realistic in length for the survey mode and respondent burden.
- Where validated measures exist, note that adaptation decisions should be justified and documented.

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 structured instrument outline.
  • A construct-to-item map.
  • A validation and analysis checklist.

Good inputs improve this prompt

  • State whether comparability with prior studies is important.
  • If the survey is multilingual, mention that so wording can be simplified for translation.
  • If the questionnaire must be short, give a maximum completion time.

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.