Simply Onward / Home

SIMPLY ONWARD · FIELD TEST 001

Your client can fill the form.
Can they upload the brief?

Google Forms vs Tally for a simple consultant intake: what worked, what hit a limit, and what we have not verified yet.

Tested 10 October 2026. Google: published form, attachment and saved response verified. Tally: published submission, stored attachment, required fields and size rejection verified. This is a bounded intake test, not an exhaustive product review.

The useful difference

Google Forms: account required for uploads

We submitted a small dummy brief and found the saved response in the editor. Adding an upload question displayed a Google sign-in requirement. Google confirms the requirement.

Practical choice: if clients already use Google and are comfortable signing in, test the existing tool before switching.

What actually happened

CheckGoogle FormsTally
Small dummy attachmentAttached, submitted; 1 saved response confirmedPublished submission and saved attachment confirmed
11 MiB attachmentRejected at our selected 10 MB settingRejected by published free form at 10 MB
Google login for uploadsRequired: editor warning + official documentationNo respondent account required per docs; independent logged-out test pending
Required answer omittedRequired-question error observedBlank submission blocked; answer and file both required
Export / automationNot testedNot tested

One synthetic scenario, an 83-byte text file and an 11,534,336-byte file. Google’s 10 MB setting is configurable: its editor showed larger options, which were not upload-tested. Both forms blocked a blank required answer; Tally also showed an explicit missing-file error. No timing, conversion or customer-demand claim.

Actual test screens

Google Forms says Your response has been recorded
Google: submitted; editor separately showed 1 stored response and the attached file.
Tally dashboard shows one saved test response and its file
Tally: one completed synthetic response with the attached qa-small.txt file.

Before you send your own form

  1. Decide whether a file is really needed at inquiry stage. A description may be enough to start.
  2. If a file is needed, test with the actual size and type clients send.
  3. Test without your creator session; do not assume a successful owner test proves public access.
  4. Submit once and verify the answer and file arrived in the destination.

See the Instagram summary