Google Forms

What Google Forms is

Google Forms is Google’s browser-based service for creating and distributing forms, surveys and quizzes. It works with Google accounts and within Google Workspace. Authors can prepare questions, receive submissions and inspect results without programming a data-collection application. Integration with Drive and Sheets brings documents and responses into the same working environment.

Separate three objects: the form defining the questions, each submitted response and the spreadsheet that may receive a tabular copy. They are not interchangeable. Changing a question affects what later respondents see; editing an analysis cell does not retrospectively correct what an earlier respondent understood.

Forms is designed for structured input and consultation. A process involving approvals, statuses, assignment and follow-up needs those steps designed in addition to the form. A simple intake mechanism is useful when the team knows which decision the collected information will support.

Reference documentation: Google Help — Use Forms · Google Help — Question types · Google Help — Publishing and sharing.

History and development

On 6 February 2008, Google announced interactive forms that fed submissions into a spreadsheet. This origin explains the close relationship between Forms and Sheets: separating the input screen allowed information collection without giving every respondent editing access to the entire spreadsheet.

Add-ons arrived in October 2014, opening extension possibilities for outside developers. In July 2017, Google introduced suggested validation based on question type alongside improvements to response collection and organisation. Such assistance automates part of preparation, but suggested rules still need review.

In June 2025, Google announced Gemini response summarisation. Current development combines assisted creation, interpretation of comments and more explicit publishing controls. AI capabilities depend on plans and rollout; describe the specific task rather than assuming every form includes an unrestricted automatic analyst.

Reference documentation: Google — Forms introduced in spreadsheets · Google Developers — Forms add-ons · Google — Smarter Forms, July 2017 · Google — Gemini response summaries launch.

Forms connected to a response register

Google Forms collects information through questions and section-based routes. Responses can be reviewed within the form and linked to Google Sheets for processing. Distinguish question design, original responses and subsequent analysis: changing a spreadsheet formula does not change what participants were asked.

Section logic can reduce irrelevant questions, but test it from the respondent’s perspective. Explain the purpose, required information and what happens after submission. A confirmation message should describe receipt, not promise that a person has already reviewed or resolved the request.

Reference documentation: Google Docs Editors Help — View and manage form responses · Google Workspace Learning Center — Tips to customize your forms.

Question types and validation

The editor supports short answers and paragraphs, single choice, checkboxes, dropdowns, scales, ratings, grids, dates, times and file uploads. Grids present the same scale for several statements but can be demanding on small screens. Choose a format that helps people answer correctly rather than compressing as many questions as possible.

Validation checks numeric ranges, text length, format or patterns expressed with regular expressions. Confirming that an address looks like an email does not prove it exists or belongs to the respondent. An overly narrow rule can reject a legitimate answer. Test ordinary values, boundaries and expected exceptions.

File uploads require respondents to sign into a Google account and are stored in the owner’s Drive. Restrictions apply, including forms in shared drives and certain data-loss-prevention policies. Test external collection involving attachments before distributing its link.

Reference documentation: Google Help — Question types · Google Help — Response rules.

Routes, presentation and response continuity

Conditional navigation sends respondents to sections based on single-choice or dropdown questions. It is not a general rules engine for arbitrary combinations of questions. Draw the journey before configuring it and check every section’s exit, including an early submission path.

Themes, images and presentation help establish context. Shuffling questions or choices can suit some surveys, but not when it breaks a sequence dependent on earlier instructions. Each question must remain understandable if its position changes. Images containing essential information need an equivalent textual explanation.

Signed-in users can have progress saved as a draft for 30 days. Autosave does not work offline and is not the same as a received submission. For locations with unreliable connectivity, establish how submission will be confirmed and what alternative exists if someone cannot finish. Browser state alone is insufficient evidence of receipt.

Reference documentation: Google Workspace Learning Center — Tips to customize your forms · Google Help — Branching · Google Help — Autosave.

Quizzes and assessment

Quiz mode provides answer keys, points and feedback. Grades can be released after submission or following review, depending on settings. Immediate-feedback practice and an assessment requiring individual review need different journeys.

Before using a score, check that each question serves an objective and its answer key accepts the intended responses. An ambiguous choice can penalise someone who understands the content but interprets the wording differently. Open questions need an explicit review criterion.

In preventive training, a correct response provides evidence about that item. It does not by itself demonstrate safe task performance, recognition of a real situation or retained learning. Preserve the activity’s context and decide which additional observation or check is needed.

Reference documentation: Google Help — Quizzes.

Publishing, access and separate permissions

Creating a form and publishing it for respondents are separate actions. Publication enables access under the chosen audience and rules; a link to an unpublished form is insufficient. Respondents are also distinct from editors who can change questions and inspect data.

Settings can limit responses, collect addresses and permit subsequent editing. An address typed by a respondent is not equivalent to verified identity. If response summaries are enabled, people allowed to respond can see charts and response text; review that content before enabling the feature for convenience.

A prefilled link reduces typing, but its values do not prove identity or represent necessarily confirmed information. Avoid sensitive information in links that can be forwarded. At closure, review access, new submissions, the linked sheet and exported copies as separate parts of the same process.

Reference documentation: Google Help — Publishing and sharing · Google Docs Editors Help — View and manage form responses.

Sheets, add-ons, Apps Script and the API

Analysis can take place in Forms, a new or existing Sheets spreadsheet, or a downloaded CSV. A linked sheet supports cleaning, tables and charts, but retain original responses separately from calculations. Deleting an analysis row should not be assumed to delete equivalent information across all resources.

Add-ons provide features from other developers and may request data access. Apps Script automates form operations; the Forms API supports creation and modification, response retrieval and change notifications. These are extension routes beyond the ordinary editor.

An integration should identify submissions consistently, prevent repeat processing and record failures. If it generates a document or task, verify that each response produces the intended result exactly once. Script and owner permissions also need maintenance when the team changes. Automating one survey does not automatically create a valid process for every other survey.

Reference documentation: Google Developers — Forms add-ons · Google Developers — Forms API · Google Developers — Apps Script Forms service · Google Docs Editors Help — View and manage form responses.

Gemini: assisted creation, summaries and analysis

With an eligible Google Workspace or Google AI plan, Gemini can create a form from a description. The feature has specific limits: documentation distinguishes generating a form from editing an existing one and notes restrictions on sections and quiz settings. Review the draft before publication, particularly when changing a previously used question.

Gemini also summarises open responses and groups themes. Actionable Insights extends analysis under specific conditions: at least 12 responses and three questions, with quiz mode disabled. A technical minimum is not a statistical representativeness criterion.

Useful review compares each theme against actual comments, checks exceptions and preserves nuance. A minority reporting an important problem may receive little attention in a frequency-focused summary. In OSH, use this to prepare reading, not to convert comment frequency automatically into risk severity. Distinguish received data, generated interpretation and the eventual decision.

Reference documentation: Google — Gemini response summaries launch · Google Help — Create with Gemini · Google Help — Summaries and analysis with Gemini.

Collecting useful information without turning it into diagnosis

• Session feedback: ask what was understood and what needs clarification, separating satisfaction from learning.
• Activity preparation: collect access, availability or material requirements for an intervention.
• Communication review: identify confusing language and inaccessible formats before distributing a guide more widely.

These Sabentis use cases support organisational decisions. An informal survey should not be presented as a validated psychosocial risk-assessment instrument or health diagnosis. Method and interpretation need justification independent of the tool.

Worked example: improving a guide through feedback

Hypothetical example. A team trials an induction guide with a small group before introducing it at other sites.

1. Identify the guide version and decisions the responses will inform: clarifying terms, reorganising content or providing extra support.
2. Ask about specific aspects and allow respondents to indicate sections they did not use. Avoid double questions, such as rating clarity and usefulness in one answer.
3. Where routes differ, test every section and ending. Check the form on a phone using the intended access arrangement.
4. Link responses to a spreadsheet only where needed and review permissions for both resources separately. Label and exclude test submissions.
5. Analyse comments in context, document accepted changes and retain which guide version produced each response set.

An acceptable result is a reasoned improvement list with unresolved questions. Do not automatically generalise a small group’s views to the whole organisation or interpret silence as complete understanding. Keep the number of invited people separate from the number responding.

Numerical check: a pilot invites 24 people and receives 18 valid responses plus two tests. Coverage is 18/24, or 75%, after excluding tests. If seven participants request clarification of a term and five request an image, with three in both groups, nine different people made at least one of those requests, not twelve. The improvement list retains both needs and their overlap rather than counting mentions as unique participants.

Reference documentation: Google Docs Editors Help — View and manage form responses · Google Workspace Learning Center — Tips to customize your forms.

Spreadsheet permissions, anonymity and questionnaire changes

Google warns that removing a collaborator from a form does not necessarily remove them from its linked spreadsheet: both access settings need management. Check which results respondents can see and what information is exported elsewhere.

Do not promise anonymity merely because no name question exists. Identification settings and response content may reveal a person. Document question changes made during collection so answers from different conditions are not treated as equivalent. Required fields do not guarantee sincere or complete answers; unnecessary demands can cause abandonment or filler responses. Check who can access exports after the original collection closes.

Reference documentation: Google Docs Editors Help — View and manage form responses.

When to choose Google Forms

It may suit bounded consultations and information collection in Google Workspace. Assess who can respond, who administers the form and what happens if its owner leaves the team.

Google Sheets can support analysis, while Typeform offers another approach to presentation and routing to compare. Consider permissions, respondent effort, export and maintenance rather than the number of question types alone.

Frequently asked questions about Google Forms in OSH

Does receiving a response mean a request has been handled?

No. Receipt, review and resolution are different states. The final message should make that clear.

Does a satisfaction survey prove learning?

It describes the participant’s assessment. Appropriate questions or activities are needed to evaluate learning.

What happens to linked-spreadsheet permissions?

Review them independently. Removing form access does not replace checking the spreadsheet and exported copies.

Reference documentation: Google Docs Editors Help — View and manage form responses.