Editorial disclosure: StackEvidence researches software independently and has an existing affiliate relationship with Fillout. This guide contains no paid product placement or affiliate referral link; links to vendors below point to official documentation. The tests are recommendations, not tests we claim to have completed.
A client fills in your form, attaches a brief and presses Submit. You receive a notification. So far, so good. Then you forward it to the person doing the work, and they cannot open the file.
The missing detail is who can use the record once it arrives. A product may offer file uploads, PDF export and email notifications without giving your colleague the handoff you expected.
Before paying for another form builder, follow one request through the setup you already have. The example specification, requirements sheet and nine tests below will help you see where the work gets stuck—and whether you need a different tool at all.
The examples are hypothetical. The product notes come from official documentation checked on October 20, 2026, rather than hands-on account tests. Links go to ordinary vendor documentation; this edition contains no affiliate tracking links. StackEvidence's existing Fillout relationship, recorded in project records, did not determine the test criteria or a product winner.
Which attachment do you mean?
Start by separating three things that can arrive with a submission:
- The uploaded file: a client's photograph, brief or spreadsheet.
- A submission PDF: a document containing some or all of the answers entered into the form.
- A generated document: a separate template populated with selected answers, such as a project summary.
A PDF that lists kitchen-photo.jpg has recorded the filename. It has not necessarily included
the photograph or given a colleague permission to download it. A notification containing a link is different
again: someone has to open that link, and access may depend on permissions or how the service shares files.
Decide which record each recipient needs. If the office only needs a project reference and a way to open the original submission, an attached PDF may be unnecessary. If the client needs a copy of what they requested, a bare “Thanks” message may be insufficient.
A completed example: a small design studio
Imagine a studio accepting brochure requests. The owner qualifies the work; a designer prepares the estimate. A customer uploads a brief and a reference image. This is the studio's desired workflow, not a reported customer result.
| Requirement | Example decision |
|---|---|
| Information collected | Name, reply email, project type, deadline and a short description |
| Uploads | One PDF brief and one optional image; each must fit the studio's chosen size limit |
| Client confirmation | A receipt identifying the request and explaining the next step; no internal notes |
| Owner notification | A new-request alert with enough detail to qualify the work |
| Designer access | Access to the approved brief and image through an authorized route |
| Working record | One request record with an assigned person and status |
| PDF purpose | A readable summary for the estimate file, if the studio needs one |
| Correction route | Client can contact the studio with the request reference; editable submissions are optional |
| Initial fallback | The owner checks saved submissions while the new process is being evaluated |
The owner should test those roles separately. An administrator opening a file successfully does not prove that the designer can open it. If the designer needs access to one brief, opening every client record to them would not satisfy that requirement.
Your requirements sheet
Copy this table once per workflow. Fill in the business need before looking at a vendor's paid plans. “Unknown” is a useful answer because it tells you what to check.
| Decision | Your answer | Example of a precise answer |
|---|---|---|
| Who submits? | __________ | New clients requesting a brochure estimate |
| Who acts first? | __________ | Owner reviews requests each working morning |
| What files are necessary? | __________ | PDF brief required; image optional |
| Largest expected file? | __________ | A sample file representative of the actual work |
| Does the client need a copy? | __________ | Summary in email; no attachment needed |
| Who needs file access? | __________ | Owner and assigned designer, using separate authorized access |
| Must a PDF follow a template? | __________ | No; a legible answer summary is sufficient |
| Where is the working record? | __________ | A chosen submission table or existing project system |
| What happens after correction? | __________ | Owner updates the working record and notes the change |
| What can remain manual? | __________ | Owner assigns the designer; no automatic routing yet |
| What is the fallback? | __________ | Named person checks saved submissions if alerts fail |
| What spending is justified? | __________ | A limit based on this workflow, including any required add-on |
For the studio, the first decision is whether to discuss the project. A full mailing address probably does not help with that decision. Leave it for later unless the studio can explain why it needs it now.
If you are replacing an existing form, keep the old request records available while you evaluate the new route. Check whether previously collected files remain usable by the people who need them. A new form passing today does not tell you what happens to yesterday’s records.
For an affiliate publisher using a form to screen potential advertisers or partners, apply the same access and receipt tests. Check intended-use policies and permission for any promotional links separately; a working form does not establish approval for a campaign.
Where the product documentation changes the decision
The documentation points to different things to check in each product. These notes do not rank reliability or speed; neither was tested. Check plan inclusion against the workflow you intend to run.
| Buyer requirement | Fillout | Jotform | Tally |
|---|---|---|---|
| Staff notifications | Documents notifications to multiple recipients. New Free organizations have an important account-verification restriction described below. [1] | Documents notification emails for form submissions. [4] | Basic owner notifications are free; customization and PDF attachments are Pro features. [6] |
| A PDF record | Documents mapping answers into an uploaded PDF/document and emailing generated documents. [2] | Documents attaching a submission PDF to a notification. [5] | Manual submission PDF export is free; automatic email PDF attachments are Pro. [7] |
| Original uploaded files | Documents a file-upload field and plan-dependent size limits. Access and delivery still need testing. [3] | Documents a distinct option for sending uploaded files as email attachments. [4] | Notification uploads are links; the submission PDF lists filenames, rather than including the files themselves. [7][8] |
| Client confirmation | Check the intended respondent email and document settings; do not infer them from staff alerts. [2] | Treat client autoresponders and staff notifications as separate messages. [4] | Respondent confirmation emails are Pro. [8] |
Fillout has a timely exception worth checking. Its notification documentation says Free organizations created on or after October 5, 2026 can notify only organization members until the account is verified or upgraded. That can matter if you intend to notify an outside collaborator. Account verification and a paid upgrade are different routes; do not assume payment is the only remedy. No verification was performed for this resource. [1]
File-size limits also need their own check. Fillout currently documents up to 20 MB per file on Free, Starter and Pro, subject to its broader usage rules. Tally documents free uploads up to 10 MB per file. Neither figure tells you how much a recipient's mailbox will accept or whether your intended delivery method passes your access test. [3][9]
Tally also distinguishes access inside the product from links exported through integrations. Its upload guide says exported file links can contain an access token, allowing someone with access to the destination sheet to open the file without a Tally login. Test the intended sharing route, including who can see that sheet. [9]
These details are enough to choose what to test next. They are not enough to declare one product cheapest for every workflow. A free upload field can sit alongside a paid confirmation feature; a template-generated PDF solves a different need from a simple answer export.
Run these nine tests before committing
Use made-up names and harmless sample files in an environment you are authorized to test. Do not put real client records into several products just to compare them. You will need the actual recipient roles represented; one administrator impersonating everyone will conceal permission problems.
Record Pass, Fail, Not tested or Not required. A missing observation is not a pass. These are acceptance tests for your workflow; no vendor has been scored in advance.
| Test | What to do | What counts as a pass |
|---|---|---|
| T01: ordinary request | Submit a complete sample request with a harmless PDF and image. | Required answers and both files appear in the intended saved record. |
| T02: optional file absent | Submit another request without the optional image. | Submission succeeds; staff can distinguish “not supplied” from a missing required item. |
| T03: size/type boundary | Try a representative allowed file and a harmless file outside your configured size or type rule. | The allowed file arrives; the rejected one produces understandable guidance. Record the actual configured rule. |
| T04: staff delivery | Receive the alert in each intended staff role. | Each intended recipient receives the required message and understands what to do next. Note delivery time and any spam-folder placement. |
| T05: colleague access | Use the colleague's authorized access route, independently of the owner's session. | The colleague can open exactly the records and files needed for the job. No broader access is required to make it work. |
| T06: client receipt | Inspect the sample client's confirmation. | It identifies the request and next step, includes the promised copy, and exposes no internal-only material. |
| T07: PDF contents | Open the actual exported or generated PDF. | Required answers are readable; you know whether uploads are embedded, linked, named or omitted. |
| T08: changed information | Correct the sample request using the intended correction process. | Staff know which version is current and can reconcile the working record. No assumption that every email updates automatically. |
| T09: recovery | In a safe test setup, review the fallback without relying on an arriving email. | The responsible person can find the saved submission and identify requests awaiting action. |
For T03, test the boundary your business needs rather than deliberately uploading enormous files. For T05, use a real authorized colleague or an appropriately permitted test role; do not share an administrator's password. For T09, a saved response is the starting point. You still need someone responsible for finding it and taking the next step.
If the form connects to another system, record both sides of the handoff. “Saved in the form tool” and “created in the project system” are separate observations. Do not erase the original record to simulate an outage.
Keep an evidence record you can use later
Duplicate the row below for each test. Write what happened, not just whether you liked the result. “Designer opened sample-image.jpg using their own approved access” is more useful than “uploads work.”
| Product / plan / date | Test ID | Expected behavior | Observed behavior | Result | Evidence reference / next check |
|---|---|---|---|---|---|
| __________ | T__ | __________ | Not observed yet | Not tested | __________ |
Also record the account creation date where a rule depends on it, configured recipients, file restrictions and any connected service. A test from one plan is not evidence for a cheaper plan. Do not store sensitive test credentials or private customer data in this sheet.
Three common outcomes—and the decision each supports
The PDF arrives, but the file does not. Check whether the PDF is merely an answer record. If staff need the original upload, test its separate delivery or access route. Switching PDF templates will not necessarily solve a permission problem.
The owner gets an alert, but the client gets nothing. Inspect the respondent-confirmation requirement separately. If a paid feature is required, decide whether a manual receipt is acceptable at your current workload before upgrading.
Every email arrives, but nobody owns the request. The form may already be adequate. Add a clear assignment and status process in the system you use rather than buying another form builder to fix an unassigned task.
These outcomes are diagnostic examples, not observations from Fillout, Jotform or Tally accounts.
Copyable messages for the studio example
These messages demonstrate the distinction between receipt and acceptance. Adapt the service details and response commitment before using them. Square brackets are fields to configure, not guaranteed vendor merge syntax.
Client receipt
Subject: We received your brochure request — [request reference]
Thanks for sending your brief. We received your request for [project name]. We will review the details and reply about availability and the next step. This confirms receipt; it does not confirm a booking or an agreed deadline. If something needs correcting, reply with the request reference above.
Staff alert
Subject: Brochure request to review — [request reference]
A new request is ready for review. Requested deadline: [date]. Open the request through the approved access route, check the brief and assign the next action. Do not treat the requested deadline as an accepted commitment.
Replace “approved access route” with the method that passed your colleague test. A forwarded email is useful only if its recipient can use what it contains. Include a response timescale in the client receipt only if the business can keep it.
Decide whether to buy, simplify or stay put
Start with the things the job cannot proceed without. If the designer cannot open the brief, nicer styling will not help. If the existing workflow passes, more integrations alone are not a reason to replace it.
| Your result | Sensible next step |
|---|---|
| Every necessary test passes on the existing setup | Keep it. Save the evidence and revisit when the workflow changes. |
| A necessary test fails because of a setting | Correct it in an authorized test environment and rerun that test before comparing subscriptions. |
| A necessary feature needs a paid plan | Compare the total cost of that plan, required seats and connected services against one alternative that meets the same requirements. |
| Only an optional convenience is missing | Keep the manual step unless its recurring effort justifies the expense. |
| File access or sensitive-data handling remains unresolved | Pause the rollout. A successful upload alone does not settle the handling requirement. |
| Email already meets the real need | Keep an email route and a clear response process; a form is optional. |
This pack is for ordinary business enquiries and intake. It is not a compliance assessment for medical, financial or other sensitive records, and it does not establish whether a signature is legally sufficient. Those requirements need their own review before selecting a workflow.
Your decision record
- The workflow we need is: __________
- The product and exact plan tested were: __________
- Necessary tests still failing or untested: __________
- Manual steps we accept: __________
- Total price and billing basis checked on: __________
- Decision: keep / adjust / compare / pause
- Person responsible for the next step and review date: __________
Start with one request. Choose a harmless sample that resembles real work and follow it from submission to the person who must act. If that path succeeds, you have a reason to keep evaluating the product. If it fails, you have a precise question to resolve before spending money.
Documentation used
Checked October 20, 2026. Documentation supports the product notes; the workflow, examples and acceptance criteria are original editorial recommendations.
- Fillout: email notifications
- Fillout: generate PDFs with form responses
- Fillout: file uploads
- Jotform: notification settings
- Jotform: attach submissions as PDFs
- Tally: self email notifications
- Tally: turn submissions into PDFs
- Tally: respondent email notifications
- Tally: file uploads
Research checked October 20, 2026; vendor limits and terms may change. This article provides a buyer-evaluation method, not legal, privacy, or security certification.