Microsoft Forms document upload for backtest reports

Microsoft Forms can collect files, but it was built for surveys and quizzes inside Microsoft 365, not for tester reports and multi-year trade logs. Before you poiht clients at it, test it with the largest real file you expect to receive. Then decide whether to keep it, ask for zipped exports, or move uploads to a form builder with a higher per-file ceiling.

Where the upload step sits in a validation job

When a trader hands us a strategy, indicator or EA to check, the form is the first step, and everything after it depends on what arrives. Our Strategy Backtest & Validation Report runs out-of-sample and walk-forward checks, re-prices the trades with realistic costs, and runs a Monte Carlo drawdown pass. None of that starts until we have the tester report, the raw trade list and the settings that produced them.

So the intake form has two jobs. It has to accept files that are often larger than people expect, and it has to capture the context a file cannot carry on its own: instrument, timeframe, test window, spread and commission assumptions. A missing field costs a day of email. A rejected upload costs the client's patience.

What you are actually asking people to upload

Trade-related files are rarely small, and they come in more formats than a typical document form expects.

The two that cause trouble are the tester report (a folder pretending to be a file) and the trade list from a long test. Ask clients to zip the report with its imges, and to send CSV rather than a screenshot of a table.

Testing Microsoft Forms before clients touch it

Microsoft publishes the current file size and file count limits for upload questions on its support pages, and I would rather you read the live numbers than trust any blog, including this one. What I can tell you is how to find out whether it works for your files in ten minutes.

1. Create a form and add a file upload question. If you do not see the option, check whether you are signed in with a work or school account and whether your admin has it enabled.
2. Gather your three worst files: the biggest trade CSV you have ever received, a zipped tester report with images, and an unusual extension such as a .set file.
3. Submit each one from a different browser profile, signed out of your own account, the way a client would.
4. Note what happens at the edges: does it reject the file before upload finishes, after, or silently? Is the error message something a non-technical trader could act on?
5. Open the response and check where the file landed and who can reach it. Confirm you can get it into your analysis machine without clicking through five screens.
6. Ask one client to try it, ideally on a phone, since many traders send files from wherever they happen to be.

If all six pass with your real files, Forms is fine. It is free with a Microsoft account, it is part of Microsoft 365, and it works best when your clients and your team already live in Microsoft tools.

Workarounds when Forms refuses a file

If a file fails the test, you have a few optinos before switching tools.

Ask for a trimmed export. For a first-pass check you often do not need every column. Request the closed-trade list with entry and exit time, symbol, direction, volume, prices, commission, swap and profit, and skip the tick data. Say so in the question text, because clients will otherwise send everything.

Zip, and name the zip. A single archive solves the report-plus-images problem and sometimes the size problem. Put a naming convention in the question help text, such as clientref_platform_symbol_tf.zip, so files sort themselves.

Split by purpose. Use one upload question for the tester report and another for the trade list, each with its own instructions. A single "upload your files" box invites a pile of mixed formats.

Move large files out of band. Let the form collect the context and a link to a file the client has placed in their own storage. This works, but you are now trusting a link that can expire or change after submission, which is awkward when you need an audit trail of exactly what was tested.

Switch the upload question to a builder that takes bigger files. That is the case where the form tool itself is the limit.

How the common options compare for file intake

I am using only what the vendors state publicly, so some cells say to check.

Respondent sign-in matters more than it looks. A prospective client who is about to pay for a validation will not enjoy being told to log into a Google account to attach a CSV.

Setting up the intake in Qwenvo

Qwenvo is a form builder our team makes, and it is completely free. For this kind of intake, the free account includes webhooks, the REST API, hidden fields, custom domains, no badge, teammates and custom design, which several otger builders put behind paid plans. The file upload block takes files up to 1 GB each, and our file upload form guide covers block in more detail.

1. Start from the client intake form template, or describe the form to Ask Qwenvo with Ctrl J.
2. Add short answer or dropdown blocks for platform, instrument, timeframe, test start and end dates, and the spread and commission assumptions.
3. Add a file upload block for the tester report and a second one for the trade list. Put the format guidance in each question's text.
4. Add a hidden field for the client reference and pass it in the link, so submissions arrive already matched to a job.
5. In Settings, turn on email notifications to you and confirmation emails to the respondent. If the files are sensitive, set data retention to auto-delete after the number of days that suits your engagement.
6. On the Share tab, put the form on a subdomain such as intake.yourdomain.com by adding the CNAME and the TXT record on the Domains page.
7. Add a webhook to your own endpoint so each submission starts your pipeline.

Qwenvo does not yet offer one-click Google Sheets or Notion connections, so anything that has to reach a spreadsheet goes through the webhook, or through Zapier, Make or n8n using a webhook trigger.

On our side, we keep one record per job next to the files, so a result can be traced back to exactly what was tested:

{
  "client_ref": "C-0142",
  "platform": "MT5",
  "instrument": "EURUSD",
  "timeframe": "M15",
  "test_period": "2019-01-01/2024-12-31",
  "costs": "variable spread, 3.50 USD per lot round turn",
  "files": ["tester_report.zip", "trades.csv", "inputs.set"],
  "received": "2026-11-06"
}

Use the free client intake template

Where Qwenvo is the weaker choice

Qwenvo launched in October 2026, so there are few independent reviews yet. It is hosted in the United States, which matters if a client needs European hosting; Tally is hosted in Europe. There is no HIPAA offering. And if every client and every analyst already works in Microsoft 365 and the files are small CSVs, Microsoft Forms is the simpler path and you should keep it.

Questions teams ask

Can I just ask clients to email the files?

You can, but you lose the structure. Email gives you no required fields, no consistent filenames and no record of which submission belongs to which job. A form that insists on the test window and cost assumptions before the upload saves a round trip on almost every job.

Should I accept compiled EA files?

Only if the check really needs them, and treat them as untrusted. For most validation work the tester report, the trade list and the inputs are enough. Ask for the compiled file only when you have to run the test yourself, and open it in an isolated machine.

How do I get uploads into my analysis pipeline automatically?

Use the webhook. Each submission posts to a URL you control, your script downloads the files and writes the job record, and the REST API is there if you would rather poll. Details are in the webhooks help article.

Do I need to keep Microsoft Forms for anything?

If your team uses it for internal requests or quick quizzes, there is no reason to remove it. The question is only which form should face clients who are sending you large, sensitive files.

Next step

Take the biggest trade list you have ever received and submit it through your current form from a signed-out browser. If it fails or confuses you, rebuild the intake from the client intake template and run the same file through it.

Build your upload form free