Google Forms and Sheets for Low-Budget Research

What are they useful for in research?

Three common uses: satisfaction or context surveys, recruiting forms (the questionnaire that filters who gets invited to a session), and digital diaries in which participants log something over several days. The results land in a sheet that can be sorted, filtered, and analyzed with formulas or pivot tables.

They are especially useful when the budget is limited or when the team already works in Google Workspace. Other wiki articles, such as the one on diary studies or on recruiting participants, mention this kind of use.

How do you link responses to a sheet?

According to Google’s help, you can choose where responses are saved: in the form’s Responses tab, under Summary, then More, with the option “Select destination for responses.” From there you create a new spreadsheet or select an existing one. Each new response arrives in that sheet (Google Docs Editors Help: Choose where to save form responses).

One important detail: the form and the sheet are separate files in Google Drive. Deleting the sheet leaves the form in place, and the reverse is also true. Unlinking (“Unlink form” in the More menu) stops new responses from reaching the sheet, but the data already there remains, and you can reconnect later. Permissions are separate too: a newly created response sheet automatically gives the form’s collaborators access, but later permission changes do not sync, so update each file on its own. Check where each thing lives before you tell the team.

What question types are available?

Google lists these question types (Google Docs Editors Help: Choose a type of question for your form):

• Text: short answer and paragraph. Both can have minimum or maximum character rules.
• Choice: multiple choice, checkboxes (with an “Other” option if you need one), and dropdown.
• Files: file upload, which requires the person to sign in to a Google account. You can limit file types, the maximum number of files, and the maximum file size.
• Scales: linear scale, from 0 or 1 up to a whole number between 2 and 10, and rating (stars, hearts, or thumbs-up), from 3 to 10.
• Grids: multiple choice or checkbox grids by row and column, with rules such as one choice per column.
• Date and time.

A linear scale suits satisfaction surveys, but changing its range changes the average. If you will compare with an earlier study, keep the same scale. To understand which question each metric answers, see NPS, CSAT, and CES.

What should you watch with files and participants?

File uploads require each participant to sign in to a Google account, and they are not available if the form sits in a shared drive or if the administrator has turned on data loss prevention. Files are saved to a new Drive folder owned by the form owner. That means if you ask participants for photos or screenshots, the files land in your account, not in a separate service. Ask only for what you need and say how it will be used.

As with any survey, define which personal data you collect. A recruiting form that asks for age, location, and email should explain why it needs them and who will see them. And before you share the sheet with the team, remove the columns that do not serve the analysis.

When should you NOT use them?

• When you need to record sessions, run usability tests on a prototype, or measure clicks. Google Forms does not record how a person navigates an interface.
• When the form has complex logic, such as long branching or quotas by segment. A more specialized survey tool fits better there.
• When your team must meet strict privacy rules and has no legal review of how data is processed.
• When response volume grows and the sheet becomes slow to work with. Test with your expected volume before the study.

Illustrative example

Illustrative example: a designer wants to recruit twenty people for interviews about online shopping, with no budget. She builds a form with six questions: age range, purchase frequency, main device, availability, an open question about their last purchase, and an optional email field. She links the form to a sheet, filters responses by availability, and picks twelve people who cover different purchase frequencies. Before sending invitations, she tests the form with two colleagues and fixes a question that all of them understood differently. The process needs no software purchase, but it takes the same care as an expensive one.

To plan which questions go in the form, use a research plan. And for the sample size, check how many users you need.

Common mistakes

• Linking the sheet without testing it with a sample response.
• Changing a question’s scale between studies and comparing averages.
• Requesting files or personal data that will not be used.
• Sharing the entire sheet with the whole team, including data nobody needs.
• Deleting the sheet thinking you deleted the form, or the other way around.
• Relying on a survey to measure real behavior inside an interface.

What you can do tomorrow

1. Create a test form with one question of each type and link it to a new sheet.
2. Submit a sample response and check that it appears in the sheet with the right columns.
3. Review which personal data your form asks for and remove any you will not use.

Sources

• Google Docs Editors Help: Choose where to save form responses
• Google Docs Editors Help: Choose a type of question for your form
• Google Docs Editors Help: How to use Google Forms