File upload in Google Forms: build and test document intake

With file upload in Google Forms, you can collect a document alongside a response and store it in the form owner’s Drive; respondents must sign in to Google. In 15 minutes, you can build a test upload question, send a dummy document, and complete an owner and reviewer access checklist.

Last updated: 2026-10-14

Is file upload in Google Forms right for this intake?

Use file upload in Google Forms when the document belongs with a specific response: a contractor sample, a course assignment, or a proposal for review. For this walkthrough, imagine a small agency requesting one PDF work sample. This is a practice scenario. Decide whether you need the document or just a portfolio link.

Respondents must sign in to a Google Account for a file-upload question. Allowing anyone with the link to respond does not remove that requirement. If your intended audience cannot or will not use a Google Account, explain the barrier before sending the form, or choose a different intake channel. A useful form should not surprise people after they have prepared their application.

The question is unavailable when the form itself is stored in a shared drive, or when an administrator turns on Data Loss Prevention, usually shortened to DLP. DLP means rules intended to prevent information leakage. Do not confuse the location of the form with the location of a respondent's original document. For a text-only discovery questionnaire, the Tally client intake guide is another relevant starting point.

Build a small, testable upload question

Start with a deliberately small task. Prepare a harmless PDF containing dummy information, and call it “test-work-sample.” Do not test with a passport, a customer's contract, or a real applicant's CV. The first success condition is a readable attachment linked to the right response, not a polished form design.

1. Choose the owner. Create a Google Form in the intended owner's account and check that the form is not stored in a shared drive. Name it “Work sample intake: test.” Expected result: there is a clear owner for the form and incoming documents.
2. Add identifying fields. Ask for the applicant's name and a contact address using simple text questions. A typed email address is not independent proof of identity. Expected result: a reviewer can tell which response the file belongs to.
3. Select the file-upload question. Label it “PDF work sample.” Use the settings visible in your account to select suitable file types, file count, and maximum size per file. Expected result: the question settings reflect your intake policy.
4. Explain the request. Paste the template in the next section into the question description and replace its bracketed text. Expected result: the respondent knows what to prepare and who will review it.
5. Decide whether the file is required. Make it compulsory only if an attachment is necessary to assess the response. Expected result: a missing attachment has a deliberate meaning rather than an accidental one.

Do not copy numerical limits from an old screenshot or an unrelated tutorial. The official sources used here confirm that settings exist, but do not establish every current dropdown value. Read the options in your actual account. Requesting one PDF is a business rule for this example, not a promise about the choices every account displays.

Copy this clear upload request

An attachment request should answer the questions people would otherwise send back by email. What should the file contain? What should it be called? Do they need to sign in? What should they do if submission fails? Replace the bracketed phrases below, then compare the wording against the question's actual settings.

Please upload one PDF work sample.
File name: [your-name]-[work-sample].pdf
Include: [the specific work we need to assess].
Follow the file type and size limits displayed in this question.
You must sign in to a Google Account to submit the file.
Do not include passwords, identity documents, or unrelated personal data.
If upload fails, contact: [alternative contact channel].
Your document will be reviewed by: [team or role].

The expected result is a request a respondent can act on without guessing. “Send us your files” is not enough information. If you require a short written explanation as well, ask for it in a separate text field instead of hiding that instruction inside a long attachment paragraph. A reviewer can then read the explanation before opening the document.

Keep different intake purposes separate. Course enrollment and contractor selection need different questions and reviewers. The Microsoft Forms training registration guide covers a registration-oriented flow. For routing service inquiries before asking for a document, see qualifying inquiries with Typeform. Choose the process first; choose the form tool second.

Publish, submit, and open the actual attachment

A question on the editing screen is not proof that people can submit it. Google's sharing documentation says respondents cannot access an unpublished form even if they have its link. Publish the form, set the intended respondent access, and copy the responder link. Do not distribute the editing URL.

1. Open the responder link in another browser profile. Sign in using an account within the intended audience. Expected result: you see the response page, not the editor, and can reach the upload question.
2. Send a dummy response. Enter a made-up name, a test contact address, and the harmless PDF. Expected result: the form accepts the response and displays its confirmation screen.
3. Find it as the owner. Open the form's Responses area and identify your test entry. Expected result: the identifying fields and attachment belong to the same submission.
4. Open the document itself. Google stores uploads in a new Drive folder for the form owner. Locate the test attachment and open it. Expected result: the PDF is readable, not merely listed by name.

You can link the responses to a Google Sheet for a row-based review queue. That is a convenient view of the answers, not proof that every reviewer can open the uploaded documents. If you later want to build a follow-up process, the Google Sheets workflow automation guide is the relevant next step. Finish this manual acceptance test before adding automation.

Complete the owner and reviewer access checklist

Treat the form, its linked response spreadsheet, and the uploaded document as separate things to inspect. Google's documentation says form collaborators receive access when a response spreadsheet is created. Later changes to form permissions do not synchronize automatically. Removing someone's form access is therefore not a substitute for checking the linked spreadsheet separately.

• The form owner and reviewing role are recorded.
• The intended respondent audience can access the published form.
• “View results summary” is off for confidential intake.
• The form's collaborator list has been reviewed.
• The linked spreadsheet's sharing has been checked separately.
• The intended reviewer has opened the actual test attachment.
• The owner's available Drive storage has been checked.
• A fallback contact channel is included in the request.

The response summary setting matters because it can expose full-text answers or charts to anyone allowed to respond. Leaving it off is a practical recommendation for CVs, proposals, and private work samples. This follows the documented visibility rule.

Now switch to the account of the person who will assess submissions. Open the test document through the route that person will actually use. If the spreadsheet opens but the attachment does not, the workflow is not ready. Inspect the file's sharing and grant only the access the intended review requires. Do not assume that spreadsheet access automatically grants access to all attachments.

Keep document review separate from promotional follow-up. An applicant's contact field is not an invitation to put them into a marketing sequence. If you are redesigning that separate communication workflow, the email platform migration guide addresses the transfer process rather than attachment permissions.

What should you check when an upload fails?

Use a fixed troubleshooting order. First confirm publication and the responder link. Next check Google sign-in and the allowed respondent audience. Then compare the document against the selected type and size settings. This separates an access problem from a file mismatch without changing several settings at once.

If the upload question is unavailable, inspect where the form is stored and ask your Workspace administrator about DLP. Do not bypass an organizational rule by moving sensitive files to a personal account. If the approved account cannot support this intake, choose an organization-approved alternative.

Check the owner's Drive capacity as well. For personal accounts, storage is shared across Drive, Gmail, and Photos; reaching the storage limit blocks new Drive uploads. Do not apply a universal personal-account storage allowance to every business account. The useful action is to inspect the actual owner's current storage, not repeat an unrelated quota number.

Anar's public about page describes workshop participants working on practical micro-projects. This tutorial applies that small-output approach: build one test upload and finish one access checklist before scaling intake. It does not claim Anar delivered a particular Google Forms client project. Keep the test note for the next owner.