Describe the project and respondents. Makeform builds an evaluation of outcomes, delivery, lessons, and follow-up actions.
Send responses to Slack, Google Sheets, and Zapier.
Sample prompts for the builder
Choose a starting point, tailor it, or send it to the builder.
Audience
Cross-functional project team
Format
Anonymous retrospective with ratings and comments
Prompt size
299 chars
Example form structure
Anonymous retrospective with ratings and comments
Your role and workstream
Rate planning, communication, and delivery
What helped or blocked progress?
Outcomes, lesson, and action owner
Suggested routing tags
Outcome review
Lessons learned
Action required
Connect ratings to examples so reviewers can turn scores into lessons and actions.
Step 1
Set context
project goals, audience, and success measures
Step 2
Collect
ratings, examples, outcomes, and open feedback
Step 3
Synthesize
patterns, gaps, wins, and lessons learned
Step 4
Act
recommendations assigned to owners and dates
A useful closeout
Separate results from process, request evidence behind ratings, and finish with decisions the next project can use.
Compare targets, delivered results, and observations so the review tests whether the project achieved its purpose.
Give each respondent group relevant questions while keeping shared rating scales comparable.
Collect each recommendation with its priority, proposed owner, and due date.
One project, multiple lenses
Keep common outcome questions, then branch according to each respondent's involvement.
Planning, roles, workload, decisions, dependencies, and practices to repeat or change.
Business outcomes, communication, scope, issue handling, and handoff readiness.
Training, documentation, support readiness, unresolved risks, and operational fit.
Requirements, access, approvals, coordination, and changes for the next engagement.
Evaluation workflow
Define closeout decisions, tailor paths, and route accepted actions into improvement work.
Name the project, respondents, objectives, deliverables, success measures, and decisions to support.
Use consistent anchors, optional identity, and follow-ups for low scores or unresolved issues.
Send the link after handoff. State the deadline, reviewers, and how findings will be used.
Compare ratings and comments, identify repeated patterns, and assign approved actions.
Survey design choices
Combine comparable ratings with open context. A meeting alone may miss quieter voices.
Field guide
Connect the original case with delivery experience, outcomes, and improvements.
Respondent context
Collect role, workstream, project phase, and involvement before asking for judgments. Make names optional when anonymity matters and explain who sees results.
Outcomes and benefits
Restate agreed objectives so respondents judge the same targets. Capture actual results, observed benefits, delayed outcomes, and unplanned effects.
Delivery performance
Use anchored scales for scope, schedule, resources, quality, risks, and changes. Follow low ratings with a request for an example.
Collaboration
Ask about decisions, roles, meetings, information, approvals, and coordination. A matrix keeps ratings compact while comments capture examples.
Lessons learned
Ask what worked, what did not, what conditions shaped each result, and where the lesson applies.
Recommendations and actions
Structure each recommendation with its change, benefit, priority, owner, and timing so reviewers can decide efficiently.
Related tools
Add forms for requests, changes, communication, feedback, reporting, and event review.
Capture objectives, scope, resources, dependencies, and success measures before work begins.
Open toolRecord a change, reason, impact, decision, and owner during delivery.
Open toolCollect feedback about collaboration, communication, and team practices.
Open toolLearn how stakeholders want updates, decisions, risks, and invitations delivered.
Open toolStructure progress, results, evidence, challenges, and next steps.
Open toolEvaluate attendee experience, value, logistics, and improvements after an event.
Open toolFAQ
Answers for an actionable closeout review.
It is a questionnaire completed after closeout or handoff. Team members and stakeholders assess intended versus actual outcomes, delivery, collaboration, risks, handover, and lessons learned. The results can guide a retrospective and improvement plan.
Send it after deliverables are accepted and respondents experience the handoff, while details remain fresh. If benefits take months to appear, evaluate process and immediate outcomes now, then schedule a later benefits review.
Cover respondent context, objectives, outcomes, scope, schedule, quality, risks, communication, collaboration, handoff, and lessons. Ask what worked and what should change. End with a recommendation, evidence, priority, owner, and timing.
Anonymous responses may help people raise concerns; named responses simplify follow-up. You can make names optional, collect role and workstream separately, and state who will see individual answers.
Keep the same scale direction and label important points, such as one for strongly disagree and five for strongly agree. Include not applicable, ask one idea per statement, and request comments for low ratings.
Start with shared questions about objectives and outcomes, then branch by role. Team members see planning and dependencies; sponsors see governance and business outcomes; operational owners see training, documentation, adoption, and support readiness.
Yes. Makeform offers unlimited free forms and responses, so you can generate, edit, publish, and reuse evaluations without a response cap. The paid tier removes the Makeform badge. Duplicate a master form for each project and adjust its outcomes and paths.
Review ratings with their examples, compare respondent groups, and discuss key themes. Confirm reusable lessons, assign accepted recommendations to owners and dates, and share the decisions. Keep responses for context when planning similar work.
Close with reusable lessons.
