Describe the interaction, who took part, how much time has passed, and what decision comes next. Makeform turns your brief into a focused follow up survey that checks remembered value, real-world outcomes, unresolved needs, and permission for further contact.
Send follow-up responses to Google Sheets, Slack, and Zapier.
Sample prompts for the survey builder
Choose a complete brief, adapt the timing and audience, or send it into the Makeform builder. Each example shows a practical structure, not a live AI result.
Audience
Conference attendees contacted two weeks later
Format
Five-minute survey with attendee-type branching
Prompt size
525 chars
Example survey structure
Five-minute survey with attendee-type branching
Have you used an idea or connection from the event?
What action did you take?
What prevented you from taking action?
May our team contact you about this response?
Suggested response tags
Outcome achieved
Needs support
Open to contact
Ask what changed after the interaction, not only whether people enjoyed it. A delayed outcome question reveals value that an immediate satisfaction score cannot.
Step 1
Time
choose a delay that lets meaningful outcomes occur
Step 2
Recall
identify the event, service, course, or program clearly
Step 3
Measure
separate satisfaction, use, outcomes, and barriers
Step 4
Respond
route unresolved needs and report what happens next
Measure what happened later
An exit poll captures an immediate impression. A follow up survey checks whether someone remembered the content, used the service, changed a process, reached an outcome, or still needs help once everyday conditions have had time to intervene.
Name the period respondents should consider and ask only about changes that could reasonably occur within it. A two-week event check and a three-month program outcome survey should not use the same claims or measures.
Branch people who acted to outcome details, people who did not act to barriers, and people with unresolved needs to an optional support path. Respondents avoid irrelevant questions while your team gets usable context.
Combine concise ratings with prompts about what changed, what got in the way, and what should happen next. The result supports program improvement and service recovery instead of producing another isolated score.
Follow-up moments
Follow-up can mean checking a resolved service request, testing whether training transferred, learning what attendees did after an event, or understanding a program's longer-term contribution. Define the relationship before choosing questions.
Check whether the original need stayed resolved, whether recommendations were practical, and whether anything remains open. Offer an optional contact path without making positive feedback the price of getting help.
Ask whether attendees used an idea, made a connection, shared material, or changed a plan after returning to work. Separate session satisfaction from continuing usefulness and future-topic interest.
Measure application frequency, confidence, examples of use, and environmental barriers after learners have had a chance to practice. Add not-applicable choices when a skill has not yet been needed.
Track defined milestones and participant-reported contribution over an appropriate period. Include the option to report no change, and avoid implying that the program alone caused every outcome.
Survey workflow
Start with what your team needs to learn or do. Then set a realistic measurement window, generate answer paths for different outcomes, review the experience on mobile, and decide who handles requested contact before sending.
Write down the interaction respondents should recall, when it happened, what could reasonably have changed since, and which decision the answers will support. Choose one primary outcome and a few supporting signals rather than revisiting every original question.
Tell Makeform the audience, delay, outcome measures, known barriers, and follow-up process. Request branching for achieved, not-yet-achieved, and not-applicable responses, plus optional comments only where detail helps someone act.
Name the event, service, course, or program and include a date or milestone so people answer about the right experience. Keep scale directions consistent, define endpoints, remove double-barreled items, and test every branch on a phone.
Explain why you are following up, how long the survey takes, and what the team will do with responses. Keep feedback separate from contact permission, send requested follow-up to an owner, and share aggregate themes or next steps when appropriate.
Immediate vs delayed vs recurring
Survey timing changes the question people can answer. Immediate feedback is best for fresh impressions, delayed follow-up for application and outcomes, and a recurring check for movement over time. Use more than one only when each supports a different decision.
Field guide
A strong follow-up reconnects respondents to the right experience, measures what could have changed, and creates a clear route for unresolved needs. Use these six sections as a practical outline, then remove anything that does not support your decision.
Context and recall
People may have attended several events or used multiple services. Name the interaction and date, then collect only the context needed to interpret the response. Avoid asking again for details you already know.
Retrospective value
Immediate satisfaction can change after someone uses what they received. Ask about usefulness now, relevance to the goal, and whether expectations were met. Keep these separate so a positive interaction does not hide a result that failed to last.
Use and behavior
Turn vague impact into observable steps: tried a technique, used a resource, followed a recommendation, or changed a process. Offer no action yet and not applicable as valid responses. Branch action-takers to examples and others to barriers.
Outcomes and contribution
Ask whether a defined condition improved, stayed the same, worsened, or is too early to tell. Let respondents report milestones and the program's contribution alongside other factors, without treating an answer as proof of cause.
Barriers and unmet needs
No action or outcome is useful information. Offer a concise barrier list covering time, cost, access, confidence, unclear next steps, and competing priorities. Follow with an optional other field and a support choice your team can provide.
Contact and next steps
Respondents should be able to give feedback without volunteering for contact. Ask separately whether the team may contact them, which method they prefer, and what topic they want addressed. Keep contact details optional when identity is unnecessary.
Related tools
Use follow-up when time has passed and outcomes can emerge. Choose a focused event, customer, client, training, course, or open-feedback tool when that narrower context better matches the question you need answered.
Collect attendee reactions, continuing value, applications, and future interests after an event.
Open toolMeasure satisfaction across products, service interactions, support, and the overall customer relationship.
Open toolAsk clients about delivery, communication, usefulness, resolution, and remaining needs.
Open toolEvaluate training content, facilitation, confidence, application plans, and reinforcement needs.
Open toolReview course structure, instruction, assignments, learning support, and practical usefulness.
Open toolCreate a low-friction channel for candid comments when identity is not needed for the next step.
Open toolFAQ
Practical answers for teams measuring satisfaction, application, outcomes, barriers, and support needs after an interaction.
A follow up survey is sent after enough time has passed for someone to use what they received and experience an outcome. It can ask whether the original need remained resolved, whether someone applied an idea, which milestone they reached, what blocked progress, and whether support is wanted. Name the earlier interaction and the period respondents should consider.
Choose timing based on the change you expect. A service-resolution check may make sense after days or weeks, event application after two to four weeks, and training or program outcomes after one to three months. Send late enough that action was possible but early enough to recall the interaction. Include too early to tell when needed.
Start with a recall cue and a question about the original goal or need. Then ask about current usefulness, actions taken, outcome status, barriers, and what support would help next. Add one focused optional comment and a separate permission question if staff may contact respondents. Use balanced answer choices that include no change, no action yet, not applicable, and too early to tell where relevant. Keep every question tied to a decision or response your team can make.
An immediate survey captures fresh reactions to delivery: logistics, ease, content, staff interaction, and overall satisfaction. A delayed follow-up measures what happened afterward: continued resolution, remembered value, application, behavior, milestones, obstacles, and support needs. Both can be useful, but they should not duplicate each other. Keep immediate questions close to the experience and reserve outcome claims for a point when the outcome could reasonably have occurred.
Make it long enough to answer the decision and no longer. A focused service or event survey may take three to five minutes; a program outcome check may need more when several milestones matter. Use branching, keep scales consistent, avoid repeating known profile information, preview every path on mobile, and state an honest completion time.
Ask respondents to report current status and the interaction's contribution separately. For example, first ask whether the goal improved, stayed the same, worsened, or is too early to tell. Then ask how much the service or program contributed and invite optional context about other factors. Describe findings as participant-reported outcomes or associations, not proof of cause. Preserve no-change responses instead of forcing every answer into a success category.
Yes. Makeform supports unlimited free forms and responses, so you can generate a follow up survey, edit its questions and branching, publish it, and collect responses without a free-plan response cap. The paid tier removes the Makeform badge. You can create separate versions for an event, service, training, or program while keeping the complete survey workflow available on the free plan.
Plan the route before launch. Add a clear question asking whether the respondent wants contact about the response, collect only the contact detail and preference needed, and send that request to a named owner. Distinguish urgent unresolved service issues from general suggestions and future interests. In the invitation, explain what follow-up the team can offer and avoid promising a response time or outcome you cannot consistently provide.
Learn what changed after the interaction.
