30 Claude Prompts That Build Surveys

You are a people-analytics specialist who designs short, trustworthy engagement pulse surveys. <context> I want a recurring engagement pulse that employees actually complete, delivered as one self-contained HTML file previewable as an artifact. </context> <inputs> - Organization or team: [NAME AND SIZE] - Themes to track: [E.G. RECOGNITION, GROWTH, WORKLOAD, MANAGER, PURPOSE] - Cadence: [MONTHLY, QUARTERLY] - Anonymity level: [FULLY ANONYMOUS OR TEAM-TAGGED] - Brand color and tone: [DESCRIBE] </inputs> <task> Design a pulse survey with an overall engagement rating, one core agree-scale statement per theme, one "what is working well" and one "what should change" open question, and an optional team select for slicing results. Then build it as a single-page HTML survey with a clear anonymity notice, grouped theme statements, a thank-you state, and validation. </task> <constraints> - One self-contained responsive HTML file; inline CSS and vanilla JS only, Google Fonts allowed. - Keep it under two minutes; consistent agree scale; neutral, non-leading statements. - Prominent anonymity statement; accessible fieldsets and visible focus states. </constraints> <format> Return the question set, then the full HTML as an artifact, then a note on how to track theme scores over time and protect anonymity in small teams. </format>

You are an HR researcher who measures employee advocacy with eNPS. <context> I want to measure how likely employees are to recommend us as a place to work, delivered as one self-contained HTML file previewable as an artifact. </context> <inputs> - Organization: [NAME] - Audience: [ALL STAFF, A DEPARTMENT, TENURE GROUP] - Drivers I want to understand: [E.G. LEADERSHIP, COMPENSATION, CULTURE] - Anonymity level: [FULLY ANONYMOUS OR TAGGED] - Brand color and tone: [DESCRIBE] </inputs> <task> Design the eNPS survey: the 0-10 "how likely are you to recommend us as a place to work" question with anchors, an adaptive follow-up for detractors, passives, and promoters, driver ratings for the themes I named, one open "what would make us a better place to work" question, and an optional tenure or department field. Then build it as a single-page HTML survey with a 0-10 scale, conditional follow-up, anonymity notice, thank-you state, and validation. </task> <constraints> - One self-contained responsive HTML file; inline CSS and vanilla JS only, Google Fonts allowed. - Keep the recommend question wording standard; neutral driver statements. - Clear anonymity statement; accessible scale and visible focus states. </constraints> <format> Return the question set, then the full HTML as an artifact, then a note on how eNPS is calculated and how it differs from customer NPS benchmarks. </format>

You are an onboarding specialist who designs new-hire experience surveys. <context> I want to measure the new-hire experience at set milestones, delivered as one self-contained HTML file previewable as an artifact I can reuse at 30, 60, and 90 days. </context> <inputs> - Organization and role type: [NAME, ROLE FAMILY] - Milestone this run covers: [30, 60, OR 90 DAYS] - What good onboarding means here: [E.G. CLEAR EXPECTATIONS, TOOLS READY, SUPPORT] - Anonymity level: [NAMED OR ANONYMOUS] - Brand color and tone: [DESCRIBE] </inputs> <task> Design a milestone onboarding survey with a milestone select, ratings for clarity of expectations, access to tools and training, manager support, and sense of belonging, a confidence-in-role rating, one "what has helped most" and one "what is still unclear" open question, and a would-recommend-joining question. Then build it as a single-page HTML survey with a milestone tag, grouped ratings, a thank-you state, and validation. </task> <constraints> - One self-contained responsive HTML file; inline CSS and vanilla JS only, Google Fonts allowed. - Same core items across milestones so scores are comparable over time. - Accessible fieldsets with labels and visible focus states. </constraints> <format> Return the question set, then the full HTML as an artifact, then a note on which items to trend across the 30, 60, and 90 day marks. </format>

You are an HR analyst who designs exit surveys that capture honest departure reasons. <context> When an employee leaves I want structured, comparable exit data, delivered as one self-contained HTML file previewable as an artifact. </context> <inputs> - Organization: [NAME] - Primary reasons to distinguish: [COMPENSATION, MANAGER, GROWTH, CULTURE, ROLE FIT, EXTERNAL] - Whether responses are confidential: [YES OR NO] - Sensitive topics to include: [E.G. FAIRNESS, WORKLOAD] - Brand color and tone: [DESCRIBE] </inputs> <task> Design an exit survey: a single-select primary reason for leaving plus other, ratings of the role, manager, growth opportunities, compensation, and culture, a "what could we have done to keep you" open question, a would-you-return and would-you-recommend question, and an optional destination or new-role field. Then build it as a single-page HTML survey with a confidentiality notice, grouped ratings, a thank-you state, and validation. </task> <constraints> - One self-contained responsive HTML file; inline CSS and vanilla JS only, Google Fonts allowed. - Non-judgmental, neutral wording; make sensitive fields clearly optional. - Clear confidentiality statement; accessible controls and visible focus states. </constraints> <format> Return the question set, then the full HTML as an artifact, then a note on how to aggregate reasons into a retention-risk view without exposing individuals. </format>

You are an organizational-development specialist who designs upward manager-feedback surveys. <context> I want team members to rate their manager on behaviors that matter, delivered as one self-contained HTML file previewable as an artifact. </context> <inputs> - Organization: [NAME] - Manager competencies to assess: [E.G. CLARITY, COACHING, FAIRNESS, COMMUNICATION, TRUST] - Anonymity guarantee: [FULLY ANONYMOUS, MIN TEAM SIZE] - Rating style: [AGREE SCALE OR FREQUENCY SCALE] - Brand color and tone: [DESCRIBE] </inputs> <task> Design a manager-feedback survey with behavior statements per competency on a consistent scale, a "what should this manager keep doing" and a "what should they start or stop" open question, an overall confidence-in-manager rating, and an optional tenure-with-manager field. Then build it as a single-page HTML survey with a strong anonymity notice, grouped competencies, a thank-you state, and validation. </task> <constraints> - One self-contained responsive HTML file; inline CSS and vanilla JS only, Google Fonts allowed. - Behavior-based, observable statements; neutral, non-leading wording. - Prominent anonymity guarantee; accessible fieldsets and visible focus states. </constraints> <format> Return the question set, then the full HTML as an artifact, then a note on how to summarize results per competency and share them without breaking anonymity. </format>

You are an events researcher who designs post-event feedback surveys. <context> My conference or event just ended and I want structured attendee feedback, delivered as one self-contained HTML file previewable as an artifact. </context> <inputs> - Event name and type: [NAME, CONFERENCE / SUMMIT / MEETUP] - What I most want to improve: [CONTENT, LOGISTICS, VENUE, NETWORKING] - Key sessions or tracks: [LIST A FEW] - Whether I run this event again: [YES OR NO] - Brand color and tone: [DESCRIBE] </inputs> <task> Design a post-event survey with an overall event rating, an event NPS, ratings for content, speakers, venue and logistics, and networking, a best-and-worst part pair of open questions, a favorite-session single-select, a likelihood-to-attend-next-time question, and an optional testimonial field with a permission checkbox. Then build it as a single-page HTML survey grouped by theme, with a thank-you state and validation. </task> <constraints> - One self-contained responsive HTML file; inline CSS and vanilla JS only, Google Fonts allowed. - Keep it under three minutes; balanced scales; neutral wording. - Testimonial permission checkbox; accessible controls and visible focus states. </constraints> <format> Return the question set, then the full HTML as an artifact, then a note on which ratings predict return attendance and how to harvest testimonials. </format>

You are a digital-events specialist who designs webinar feedback surveys. <context> My webinar just ended and I want quick, useful feedback plus follow-up signals, delivered as one self-contained HTML file previewable as an artifact. </context> <inputs> - Webinar topic and host: [TITLE AND PRESENTER] - Goal of the webinar: [EDUCATE, GENERATE LEADS, DEMO] - Follow-up I want to offer: [DEMO, TRIAL, CONTENT, NEXT WEBINAR] - Audience: [PROSPECTS, CUSTOMERS, MIXED] - Brand color and tone: [DESCRIBE] </inputs> <task> Design a webinar survey with an overall rating, a content-usefulness rating, a presenter-clarity rating, a pacing question, a "what one topic should we cover next" open question, an interest-in-follow-up single-select tied to my offer, and an optional email field for those who want the follow-up. Then build it as a single-page HTML survey with a thank-you state that surfaces the relevant next step and validation. </task> <constraints> - One self-contained responsive HTML file; inline CSS and vanilla JS only, Google Fonts allowed. - Under 60 seconds; balanced scales; neutral wording. - Only ask for email when a follow-up is chosen; accessible controls and visible focus states. </constraints> <format> Return the question set, then the full HTML as an artifact, then a note on how to route follow-up interest to sales or a nurture sequence. </format>

You are a learning-and-development evaluator who designs training-effectiveness surveys. <context> A workshop or training session just wrapped and I want to measure its effectiveness, delivered as one self-contained HTML file previewable as an artifact. </context> <inputs> - Training title and format: [NAME, IN-PERSON / VIRTUAL] - Learning objectives: [LIST 2-4] - Audience: [ROLE OR TEAM] - What success looks like: [E.G. CAN APPLY IT AT WORK] - Brand color and tone: [DESCRIBE] </inputs> <task> Design a training-evaluation survey following a reaction-and-learning model: an overall rating, a per-objective "I can now do this" confidence rating, ratings for the facilitator, materials, and pacing, a relevance-to-my-job rating, a "what will you apply first" open question, a "what was missing" open question, and an intent-to-apply question. Then build it as a single-page HTML survey grouped into reaction and learning sections, with a thank-you state and validation. </task> <constraints> - One self-contained responsive HTML file; inline CSS and vanilla JS only, Google Fonts allowed. - Tie the confidence ratings directly to the stated objectives; balanced scales. - Accessible fieldsets with labels and visible focus states. </constraints> <format> Return the question set, then the full HTML as an artifact, then a note on how to read reaction versus learning scores and measure on-the-job application later. </format>

You are an event-program manager who designs per-session speaker-rating surveys. <context> I want attendees to rate individual sessions and speakers, delivered as one self-contained HTML file previewable as an artifact I can reuse per session. </context> <inputs> - Event name: [NAME] - Session title and speaker: [TITLE, SPEAKER] - What I want to learn: [CONTENT QUALITY, DELIVERY, RELEVANCE] - Whether to rank sessions overall: [YES OR NO] - Brand color and tone: [DESCRIBE] </inputs> <task> Design a session-rating survey with a session and speaker select or hidden field, an overall session rating, ratings for content depth, speaker delivery, and relevance, a would-recommend-this-session question, a "best takeaway" open question, a "what would have made it better" open question, and an optional "topics you want more of" field. Then build it as a single-page HTML survey that carries a session ID, shows a thank-you state, and validates required answers. </task> <constraints> - One self-contained responsive HTML file; inline CSS and vanilla JS only, Google Fonts allowed. - Session ID passed via URL query string so one file serves every session. - Balanced scales; accessible controls and visible focus states. </constraints> <format> Return the question set, then the full HTML as an artifact, then a note on how to reuse one file across sessions and rank speakers from the results. </format>

You are an event planner who surveys registrants before an event to tailor the program. <context> Before my event I want to learn what registrants expect so I can tune content and logistics, delivered as one self-contained HTML file previewable as an artifact. </context> <inputs> - Event name and type: [NAME, TYPE] - Draft agenda or topics: [LIST] - What I can still change: [SESSIONS, FORMAT, FOOD, TIMING] - Audience: [WHO IS REGISTERING] - Brand color and tone: [DESCRIBE] </inputs> <task> Design a pre-event survey with a primary-goal-for-attending single-select, a topic-interest ranking from the draft agenda, an experience-level question, a preferred-format question, a "one question you want answered" open field, a dietary or accessibility needs field, and an optional networking-interest opt-in. Then build it as a single-page HTML survey with grouped sections, a thank-you state, and validation. </task> <constraints> - One self-contained responsive HTML file; inline CSS and vanilla JS only, Google Fonts allowed. - Only ask about things I can actually change before the event; neutral wording. - Accessible fieldsets with labels and visible focus states. </constraints> <format> Return the question set, then the full HTML as an artifact, then a note on how to use topic-interest data to finalize the agenda and prep speakers. </format>

You are a customer-discovery coach trained in the "talk about their life, not your idea" school of interviewing. <context> I need a structured discovery interview guide, not a pitch, that helps me learn whether a real problem exists. Deliver it as a clean, ready-to-use document. </context> <inputs> - The problem I think exists: [HYPOTHESIS] - Who I want to interview: [TARGET PERSON] - What I must learn to proceed: [KEY UNKNOWNS] - My riskiest assumption: [THE THING THAT WOULD KILL THE IDEA] - Interview length: [E.G. 20-30 MINUTES] </inputs> <task> Build a full interview guide: a warm-up, a set of open past-behavior questions that ask about real events ("tell me about the last time..."), probes that dig into current workarounds and what they cost, questions that test my riskiest assumption without leading, traps to avoid (compliments, hypotheticals, pitching), and a close that asks for referrals and permission to follow up. Include a one-line goal per section and note which answers would validate or invalidate the hypothesis. </task> <constraints> - Deliver as a structured document with clear sections and bullet questions. - Questions must be open and about the past, never leading or hypothetical. - No pitching the solution; keep the focus on the interviewee's real experience. </constraints> <format> Return the interview guide as a ready-to-use document, then a short cheat sheet of good-signal versus bad-signal answers to listen for. </format>

You are a demand-validation researcher who designs surveys that test real buying intent. <context> I want to test whether people would actually pay for a product idea, delivered as one self-contained HTML file previewable as an artifact. </context> <inputs> - The offer: [WHAT IT IS AND THE OUTCOME] - Target buyer: [WHO] - Price points to test: [2-3 CANDIDATE PRICES] - Problem it solves: [PAIN POINT] - Brand color and tone: [DESCRIBE] </inputs> <task> Design a demand-test survey with a problem-severity rating, a current-spend question on the problem today, a purchase-intent question at each candidate price, a "how disappointed would you be without this" question, a commitment step (join a waitlist or leave an email to pre-order), and a "what would make this a clear yes" open question. Then build it as a single-page HTML survey with a real commitment field, a thank-you state, and validation. </task> <constraints> - One self-contained responsive HTML file; inline CSS and vanilla JS only, Google Fonts allowed. - Prioritize behavioral commitment over stated intent; neutral, non-leading wording. - Accessible controls with labels and visible focus states. </constraints> <format> Return the question set, then the full HTML as an artifact, then a note on why the email or waitlist step matters more than the stated-intent answers. </format>

You are a go-to-market researcher who builds ICP and persona intake surveys. <context> I want to profile my best-fit customers to sharpen my ICP, delivered as one self-contained HTML file previewable as an artifact. </context> <inputs> - Product: [NAME AND WHAT IT DOES] - Who I think my ICP is: [CURRENT GUESS] - Firmographics or demographics that matter: [ROLE, COMPANY SIZE, INDUSTRY, ETC] - Behaviors that signal fit: [E.G. TOOLS USED, TEAM SIZE, TRIGGER EVENT] - Brand color and tone: [DESCRIBE] </inputs> <task> Design an ICP intake survey with role and firmographic fields, a primary-goal and main-challenge pair of questions, a current-tools checklist, a trigger-event question ("what made you start looking"), a decision-role question, a budget-authority question, and an open "describe your ideal outcome" field. Then build it as a single-page HTML survey grouped into who-you-are and what-you-need sections, with a thank-you state and validation. </task> <constraints> - One self-contained responsive HTML file; inline CSS and vanilla JS only, Google Fonts allowed. - Fields that map cleanly to CRM properties; neutral wording; put contact fields last. - Accessible fieldsets with labels and visible focus states. </constraints> <format> Return the question set, then the full HTML as an artifact, then a note on which answers separate best-fit leads from poor-fit ones for routing and scoring. </format>

You are a Jobs-to-be-Done researcher who runs switch interviews to uncover why people change solutions. <context> I want to understand the forces behind why customers switched to (or away from) a product, delivered as a ready-to-use interview guide document. </context> <inputs> - Product or category: [NAME AND CATEGORY] - The switch I want to study: [E.G. FROM SPREADSHEETS TO OUR TOOL] - Who to interview: [RECENT SWITCHERS] - What decision I need to inform: [POSITIONING, ONBOARDING, PRICING] - Interview length: [E.G. 30-45 MINUTES] </inputs> <task> Build a JTBD switch-interview guide that reconstructs the timeline: first thought of a change, the passive and active looking phases, the moment of purchase, and first use. Include questions that surface the four forces (push of the old, pull of the new, anxiety of switching, habit of the present), probes for the emotional and social job, and the specific event that triggered the search. Add a one-line goal per phase and note what each force reveals. </task> <constraints> - Deliver as a structured document with phases, goals, and bullet questions. - Questions must reconstruct real events on a timeline, not ask for opinions. - Cover functional, emotional, and social dimensions of the job. </constraints> <format> Return the interview guide as a ready-to-use document, then a short note on how to map answers onto the four forces of progress. </format>

You are a growth researcher who designs micro-surveys for waitlist and landing-page visitors. <context> I want a two-question micro-survey shown right after someone joins my waitlist, delivered as one self-contained HTML file previewable as an artifact. </context> <inputs> - Product teaser: [WHAT IS COMING] - Audience: [WHO IS SIGNING UP] - The one thing I most need to learn: [E.G. USE CASE, ROLE, URGENCY] - Segments I want to sort people into: [LIST 3-5] - Brand color and tone: [DESCRIBE] </inputs> <task> Design a post-signup micro-survey that appears after the email is captured: one single-select segmentation question that sorts people into my listed segments, one "what problem do you most want this to solve" open question, and an optional urgency question. Then build it as a single-page HTML confirmation view with a brief thank-you, the two micro-questions inline, a skip option, and a final confirmed state. Keep it feather-light so it never blocks the signup. </task> <constraints> - One self-contained responsive HTML file; inline CSS and vanilla JS only, Google Fonts allowed. - Two questions maximum shown after signup; a visible skip so it is never a wall. - Accessible controls with labels and visible focus states. </constraints> <format> Return the question set, then the full HTML as an artifact, then a note on how the segmentation answer can personalize the welcome email. </format>