Designing Feedback Forms and Reviewing Responses

Create a short unpublished feedback form, review data collection choices and understand who can respond or edit.

Part 9 of 10 | Email and Google Workspace for Beginners

Learning goals

Design a form that collects only the information needed for a clear purpose. Distinguish question types, required fields, responder access and collaborator editing. Review a fictional set of responses without treating test information as real feedback or publishing a form before its access settings are understood.

Before you begin

Use the fictional beginner session and keep the form unpublished. You will preview questions and analyse invented responses in a separate practice sheet. The lesson does not require collecting personal data or notifying participants. If your account blocks Forms, complete a paper design and record the creation step as untested.

Begin with the decision you need to make

The form's purpose is to identify which activity needs clearer explanation in a future session. That purpose does not require a home address, identification number or financial information. Write a short introduction explaining that the form is a practice design, what kind of feedback is requested and that respondents should not include private details in free text.

Choose three questions: which activity was most useful, which activity needs more practice and one optional suggestion for improvement. Offer the same activity names used in the agenda. A question should ask one thing at a time. “Was the session useful and easy to follow?” combines two judgements that could have different answers.

Match the question type to the task

Use a single-choice question when the respondent should select one activity. Use checkboxes only if several selections are meaningful and allowed. A short or paragraph response can collect an explanation, but it requires more effort to review and can contain unexpected private information. Give enough guidance to keep answers relevant without steering people toward praise.

Required should mean that the answer is necessary for the stated purpose. Making every question compulsory can encourage meaningless responses or discourage completion. Leave the improvement suggestion optional in this practice form. Include a suitable option for someone who cannot assess an activity rather than forcing them to choose an inaccurate answer.

Create and preview the form

Open forms.google.com, create a blank form and name it Practice_Session_Feedback. Add the introduction and three questions. Select the intended question type for each and review the Required controls. Use Preview to inspect what a responder would read, but keep the form unpublished and do not collect real responses.

Read the questions in order as if you had attended the session. Check whether the choices are understandable on a small screen and whether any question assumes knowledge the respondent may not have. Correct spelling and inconsistent activity names. A visually simple form can still be confusing if the wording does not match the event.

Separate editing from responding

A collaborator who edits a form has a different role from someone who submits answers. Do not send an editing link to people who only need to provide feedback. Current Google Forms guidance uses publishing and responder-access controls; a form must be published before responders can access it. Review those controls before any future authorised release.

For this lesson, inspect the choices without completing publication or notifying anyone. Record the intended audience and how it would be restricted. Available controls can depend on the account and organisation. An old tutorial that says simply to send a form may not match the current interface, so use the linked official guidance when the controls differ.

Review identity and results settings

Decide deliberately whether email collection is necessary. Do not call a form anonymous while its settings or questions collect identifying information. Limiting a form to one response involves sign-in requirements under Google's guidance, so check what that means for your intended audience. The practice design does not need email collection or a one-response rule.

Keep response-summary visibility off for the practice plan. Google's guidance warns that summaries can include full-text answers or charts visible to people who can respond. A free-text answer may reveal information you did not expect, even when names were not requested. Review all settings as a whole rather than assuming one privacy choice controls every kind of exposure.

Analyse a small fictional dataset

In a separate sheet, record five invented answers to the question about needing more practice: Email, Drive, Drive, Sheets and Drive. Count each category. Drive has three selections, Email has one and Sheets has one, for five total responses. These are demonstration figures, not evidence about real learners or the quality of an actual session.

Write a cautious interpretation: in this fictional set, Drive is the most frequently selected topic for more practice. Do not claim that every learner needs it or that the form proves the reason. One optional comment might help suggest a question to investigate, but a small sample is not a complete explanation of what happened.

Plan a responsible future close

For a real feedback exercise, decide who reviews responses, how long the collection should remain open and which organisational requirements govern storage. This course does not prescribe a universal retention period or legal consent wording. Keep responses and any linked sheet restricted to the people who need them for the agreed purpose.

Before a future authorised publication, test the intended respondent experience and verify access using an appropriate controlled account. An owner's preview does not prove that every intended respondent can submit. Keep the difference between previewed, published and tested clear in your records.

Guided exercise

1. Write the feedback purpose and design three questions with suitable answer types. Make the free-text suggestion optional.

2. Create an unpublished practice form or a labelled paper design. Preview the wording and correct one unclear element.

3. Record planned responder access, email collection and result-summary settings. Explain how editing access differs from responding.

4. Enter and count the five fictional answers in a separate practice sheet. Verify that the counts add to five.

5. Write a cautious interpretation and a future publication checklist. Keep the form unpublished and do not notify anyone.

Knowledge check

1. Should feedback recipients receive a form-editing link?

2. Can response summaries expose free-text answers?

3. Which topic has the most selections in the fictional dataset?

Answer guide

1. No. Responding and editing are different permissions.

2. Yes. Review that setting and the intended audience carefully.

3. Drive, with three of the five fictional selections.

Completion standard

Submit a clear three-question design, preview observations, a permission and settings plan, and correct fictional counts. Keep publication unperformed and distinguish test data from real feedback. No unnecessary personal information or unverified anonymity claim may appear.

Sources and verification notes

Create your first Google form. Checked 15 September 2026. Question types, required fields and preview guidance. Practice uses fictional responses and minimal data.

Publish and share forms with responders. Checked 15 September 2026. Current Forms publishing and responder access. Publishing, responder access and collaborator editing are distinct. Response summaries can expose answers to responders.